Getting the below error while creating/enabling/disabling processing rules in TN on wM 8.2.2.

Error Details:.

wm.tn.route:update com.wm.app.b2b.server.ServiceException The following sender(s) configured in the processing rule do not exist in the system: "000000000000000000000127" com.wm.app.b2b.server.ServiceException: The following sender(s) configured in the processing rule do not exist in the system: "000000000000000000000127" at wm.tn.route.validateRule(route.java:1669) at wm.tn.route.update(route.java:178) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:443) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:643) ...

Fix Details:
TNS_8.2_SP2_Fix27 8.2.2.0.73 2015-06-09 15:59:36 GMT-05:00 Software AG

This is happening only when i use my sender / receiver is “Enterprise Profile”

#Integration-Server-and-ESB
#webMethods-General
#webMethods

Every thing working fine from MWS. This seems to be problem with TN console deprecation in wM 8.2.2 version.

Any idea on this.

#Integration-Server-and-ESB
#webMethods-General
#webMethods

“000000000000000000000127” doesn’t look like a partner ID.
Can you check what’s the internal ID for your own profile?
Do you see “000000000000000000000127” anywhere?

#webMethods
#Integration-Server-and-ESB
#webMethods-General

Is it DUNS Number?

DUNS = NO986218608

#webMethods
#webMethods-General
#Integration-Server-and-ESB

Krishna – I suggest, for whom ever partner you are getting this error, please take the partner details, delete, create again.

Thanks,

#webMethods-General
#Integration-Server-and-ESB
#webMethods

This issue occurs only when I use the Enterprise Profile as sender/receiver in processing rule, then TN throws this error.

#webMethods
#webMethods-General
#Integration-Server-and-ESB

Hi Krishna,

Have you identified what 000000000000000000000127 really is?

You can use the wm.tn.profile:getInternalId to find the internal id of your profile.

Does the problem happen regardless if the Enterprise partner is the sender or receiver?

Vlad Turian

#Integration-Server-and-ESB
#webMethods
#webMethods-General

Hi Vlad,

This happens only when i used Enterprise Partner profile in processing rule, otherwise it’s working fine.
How to use this service? What are the inputs that i need to give?

#webMethods-General
#Integration-Server-and-ESB
#webMethods

Hi Krishna,

For the wm.tn.profile:getInternalId service use the following inputs:

id: the “nice” id of the partner, aka, the value
idType: the type of the id, ex: DUNS

also see below attachment.

Best regards,
Vlad Turian

#webMethods
#webMethods-General
#Integration-Server-and-ESB