The problem is that a routing rule in the SAP adapter 4.6 uses the sender address, reciever address and flow to invoke. This changes by environment.
So, the sender address in DEV is different than the sender address in QA. When you generate the service from the admin screen in IS, the folder structure includes the name of the SAP server. We have different names in DEV compared to QA.
The dev sap server is xDN , QA is xQN, Prod is xPN.
What do you think of putting all the routing rules in a seperate package?
That way we could call the same service from 3 different folder structures depending on a parameter value (by environment). What happens in PROD when a fix to this Routing rule package is promoted and the whole package is refreshed. If there are transactions using one of the other rules when the package is refreshed, won’t it lose the rule for a short time while the package is reloaded? Could we lose transactions? There is a queue in the SAP adapter that could queue up the transactions until the routing rule is available, has anybody tested this?