Developer's-Panther WebSphere

Packaging the EJBs

As you develop and test EJBs in your application, the EJBs can be in separate jar files. When you are ready to deploy your application, you will want to package a group of EJBs in a single jar file.

How to Package EJBs

1. Delete the test versions of the EJBs from WebSphere Application Server.
2. Run the makeejb utility on an application library. This utility generates the EJBs, compiles them, and packages them in a deployable jar file.
3. Re-install and redeploy the EJBs in WebSphere Application Server.

---

Configuring the Application Server

The section "How to Set Up the Application Server Engine" describes the process for setting up an application server machine. This process is summarized here as a runtime checklist.

At runtime, the application server must have:

• $SMBASE/config/pro5.jar and $SMBASE/servlet/proweb.jar included in its classpath setting. This can be set in the WebSphere Administrative Console.

• The Panther shared libraries must be in the system's PATH. For Windows, the Panther installer places them in the Windows system directory. For UNIX, they must be added to LD_LIBRARY_PATH or LIBPATH.

• The EJBs must be deployed and installed in WebSphere Application Server.

• The following files are in the application server's working directory:

  • panther.ini, the Panther initialization file, specifies the Panther installation location, license information, the application libraries for the server, database shared library information, and other Panther settings.

  • The application library containing the Panther service components. The default setting opens server.lib. To access another application library, it must be specified in panther.ini.

  • The Panther-generated jar file is also in this directory, but is no longer needed once the EJB has been deployed and installed in WebSphere.

Setting the Number of Application Servers

A Panther/WebSphere application consists of a group of Panther-built EJBs deployed in WebSphere Application Server. These EJBs can share an application server process, a container, a Java package, a Panther application library, a jar file, and a panther.ini file with its global and class settings.

If needed, you can distribute the application among server processes. All Panther-built EJBs must have the same global settings in panther.ini and access the same database drivers.

Configuring Runtime Clients

The section "How to Set Up the Development Client" describes the process for setting up development clients. This process is summarized here for runtime clients.

The runtime client must have:

• deployedEJB.jar

• Panther application client library (for example, client.lib)

• WebSphere Developer's Client files

• Oracle's JVM (available on the WebSphere software CD)

• Oracle's JDK/JVM setting for SMJAVALIBRARY (for example: %JAVA_HOME%\jre\bin\classic\jvm.dll)

• Settings for the JVM in SMJVMOPT

• CLASSPATH in the Environment section of prol5w32.ini; prol5w64.ini or prol5unix.ini with:

  • $SMBASE/config/pro5.jar

  • $WAS_HOME/properties

  • $WAS_HOME/lib/bootstrap.jar

  • $WAS_HOME/lib/j2ee.jar

  • $WAS_HOME/lib/lmproxy.jar

  • $WAS_HOME/lib/urlprotocols.jar

  • deployedEJB.jar

  • Java event handlers for the client screens (if applicable)

• provider_url with the server machine's host name and port number (iiop://hostName:portNumber), which can be initialized from SMPROVIDERURL

Configuring the Web Application Broker

The section "How to Set Up the Web Application Broker" describes the process for setting up an HTTP server machine. This process is summarized here as a runtime checklist.

At runtime, the HTTP server must have:

• deployedEJB.jar

• Panther application client library (for example, client.lib)

• WebSphere Developer's Client files

• Oracle's JVM

• Panther web initialization file (myApp.ini) located in ~proweb/ini on UNIX servers and the Windows directory (for example, C:\Winnt) for Windows servers with:

  • JAVA_HOME

  • WAS_HOME

  • PATH with:

    • PantherInstallDir/util

    • JavaInstallDir/bin

    • WebSphereInstallDir/bin

  • (UNIX only) LD_LIBRARY_PATH or LIBPATH with:

    • PantherInstallDir/lib

    • WebSphereInstallDir/bin

    • JVM shared libraries

  • CLASSPATH with:

    • PantherInstallDir/config/pro5.jar

    • PantherInstallDir/servlet/proweb.jar (for Java servlets)

    • DeployedEJBDirectory/deployedEJB.jar

    • $WAS_HOME/properties

    • $WAS_HOME/lib/bootstrap.jar

    • $WAS_HOME/lib/j2ee.jar

    • $WAS_HOME/lib/lmproxy.jar

    • $WAS_HOME/lib/urlprotocols.jar

  • SMPROVIDERURL with the server machine's host name and port number (iiop://hostName:portNumber)

  • SMJVMOPT with the JVM's options.

    Note: Web initialization files must contain the full pathname for Panther, WebSphere and Java installations. Environment variables cannot be expanded.