Enahancements

[Former Member]

Hi All,

Any one give me the enhancements between XI 3.0, PI 7.0, PI 7.1.

Reagrds,

Hari

[Former Member]

Hi Hari,

Kindly find the below information will provide you all enhancements of XI 3.0, PI 7.0 & PI 7.1.

Features of PI 7.0 over XI 3.0

1. Simple Overview of all messages is introduced in Message Monitoring with the help of Message status overview.

2. Mass restart of messages is possible

3. Critical alerts can be raised for all adapters. (e.g. - if JDBC adapter can't connect to database)

4. Adapter Modules are introduced in channel templates

5. Improved usability of adapters is possible by introduction of tabs (Information is classified and distributed across tabs)

6. Archived messages can be displayed in Message Monitoring

7. Maximum concurrency can be defined in receiver adapters (FILE, JDBC).

8. Optimizing thread usage is possible in JMS adapter by reusing the spare threads from SAP J2EE Engine

9. Extended SOAP adapter usage is possible by AXIS Framework and Encryption methods for SOAP 1.2

10. Maximum File size can be determined in File Adapter to limit the memory usage

Features of PI 7.1 over PI 7.0

a) Repository Objects

1. Integration Repository(IR) is renamed as Enterprise Service Repository (ESR)

2. Message Interface (MI) is renamed as Service Interface (SI).

3. Service Registry (SR) is to support publishing, classifying, discovering services.

4. 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

5. 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)

6. Operation Patterns depends on Interface patterns (Normal / Commit/ Rollback / Confirm/Tentative Update/Compensate)

7. SAP Global Data type (GDT) is introduced to have business semantics in order to replace SAP Core DT

8. Interface Mapping is renamed as Operation Mapping.

9. Folders are introduced to organize projects and interfaces which have access authorizations

10. We can use either XML toolkit / JDK 1.5 toolkit for JAVA and XSLT Mapping.

b) Mapping Enhancements

1. We can set Failure Behavior in FIX values and value mapping (Return initial value/Default/Exception)

2. Output of fields and functions can be used for Multiple target fields for Reusable / Better Runtime Performance

3. Tool support to adjust the mappings after the structure changes to avoid structural inconsistencies.

4. Storing intermediate Results in a variable can be possible and can be reused.

5. Complete copy of XML sub trees is possible

6. Parameterized mapping is useful for Channel Lookup and Reuse of multiple mapping in Interface Determinations and to transfer content of Container in UDF.

7. Function Libraries is useful for Reuse of UDF and enhanced portability of UDF.

8. Graphical Support of RFC Lookup and JDBC Lookup is available.

9. Importing SQL Tables Meta Data is possible

c) CCBPM

1. 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.

2. 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.

3. User Interaction - User Decision Step in IP with an agent configured in ID is used to get the workflow message to make a decision

d) Configuration Objects

1. 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.

2. 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.

3. Advanced Adapter Engine (AAE) is used to increase the performance of message processing by eliminating the need for ABAP stack during the process.

4. Reusable Receiver Rules for logical routing can be used in different Receiver Determination.

5. Cache Notification function is enhanced to analyze the possible error.

6. XML Payload validation is possible in sender and Receiver agreement.

7. Publish the sender agreement in Service Registry (SR) for WS Client and Provider connected to IS.

8. Centralized administration and monitoring is done by SAP NetWeaver Administrator.

9. Message Packing enables processing bulk messages in one service call and reduce context switches.

Regards

Venkata Rao .G

[Former Member]

Dear Gutta,

Kindly read the forum rules before replying

please donot dump ,data

expalin with point r send links

thanks

pratap

[rajasekhar_reddy14]

Hi ,

New Features in PI7.1

u2022 Based on Enterprise Service Oriented Architecture (ESOA).

u2022 Enterprise Services Repository as the central design time repository for service modeling, service metadata, and design time governance.

u2022 UDDI v. 3-based Service Registry for discovery of Services.

u2022 Modeling.

u2022 Global Data Types.

u2022 Message Bundling.

u2022 Enhanced Adapter Engine.

u2022 Direct Adapter-to-Adapter communication for many scenarios

u2022 High Volume Support.

u2022 Reduced Sizing.

u2022 Mapping Improvements.

u2022 Functional Enhancements

u2022 Central Configuration and Monitoring

u2022 Payload Validation.

u2022 BAM Support.

u2022 Unified administration is Net Weaver Administrator

Regards,

raj

[JaganMohan]

Dear Hari,

Please go through the above links. This may answer your question.

Regards,

JP.