Dynamic routing in OSB

Question

Environment: OSB 10.3.1
To avoid manual configuring all published services one-by-one (eg. alter logging), I'd like to implement a generic proxy pattern in OSB. Assume that I have business services at /bs1, /bs2, etc, proxy services at /ps1, /ps2, etc.
What I'd like to achieve is to publish proxy services which routes to the generic proxy first and then reroute to the original proxy service. For this I published eg. /pps1, /pps2, etc all with an Insert action which saves $inbound/ctx:transport/ctx:uri to . in $header and then route to the genericproxy proxy service.
Generic proxy starts by executing common logic in the pipeline (log, etc), then should fetch the original routing information from the header and use dynamic routing to direct the message to the right proxy service (/ps1, /ps2, etc).
Now the questions:
1. is this the right approach to solve the problem of generic configuration of multiple published services in OSB?
2. appearently the uri itself is not enough for dynamic routing - what else do I need to save from the original message?
3. can I construct a <ctx:route><ctx:service..><ctx:operation..> construct with only Insert actions? I'd need a concrete example here accomplishing this.
Thanks.

Answer 1

Well you have to add Route Node to your proxy pipeline and inside it add a Dynamic Routing action.
If you select the Dynamic Routing action you'll see in the Properties view something like:
Service: <Expression>
Here is where you have to define the <ctx:route> element. You can basically paste the text here.
You could also create an XQuery transformation (so you can reuse it later) and invoke it here (with the XQuery Resources tab). But if you're not very familiar with XQuery I'd advise to start with the first option just to see it working.
At first you could also omit the {$proxy} variable and statically specify the service you want to route to. Or you could use an Assign action to define the $proxy (or any name you want to give it) variable. And then once that's working see if you can get the service path from the headers.
Hope that helps