InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.30: Administering Object Request Brokers (overview)
6.6.30: Administering Object Request Brokers (overview)
The WebSphere Application Server uses the ORB to manage communication
between client applications and server applications, as well as, communication
between WebSphere components, such as the application server
. During WebSphere Application Server installation, default values are established, called
ORB properties, which are used when WebSphere is started and the ORB is
initialized. These properties control the run-time behavior of the ORB and can also
affect the behavior of WebSphere components which are tightly integrated with the
ORB, such as security.
It might be necessary to modify some of the ORB properties under certain
circumstances. For example, it may be necessary to modify the default timeout
delay the ORB uses when waiting for a response to a request, or to modify the
maximum number of active connections the ORB caches for better performance,
and so on.
In every request/response exchange, there is a client-side ORB and a server-side
ORB, depending on which side initiated the exchange. It is important that the ORB
properties be set for either the client-side or server-side as necessary because
each ORB is, in general, independent of the other.
IBM WebSphere Application Server security does not support the
programming model of using multiple ORB instances.
To obtain its ORB instance, every application should always make calls to:
com.ibm.ejs.oa.EJSORB.getORBinstance()
After the ORB instance has been established with a process, the process should
not change ORB-related properties because property changes will trigger a new ORB
instance to be created. A multiple ORB scenario will occur, which is not supported.
For information about the Request Interceptor Interface of the
IBM Java ORB, see the IBM Web site:
http://www.ibm.com/software/webservers/appserv/request_interceptors.html
|