on 05-06-2010 11:34 AM
Hello All
I've created simple async Integration Scenario.
Sender is SOAP, then message is being processed by BPM Integration Process (some simple mapping inside - for now it is just proof of concept - later on it will split messages etc.) . Receiver is JDBC adapter.
Now, when I test Sender-> BPM (using Test Configuration tool ) - works fine, no errors.
BPM -> Receiver - as well.
But when I'm trying to test Sender -> Receiver it fails (so it does when I call Sender webservice from external tool).
Error is:
Receiver Agreement
<Trace level="1" type="B">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>
<Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
<Trace level="2" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for: </Trace>
<Trace level="2" type="T">-SENDER </Trace>
<Trace level="2" type="T">-RECEIVER </Trace>
<Trace level="2" type="T"><a href="http://company.com/xi/sn.DataOut" TARGET="test_blank">http://company.com/xi/sn.DataOut</a> </Trace>
<Trace level="1" type="T">error with outbound binding. </Trace> <Trace level="1" type="T">
No standard agreement found for , SENDER, RECEIVER, <a href="http://company.com/xi/sn" TARGET="test_blank">http://company.com/xi/sn</a>, DataOutt </Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>
In fact there is no Receiver Agreement for this pair of sender-receiver, but in scenario those are connected via BPM.
What am I missing in configuration to force PI to send messages correctly?
TIA
Regards
Maciej
Hi Maciej,
If you are trying to test it from the RWB -> Component Monitring-> Integration Engine-> Test Message option, then you should not be giving the receiver system and interface details.
Just specify the details of the sender system, interface name and namespace.
Give the user id and pwd details.
Give the Quality of service as "Exactly Once".
Paste the payload and click on SEND button. (DO NOT GIVE THE RECEIVER SYSTEM details).
It will work.
Thanks and Regards,
ravi Kanth Talagana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've solved it.
It came out that my process was missing the sender agreement.
WSDL taken from this one also solved problem with sync/async communication.
Thanks for your assistance.
MG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.