Performing Post-Installation Tasks

e-docs > WebLogic Java Adapter for Mainframe > Installation and Configuration Guide for DCL SNAP-IX > Performing Post-Installation Tasks

Installation and Configuration Guide for DCL SNAP-IX

Performing Post-Installation Tasks

After you have completed the installation process, complete the post-installation tasks in the following sections to ensure that WebLogic JAM operates properly.

Editing the Stack Type in the jamconfig.xml File

After completing the installation process, you must edit the jamconfig.xml file to use the correct stack type value. Edit the jamconfig.xml file and specify stackType="spx70". This step must be completed or WebLogic JAM will not boot.

Verifying Installation Files and Directories

The following libraries and executable programs are installed for each of the following installation components. After installing the WebLogic JAM software, verify that these libraries and programs are installed on your system.

WebLogic JAM Gateway Installation

Verify that the WebLogic JAM Gateway files listed by section are installed on your system. All directories are relative to the specified installation directory.

Table 4-1 WebLogic JAM Gateway Installation Files and Directories

Directory	Files
bin	egencobol
lib	jam.jar jam.ear jamdcl.jar jamjca.jar jamjca.rar
classdocs	jamdoc.jar
config	See Appendix A for a list of files.
samples	See Appendix A for a list of files.

WebLogic JAM CRM Installation

Verify that the WebLogic JAM CRM files listed by section are installed on your system. All directories are relative to the specified installation directory.

Table 4-2 WebLogic JAM CRM Installation Files and Directories

Directory	Files
bin	CRMLOGS CRM crmlkon crmlkoff crmdown solaris.env
lib	libctxdebugs_12.so libctxos_12.so libctxprim_12.so libctxplat_12.so libcsxappc.so libcsxxfm.so libcsxgpw.so libcsxcrm.so libcsxscrm.so libcsxspx70.so libengine.so.71 libgpnet.so.71

Using the Installation Verification Sample

After you have verified that the files have been installed, run the Installation Verification Sample.

Note: Please refer to the "Using the Installation Verification Samples" topic in the BEA WebLogic Java Adapter for Mainframe Installation Guide for information and instructions on running the installation verification samples.

Starting the CRM

Scripts are commonly used when starting the CRM. Two scripts are provided to ease the use of the CRM. The first script, solaris.env, is installed with the CRM in the <CRM_INSTALL_DIR>/bin directory. This script appends the necessary values to your environment variables. The second script, startcrm.sh, is a CRM start-up script that is installed with the Gateway in the <JAM_INSTALL_DIR>/samples/crm/unix directory.

Copy the startcrm.sh script to the directory from which the CRM will be run.
Edit solaris.env. Supply the correct values for the APPDIR and CRMDIR variables. APPDIR is the directory from which the CRM will be run. CRMDIR is the CRM installation directory. Also include the stack library in the LD_LIBRARY_PATH variable if this is not already set in your environment.
Copy the solaris.env to the crm.env.
Edit startcrm.sh. To use a different port, change the port number. However, if you change the port number, make sure to change the port number in the WebLogic Administration Console CRM1 panel. You do not need to change the address because the script will run on the machine where the CRM is installed. BEA recommends that you do not change the CRM name from CRM1. This name for the CRM is pre-configured for all of the samples.
Execute the startcrm.sh script:
```
../startcrm.sh
```

The port number is 7101. You can change the port number; however, if the port number is changed, make sure to change the port number in the Gateway configuration CRM1 panel.

Listing 4-1 Value of the STARTCMD parameter in the CRMSTART JCL

$CRMDIR/bin/CRM //127.0.0.1:7101 CRM1 </dev/null> std.out 2>std.err &

Configuring the WebLogic JAM Gateway

Most configuration tasks were pre-configured or were completed during the installation process by the installer program. For additional information about configuring WebLogic JAM, refer to the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

You must make some configuration changes for the Installation Verification Sample for CICS or IMS to run on your system. To configure the CRM to the WebLogic JAM Gateway, use the WebLogic Administration Console.

You must also edit the startverifyServer.sh to add the jamdcl.jar filename to the CLASSPATH. The jamdcl.jar must be defined in the CLASSPATH before the jam.jar.

Note: Please refer to the "Using the Installation Verification Samples" topic in the BEA WebLogic Java Adapter for Mainframe Installation Guide for additional information and instructions on configuring the WebLogic JAM Gateway.

Updating Your license.bea File

You must update your license.bea file if at least one of the following is true:

You are downloading the 60-day extension to your 30-day evaluation period of WebLogic JAM.
You possess a non-expiring license file for a previous version of WebLogic JAM, and you want to upgrade to a WebLogic JAM license after downloading WebLogic JAM from the BEA Web site.

In each case, you receive a license update file in an e-mail attachment. Update your license.bea file by performing the following steps for your system.

Updating Your license.bea File on a Unix System

To update your existing license.bea file on a Unix system, follow these steps:

Log in to the Unix system.
Save the license update file that you received through e-mail with a name other than license.bea in the target BEA Home directory.
Open a command prompt window.
Navigate to the target BEA Home directory.
Include the path to the JDK at the front of your PATH. Note the following example:
```
PATH=./jkd131_02/bin;$PATH
```
```
export PATH
```
Merge the license update file into your existing license by entering the following command:
```
sh UpdateLicense.sh license_update_file
```
license_update_file is the name to which you saved the license update file that you received through e-mail. Running this command updates your license.bea file.
Save a copy of your license.bea file in a safe place outside the WebLogic JAM product directory. Although no one else can use your license file, you should save this information in a place protected from either malicious or innocent tampering by others.

Deploying WebLogic JAM in the WebLogic Server Environment

