Preparing for Installation


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Search \| PDF Files \| Contact

WebLogic Java Adapter for Mainframe Doc Home \| WebLogic Java Adapter for Mainframe Installation Guide \| Previous Topic \| Next Topic \| Contents \|

This section contains information about pre-installation preparation that is necessary before installing the BEA WebLogic Java Adapter for Mainframe (JAM) software. To ensure successful installation and operation of the JAM software, complete the tasks described in this section.

This section contains the following topics:

Determine Your Configuration

Configuration is important to consider when planning the installation of the JAM software. The normal JAM environment generally includes two properly configured components: the Java Communication Resource Manager Gateway (JCRMGW) and the Systems Network Architecture Communications Resource Manager (SNACRM). The type of network connectivity will determine which type of SNACRM installation and configuration is required.

When JCRMGW and SNACRM are installed on the same machine, the installation is referred to as a combined (or local) configuration. When these components are installed on different Unix, NT, or OS/390 platforms, the installation is referred to as a distributed (or remote) configuration. The diagrams in the following sections show examples of the relationships of the JAM components in three types of configurations.

Local Configuration

The local configuration combines the Java application, JCRMGW, WebLogic Server, and the SNACRM with the stack (PU2.1 server) on the same Unix or Windows NT platform. It employs the IBM proprietary SNA protocol for transactions with the mainframe via the stack.

Figure 1-1 JAM Local Configuration

Distributed Configurations

One type of distributed configuration separates Java applications and the JCRMGW from the SNACRM by installing the SNACRM to the IBM OS/390 Mainframe. This configuration eliminates the need for a third-party stack on the Unix or NT machine. Note that this configuration requires a one-to-one relationship between the local JCRMGW and the remote SNACRM.

Figure 1-2 JAM Distributed Configuration

Another type of distributed configuration separates Java applications and the JCRMGW from the SNACRM on different Unix or Windows NT platforms. It employs Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity between the Java applications platform and the SNACRM platforms, as well as the SNA connectivity to the mainframe environment(s). This configuration gives you the flexibility to deploy WebLogic Server separately from the SNACRM at installations that require WebLogic Server on a platform other than the one on which the SNA stack is running. Note that this configuration requires a one-to-one relationship between the local JCRMGW and the remote SNACRM.

Figure 1-3 Alternate JAM Distributed Configuration

The New Distributed CRM

As in prior releases, the JAM product includes two JAM software components:

JCRMGW-Java Gateway component
SNACRM -Communication Resource Manager component

In prior releases, the JCRMGW operated under WebLogic; and the SNACRM operated on the same operating system as WebLogic, but outside of the confines of WebLogic. The communication between these two components was through TCP/IP. The JCRMGW conversed bidirectionally via TCP/IP with the SNACRM. The SNACRM communicated with the mainframe through SNA LU 6.2 protocols to the supported third party SNA stack. These supported SNA stacks included Windows NT Server and Microsoft SNA Server, Hewlett Packard SNAplus2, SUN SunLink, and Data Connection Limited SNAP-IX. This architecture is illustrated in the following diagram.

Figure 2 JAM Architecture in Previous Releases

WebLogic Java Adapter for Mainframe v4.1 provides an additional configuration option: the distributed CRM. This new feature allows the SNACRM to be installed on the mainframe. Because communication between the two components (JCRMGW and SNACRM) is TCP, this configuration allows TCP/IP communication to the mainframe. This feature has been added by enhancing a layer within the SNACRM. This abstraction layer converses with VTAM, eliminating the need for a PU2.1 SNA stack altogether. The communication from the SNACRM to VTAM on the mainframe is still SNA, while the network protocol is TCP/IP. The following diagram illustrates the configuration architecture of the new JAM feature.

Figure 3 New JAM Architecture

Note that module names within the JAM product have been retained from JAM v4.0 to JAM v4.1. The JAM gateway (JCRMGW) and Communications Resource Manager (SNACRM) still exist. The SNACRM component is used to communicate both SNA and TCP protocols. TCP protocols always flow between JCRMGW and SNACRM. SNA protocols always flow from the SNACRM to the mainframe and from either an SNA stack or VTAM on the mainframe to the SNACRM depending upon the configuration option.

How the Configuration Affects Installation

Make sure you understand which configuration applies to your application development environment. During installation, you must enter the destinations for the two major JAM components, the SNACRM and the JCRMGW. These destinations are determined by your configuration. If you are using the combined configuration, both components are installed on the same platform. If you are using a distributed configuration, the components are installed on different platforms; the JCRMGW must be installed on the platform with WebLogic Server and the SNACRM must be installed on the same platform with the SNA stack. Some platforms do not support local SNACRMs. Check the BEA WebLogic Java Adapter for Mainframe Release Notes for detailed information about supported platforms.

Determine Requirements for Other Components

Because JAM interacts with mainframe applications, be sure to involve your mainframe system support personnel early in the process of planning and installing your JAM software. In a large shop, separate individuals may be responsible for Multiple Virtual System (MVS), Virtual Telecommunications Access Method (VTAM), Information Management System (IMS), and Customer Information Control System/Enterprise Systems Architecture (CICS/ESA). Make sure everyone is involved.

Whether your JAM software is installed on Windows NT, Unix, or a mainframe, you will need to make sure your system meets the appropriate requirements and that supporting software is operating correctly. The following sections describe mainframe and non-mainframe requirements, and verification of supporting software installations.

Mainframe Requirements

The SNACRM component of JAM may or may not be located on the mainframe environment; however, mainframe configurations affect how JAM works. The following configurations are required on the mainframe in order to conduct operations within the JAM/WebLogic Server environment:

