Corporate Info | News | Solutions | Products | Partners | Services | Events | Download | How To Buy
WebLogic Java Adapter for Mainframe Doc Home | Previous Topic | Next Topic | Contents | Index

About This Guide

This guide provides information about the BEA WebLogic Java Adapter for Mainframe (JAM), a product that enables client/server transactions between Java applications and OS/390 CICS or IMS programs.

This guide provides you with scenarios for developing and deploying applications by using the software components within the JAM environment. The scenarios depict specific tasks that work in conjunction with development and deployment procedures also provided in this guide. It is best to read and become familiar with the contents of Developing Java Applications and Deploying Applications before attempting the exercises in Programming Scenarios.

To learn more about how the System Network Architecture Communications Resource Manager (SNACRM) provides the emulation that enables CICS DPL protocols to flow into and out of the JAM environment, refer to the BEA SNACRM Administration Guide. This guide is accessible from the JAM online documentation in both HTML and PDF formats.

This section covers the following topics:

- Who Should Read This Guide

- How this Guide Is Organized

- Product Documentation

- Contact Us

Who Should Read This Guide

The audience is primarily Java application developers, Customer Information Control System (CICS) application developers, Information Management System (IMS) application developers, and system administrators who configure gateway software on BEA Web Logic Server (WLS) platforms.

System Administrators

As the application administrator, you install the WLS platform software and configure the JAM gateway. You must have sufficient System Network Architecture (SNA) knowledge to configure the underlying SNA stack (PU2.1 server) so it conforms with definitions created in Virtual Telecommunications Access Method (VTAM) and CICS for each remote domain. Refer to stack vendor documentation for details.

Successfully linking and establishing conversations between Java applications and mainframe-based programs requires special coordination. The names and characteristics of mainframe resources, configured in the SNA stack, must agree with resources and characteristics defined in VTAM and CICS.

Typically, remote VTAM and CICS resources are defined by system personnel in a data center where IBM mainframes are located. Therefore, you need to request the remote names of IMS and CICS resources from data center systems personnel and use those names to configure the SNA stack and the JAM gateway.

Java Application Developers

The JAM facility provides application developers bidirectional, transparent processing using platform native Application Programming Interfaces (API). Java application programmers can develop clients or servers using standard object-oriented programming techniques without regard for mainframe protocols.

CICS Application Developers

CICS programmers can develop servers or clients using the CICS Link command and the Distributed Program Link (DPL) subset API as a standard distributed CICS application. In addition, any existing CICS application designed to be invoked from a DPL can be used without modification.

IMS Application Developers

IMS programmers can use any IMS program (without modification) that sends and receives messages to and from the IMS message queue as either a client or a server.

How this Guide Is Organized

The BEA WebLogic Java Adapter for Mainframe User Guide is organized as follows:

- Understanding the BEA WebLogic Java Adapter for Mainframe Solution

  This section gives an overview of the JAM environment and describes two configurations for the product.

- Understanding How JAM Uses XML

  This section explains how JAM uses the capabilities of XML to exchange data between different applications and operating systems.

- Configuring the BEA WebLogic Java Adapter for Mainframe

  This section provides information and procedures for configuring the JAM development environment to create a basic servlet that can execute a CICS DPL.

- Developing Java Applications

  This section explains how to build a base Java application from a COBOL copybook and generate Java application source code.

- Deploying Applications

  This section gives procedures for installing developed servlets and/or EJB into an operational environment.

- Security

  This section describes the basic level of security supported by the JAM product software.

- Programming Reference

  This section provides data mapping rules for the EgenCobol tool used to generate Java code from COBOL copybooks.

- Using BEA WebLogic Process Integrator with JAM

  This section gives an overview of how JAM integrates with WebLogic Process Integrator to provide a user modeling tool and workflow environment that combines the functions of static data and server administration, workflow definition, and workflow monitoring.

- Developing a Multi-Service Data Entry Servlet

  This section contains a scenario that shows how to develop a multi-service application, as opposed to the single-service application presented in Generating a Servlet-Only JAM Application.

