UDMS PI7.31 Single stack Payload XPATH determination

[aakash_patel]

Hi Experts,

Sorry for the noob question from novice but I am facing issue while configuring UDMS  in PI 7.31 single stack. I know there are lot of support documents for this and i guess i have gone through almost of them. I have successful configured this for integration engine but facing issue in adapter engine.

for adapter engine i am stuck at xpath level. Attached here with screen shot of payload. Can you please help me to determine xpath and prefix for field "TSLShipmentNumber" from that payload ?

I have tried with this xpath " /SiebelMessage/ListOfTslPrmPiTransaction/TslReturnOrderTransactionBc/TSLShipmentNumber" but  Test Search Criteria is not working with this filter having this xpath.

for this interface payload is looking completely different in my integration engine and there i can easily determine xpath and prefix and its working fine there. but here payload in adapter engine is different so..

Appreciate your kind suggestions.

[aakash_patel]

Thanks Praveen and Raghuraman for quick response and suggestions.

I tried all the things from scratch as you guys have suggested but no luck.

I also tried for one inbound interface and that is working perfectly well. Only issue i m facing in outbound interfaces.

[former_member186851]

Himmel,

Are you searching for message before mapping or after mapping?

You need mentioned Service interface details accordingly.

And did you cross check on the Indexing part?

[aakash_patel]

Hi Raghuraman,

I m trying to search msg after mapping and yes indexing was done properly.

please find the msg log.  seems like extractor is not working.

Any further suggestions..

[former_member186851]

Hello Himmel,

After mapping,So you should give ur inbound interface details.

And for XPATH to be correct without any typo you can go to mapping ,right click on the node and copy the XPATH.

Please post all ur UDS configuration.

[former_member182412]

Hi Himmel,

Also you need to enable the logging the mapping step like below.

Regards,

Praveen.

[former_member182412]

Hi Himmel,

• Make sure you give the right values as you have seen in the message monitor.

• XPath expression is right what you are using currently
• No need to specify the namespace prefix because you dont have prefix in the payload.

Try configure as i said and test again and let me know.

Regards,

Praveen.

[former_member186851]

Praveen he has namespace for each fields right?

Is it correct not to give the namespace prefix?

[former_member182412]

Hi Raghu,

Elements does not contain namespace prefixes.

Regards,

Praveen.

[former_member186851]

Hello Praveen,

Ya,Got it..Didnt see the XML properly.

Guess the xpath like below should work then

//SiebelMessage/ListOfTslPrmPiTransaction/TslReturnOrderTransactionBc/TSLShipmentNumber

[former_member182412]

Hi Raghu,

Both will work because element SiebelMessage is root node.

• /SiebelMessage  - means xslt engine will find the element at the root of the XML tree
• //SiebelMessage - means xslt engine will find the element at any depth within XML tree.

Regards,

Praveen.

[former_member186851]

yaya Praveen..

let him try and get back to us.

[former_member186851]

Hello Himmel,

Try this way

Xpath-

//ns0:SiebelMessage/ListOfTslPrmPiTransaction/TslReturnOrderTransactionBc/TSLShipmentNumber

And in namespace definition

ns0 give the namespace of the particular field.

And make sure you indexing as well if your searching for messages already processed.