After WebLogic JAM has been installed, it must be deployed in the WebLogic Server environment. You can deploy WebLogic JAM in the following ways:

If you are creating applications, the example domain and the verify domain are examples of domains deployed in the WebLogic Server environment. You may want to use these domains as a starting point, adding other J2EE applications to meet your specific requirements.
If you are adding WebLogic JAM to existing WebLogic Server applications, you need to manually deploy WebLogic JAM by completing the following steps:

Modifying the WebLogic Server CLASSPATH

The jamdcl.jar and the jam.jar files add classes to the WebLogic Server CLASSPATH. The .jar files must be added to the CLASSPATH in the WebLogic Server startup script for each server where it will run.

To manually add the jamdcl.jar and the jam.jar files to the WebLogic Server CLASSPATH, perform the following steps:

Using the text editor of your choice, locate the script you use to start WebLogic Server in your domain. For example, use the startWebLogic script in your config/mydomain directory mydomain is the name of your domain.
- For example, use your startWebLogic.sh script in your config/mydomain directory where mydomain is the name of your domain and startWebLogic.sh is the script to start WebLogic Server.
Edit the startWebLogic script by adding the jamdcl.jar and the jam.jar file to the CLASSPATH setting as shown in the following examples:
```
CLASSPATH=$WL_HOME:$WL_HOME/lib/weblogic_sp.jar:$WL_HOME/lib/weblogic.jar:./ext/weblogic-tags.jar:/bea/wljam5.1/lib/jamdcl.jar:/bea/wljam5.1/lib/jam.jar
```
Note: The jamdcl.jar must be defined in the CLASSPATH before the jam.jar.

In this example, /bea/wljam5.1 is the install directory for WebLogic JAM.
Save the file and close the text editor.

Deploying the jam.ear File

The jam.ear file deploys the WebLogic JAM applications and the WebLogic JAM extension to the WebLogic Administration Console. This file contains the following EJBs:

jambeans
jamtojms
jam.war (for the console)

Deploy the jam.ear file on the appropriate servers using the WebLogic Administration Console. For more information about deploying WebLogic JAM, refer to the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide. For general information about deploying applications using WebLogic Server, refer to the WebLogic Server documentation at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs70/index.html

Defining the WebLogic JAM Startup Class

The WebLogic JAM startup class defines a class that is launched at WebLogic Server startup. To manually define the WebLogic JAM startup class using the WebLogic Administration Console, perform the following steps:

In the WebLogic Administration Console, select Deployments—>Startup & Shutdown to invoke the Startup & Shutdown table.
Click on Configure a new Startup Class to invoke the Create a new Startup Class page.
Fill in the fields.
1. Assign a name for the Name field.
2. The ClassName must be com.bea.jam.GatewayStartup.
Click Create to create the new startup class.
Select the Targets tab. Select the target server from the available list and click the arrow to add it to the chosen list. Click Apply to apply the new startup class.

After you have completed the post-installation tasks for WebLogic JAM, refer to the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide for information about configuring WebLogic JAM.

Uninstalling WebLogic JAM for DCL SNAP-IX

The following sections describe the process for uninstalling BEA WebLogic Java Adapter for Mainframe (WebLogic JAM). The WebLogic JAM product may be removed or uninstalled in the following ways:

In Graphical Mode

Graphical-mode installation is the graphics-based method of executing the BEA installation program.
In Console Mode

Console-mode installation is the text-based method of executing the BEA installation program.

Uninstalling in Graphical Mode

To uninstall WebLogic JAM for DCL SNAP-IX using graphical mode, perform the following steps:

Change directories to your uninstaller directory. The following command offers an example:
```
>cd /usr/bea/wljam5.1/uninstaller
```
Start the uninstall program by performing the following command:
```
/usr/bea/wljam5.1/uninstaller> sh Uninstall
```
The About to uninstall screen displays.
Click Uninstall to start uninstalling BEA WebLogic Java Adapter for Mainframe. The following screen displays.
When the following screen displays, uninstallation is complete.
Click Exit to complete the uninstallation.

Uninstalling in Console Mode

To uninstall WebLogic JAM in console mode, perform the following steps:

Change directories to the uninstaller directory. For example:
```
> cd /usr/bea/wljam5.1/uninstaller
```
Start the uninstallation program using the following example command:
```
/usr/bea/wljam5.1/uninstaller> sh Uninstall -i console
```
At the prompt, press ENTER to begin the uninstall. The following listing displays a WebLogic JAM uninstallation. If you want to exit the uninstall program, enter QUIT at the prompt.

Note: The single-dash bar just beneath the double-dash bar is a progress indicator. When the single-dash bar becomes the same length as the double-dash bar, uninstallation is complete.

Listing 4-2 Unix Unstallation Example

machine name:/bea/loads/wljam5.1/uninstaller sh Uninstall -i console

Preparing CONSOLE Uninstall...

===============================================================================

BEA WebLogic Java Adapter for Mainframe (InstallAnywhere Uninstaller by Zero G)

-------------------------------------------------------------------------------

About to uninstall...

   BEA WebLogic Java Adapter for Mainframe

This will completely remove all components installed by InstallAnywhere. It will not remove files and folders created after the installation.

PRESS <ENTER> TO BEGIN THE UNINSTALL, OR 'QUIT' TO EXIT THE UNINSTALLER:

===============================================================================

Uninstall...

------------

 [==================|==================|==================|==================]

 [------------------|------------------|------------------|------------------]

===============================================================================

Uninstall Complete

------------------

All items were successfully uninstalled.

PRESS <ENTER> TO EXIT THE UNINSTALLER: