setupCmdLineXJB.bat, launchClientXJB.bat and other ActiveX batch files

Client applications and client services can use aids to access the ActiveX to EJB bridge. These aids enable the ActiveX to EJB bridge to find its XJB.JAR file and the Java run-time environment.

The include file is located in the was_client_home\aspIncludes directory. We can include the file into your Active Server Pages (ASP) application with the following syntax in your ASP page:

<--  #include virtual ="/WSASPIncludes/setupASPXJB.inc" -->

This syntax assumes that we have created a virtual directory in Internet Information Server called WSASPIncludes that points to the was_client_home\aspIncludes directory.

Usage notes

The following batch files are provided for client applications to use the ActiveX to EJB bridge:

• setupCmdLineXJB.bat

  Sets the client environment variables.

• launchClientXJB.bat

  Calls the setupCmdLineXJB.bat file and launches the application we specify as its arguments; for example:

  launchClientXJB.bat myapp.exe parm1 parm2
  

  or

  launchClientXJB MyApplication.vbp
  

• Active Server Pages (ASP) include file

  An include file is provided for ASP users to automatically set the following page-level (local) environment variables:

  • com_ibm_websphere_javahome. Path to the Java run-time directory installed with the WebSphere advanced server client.
  • com_ibm_websphere_washome. Path to the WebSphere advanced server client directory.
  • com_ibm_websphere_namingfactory. Sets the Java java.naming.factory.initial system property.
  • com_ibm_websphere_computername. (Optional) Name of the computer where the WebSphere Advanced Server Client is installed. If we intend to talk to a single specific computer, we are recommended to change this value to become the server name that we intend to access.

• System settings

  To enable the ActiveX to EJB bridge to access the Java run-time dynamic link library (DLL), the following directories must exist in the system PATH environment variable:

  was_client_home\java\jre\bin;was_client_home\java\jre\bin\classic
  

  Where was_client_home is the name of the directory where we installed the WAS client (for example, C:\WebSphere\AppClient).

  This technique enables only one Java run time to activate on a machine, therefore all client services on that machine must use the same Java run time. Client applications do not have this limitation because they each have their own private, non-system scope.

Starting an ActiveX application and configuring service programs

Starting an ActiveX application and configuring non-service programs