about changes in PI 7.1

[Former Member]

Hi experts,

I am not sure why few things keep changing all the time in PI in each version.

Generally we add more options and enhance existing components.

Collaboration profile, collaboration agreements were seen in 7.0, XI has become PI.

service witout party to communication component

Integartion process to process component

define web servies to display WSDL (this option has no new options added)

Interface mappings to Operation mappings

The list goes on if we keep comparing the differences in old versions of XI/PI with PI 7.1.

Integration repository to ES Repository is acceptable.

Even after 7.1 in market, a lay man ( clients or persons at their place) knows XI as SAP's middleware better than PI.

Does SAP document reasons for changing these things any where?

Why does these things have to be renamed when the working nature of many are same even in upper versions?

Help me.

Thanks,

Nikhil.

[prateek · Accepted solution]

Generally we add more options and enhance existing components.

If you talk about PI 7.1, then there is a lot of change as compared to the earlier versions. It is completely brought to behave as a SOA backbone for ESA implementations (which is thought about as an organizational growth path).

Does SAP document reasons for changing these things any where?

The changes are very well docmented. Reasons should be the growing market needs in order to provide a complete middleware solution which could be found as a long term integration solution in organizational perspective.

Why does these things have to be renamed when the working nature of many are same even in upper versions?

This should be considered more of a strategic decision to provide a name in-line with the other components of NetWeaver stack fulfilling the requirement of a Enterprise bus for future SOA vision.

Regards,

Prateek

[Former Member · Accepted solution]

Thanks Prateek,

If you talk about PI 7.1, then there is a lot of change as compared to the earlier versions. It is completely brought to behave as a SOA backbone for ESA implementations (which is thought about as an organizational growth path).

Generally, even in all the modules of SAP, enhancement are added to the existing object, if exists. Very rarely that the name with the same functionality is changed/enhanced.,

can you tell me where is this document available?

Thanks,

Nikhil.

[former_member732072 · Accepted solution]

Hi Nikhil,

Please have a look at the following link and see if it helps you.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40328fc8-4844-2b10-b7a2-8930c16d...

Also please have a look athe following link

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239...

Best Regards.

Edited by: Prakash Bhatia on Apr 22, 2009 8:44 AM

[Former Member · Accepted solution]

Give me ur id..will send u the pdf..

[prateek · Accepted solution]

Very rarely that the name with the same functionality is changed/enhanced.,

First of all its not the same functionality. Functionalities have changed drastically. If you talk about the change of names, then R/3 was changed to ECC and then to current ERP.

Regards,

Prateek

[Former Member · Accepted solution]

There is one feature I know is extra.

For ex if u have FIle to File scnario and u donot want the transformation.

In earlier XI and PI 7.0 U have to make dummy interface and only use ID.

But in this scenario IE will come in picture.

But in PI 7.1 u can do the same scenario without the help of IE means file will come in AE and goes out from AE no IE comes in picture.

[Former Member]

Hi,

PI 7.1 totally SOA based, Modeling, Service Registry etc

PI 7.1 Message Interface called u201CService Interfaceu201D and Interface Mapping called u201COperation Mappingu201D

PI 7.1 includes new features u201Cfolder conceptsu201D Modeling, Parameterize mapping

PI 7.1 came up with Enhancement for mapping concepts Like Lookup JDBC, RFC and SOAP (without creating UDF) Re-usable User Defined Functions Parameterize mapping etc

PI 7.1 includes Advance Adapter Engine (AAE) concepts which by pass Integration engine IE

PI 7.1 provides new concept of XML Validation in IE and AE for incoming and outgoing messages.

These are the new Features that 7.1 has, and the rest are the difference ..

1. Enterprise Services Repository as a central storage location for enterprise service definitions and lifecycle management data for all enterprise services (Concept of Folders,.

2. Universal Description, Discovery, and Integration (UDDI) 3.0u2013compliant services registry for runtime management of enterprise services.

3. Enterprise Service Oriented Architecture (ESOA), Global Data Types, Modeling Tool Concept.

4. Improved support for standards such as Web Service Reliable Messaging (WS-RM), WS Policy, Security Assertion Markup Language (SAML).

5. Support Business Activity Monitoring (BAM).

6. Advanced Adapter Engine Features (Eg. Bypass Integration Engine Process)

7. Enhancement for Mapping (Eg. Re-usable User Defined Functions, Look-up function reads multiple fields, Specify mapping parameters at configuration time, Synchronous DB RFC lookups, Message Packing etc.)

8. Extended support for high volume scenarios

9. Business Activity Monitoring for process definition of milestone monitoring (event correlation).

10. Improved SAP NetWeaver Administrator support for central configuration and administration of both mediated and point-to-point scenarios.

11. XML payload validation and validations using JAVA.

12. Process editor modeling enhancements: step groups, integrated alert management and configurable parameters.

13. Integration of human interaction (generic user decision).

14. Language dependent texts for end-user display.

15. WS-BPEL 2.0 adoption (Preview and implementation BPEL4People, BPLE-SPE Simple User Defined Functions can be configured directly in the process.)

Sameer!

Edited by: sameer Khanna on Apr 22, 2009 9:16 AM

[JoelTrinidade]

hi Nikhil,

I think you are not familiar with the game which can be best described as packaging old wine in a new bottle. this is not a new its a concept used by business organizations worldwide. SAP is no different.

Regards

joel