We are upgrading webMethods 6.1 to 7.1 and hence WmSAP 4.6 to 6.5.
In earlier implementation we had 4 integrations connecting to same SAP system.Only difference was User ID for the connections.
Now we have
3 SAP Connections in wM7.1
2)All are connecting to same SAP System ID(XYZ) and Client ID(111)
Result
All SAP adapter services work as expected.
2)RFC Notifications work fine
Routing notification fails.
When we delete all connections apart from the one mentioned in Listener and restart server it worked.
As per an article in Advantage(SR Closure Summary) its a design change for WmSAP6.5 which does not support the implementation of having more than 1 SAP connection connecting to same SAP system(with different User ID) and one listener being associated with one of those connections.
Has anybody been through the same issue…or got any alternative to work on…?
If we have 3 RFC’s we need to run, and we need to keep them separate by user ID, can we configure 3 SAP listeners with each having it’s own list of RFC’s it listens for?
Well, yes and no… First of all, configuring 3 listeners doesn’t achieve anything: the R/3 system does not care what you define on wM side. It makes loadbalancing and then it is complete coincidence, which listener will receive which RFC… So you can as well have only one listener. (In fact, starting with wM 6.5 = SAP JCo 3.0, JCo does no longer allow to have multiple listeners with the same “Program ID”.)
The option of tying certain function modules to a listener is a bit misleading, because in fact all function modules are kind of “global”. I think the only reason why this has been done that way is in order to specify, which “Repository” should be used for the function module metadata.
But what you are trying to achieve, can be achieve easily in the following way: basically you want to setup a user authorization check for your 3 function modules. But this is independent of things like “listener”, “RFC connection”, “RFC destination”, etc.
All you need to do is, define the 3 SAP users in the wM user management as well. Then, when an RFC call arrives from R/3 (no matter via which listener), wM will execute this call in a wM user session corresponding to the SAP user ID. (Only if the SAP user ID does not exist in wM user management, it uses a default user named “SAPUser”.) So by having 3 wM user IDs spelled exactly like the corresponding SAP user IDs, you can protect your 3 RFCs with a corresponding ACL in the wM authorization management and enforce that only the correct SAP user can execute these RFCs.
Well, it’s a bit confusing at first, but I hope you understand what I’m trying to say…
If we have 3 RFC’s we need to run, and we need to keep them separate by user ID, can we configure 3 SAP listeners with each having it’s own list of RFC’s it listens for?
–>For this,you can configure SAPAdapter connections (with 3 diff program id’s/rfc destination) and of-course it causes maintenance overhead.