Established VTAM configuration
CICS/ESA Logical Unit (LU) configured with proper connections created and sessions defined
If using IMS, APPC and transaction definitions must exist for that environment

Non-Mainframe Requirements

A non-mainframe environment is a Unix-based or Windows NT-based machine running the JAM software. The software is fully bi-directional, supporting the local system as either a client or server. This environment consists of the following components:

Hardware, which is any workstation and network interface supported by the required software
Operating system software and SNA protocol stacks (PU servers) if the SNACRM is not installed on the mainframe (Refer to the BEA WebLogic Java Adapter for Mainframe Release Notes for a complete listing.)
Stack installation should also be completed and verified. (Refer to vendor documentation for stack installation and verification information.)
BEA WebLogic Server 5.1
For JAM installations in a WebLogic Server environment, you must have the BEA WebLogic Server 5.1 software installed.

Install the Prerequisite Software

The following software should be installed prior to installing the JAM software:

Install and configure a supported SNA stack on the operating system where the SNACRM will be installed.
A properly configured SNA protocol stack is required for the SNACRM to communicate with a mainframe.

The Java gateway requires the following parameters from the SNA stack configuration:
- Local LU - The local name of the SNACRM that will be used by the mainframe application.
- Remote LU - The name of the mainframe application that the SNACRM will use.
- Mode Name - The SNA mode definitions provide session characteristics for a given local/remote LU pair.
- Max sessions - Sessions are required for connections to be made between two LUs. Max sessions should be high enough to handle the expected gateway traffic. This parameter is optional and defaults to 4.
- Minimum Contention Winners - Determines the priority of the session activation. This parameter is optional and defaults to one half the value specified for max sessions.
  Refer to the BEA WebLogic Java Adapter for Mainframe Release Notes for a list of supported SNA stacks.
  
  Note: Refer to the SNA stack vendor's documentation on configuring for your environment. Ensure that the stack is properly installed and that the configuration can be activated.
Install the appropriate Java JDK for the WebLogic Server platform. Refer to the BEA WebLogic Java Adapter for Mainframe Release Notes for the correct version for your platform.
Obtain the JDK from the OEM who provided the hardware on which WebLogic Server is to run. Follow the installation instructions provided with the JDK distribution. Be sure to get the most recent service patch available.
Install and configure WebLogic Server.
Refer to the WebLogic Server Installation Guide for installation and configuration information. Some specific WebLogic configuration tasks must be completed to install JAM.

Add the JAM .jar files to the WEBLOGICCLASSPATH variable in your start WebLogic script. This script is provided with the WebLogic Server install and is named start WebLogic.cmd on Windows NT systems and start Weblogic.sh on UNIX systems. Both the jam.jar and the ebase.jar files must be added to the WEBLOGICCLASSPATH. Both of these files may be found in the "lib" directory of your JAM installation.
Add the following necessary lines to your weblogic.properties file. The weblogic.properties file is located in the WebLogic installation directory.
1. The following line is for gateway startup class specification:
```
weblogic.system.startupClass.jcrmgw=com.bea.sna.jcrmgw.gwboot
```
2. The following options will specify gateway startup arguments, if necessary:
```
weblogic.system.startupArgs.jcrmgw=options
```
  Where:
  
  -t
  
  will turn on tracing in the SNACRM.
  
  -r
  
  indicates that the SNACRM is remote. The SNACRM should run on the same platform as the SNA stack. The SNACRM can be the same machine as the WebLogic Server. In this case -r is omitted and the JCRMGW will spawn a new SNACRM using the address specified in the jcrmgw.cfg file. If -r is used, the SNACRM will not spawn, but is assumed to already be running at the address specified in the jcrmgw.cfg, even if this is the same machine running the gateway. In addition, the local SNACRM group identifier must match the group identifier specified on the command line used to start the remote SNACRM.
  
  -u<userid>
  <userid> is the mainframe userid that should be associated with all requests originating from this gateway. This parameter is useful for IDENTIFY type security where the client cannot provide a userid.
  
  Note: The WEBLOGICCLASSPATH must contain the fully-qualified name of the jam.jar file and the ebase.jar file.
  The JAM EJB deployment specification:
  weblogic.ejb.deploy=/jam-install-directory/lib/jam.jar
  Listing 3-1 Sample Lines from weblogic.properties File
  weblogic.system.startupClass.jcrmgw=com.bea.jcrmgw.gwboot
  weblogic.system.startupArgs.jcrmgw=-t -r -u userName
  weblogic.ejb.deploy=/jam-install-directory/lib/jam.jar

Establish Your Mainframe Environment

Refer to the SNACRM Administration Guide for additional information about configuration/environment options. The following configurations are required on the mainframe in order to conduct operations with the BEA eLink Platform/WebLogic Server environment:

Established VTAM configuration
CICS/ESA Logical Unit (LU) configured with proper connections created and sessions defined
If using IMS, APPC and transaction definitions must exist for that environment

Verify SNA Stack Installation

Proper stack installation will ensure that your applications deploy and operate correctly. Complete the following installation tasks in order:

Install the stack software per vendor instructions.
Start the stack.
Successfully activate definitions.
Execute vendor-provided tests.

Verify WebLogic Server Installation

Proper WebLogic Server installation will ensure that your applications deploy and operate correctly.

Validate the WebLogic Server software installation by running the sample applications found at the following url:

http://www.weblogic.com/docs51/examples/index.html

You should run at least one of the servlet examples.