Manage Object Request Brokers
An Object Request Broker (ORB) manages the interaction between clients and servers using the Internet InterORB Protocol (IIOP). There are several ways to manage an ORB. For example, we can use ORB custom property settings, or system property settings to configure an ORB, or we can provide objects during ORB initialization.
Default ORB property values are set when the product starts and the ORB service initializes. These properties control the run-time behavior of the ORB and can also affect the behavior of product components that are tightly integrated with the ORB, such as security. We might have to modify some ORB settings to fit the system requirements.
After an ORB instance is established in a process, changes to ORB properties do not affect the behavior of a running ORB instance. We must stop the process and restart it before the modified settings take effect.
A list of possible tasks for managing an ORB follows.
- Adjust timeout settings to improve handling of network failures. Before making these adjustments, review the Object Request Broker tuning guidelines.
- Tune the ORB. For example, if most of the initial method invocations are very small, you might want to set the com.ibm.CORBA.enableLocateRequest custom property to false.
- Adjust the size of General Inter-ORB Protocol (GIOP) fragments that the ORB uses. We might want to make this adjustment if the applications frequently send large requests.
- Change the port that the ORB listens on.
- Specify an alternative to the default RAS manager of the ORB.
- Change the maximum number of connection requests that can remain unhandled by the product ORB before the application server starts to reject new incoming connection requests.
- Adjust thread-pool settings used by the ORB for handling Internet InterORB Protocol (IIOP) connections.
- Troubleshoot an ORB problem.
If we experience problems with the ORB, you should review the Object request broker troubleshooting tips. If necessary, we can then enable ORB tracing, and then review the contents of the ORB communications trace.
- Adjust the logical pool distribution mechanism settings.
Subtopics
- Object Request Brokers
An Object Request Broker (ORB) manages the interaction between clients and servers, using the Internet InterORB Protocol (IIOP). It enables clients to make requests and receive responses from servers in a network-distributed environment.
- Tune Object Request Brokers
- Administer Object Request Brokers
- Develop Object Request Brokers
- Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. Become familiar with the conventions in use for WebSphere Application Server.
- Troubleshooting Object Request Brokers
- Enable HTTP tunneling
HTTP tunneling enables clients, that reside outside of a firewall, to bundle all of the information, that the client-side Object Request Broker (ORB) needs to send to the server-side ORB, into a normal HTTP request. This request can then be sent to the server on port 80, just like any other HTTP request.
Related concepts
Related tasks
Stopping an application server Start an application server
Object Request Broker service settings Object Request Broker custom properties Client-side programming tips for the Object Request Broker service Character code set conversion support for the Java Object Request Broker service Object Request Brokers: Resources for learning (zos) ORB services advanced settings on the z/OS platform
Object request broker troubleshooting tips
(zos) Object request broker component troubleshooting tips