You can use a custom version of the Object Request Broker (ORB) with WebSphere® eXtreme Scale when you run stand-alone, Java™ Platform,
Standard Edition processes in your environment.
Before you begin
WebSphere eXtreme Scale and WebSphere Application
Server both provide an ORB, which is already configured for use with eXtreme Scale. In normal circumstances, you do not have to configure the ORB or use a different ORB.
About this task
WebSphere eXtreme Scale uses the Object Request Broker (ORB) to enable communication between processes. An ORB is included with eXtreme Scale and WebSphere Application
Server. If you are using an IBM Developer Kit or a SDK that is supplied with WebSphere Application
Server, the ORB is included in the JRE.
You can use the ORB that is supplied with eXtreme Scale, the ORB that is supplied with the IBM SDK, or the ORB that is supplied with WebSphere Application
Server. Any problems that you encounter when you use ORBs from independent software vendors must be reproducible with the IBM® ORB and compatible JRE before you contact support. eXtreme Scale does not support the ORB that is supplied with Sun Microsystems Java Development
Kit (JDK). While eXtreme Scale supports developer kits from most vendors, it is recommended you use the ORB that is supplied with eXtreme Scale.
- If your environment contains a Version 5 SDK or later, update the scripts that start the Java command by specifying an alternative directory.
- Copy the custom ibmorb.jar file and the ibmorbapi.jar file to an empty directory.
- Complete the following step when you use product scripts in a stand-alone eXtreme Scale environment:
- Edit the path for the OBJECTGRID_ENDORSED_DIRS variable in the setupCmdLine file to refer to the custom ORB directory. Save your changes.
Edit the objectgridRoot/bin/setupCmdLine.sh file.
Edit the objectgridRoot\bin\setupCmdLine.bat file.
- Complete the following step when you use product scripts in a WebSphere Application
Server environment:
- Add the following system property and parameters to the startOgServer script:
-jvmArgs –Djava.endorsed.dirs=custom_ORB_directory
- Complete the following step when you use a custom script to start a client application process or a server process:
- Add the following system property to the custom script:
-Djava.endorsed.dirs=custom_ORB_directory
- If your environment contains a Version 1.4.2 SDK, integrate the IBM ORB into the specified SDK.
- Download and extract the ORB from an IBM SDK. If no IBM SDK is available for your platform, download and extract the IBM Developer Kit for Linux®, Java Technology Edition. See IBM developer kits for more information.
- Copy the java/jre/lib/ibmorb.jar and java/jre/lib/ibmorbapi.jar files to the java/jre/lib/ext directory on the target SDK.
- Create or edit the orb.properties file, which is in the java/jre/lib directory of the SDK. Add the following properties or verify that the following properties exist in the file:
org.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB
org.omg.CORBA.ORBSingletonClass=com.ibm.rmi.corba.ORBSingleton
org.omg.PortableInterceptor.ORBInitializerClass.com.ibm.ws.objectgrid.corba.ObjectGridInitializer
For descriptions of the properties and settings, see ORB properties file.
- Download Xerces2 Java 2.9. See The Apache Xerces Project - Downloads for more information.
- Copy the xercesImpl.jar and xml-apis.jar files to the lib/ext directory.
Results
You can use the custom ORB with eXtreme Scale when you run stand-alone Java SE client and server processes.