Object Request Broker on WebSphere Application Server
The ORB (Object Request Broker) plays an integral part in the application server runtime. The ORB is implemented as part of the Java Virtual Machine (JVM). IBM WebSphere Application Server includes additional code (generally referred to as the extension ORB) that manages the ORB instance, and also provides the plug-in framework for object services (such as security).
WebSphere Application Server uses the ORB to facilitate client/server RMI communication, as well as to communicate between components. The ORB manages inbound and outbound requests for remote Java objects, like EJB components. ORB provides a framework for clients to locate EJBs on the server and invoke operations on those as if they were local. (This concept is referred to as local-remote transparency.)
Communication between ORBs is accomplished via the IIOP, which is a concrete implementation of the General Inter-Orb Protocol (GIOP) abstract reference specification. The Interoperable Object Reference (IOR) is simply a string representation of the CORBA or RMI-IIOP object reference in a format that ORBs can understand.
ORB related problems and(or) errors can be categorized based on different types of connectivity issues that are seen during ORB communications. The technote below should be used as a reference guide to troubleshooting ORB problems and additional diagnostic trace data can be requested or generated for further investigation into the problem:
– TroubleShooting: Object Request Broker (ORB) problems
Considerations for Configuring Static Ports for Object Request Broker (ORB)
Object Request Broker tuning guidelines
Object Request Broker service settings
Enabling HTTP tunneling
MustGather: Object Request Broker (ORB) problems with WebSphere Application Server
“IBM prides itself on delivering world class software support with highly skilled, customer-focused people. ”
Contact Support