You are on page 1of 4


ESR- Enterprise Service Repository The ESR- Enterprise Service Repository is based on the Integration Repository. The ESR stores objects such as GDTs and message interfaces. ES Repository provides a comprehensive metadata repository. Objects in the ES Repository:     Integration Scenarios Process Component Models Service Interfaces Interface Mappings

The ESR includes: Integration scenarios, process component models, service interfaces and interface mappings. The ESR includes the integration scenario models, process component models, business objects, service interfaces and interface mappings. Functionality of process component exposed through enterprise services. Process components exposed through enterprise services. Enterprise Services built in the ES Repository. Enterprise Services: It is mapped to the service Interface objects in the ES Repository. Global data types defined in the Enterprise Service Repository. Global data types are the building blocks for the service Interfaces. Process Component architecture model enables SOA governance. Drill down from high level models to service interfaces and service operations. Service Registry: The service registry is based on UDDI 3.0. BPM- Business Process Management Enhancements in mappings

homogeneous infrastructure that drives collaborative business.  Enterprise Service Repository(ESR): Contains design objects like interfaces. process definitions. monitoring and error handling SAP NetWeaver Process Integration comprises various components  System Landscape Directory (SLD): It contains information about the landscape (technical systems and business systems) and software catalog (product and software component versions). We can configure any sap system to register itself in the SLD.Synchronous DB/RFC Lookups Uses graphical functions to model look ups Parameterizable Mapping Specify mapping parameters at configuration time XML Payload Validation Validate Incoming/Outgoing xml message against XML Schema Forward and Backward error handling SAP PI is open standard based tool to integrate any system within the enterprise and between enterprise and business partners into one.  Integration Engine: .  Integration Directory: Integration Directory is used to configure scenarios for the message exchange. It is used for:     For integrating both SAP & Non SAP applications For both internal and external process Integrations Graphical design and implementation Central Configuration. mappings.  Runtime Workbench: Runtime Workbench is used for central monitoring of components nad messages.

Login to the PI system: Home screen is called Enterprise Service Builder. Integration engine of the integration server is used to process messages in the integration directory according to the configuration. .  Service Registry: Service Registry is a UDDI complaint registry. T-code.  Advanced Adapter Engine: The advanced adapter engine provides multiple adapter to the systems to connect to the integration server.sxmb_ifr is used to launch Integration Builder. listing available web service definitions based on WSDL extended with a classification system. SLD: System Landscape Directory Technical System and Business System Business systems are logical systems that function as sender and receiver within PI. SLD maps business system names to the Technical Names so that PI can determine the receiver of the message. Business Process Engine: Business Process Engine controls the message correlations and how messages are processed as part of the cross component business process management (ccBPM).