Interface Determination Xpath validation failure during PI migration

[former_member238007]

Hi Experts,

Interface : JMS (Text file) to IDOC

Requirement is to read text file from JMS queue, there is a key field Message Type in the source text field, based on this key field the mapping logic will be varied.

There are 4 different mappings used to populate data to IDOC based on message type.

These condition of executing mappings were defined in Interface determination as "XPATH".

It was working fine in our old PI 7.0, after migration to PI 7.5 AEX, we are facing issues now and in sender JMS adapter its throwing below error

Please advise if there is any note to be applied

Thanks,

--Kishore

[former_member186851]

Hello Kishore,

Can you check if the operation and service interface are name,If not select operation-specific tab in RD.

Also are you selecting the condition from the message structure displayed or copying and pasting the xpath?

Do some dummy changes and re-activate and check.

[former_member238007]

Hi Pavan

Yes there is space associated with message type in payload, for this we use a condition (~), it was working in PI 7.0, but failing in PI 7.5 AEX.

Do we have any notes to fix this issues. Please suggest.

Thanks,

--Kishore

[former_member182412]

Can you post the xpath which you are using

[former_member183908]

Hi,

Can you please check if there was any spaces in the string for the conditions which you set in XPATH.Please check both in payload and in XPATH condition.

Thanks

[former_member238007]

Cache is upto date. No context objects used

Thanks,

--Kishore

[former_member182412]

Hi Kishore,

Are you using context objects in the conditions?? make sure the cache is up to date for the ICO.

Regards,

Praveen.