on 03-18-2015 9:05 AM
Yes followed the same as mention in above link.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Both Namespaces are same.
also RD is operation specific.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Parin,
When using operation specific RD, your input payload must have the root element that matches exactly the message type used in the outbound service interface.
So you need to have something like that in your payload. Check out what was sent in by the sender.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<ns:MT_UNAME xmlns:ns="namespace">
.... payload content
</ns:MT_UNAME>
Rgds
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does the namespace matches exactly too? You have blanked out both screenshots so can't verify for you.
It looks like you are using Extended Receiver Determination via Operation Mapping. Check also if the source message type of the mapping matches the input payload.
Try running the payload through the Test Configuration tool in Integration Directory to see if it works there or not.
Hi Parin
the problem is in determining the receiver determination
you need to check your RD
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.