Skip to Content
0

Issue with multiple root nodes in the input payload

Sep 05, 2017 at 09:57 AM

97

avatar image
Former Member

Actual flow 3rd Party ->PI ->Proxy Proposed flow 3rd Party -> PI -> File (NFS) Al11 ( append mode , collect all proxy XML within a second /min based on dynamic configuration that we can set) Al11 -> PI ( XSLT mapping to remove XML version tags)and No Mapping conversion -> Proxy (No Structure changes) Just need to make sure proxy structures should be table type. We have two interfaces in this approach 1. 3rd party--------->PI--------->SAP system(Here we are using Dynamic configuration with time limit) JMS File(Append) 2. SAp------->PI-------SAP File Proxy The issue is in the AL11 path we have single file with appended messages when we try to runn the second interface(output payload of first interface is input payload of second interface) but the appened messages have multiple root nodes due to this second interface was failing Could you please suggest ho we can achieve this.

Thanks & Regards,

Vijaya

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

8 Answers

Evgeniy Kolmakov Sep 05, 2017 at 12:20 PM
0

Hi Vijaya!

1. Use FCC to convert XML to flat csv structure before appending contents to result file and use FCC to convert flat contents back to XML in second interface.

2. Use java mapping before your main mapping in second interface to manually add the common root tag to your source message.

Regards, Evgeniy.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 05, 2017 at 04:39 PM
0

Hi Evgeniy,

Thank you so much for your inputs.

Actually I am using the java mapping to remove extra root nodes but I have configured java mapping after main mapping(message mapping).

I will try as per suggestion and let you the result.

Regards,

Vijaya

Share
10 |10000 characters needed characters left characters exceeded
Evgeniy Kolmakov Sep 07, 2017 at 08:28 PM
0

Hi Vijaya!

I guess you should check your interface determination to ensure if any operation mapping exists for source interface/message type.

Regards, Evgeniy.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 08, 2017 at 06:23 AM
0

Hi Evgeniy,

The source interface was existed for the configured OM.Attached the screen shotcapture.jpg

Regards,

Vijaya


capture.jpg (83.5 kB)
Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 08, 2017 at 01:31 PM
0

Hi All,

I did all the changes in my scenario i changed the pattern of sender service interface to xi 3.0 and deleted the ICO (PI 7.1 dual) created again,removed the SWCV but still getting the below error.

Transmitting the message to endpoint using connection JMS_http:// sap.com/xi/XI/System failed, due to: com.sap.aii.af.service.mapping.MappingException: Unexpected exception caught while executing mapping: com.sap.aii.adapter.xi.routing.RoutingException: Configuration for AllInOne object {0} seems to be broken. No InterfaceDetermination at all is available in CPA Cache.

I asked my basis people they told the CPA cache is updated.

Please suggest me the solution.And one more point here i trying to reprocess failed messages would this cause the issue?

waiting for your valuable suggestions.

Regards,

Vijaya

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 07, 2017 at 04:33 PM
0

Hi Evgeniy ,

We are facing the new error in sender JMS channel, which is in green in PI but it is not picking the message from queue(MQ).Previously we have tested same interface but it was failed. Now we are trying to reprocess them but those are failing with below error.

Execution of mapping "<unknown>/<unknown>" failed. Reason: RoutingException: InterfaceDetermination cannot be found anymore. Manual action is required.

Could you please suggest me the solution.

Regards,

Vijaya

Show 2 Share
10 |10000 characters needed characters left characters exceeded

check the parameters in FCC, namespace or structure could be wrong.

0
Former Member

Hi Raghuraman,

Thank you for your inputs, we are not using any FCC parameters.namespace or structure could be wrong....I am not getting this point-Namespace and structure is sender interface or receiver.

Regards,

Vijaya

0
avatar image
Former Member Oct 18, 2017 at 06:47 AM
0

error.png

Hi Experts,

from the AL11 path(appended messages with multiple root node) the sender file channel picking the file and try to process in PO(single stack) but it is failing with "The xml is not well formed" due to multiple root node.

Could you please provide valuable suggestions.

Thanks in advance

Regards,

Vijaya


error.png (15.0 kB)
Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Oct 18, 2017 at 06:48 AM
0

For removing the multiple root nodes we are using JAVA mapping ..i have configured JAVA mapping before the MM but still it is failing the xml parser exception

Regards,

Vijaya

Share
10 |10000 characters needed characters left characters exceeded