XI 3.0 to PI 7.3 Post upgrade PI objects changes required?

[Former Member]

Hi All,

We are about to start XI 3.0 to PI 7.3 dual stack in-place upgrade and I am trying to list out the post upgrade scenario based changes required.

Definitely we will do regression testing and identify the issues and fixes, however I would like to estimate the changes required beforehand.

As a starting point, I am considering the below changes,

1. Java mapping, adapter module API changes?

2. Redeploying JDBC, JMS external drivers?

3. Regenerating Public/privates keys, encryption algorithm after upgrade (we have PGP encryption for banking scenarios)? Encryption accomplished in XI 3.0 using File adapter + UNIX scripts.

What are the other cases I need to consider apart from above?

Please note that, as of now we are not planning to reengineer production scenarios with new PI 7.3 features, idea is to upgrade with minimal development effort.

Cheers,

Rakesh

[baskar_gopalakrishnan2 · Accepted solution]

In addition to above, few more things ...

1) Java Version in  xi 3.0 is jdk 1.4. Whereas Pi 7.3 uses  1.5 + . So you will have to take care compiling java mappings with the latest jvm and deploy in 7.3. Higher version java already has preloaded XML parsers . So you dont need to use other XML parsers in your java mapping. Rather use just java for mapping and create /parse xml documents. This would be better for going forward. SAP also recommend this.

2) You can do graphical jdbc and rfc lookup instead of traditional UDF codings, if any.

3) You might set XML schemal validation here during pipeline steps. (Though that is not mandatory)

4) PI 7.3 supports processing huge files processing . So if you have logic in x.3 to split files, you dont need any more.

5) Proxy adapters use SOAP Adapter (XI) also in the higher versions. You can use this if you want to implement the scenario entirely in Advanced Adapter Engine.

6) Service Interface  supports more than one method within the same interface in 7.1 and above.

Hope that helps.

[Former Member · Accepted solution]

In additions to what wrote above:

- Additionals Adapter Modules (installation/configuration)

- XSLT Mapping

- About PGP Enc/Dec: PGP software reinstallation on new OS

[Former Member]

Dear Rakesh

You can also consider the new PGP module by SAP and SFTP Adapter.

Also BPM scenarios will have to be re engineered using BPM.

External drivers will have to redeployed on new server.

ESR content can be transported as it is.

ID objects like Receiver Agreement, Receiver determination etc needs to be recreated.

Regards

Monika

[Former Member]

Thanks Raja, Praveen!

[MichalKrawczyk]

Hi,

other things:

http://scn.sap.com/people/michal.krawczyk2/blog/2009/03/04/pixi-pi-71-upgrademigration--message-mapp...

http://scn.sap.com/people/michal.krawczyk2/blog/2010/03/09/pixi-pi-71-upgrademigration--message-mapp...

http://scn.sap.com/people/michal.krawczyk2/blog/2010/03/11/pixi-upgrade-to-pi-71-checks--db-entries

Regards,

Michal Krawczyk

[Former Member]

Hi Michal,

the links don't work anymore, could you provide new ones please?

Thanks

[rajasekhar_reddy14]

Some link broken it seems, refer below link and search in SCN

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2047cd8f-fa94-2e10-1f90-8f11dcf0e...

[former_member181985]

due to SCN migration content certain links doesnt work. In this case you have to point browser to Author main page, like this

http://scn.sap.com/people/michal.krawczyk2   and then to Content Tab, then navigate to each page

You will find links given my Michal here

http://scn.sap.com/people/michal.krawczyk2/content?start=20