Hi Puneet,
Highlight of enhancement in PI7.1
1) Enterprise Service repository (ESR) contains the design Registry
2) Includes significant high-volume message processing is supported by message processed in a single
Service call
3) 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 services
In ES Repository has two parts, one is the ES Repository and the other being the Services Registry
ES 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 and
managing service metadata from different sources, including application deployments - this is
where the Services Registry comes in. The Services Registry is the UDDI part of the ESR which
enables 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 Models
Executable Integration Processes (BPEL)
Integration Scenarios
Service Interfaces (Enterprise Services)
Interface Mappings
Enterprise Services built in the ES Repository
Enterprise 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 Interfaces
Defined in the ES Repository
Defined company-wide based on open standards (ISO 15000-5, UN/CEFACT CCTS)
Reusable semantic building blocks for service interfaces and message types
Process Component Models
Drill down from high-level models to service interfaces and operations
Process component architecture models enable SOA governance
Process 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 Mapping
Re-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 SAML
This feature uses the WS-RM protocol.
The implementation of this feature is based on the open standard SAML and can
be 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 Automation
Human 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.
Thanks.
Message was edited by:
rama krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.