Change Adapter Type Version after Upgrade

[Former Member]

Hello PI-experts,

we make an upgrade from 7.10 to 7.40. How we can change the adapter type version automatically from 7.10 to 7.40? Manual it's possible but we have to much adapters to make the change manually.

Have anyone some experience or information?

Thanks in advance for your answers.

Regards Johann

[vadimklimov · Accepted solution]

Hello Johann,

You can try Integration Directory Migration Tool > Channel Migration. Using this application, you can perform mass change of selected communication channels - in your case, change software component version (adapter metadata version) for them. Please note that the tool should be started on the target system - which means for you, on the PI 7.40 system.

More information on the tool can be found at Migration and Mass Change of Communication Channels - Integration Directory - SAP Library .

Regards,

Vadim

[Former Member · Accepted solution]

Hello Vadim,

thanks a lot for your answer . It worked well. We have only one problem. our pi modules are structured in many folders. After the change the tool moved the changed communication channels from the folders to the general "communication Channel" group. is there any way to avoid that problem? We didn't find any notice about this action in your information.

Regards Johann

[vadimklimov · Accepted solution]

Hello Johann,

You are correct in your observation. Unfortunately, there is no possibility to enter or verify folder for the communication channel in the UI of Integration Directory Migration Tool, meanwhile it initializes the value of the attribute "FolderPathID" of the communication channel (that is, assignment of the channel to the folder) and sets it to "/" (that is the reason why you see all migrated channels in the section "Communication Channel" and not in their original folders in Integration Directory). I would consider this is a bug or current limitation of the tool, and suggest to create a SAP Incident regarding this issue and send it to SAP for further clarification.

Regards,

Vadim

[Former Member · Accepted solution]

Hello Vadim,

Thanks for your answer but we have no time to wait of a bugfix from SAP .

Regards Johann

[vadimklimov · Accepted solution]

Hi Johann,

Then, the alternative option could be usage of Integration Directory API. Here, it will be necessary to invest some efforts into development of client side (web service consumer) since Integration Directory API is exposed as a bundle of web services that can be consumed by client applications, but development of the client application for them is a subject for custom development.

Following this approach, you can find the web service named "CommunicationChannelIn" (namespace http://sap.com/xi/BASIS) that is provided by the PI system and that exposes operations for manipulation with communication channels. Here, you can retrieve communication channels' properties (inlcuding adapter type and GUID that can be further used to identify version of adapter metadata, folder path ID, etc.). The next step would be to change value of the element "SoftwareComponentVersionID" (in "AdministrativeData") to the GUID of the software component version that contains adapter metadata corresponding to the required version. Here, it will be also necessary to employ ESR because via Integration Directory API, you only operate with GUID of adapter metadata, but actual adapter metadata is stored in ESR: there, in software component "SAP BASIS", you can find different software component versions and in them - respective adapter metadata definitions (under namespace http://sap.com/xi/XI/System). GUID of the respective software component version (e.g. software component version "SAP BASIS 7.40" if you would like to use adapter types of version 7.40) is the one that you can correlate with the value of the element "SoftwareComponentVersionID" that is used within operations of the web service "CommunicationChannelIn".

Regards,

Vadim

[Former Member · Accepted solution]

Hi Vadim,

thank you very much.

Regards Johann

[Former Member]

Hi Johann,

We've come across this kind situation, but we couldn't find any automatic option to change the adapter version. We have followed manual update.

Regards,

Krupa