bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Java Adapter for Mainframe > Samples Guide > BEA WebLogic Java Adapter for Mainframe Samples Overview |
Samples Guide
|
BEA WebLogic Java Adapter for Mainframe Samples Overview
BEA WebLogic Java Adapter for Mainframe (WebLogic JAM) is designed to integrate applications running in a WebLogic Server environment with applications running in a mainframe environment. WebLogic JAM includes complete samples that are installed as part of the product installation. These samples are provided to demonstrate how WebLogic JAM integrates WebLogic and mainframe applications. This guide explains how to run the samples that are included with WebLogic JAM.
The following topics are described in this section:
About the WebLogic JAM Samples
The samples included with WebLogic JAM allow you to see different capabilities of WebLogic JAM. The samples are much less complex than any standard production application and are not intended to be guides to application programming.
Samples have been included as a part of the WebLogic JAM software to:
Samples are designed to run "out of the box" with minimal modification. Most tasks are preconfigured or configured during installation by the installer program. You are required to only enter configuration that applies to your specific environment.
Two types of samples are installed when you install WebLogic JAM:
Verification Samples
WebLogic JAM provides two installation verification samples, one for an IMS region and one for a CICS region. These samples allow you to verify the success of the WebLogic JAM installation as well as demonstrate WebLogic JAM integration in a WebLogic and mainframe environment. These samples are described in the BEA WebLogic Java Adapter for Mainframe Installation Guide.
Programming Samples
The samples that are categorized as programming samples demonstrate how WebLogic JAM can be used with your system.
This sample demonstrates making an asynchronous call through WebLogic JAM from IMS to a Java application running under WebLogic Server.
This sample demonstrates a Java client calling remote services located in an IMS region.
This sample demonstrates how a Java client makes calls to remote services located in an IMS region. The service calls that alter the data on the mainframe occur within the boundaries of two-phase commit transactions.
This sample demonstrates the functional capability provided by WebLogic JAM to invoke the services of an EJB (Enterprise Java Bean) deployed in a WebLogic Server from a CICS client.
This sample demonstrates the invoking of CICS services from requests that originate from a Java client.
This sample demonstrates making calls to remote services located in a CICS region from a Java client. The service calls that alter data on the mainframe occur within the boundaries of two-phase commit transactions.
The purpose of this sample is to demonstrate the functional capability of invoking the services of an EJB (Enterprise Java Bean) deployed in a WebLogic Server from the mainframe environment, specifically from a batch MVS client using explicit APPC.
About the Samples User
The samples are provided to demonstrate various capabilities and functions of WebLogic JAM. Samples users typically fulfill one of the following roles:
For a description of user roles, see the BEA WebLogic Java Adapter for Mainframe Home Page.
How to Use the Samples
While the WebLogic JAM samples contain precompiled source for the Java portion of the sample, you may choose to generate and compile source. Depending on your skill level, experience, and time-constraints, you may choose to work with the Java portion of the samples in the following ways:
Because of the contents shipped with the samples, in most cases, you can simply run the sample with minimal configuration to run on your system. The sample will use the supplied .class files.
Each sample provides build scripts that allow you to compile the source. This option allows you to see how the source is compiled and run the sample.
Each sample provides eGen scripts. This option allows you to use the eGen Application Code Generator to generate the source. You can then run the build scripts. By using this option, you can see how the eGen utility generates source and run the sample.
In general, each of the samples include:
Java Sample Code
The philosophy of keeping the samples simple is demonstrated in the Java segments of the samples. For samples with Java clients and mainframe servers, stand-alone client classes are used instead of using client EJBs because the standalone clients are simpler to code, understand, deploy, and include in your applications. The servlets that can be generated by the eGen Application Code Generator are not used because you may have difficulty enhancing them to improve their presentation or functionality.
Mainframe Sample Code
Mainframe sample programs are minimal, but are sophisticated enough to demonstrate the features of WebLogic JAM. Mainframe samples are designed to take advantage of the "least common denominator" of IMS or CICS features that you might have available. For example, some of the IMS samples interact with the installation verification transaction, IVTNO, that is shipped with IMS. CICS samples use Temporary Storage (TS) queues and VSAM files to imitate the behavior of databases, rather than assume you have a database installed.
Note: JCL to compile the mainframe sample programs is included as examples to provide completeness. The sample JCL may not conform to your standards or installations. It may need to be modified or replaced to meet your needs.
Program definitions and other configuration for your CICS or IMS region may require coordination with your IMS or CICS system programmer.
Preconfigured WebLogic Server Domains
The WebLogic JAM installation includes a directory named config. This config directory contains subdirectories for two preconfigured WebLogic Server domains. These WebLogic Server domains are:
WebLogic Server domain that is set up for running the installation verification
WebLogic Server domain that is set up for examples of WebLogic JAM running with WebLogic Server and mainframe applications
Before You Run the Samples
Before you run the samples, the following tasks must be completed:
After these tasks have been completed, determine which of the samples you want to run and refer to the corresponding section:
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |