PI 7.1与PI7.0的比较

Name changes PI 7.0 -> PI 7.1

Integration Repository (IR) -> Enterprise Service Repository (ESR)
message interface -> service interface
interface mapping -> operation mapping
business service -> business component

Features of PI 7.1 over PI 7.0

a) Repository Objects

• Service Registry (SR) is to support publishing, classifying, discovering services.
• Service Interfaces (SI) may contain several operations where each operation describes one communications (Synchronous / Asynchronous). The various attributes are Category (I/O/A), Mode(S/A), Interface Pattern & Operation Pattern
• Interface patterns is a new attribute of a service interface that describes the type of communication that is to be executed on the message (Stateless/ Stateless Xi 3.0 Compatible / TU&C/C and Stateful)
• Operation Patterns depends on Interface patterns (Normal / Commit/ Rollback / Confirm/Tentative Update/Compensate)
• SAP Global Data type (GDT) is introduced to have business semantics in order to replace SAP Core DT
• Folders are introduced to organize projects and interfaces which have access authorizations
• We can use either XML toolkit / JDK 1.5 toolkit for JAVA and XSLT Mapping.

b) Mapping Enhancements

• We can set Failure Behavior in fix values and value mapping (Return initial value/Default/Exception)
• Output of fields and functions can be used for multiple target fields for Reusable / Better Runtime Performance
• Tool support to adjust the mappings after the structure changes to avoid structural inconsistencies.
• Storing intermediate Results in a variable can be possible and can be reused.
• Complete copy of XML sub trees is possible
• Parameterized mapping is useful for Channel Lookup and Reuse of multiple mapping in Interface Determinations and to transfer content of Container in UDF.
• Function Libraries is useful for reuse of UDF and enhanced portability of UDF.
• Graphical Support of RFC Lookup and JDBC Lookup is available.
• Importing SQL Tables Meta Data is possible

c) ccBPM

• Step Groups - Set of steps that can be reused by embedded in Integration Process across SWCV. Step Parameters can also be used in step groups.
• Configurable Parameters - Defined in Integration process and the values can be used assigned in ID. Here Agents, Communication channel and simple data type can be used as parameters.
• User Interaction - User Decision Step in Integration Process with an agent configured in ID is used to get the workflow message to make a decision

d) Configuration Objects

• Web Service Reliable Messaging WS-RM for Asynchronous messaging is configured in Sender Agreement and Communication Channel for a considerable level of reliability and security.
• Principal Propagation based on Security Assertion Markup Language (SAML 1.1) can be configured in WS adapter. It means user is securely propagated from a sender system to receiver systems. An authorization check in receiving system based on original user.
• Advanced Adapter Engine (AAE) is used to increase the performance of message processing by eliminating the need for ABAP stack during the process.
• Reusable Receiver Rules for logical routing can be used in different Receiver Determination.
• Cache Notification function is enhanced to analyze the possible error.
• XML Payload validation is possible in sender and Receiver agreement.
• Publish the sender agreement in Service Registry for web service Client and provider connected to IS.
• Centralized administration and monitoring is done by SAP NetWeaver Administrator.
• Message Packing enables processing bulk messages in one service call and reduce context switches