setupCmdLineXJB.bat, launchClientXJB.bat and other ActiveX batch files
This topic provides reference information about the aids that client applications and client services can use to access the ActiveX to EJB bridge. These enable the ActiveX to EJBs 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. You can include the file into your ASP application with the following syntax in your ASP page<-- #include virtual ="/WSASPIncludes/setupASPXJB.inc" -->
This syntax assumes that you have created a virtual directory in Internet Information Server called WSASPIncludes that points to the was_client_home\aspIncludes directory.
The following batch files are provided for client applications to use the ActiveX to EJB bridge...
Sets the client environment variables.
Calls the setupCmdLineXJB.bat file and launches the application you specify as its arguments; for exampleorlaunchClientXJB.bat myapp.exe parm1 parm2launchClientXJB MyApplication.vbp
- 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 you intend to talk to a single specific computer, you are recommended to change this value to become the server name that you 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 variableWhere was_client_home is the name of the directory where you installed the WAS client (for example, C:\WebSphere\AppClient).was_client_home\java\jre\bin;was_client_home\java\jre\bin\classic
Note that This technique enables only 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.