Program guide > Plan to develop applications
Set up a stand-alone development environment
Configure an Eclipse-based integrated development environment to build and run a Java SE application with the stand-alone version of WebSphere eXtreme Scale.
Before you beginInstall the WXS product into a new or empty directory and apply the latest WXS cumulative fix pack. You can also use the WXS trial version by unzipping the zip file.
Configure Eclipse to build and run a Java SE application with WXS
- Define a user library to allow the application to reference WXS application programming interfaces.
- In the Eclipse or IBM Rational Application Developer environment, click...
Window | Preferences | Java | Build Path branch | User Libraries | New | eXtreme Scale user library | Add JARs
- Browse and select the objectgrid.jar or ogclient.jar files from...
Click OK. Select the ogclient.jar file if you are developing client applications or local, in-memory caches. If you are developing and testing WXS servers, use the objectgrid.jar file.
- To include Javadoc for the ObjectGrid APIs, select the Javadoc location for the objectgrid.jar or ogclient.jar file that you added in the previous step.
Click Edit. In the Javadoc location path box, type the following web address:
- Click OK to apply the settings and close the Preferences window.
The WXS libraries are now in the build path for the project.
- Add the user library to the Java project.
- From the package explorer, right-click the project and select...
Properties | Libraries tab | Add Library | User Library | Next | WXS user library configured earlier | OK
Run a Java SE application with WXS with Eclipse
Create a run configuration to execute the application.
- Configure Eclipse to build and run a Java SE application with WXS.
From the Run menu select...
Run Configurations | Java Application category (right-click) | New | New_Configuration
- Configure the profile.
Project main tabbed page your_project_name Main Class main tabbed page your_main_class VM arguments arguments tabbed page -Djava.endorsed.dirs=wxs_root/lib/endorsed
Problems with the VM Arguments often occur because the path to java.endorsed.dirs must be an absolute path with no variables or shortcuts.
Other common setup problems involve the Object Request Broker (ORB). You might see the following error.
Caused by: java.lang.RuntimeException: The ORB that comes with the Sun Java implementation does not work with ObjectGrid at this time.
If you do not have the objectGrid.xml or deployment.xml accessible to the application, you might see the following error:
Exception in thread "P=211046:O=0:CT" com.ibm.websphere.objectgrid. ObjectGridRuntimeException: Cannot start OG container at Client.startTestServer(Client.java:161) at Client. main(Client.java:82) Caused by: java.lang.IllegalArgumentException: The objectGridXML must not be null at com.ibm.websphere.objectgrid. deployment.DeploymentPolicyFactory.createDeploymentPolicy (DeploymentPolicyFactory.java:55) at Client.startTestServer(Client. java:154) .. 1 more
- Click Apply and close the window, or click Run.
Parent topic:Plan to develop applications
WXS programming interfaces
Class loader and classpath considerations
Run a WXS client or server application with Apache Tomcat in Rational Application Developer
Run an integrated client or server application with WAS in Rational Application Developer