- Enhancing an Existing Servlet to Originate a Mainframe Request

  This scenario illustrates how to enhance an existing servlet to originate a mainframe request. Use the WebLogic Serversurvey servlet and add a mainframe request to the post routine.

- Updating an Existing EJB to Service a Mainframe Request

  This section contains a scenario that shows how to update an existing EJB to service a request from the mainframe.

- Integrating JAM with Crossplex

  This section contains a scenario that shows how to develop a single service servlet-based application that invokes a CrossPlex script on the mainframe.

In addition, the appendixes contain the following information:

- Code Generator Reference Pages

  This appendix contains reference pages for the EgenCobol tool.

- Configuration Checker Utility

  This appendix describes the configuration checker utility that can be used to verify the contents of the jcrmgw.cfg file before starting the Java Communications Resource Manager Gateway (JCRMGW).

- Error and Informational Messages

  This appendix gives descriptions of messages that may be encountered while using JAM software.

- Java Docs

  This appendix tells how to use the HTML pages describing JAM Java classes.

- Glossary

  The glossary contains definitions of some important terms used in this guide.

Product Documentation

The JAM documentation consists of the following:

- BEA WebLogic Java Adapter for Mainframe Release Notes

- BEA WebLogic Java Adapter for Mainframe Installation Guide

- BEA WebLogic Java Adapter for Mainframe User Guide

- BEA WebLogic Java Adapter for Mainframe, SNACRM Administration Guide

How to Use The Documentation

The Documentation CD-ROM included in the package with your product software CD-ROM contains an HTML Web User Interface (WUI). The WUI links to HTML versions and PDF versions of JAM documentation. The WUI should be viewed on an online browser. The PDF versions should be used for printing. (Information on how to view the online documentation is available in the BEA WebLogic Java Adapter for Mainframe Release Notes.)

Note: The WUI requires a Web browser that supports HTML 3.0. Netscape Navigator 2.02 or Microsoft Internet Explorer 3.0 or later.

You must have the Adobe Acrobat Reader to print the PDF file. If you do not have this reader, you can obtain it free of charge from the Adobe Systems Incorporated home site at www.adobe.com. (The BEA WebLogic Java Adapter for Mainframe WUI contains a hot link to this site.)

Document Conventions

The following documentation conventions are used throughout this manual:

####

Convention | Item
--- | ---
blue text | Indicates hypertext link to related topic in PDF file or HTML document.
boldface text | Indicates terms defined in the glossary.
Ctrl+Tab | Indicates that you must press two or more keys simultaneously.
italics | Indicates emphasis or book titles.
monospace text | Indicates code samples, commands and their options, data structures and their members, data types, directories, and file names and their extensions. Monospace text also indicates text that you must enter from the keyboard. Examples: #include <iostream.h> void main ( ) the pointer psz chmod u+w * \tux\data\ap .doc tux.doc BITMAP float
monospace boldface text | Identifies significant words in code. Example: void commit ( )
monospace italic text | Identifies variables in code. Example: String expr
UPPERCASE TEXT | Indicates device names, environment variables, and logical operators. Examples: LPT1 SIGNON OR
{ } | Indicates a set of choices in a syntax line. The braces themselves should never be typed.
[ ] | Indicates optional items in a syntax line. The brackets themselves should never be typed. Example: buildobjclient [-v] [-o name ] [-f file-list]... [-l file-list]...
| | Separates mutually exclusive choices in a syntax line. The symbol itself should never be typed.
... | Indicates one of the following in a command line: That an argument can be repeated several times in a command line That the statement omits additional optional arguments That you can enter additional parameters, values, or other information The ellipsis itself should never be typed. Example: buildobjclient [-v] [-o name ] [-f file-list]... [-l file-list]...
. . . | Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.

Contact Us

If you have any questions about this version of BEA WebLogic Java Adapter for Mainframe, or if you have problems installing and running the software, contact BEA Customer Support through BEA WebSupport at www.bea.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

- Your name, e-mail address, phone number, and fax number

- Your company name and company address

- Your machine type and authorization codes

- The name and version of the products you are using

- A description of the problem and the content of pertinent error messages

Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.