Oracle Service Bus (OSB) is Oracle's Enterprise Service Bus (ESB) implementation. It is configuration-based and policy-driven and provides reliable service-oriented integration, service management, and traditional message brokering across heterogeneous IT environments. 

This service-infrastructure software adheres to the SOA principles of building coarse-grained, loosely coupled, and standards-based services. Additionally, OSB acts as a message brokering, service monitoring, administration, dynamic routing, and message transformation layer to infrastructure.

OSB relies on Oracle WebLogic Server run-time facilities. OSB supports various service types and transports.

From agent release 4.5.8, AppDynamics supports Business Transaction entries and exits for the HTTP and JMS transports and correlates activity through the broker to give end-to-end transaction visibility. Outbound flows using other transports will be shown as uncorrelated custom backends on the flowmap.

If you want to use custom configuration to influence how the agent instruments non-http and jms outbound transportation, you can use the ignore-exit-types node property to disable the default behavior. 

For Business Transactions originating in OSB itself, the transaction naming scheme that will be used is dependent on the OSB Proxy Service Type.

Service TypeNaming Scheme
REST, WSDL, SOAPWebService Entry
Messaging, XMLServlet Entry

For more details on proxy service types and transports in OSB, see Oracle documentation.