B2B 11g Import Fails If Have A Callout Configured For Transport Server
(Doc ID 1319070.1)
Last updated on MARCH 05, 2019
Applies to:Oracle SOA Suite - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
When using the export/import functionality of B2B 11g, when a transport callout is defined and attached to trading partner's channels.
When export the agreement there are not errors/warnings, but when trying to import the configuration, the following appears.
Import of file MDS_EXPORT_21_10_2010.zip failed. MDS-01611: not saving changes in MDS session because some changes are not valid MDS-02202: Content of the metadata object "/soa/b2b/tp_MyCompany.xml" is not valid. MDS-01609: The document /soa/b2b/tp_MyCompany.xml contains relationships that do not conform to the relationship definition. MDS-01605: The relationship from /soa/b2b/tp_MyCompany.xml#CHANNEL_XiYkKM-8696754469971476743 to /soa/b2b/callout_E1207777721624978402.xml#callout_E1207777721624978402 is invalid because the latter does not exist.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document