BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
JAM Documentation | JAM Configuration and Administration Guide | Previous Topic | Next Topic | Contents | Index

Putting It All Together

The topics in this section cover examples of configurations for cross-platform definitions. The configurations put together the information described in Preparing Mainframe Configurations for CRM Requirements and Defining the JAM Gateway Configuration. These examples are for reference only and do not represent all configuration possibilities. Consult with your system administrator for specific information about your system.

Action List

Before you review the sample configurations included in this section, see the following action list and refer to the appropriate information sources.

| Your action... | Refer to...
--- | --- | ---
1 | Complete all prerequisite tasks. | Prerequisites
2 | Reveiw an example of Windows NT or UNIX cross-platform definitions. | Example of Windows NT or UNIX Cross-Platform Definitions
3 | Review an example of OS/390 cross-platform definitions. | Example of OS/390 Definitions
4 | Prepare for the next step. | What Do I Do Next? and Using the CRM Administration Commands

Prerequisites

Before you use the CRM Administrative commands, 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 | Learn about mainframe configuration requirements for the CRM. | Preparing Mainframe Configurations for CRM Requirements
4 | You may have already created a JAM configuration file and verified that the gateway was properly configured. This action may be done before or after reviewing the configuration examples. | Defining the JAM Gateway Configuration

Example of Windows NT or UNIX Cross-Platform Definitions

Before installing JAM software, review Table 3-1 for an example of Windows NT or UNIX cross-platform definitions. Consult with your VTAM system administrator to obtain the value indicated in the Name column and make the corresponding entries shown in the Needed In column.

Note: DCL-based stacks referred to in Table 3-1 include the following stacks:

- Solaris SNAP-IX

- IBM Comm Server for Windows NT

Listing 3-1 shows the corresponding JAM configuration file.

.

Table 3-1 Summary of Windows NT or UNIX Definitions

Name

Originates In

Needed In

SNA Network ID
(e.g. SNANET1)
and VTAM Host ID
(e.g. VTAMHOST)

VTAM configuration

DCL-based Stack Configuration:

Example:
fqcp_name=SNANET1.SPARC1
adj_cp_name=SNANET1.VTAMHOST
fqplu_name=SNANET1.CICSSYN

Mode Name
(e.g. SNA62)

VTAM-MODEENT definition

CICS Sessions Definition:
Example:
MODENAME(SNA62)

DCL-based Stack Configuration:
Example:
mode_name=SNA62

JCRMGW Configuration:
Example:
JC_SNALINKS
MODENAME="SNA62"

Control Point Name
CPNAME
(e.g. SPARC1)

VTAM-PU definition

DCL-based Stack Configuration:
Example:
fqcp_name=SNANET1.SPARC
cp_alias=SPARC1

Local LU Name
(e.g. L0F0024A)

VTAM-LU definition

CICS CONNECTION definition:
Example:
NETNAME(L0F0024A)
DCL-based Stack Configuration:
Example:
lu_name=L0F0024A
lu_alias=L0F0024A

JCRMGW Configuration:
Example:
JC_SNASTACKS
LOCALLU="L0F0024A"

CICS LU Name
(e.g. CICSSYN)

VTAM-LU definition

DCL-based Stack Configuration:
Example:
fqplu_name=SNANET1.CICSSYN
plu_alias=CICSSYN

JCRMGW Configuration:
Example:
JC_SNALINKS
RLUNAME="CICSSYN"

Terminal Identifier
(e.g. 05DF0024)

VTAM
(IDNUM+IDBLK)

DCL-based Stack Configuration:
Example:
node_id=<05000002>

SYNCLVL supported by jcrmgw

Stacks

DCL-based Stack Configuration:
Example:
[define local_lu]
syncpt_support=CONFIRM

Map all incoming conversations to JAM gateway (make sure TPs have all privileges available, e.g. CNOS, service conversations, etc.).

Stacks

DCL-based Stack Configuration:
Example:
Sna_tps
<404040...hex representation of 64 EBCDIC spaces...404040>
TYPE=QUEUED
TIMEOUT=-1
USERID=authorized_user_here
GROUP=authorized_group_here
LUALIAS=LOF0024A

