My Oracle Support Banner

Overriding AS2 Identifier Not Used in Functional or MDN Acknowledgement (Doc ID 1969768.1)

Last updated on SEPTEMBER 05, 2018

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.0 version, B2B Engine

ACTUAL BEHAVIOR
---------------
B2B is not using the overriding AS2 identifier when acknowledging receipt of a document.

EXPECTED BEHAVIOR
-----------------------
It is expected that the overriding AS2 identifier is used when sending a functional (and MDN) acknowledgement.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Create an Acme B2B 850 agreement configuration in one B2B instance:

host: Acme (AS2 identifier Acme_AS2)
partner: GlobalChips with AS2 channel (AS2 identfiers GlobalChips_AS2, GlobalChips2_AS2)
support doc def: send/receive 850
agreement: send 850 to GlobalChips
agreement: receive 997 from GlobalChips

2) Create a GlobalChips B2B 850 agreement in another B2B instance:

host: GlobalChips (AS2 identfiers GlobalChips_AS2, GlobalChips2_AS2)
partner: Acme with AS2 channel (AS2 identifier Acme_AS2)
support doc def: send/receive 850
agreement: receive 850 from Acme
agreement: send 997 to Acme

3) Deploy agreements.
4) Using the B2B utility, enqueue 850 XML document to be sent to GlobalChips (with AS2 identifier GlobalChips2_AS2):

user=dev_soainfra
password=welcome1
url=jdbc:oracle:thin:@localhost:1521:orcl01
replyToMsgID =
from =AS2 Identifier:Acme_AS2
to =AS2 Identifier:GlobalChips2_AS2
doctypeName =850
doctypeRevision =4010
payload = Acme_850_11g.xml

5) On the GlobalChips side, check the 850 inbound wire message and it shows the correct AS2 identifier (GlobalChips2_AS2).
6) Now check the 997 outbound wire message and it shows an incorrect AS2 identifier (GlobalChips_AS2) is being used for the functional acknowledgement.

Cause

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
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.