I would check out the Application Basics section of the User Guide to get a feel for the structure of an application:
Here are the pieces you'll need for your scenario:
1) A composite service with a JMS binding.
2) A composite reference with a SOAP or HTTP binding.
3) A service component which has routing logic that takes messages from (1) and routes them to (2).
The routing logic can be implemented using any of the service implementations available in SwitchYard. Here's one example:
There are many quickstarts available which demonstrate different implementations, bindings, transformations, policies, etc.
A great way to get started is to following our training lab here: