SAP PI 7.

1 Architecture and Component Overview

Posted on October 5, 2011

2 Votes

SAP Process Integration (PI) is a powerful middleware by SAP to provide single point of seamless, end to end integration between SAP and Non-SAP applications, 3rd party systems and middle-wares, within and outside the corporate boundary. SAP PI leverages SOA capabilities of service enablement and service & process orchestration for an organization via various soa tools. SAP PI supports B2B (Business to Business) as well as A2A (Application to Application) exchanges, supports Synchronous and Asynchronous message exchange and includes a built in engine for designing and executing Integration Processes. Architecture Overview The PI is not a single component, but rather a collection of components that work together flexibly to implement integration scenarios. The architecture includes components to be used at design time, at configuration time and at run time. Details of SAP PI Components usage and relation with SAP CE based SOA tools (ESR, SR, SOAMANAGER etc).

SAP PI 7.1 and CE 7.1 Architecture Components Overview

PI components includes System Landscape Directory (SLD) is a central repository of information about software and systems in data center and simplifies the administration of your system landscape. The SLD server contains component information, a landscape description and a name reservation which are based on the Common Information Model. The component description provides information about all available SAP software modules. The SLD is a server application that communicates with a client application by using the Hypertext Transfer Protocol (HTTP).

Integration Builder is a client-server framework for accessing and editing integration objects. Integration Builder is a toolset which contains two related tools for accessing and editing integration objects. Integration Repository (IR) provides you an environment to design develop and maintain data types, message structures, interfaces, mappings, integration processes and integration scenarios independently of system landscape. These objects are stored in the Integration Repository and are associated with software component versions that belong to a product that is to be shipped. Integration Directory (ID) is a tool which provides environment for configuring scenarios from Integration Repository. With help of ID we can define and maintain specification of potential senders and receivers of messages, description of their technical options for exchanging messages and specifications of routing rules for exchanging messages. Integration Server is central processing engine of the PI. All messages whether SAP or non-SAP, A2A or B2B, regardless of backend technology or vendor, are processed in a consistent way. Central Monitoring of SAP PI offers you the option of executing various monitoring activities. Runtime Workbench is the central tool for accessing PI monitoring. The Runtime Workbench gives you the option of navigating to the monitoring functions of the Integration Engine, as well as integration with the Computing Center Management System (CCMS), and the Process Monitoring Infrastructure (PMI) of SAP. Adapter Engine is used to connect the Integration Engine to SAP systems and other systems. Various adapters are used in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems. These adapters are part of Adapter Framework which is based on the SAP J2EE Engine and the J2EE Connector Architecture (JCA). The Adapter Framework provides interfaces for configuration, management, and monitoring of adapters.

Introduction to SAP NETWEAVER:

Java tools overview Config tool SDM , JSPM

Enterprise Portal:
NWA 1. 2. 3. a. b. c. 4. 5. 6. 7. EP overview. EP Installation and Post installation EP Administration Content administration User administration System administration. Portal security administration. SSO Configuration. Collaboration. Knowledge management.

SAP Netweaver Training Contents:

1. 2. 3. 4. a. b. c. d. e. 5. SAP NW OVERVIEW SAP NW Installation , Post installation SAP WEBAS JAVA Architecture Java tools overview Config tool Visual admin SDM JSPM NWA Java security administration

SAP Solution ManageR.

Process integration:
1. 2. 3. PI installation and Post installation SLD configuration. PI monitoring Tools.

If after cleanup and you encounter one of these errors: A. SPOOL_INTERNAL_ERROR B. spool overflow (assume you have not adjust max spool number before) C. ...no more free spool request numbers... SAP note 48284 mentioned that change: 1. In Client 000, execute transaction SNRO -Number Range button - Interval. Default numbering range is 100 - 32,000 (which can print up to 31,900 requests) To do this: Transaction SNRO > Table SPO_NUM > Number Ranges (button) > Modify > change the max limit to desired number. What is spool overflow ( SPAD, RZ20 & SNRO ) 2. Define profile parameter rspo/spool_id/max_number up to 2^31 3. Define rspo/spool_id/loopbreak to same value as above. This is optional.

We don't see a need to have more than 31,900. Well if this happens, do the things above. Indirectly, database table size going to grow to few GB, and indirectly slowing down all print request, as well as unnecessary database size