Skip to end of metadata
Go to start of metadata
 

 Highlight of enhancement in PI7.1 1) Enterprise Service repository (ESR) contains the design Registry2) Includes significant high-volume message processing is supported by message processed in a single     Service call3) Also importantly support for asynchronous messaging based Reliable Messaging (WS-RM) for both      brokered communication between two systems will be supported in this release.4) Provide Service Registry benefits based on UDDI 3.0 Enterprise Service Repository

 In PI7.1 ES Repository is at the heart of Enterprise SOA

ES Repository is really the master data repository of service objects for Enterprise SOA

It contains the definition & process of servicesIn ES Repository has two parts, one is the ES Repository and the other being the Services RegistryES Repository (ESR) is really the master data repository of service objects for Enterprise SOA Besides service definition the ES Repository also provides you with a central point for finding andmanaging service metadata from different sources, including application deployments - this iswhere the Services Registry comes in. The Services Registry is the UDDI part of the ESR whichenables service consumers to find services The SAP XI Integration Repository used by process integration has become the basis of the central Enterprise Service Repository: powering Enterprise SOA and Service Enablement. Objects in the ES Repository include:Global Data Types (CCTS based)Process Component ModelsExecutable Integration Processes (BPEL)Integration ScenariosService Interfaces (Enterprise Services)Interface MappingsEnterprise Services built in the ES RepositoryEnterprise Services includes:Are built using a consistent enterprise model based on: GDTs, Process Components, and Business Objects.Are based on open standards.Are mapped to the Service Interface object in the ES Repository. Global Data Types - Building blocks for Service InterfacesDefined in the ES RepositoryDefined company-wide based on open standards (ISO 15000-5, UN/CEFACT CCTS)Reusable semantic building blocks for service interfaces and message types Process Component ModelsDrill down from high-level models to service interfaces and operationsProcess component architecture models enable SOA governanceProcess components expose on enterprise services, which are based on service operations Web Services Reliable Messaging (WS-RM)Asynchronous messaging (EO, EOIO) based on open WS standard Support Business Activity Monitoring (BAM)Embedded Event Infrastructure: Collecting, pre-filtering and publication of events across SAP and non-SAP systems.Event handling: cast the local event to an event proxy to send out event messages to event Consumers.Transaction SWF_BAM for event filtering via filter rules and event handling.  Enhancement for MappingRe-usable user defined functions.Look-up function reads multiple fields.Synchronous DB RFC lookups: Use graphical function to model look-ups.Specify mapping parameters at configuration time. Principle Propagation based on SAMLThis feature uses the WS-RM protocol.The implementation of this feature is based on the open standard SAML and canbe used with backend systems that support the SAML technology.Forward user context from sender to receiver.Authorization check in receiving system based on original user. Support BAM Milestone Modeling (BPEL)Sub-Process Calls: Integration Process Call, User Interaction: User Decisions (initially not part of this project, but will be covered as well to draw the complete picture),Alert Categories Enhancements for Process AutomationHuman interaction:Integration paradigm (design/ configuration).Generic user decision.Language dependent texts for end-user display, enriched with variables.WS-BPEL 2.0 adoption: Preview and implementation BPEL4People, BPEL-SPE Simple user defined functions can be configured directly in the process.

  • No labels