This content has been marked as final. Show 4 replies
Only below custom JMS headers are required -
ACTION_NAME=ACTION:<businessAction>;SERVICE:<service>;SERVICETYPE:<serviceType>;FROMROLE:<From role>;TOROLE:<To role>;
For example -
Just pass the message with above headers and if a corresponding ebMS agreement is deployed then it will get identified correctly.
Remember that only ACTION, SERVICE and SERVICETYPE are used while finding an agreement. FROMROLE and TOROLE are not required so you may remove them from ACTION_NAME header, if you want.
Thanks Anuj. I made it work by passing document version and id as JMS headers.
Earlier I was setting action header as "ACTION=action1", I will try by modifying it as "ACTION_NAME=ACTION:action1".
*<UPDATE>: I tried it, still not working.*
Error: Machine Info: (apl08316uaapp01) Description: Agreement not found for trading partners: FromTP HostParty, ToTP RemoteParty with document type ACTION:rsProcessLineAvailabilityRequest Service:bcRequestLineAvailabilityv14 ServiceTypestring-OUTBOUND.
JMSXDeliveryCount=1, MSG_ID=ID:<457648.1369731952449.0>, FROM_PARTY_ID_TYPE=urn:oasis:names:tc:ebXML-cppa:partyid-type:duns, Sequencing=false, ACTION_NAME=ACTION:rsProcessLineAvailabilityRequest;SERVICE:bcRequestLineAvailabilityv14;SERVICETYPE:string, FROM_PARTY=DUNS_ID_OF_HP, TO_PARTY_ID_TYPE=urn:oasis:names:tc:ebXML-cppa:partyid-type:duns, TO_PARTY=DUNS_ID_OF_TP
Edited to Remove Organization Specific Info