Deploy Tool for WebSphere Server

OracleAS TopLink integration for IBM WebSphere Server includes a deployment tool that helps you deploy your projects to WebSphere. The Deploy Tool for WebSphere is a graphical tool that makes project deployment to WebSphere easier to configure and execute. The deploy tool also includes a command-line option that enables you to deploy your project while bypassing the graphical interface element of the tool.

Figure A-12 The Deploy Tool set up for use with WSAD

Description of the illustration deploy2.gif

Follow these steps to deploy a JAR:

Selecte the Copy generated source to directory check box to save a copy of the generated code in the specified directory. This is a quick and efficient way to copy the files into a WSAD project working directory.
Select the Turn on tracing check box if you want to see the details of the process.
Click the Deploy EJB Jar button.

Using the Deploy Tool with WebSphere Studio Application Developer (WSAD)

The Deploy tool is compatible with the WebSphere Studio Application Developer (WSAD).

Follow these steps to deploy from the Deploy Tool to WSAD:

Select the EJB Project in WSAD and choose to generate Deploy and RMIC Code.
Export the EJB Project to an EJB JAR, making sure that the OracleAS TopLink project and toplink-ejb-jar.xml files are included in the EJB JAR.
Start the OracleAS TopLink - Deploy Tool. To start the server, execute the wasDeployTool.cmd/sh script in the <ORACLE_HOME>\toplink\bin directory.
Choose the EJB project working directory so that OracleAS TopLink overrides the WSAD deploy code with the OracleAS TopLink deploy code.
If the source is copied to a directory other than the WSAD EJB Project directory, then manually copy the source files to the WSAD EJB Project under the ejbModule directory of the project.
Enter appropriate directories in the fields of the Deploy Tool.
Choose Deploy EJB JAR to create the deployed EJB JAR.
Choose Rebuild all from the Project menu to compile the deploy code to incorporate CMP.

Troubleshooting

The most common error you may encounter when you use the deploy tool is the NoClassDefFoundError exception. To resolve this error condition, add the required resources to the Classpath. The Turn on tracing option also helps to debug errors during deployment code generation.

When an obscure error appears during the generating stub phase, copy the Java command and run it at the command prompt. This gives a more detailed error message.