The key to the problem is:
“Could not process ‘processPO’ (my service name).
com.wm.app.b2b.server.ServiceException: The user that posted this document (Developer) could not be associated with a partner to check their identity”
So the first issue you ran into was that the sender/receiver were not being extracted from the document, so the rule looking for specific sender/receiver wouldn’t match. Since you added the extract queries for sender/receiver, you’re hitting a different issue.
wm.tn:receive validates that the user that is logged into IS is associated with the profile of the sender indicated in the document. If they do not match, TN aborts processing the document. My guess is that setting your rule to Any/Any no longer works–please advise if it does work. Being logged in with username “Developer” doesn’t provide the privileges needed to pass authorization.
When the profile of the sender and receiver were created, TN Console created IS accounts with usernames that matched the external ID of the profile (DUNS by default). Log in with the sender username to submit the document or submit the document when logged in as a user that is in the Administrator group (may TNAdministrator, I’m not sure). That will get you past the authorization check. Or use routeXml instead of receive.
#webMethods#edi#Integration-Server-and-ESB