PI AEX Migration Tool does not convert Adapter Type

[Former Member]

Hello guys.

I am importing some interface from dual-stack PI 7.0 to java only stack.

The documentation says:

"Choose Channel Properties. In the popup, select the target Adapter Engine for the channels and the target namespace.

If the scenario that is migrated refers to ABAP-based adapter channels, the channels are transformed into the corresponding Java adapter channels, and the properties are preserved, where applicable.

ABAP IDOC adapter is transformed to Java IDoc adapter

ABAP XI adapter is transformed to Java SOAP adapter with XI 3.0 message protocol

ABAP HTTP adapter is transformed to Java HTTP adapter"

But it is not happening for me. The Migration Tool keeps the adapter type in version SAP BASIS 7.0 and does not convert XI into SOAP with XI protocol.

The Channel Properties button only shows me one option and it is SAP BASIS 7.4.

I have no idea what is happening.

I hope someone can help me.

Thank you.

[Former Member]

Digging into the log viewer I found the following error when importing from 7.0 to AEX 7.4.

It does not appear in the Migration Tool only in the log viewer.

com.sap.pi.tools.dirmig.channel.MissingMetadataException: No metadata found for name=XI namespace=http://sap.com/xi/XI/System SoftwareComponentVersionID=b38bcd00-e471-11d7-afac-de420a1145a5

Error migrating sender agreement: java.lang.NullPointerException: while trying to invoke the method com.sap.pi.tools.dirmig.channel.metadata.AdapterTypeMetaData.getAttributes() of an object loaded from local variable 'metaData'

Error migrating receiver agreement: com.sap.pi.tools.dirmig.channel.MissingMetadataException: No metadata found for name=XI namespace=http://sap.com/xi/XI/System SoftwareComponentVersionID=b38bcd00-e471-11d7-afac-de420a1145a5

Regards

[Dimitri]

Make sure your adapter metadata (BASIS 7.4, I guess) is loaded within the ESR.

[Dimitri]

Hi Giovani,

Please have a look at http://scn.sap.com/community/process-orchestration/blog/2012/11/19/moving-integration-directory-arti...

Check the availablility and make sure your system meets the requirements.

Kind regards,

Dimitri

[Former Member]

Thanks Dimitri but I have read this article already.

I am afraid there is some configuration missing but I don't which one.

Regards

[Dimitri]

Hi Giovani,

What you should do is escalate to SAP via an OSS message.

In that case you're sure and know what to do to solve the problem.

Kind regards,

Dimitri

[Former Member]

Hi Dimitri,

what exactly you mean with "escalate to SAP via an OSS message"?

Regards.

[Dimitri]

You open a message on the SAP Service Marketplace to escalate your problem.