WAS v8.5 > End-to-end paths > Object Request BrokerManage 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. You might have to modify some ORB settings to fit your 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. 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 your 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 the ORB uses. You might want to make this adjustment if the applications frequently send large requests.
- Change the port the ORB listens on.
- Specify analternative 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 you 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.- Logical pool distribution
The Logical pool distribution (LPD) thread pool mechanism implements a strategy for improving the performance of requests that have shorter run times. Do not configure LPD unless we have already configured it in a previous release of the product.- Object Request Broker tuning guidelines
Use the guidelines in this document any time the Object Request Broker (ORB) is used in a workload.- Object Request Broker service settings
Use this page to configure the Java Object Request Broker (ORB) service.- Object Request Broker custom properties
There are several ways to configure an Object Request Broker (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. If we use the following ORB custom properties to configure an ORB, remember that two types of default values exist for some of these properties: the Java SE Development Kit (JDK) default values and the WebSphere Application Server default values.- Object Request Broker communications trace
The Object Request Broker (ORB) communications trace, typically referred to as CommTrace, contains the sequence of General InterORB Protocol (GIOP) messages sent and received by the ORB when the application is running.- Client-side programming tips for the Object Request Broker service
Every Internet InterORB Protocol (IIOP) request and response exchange consists of a client-side ORB and a server-side ORB. It is important that any application that uses IIOP is properly programmed to communicate with the client-side Object Request Broker (ORB).- Character code set conversion support for the Java Object Request Broker service
The CORBA/IIOP specification defines a framework for negotiation and conversion of character code sets used by the Java Object Request Broker (ORB) service.- Object Request Brokers: Resources for learning
Use the following links to find relevant supplemental information about Object Request Brokers (ORBs). The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.- Object request broker troubleshooting tips
Use these tips to diagnose problems related to the WAS Object Request Broker (ORB).- Enable HTTP tunneling
HTTP tunneling enables clients, that reside outside of a firewall, to bundle all of the information, 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.- 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. This article describes the conventions in use for WAS.- Troubleshooting Object Request Brokers
- Enable HTTP tunneling
HTTP tunneling enables clients, that reside outside of a firewall, to bundle all of the information, 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
Stop an application server
Start an application server