JCRMGW Configuration:
Example:
JC_LOCAL_SERVICES
RNAME="DPL1SVR"

CICS DPL program name (e.g. TOUPPER)

CICS/ESA

JCRMGW Configuration:
Example:
JC_REMOTE_SERVICES
RNAME=TOUPPER

Listing 3-1 Corresponding jcrmgw.cfg Configuration File

>     *JC_REMOTE_DOMAINS
>     #
>     CICS13        DOMAINID="13"
>     #
>     *JC_SNACRM
>     #
>     CRMAN	SNACRMADDR="//dalnt66:8650"
>                   GROUP="G1"

>     *JC_SNASTACKS
>     #
>     OS390         STACKTYPE="SPX62"
>                   LOCALLU="LOF0024A"
>     #
>     *JC_SNALINKS
>     #
>     CICS          RLUNAME="CICSSYN"
>                   RDOM="CICS13"
>                   MODENAME="SNA62"
>                   MAXSESS=8
>                   MINWIN=6
>     #
>     *JC_LOCAL_SERVICES
>     #
>     TraderHome    RNAME="DPL1SVR"
>     #
>     *JC_REMOTE_SERVICES
>     TOUPPER	       RDOM="CICS13"
>                   RNAME="TOUPPER"
>                   TRANTIME=10000

Example of OS/390 Definitions

Before installing JAM software, review Table 3-2 for an example of SNA definitions when the CRM runs on an OS/390 platform. Consult with your system administrator to obtain the value indicated in the Name column and make the corresponding entries shown in the Needed In column. Listing 3-2 shows the corresponding JAM configuration file.

.

Table 3-2 Summary of OS/390 SNA Definitions

Name

Originates In

Needed In

Local LU Name
(e.g. BEAAPPL1)

VTAM-LU definition

CICS CONNECTION definition:
Example:
NETNAME(BEAAPPL1)
VTAM Configuration:
Example:
BEASNA VBUILD TYPE=APPL
BEAAPPL1 APPL ACB=BEAAPPL1,
APPC=YES,
PARSESS=YES
JCRMGW Configuration:
Example:
JC_SNASTACKS
LOCALLU="BEAAPPL1"

Mode Name
(e.g. SNA62)

VTAM-MODEENT definition

CICS Sessions Definition:
Example:
MODENAME(SNA62)
JCRMGW Configuration:
Example:
JC_SNALINKS
MODENAME="SNA62"
VTAM Configuration (not required):
Example:
MODEENT=SNA62

CICS LU Name
(e.g. CICSSYN)

VTAM-LU definition

JCRMGW Configuration:
Example:
JC_SNALINKS
RLUNAME="CICSSYN"

Maximum sync-level allowed by jcrmgw

jcrmgw

VTAM Configuration:
Example:
SYNCLVL=CONFIRM

CICS DPL program name (e.g. TOUPPER)

CICS/ESA

JCRMGW Configuration:
Example:
JC_REMOTE_SERVICES
RNAME=TOUPPER

Listing 3-2 Corresponding jcrmgw.cfg Configuration File

>     *JC_REMOTE_DOMAINS
>     #
>     CICS13        DOMAINID="13"
>     #
>     *JC_SNACRM
>     #
>     CRMAN	SNACRMADDR="//dalnt66:8650"
>                   GROUP="G1"

>     *JC_SNASTACKS
>     #
>     OS390         STACKTYPE="SPX62"
>                   LOCALLU="BEAAPPL1"
>     #
>     *JC_SNALINKS
>     #
>     CICS          RLUNAME="CICSSYN"
>                   RDOM="CICS13"
>                   MODENAME="SNA62"
>                   MAXSESS=8
>                   MINWIN=6
>     #
>     *JC_LOCAL_SERVICES
>     #
>     TraderHome	    RNAME="DPL1SVR"
>     #
>     *JC_REMOTE_SERVICES
>     TOUPPER	       RDOM="CICS13"
>                   RNAME="TOUPPER"
>                   TRANTIME=10000

What Do I Do Next?

After you create a JAM configuration file for your environment and check it, you are ready to learn how to run the CRM so that you can deploy your configuration. Refer to Using the CRM Administration Commands for more information about starting the CRM.

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