Page History

...

1. Standard JBI routing, for example, a binding component specifies a particular service engine to dispatch to, or the bus matches the Normalized Message XML content to a service's WSDL
2. Content-based routing using XPath expressions on the Normalized Message XML content
3. Additional Enterprise Integration Patterns related to routing (also see Camel and the additional patterns supported by Camel)
4. Rules-driven routing using the servicemix-drools service engine
5. Script-driven routing using the servicemix-script service engine
6. Java code can perform routing using the servicemix-bean service engine
7. You can drop in a JBI-compliant BPEL service engine (such as Ode to perform routing (among other things)

...

• JBI routing, when configuration is needed, is configured in an XML file in the Service Unit
• XPath routing uses an entry in the XML file in the Service Unit
• XSLT transformations use an entry in the XML file and a separate XSLT file in the Service Unit
• EIP routing with ServiceMix and/or Camel can be configured with entries in the XML file in the Service Unit
• Drools rules are typically defined in an XML file bundled in the Service Unit
• Script-driven routing and transformation can use scripts in the XML file in the Service Unit
• BPEL process definitions are packaged in the Service Unit

...

You could also write custom Java code to perform orchestration.

Finally, while it's not full-fledged orchestration, Camel is integrated with ServiceMix and supports many Enterprise Integration Patterns that might otherwise require an orchestration engine to implement.

Are transactions supported?

...