Deploying Your Configuration

 

After you create your JAM gateway configuration file, you need to deploy it, set the WebLogic Server CLASSPATH, and add your JAM startup class to the WebLogic Server configuration file. Then you can verify that your JAM system is running. The topics in this section cover the steps you need to complete to start your JAM system.

 

---

Action List

Before you deploy your configuration and start the JAM system, see the following action list and refer to the appropriate information sources.

	Your action...	Refer to...
1	Complete all prerequisite tasks.	Prerequisites
2	Deploy the JAM gateway configuraton file.	Placing the Gateway Configuration File in the WebLogic Server Start Directory
3	Set your WebLogic Server CLASSPATH to locate the JAM .JAR files.	Setting the WebLogic Server CLASSPATH for the JAM.JAR File
4	Add the JAM startup class to the WebLogic Server configuration file.	Adding the JAM Startup Class to the WebLogic Server Configuration File
5	Verify that the JAM gateway is working correctly.	Verifying that the JAM Gateway is Ready
6	Prepare for the next step.	What Do I Do Next? and Using JAM Administration Utilities

 

 

---

Prerequisites

Before you deploy your configuration and start the JAM system, you should complete the following tasks.

	Your action...	Refer to...
1	Verify that system requirements have been met.	BEA WebLogic Java Adapter for Mainframe Introduction and Release Notes
2	Determine which configuration your system requires and install the JAM product as appropriate for your configuration.	BEA WebLogic Java Adapter for Mainframe Installation Guide
3	Verify that your mainframe configuration has been properly set up for the CRM.	Preparing Mainframe Configurations for CRM Requirements
4	Create a JAM configuration file and verify that the gateway has been properly configured.	Defining the JAM Gateway Configuration
5	Learn how to start or stop the CRM with the CRM administration commands.	Using the CRM Administration Commands

 

 

---

Placing the Gateway Configuration File in the WebLogic Server Start Directory

WebLogic Server supports multiple configured server domains.

Place the jcrmgw.cfg file in the top-level WebLogic directory similar to the following example:

<bea_home>/<install_dir>/config/<domain_name>

In this example, the directory resolves to the resources for one started instance of a WebLogic Server.

 

---

Setting the WebLogic Server CLASSPATH for the JAM.JAR File

When you installed your JAM product, you should have already set your WebLogic Server CLASSPATH as described in the BEA WebLogic Java Adapter for Mainframe Installation Guide.

If you have not already done so, use the following command to place the jam.jar file in your CLASSPATH:

<JAM 42 installation directory>/lib/jam.jar

 

---

Adding the JAM Startup Class to the WebLogic Server Configuration File

The JAM startup class, com.bea.jcrmgw.gwboot, must be added to the WebLogic Server configuration file called config.xml to start the JAM gateway. The JAM gateway is then automatically started when you start WebLogic Server. The startup class can be added through the WebLogic Server Administration Console. Refer to the BEA WebLogic Server Administration Guide for specific instructions on adding a Startup Class to the configuration using the WebLogic Server Administration Console.

Note: Be sure to set the CLASSPATH as described in Setting the WebLogic Server CLASSPATH for the JAM.JAR File before you start WebLogic Server.

Figure 5-1 shows an example of the WebLogic Server Administration Console displaying the settings for a JAM gateway that communicates with a distributed CRM that is started in a remote environment. The console indicates that WebLogic Server will not stop if the JAM gateway fails to start because the Abort startup on failure option is not checked.

Refer to the following general tips for adding the JAM startup class through the WebLogic Server Administration Console.

• Click the jcrmgw link to display detail about the class as shown in Figure 5-1.

  Figure 5-1 Details of the jcrmgw Startup Class

  
   

• Note that the -r and -noexit arguments are used.

  The following arguments can be used with JAM:

  Argument	Description
  -r	Specifies a remote CRM and suppresses the spawning of a CRM process. The CRM is assumed to already be running and listening at the address specified in the CRMADDR entry of the jcrmgw.cfg file. This argument is required when the CRM is running on a different machine from the JAM gateway, or if the CRM was started in its own window for purposes of testing a configuration.
  -t	Specifies tracing CRM. Turns on level 3 CRM tracing. This option can only be used if the gateway is spawning a new local CRM. If the CRM is running remotely and tracing is required, use the -t option on the command line that started the CRM.
  -noexit	Prevents the WebLogic Server from exiting when the gateway shuts down.

  
   

• Do not select the Abort startup on failure option so that WebLogic Server will not stop if the JAM gateway fails to be brought up.

 

---

Verifying that the JAM Gateway is Ready

After you deploy the configuration file, set the WebLogic Server CLASSPATH, and add your JAM startup class to the WebLogic Server configuration file, you are ready to verify that the gateway is ready.

Then, you can verify that your JAM gateway is ready by performing the following checks:

• Start the CRM. Refer to Starting and Stopping the CRM for detailed information about starting the CRM as appropriate for your operating system.

• Re-start WebLogic Server, which also starts the JAM gateway. When JAM has successfully booted and is ready for clients, the following message is given on the WebLogic console and in the WebLogic log files:

  <(Date) (Time)> <Notice> <jcrmgw> <JAM gateway ready for use>

• Use the CRM Monitor to verify the CICS connection. Refer to the next section, Using the CRM Monitor for detailed information about the CRM Monitor.
   

 

---

What Do I Do Next?

After you deploy your JAM configuration and start the system, you are ready to learn how to use the JAM Administration utilities, the CRM Monitor and JAM Administration Servlet. You will use the CRM Monitor to verify that your JAM gateway is running properly. Refer to Using JAM Administration Utilities for more information.