This content has been marked as final. Show 4 replies
Ask your partner to send acknowledgement on one of the below URL's -
host - host name of your SOA managed server
port - SOA managed server listen port
If you have enabled SSL on your SOA server (means using HTTPS) then port will be the SOA server SSL listen port (and obviously http will be replaced by HTTPS in the URL)
If you are using load-balancer then use the host and port of load-balancer in the URL. Rest of the part will remain same.
So if your load balancer URL is https://b2btst.dummy.com then your partner should send the messages to any of the below URL's -
We tested this with our remote trading partner; our TP set the acknowledgement url as
When i try to simply open this url through the browser(outside the company network), it displays the below:
B2B Server is ready to accept HTTP messages from the Trading Partner"
This means the server is reachable correctly.
Now on testing with our TP, they observed the following
– I do see 3 inbound POST’s, and in each case, our B2B server recorded the fact that it delivered the RA’s as expected. Seems like there is a break down somewhere between our delivery of RNIF RA and your B2B software recording the RA?
For this TP, our acknowledgement setups are as below;
Protocol - RosettaNet V02.00
Ack Mode - Async
Under TP>Channel Details>Security
Ack Signed is checked.
Message Signed and Message Encrypted is disabled.
Digital Signature - SMIME 3.0 with MD5 - RSA
Encryption - SMIME 3.0 with DES
Thanks a ton,
between our delivery of RNIF RA and your B2B software recording the RAFirst of all let me make it very clear that I do NOT belong to Oracle B2B product development team.
I do see 3 inbound POST’s, and in each case, our B2B server recorded the fact that it delivered the RA’s as expected.I do not understand what problem are you facing. Can you be more specific and provide exact details of the issue (error message/log etc.)?