bea.com | products | dev2dev | support | askBEA

Download Docs
Search

Installation and Configuration Guide for DCL SNAP-IX

Configuring WebLogic JAM Connectivity

The WebLogic Administration Console provides you with the tools you need to configure connectivity between your mainframe and WebLogic Server.

This section provides information on the following subjects:

- Understanding WebLogic JAM Connectivity

- Step 1: Define Where the CRM Will Run

- Step 2: Connecting VTAM and Your Local Stack

Note: Please refer to the "Configuring WebLogic Connectivity" topic in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide for instructions on performing steps 3, 4, 5, and 6.

- Step 3: Connect the CRM to Back-End System on the Mainframe

- Step 4: Enter Connectivity Information into WebLogic Administration Console

- Step 5: Define a WebLogic JAM Gateway

- Step 6: Verify Your WebLogic JAM Connectivity Configuration

Understanding WebLogic JAM Connectivity

WebLogic JAM uses two distributed software components to connect to your back-end systems: the WebLogic JAM Gateway and the Communications Resource Manager (CRM). The WebLogic JAM Gateway component runs within an instance of WebLogic Server and serves as a proxy to other applications running within WebLogic Server.

The CRM runs as a native operating system process, and it connects to your back-end system using Advanced Program to Program Communications (APPC), also known as LU 6.2, using SNA network connections. The CRM and the WebLogic JAM Gateway communicate with each other using a TCP/IP socket. The CRM connects to your back-end system using an SNA network connection called a logical unit (LU).

A logical unit is an SNA network's way of providing access to the SNA network to end users and software programs. A logical unit is a unique, addressable part of an SNA network that manages data flows between network partners. A logical unit is somewhat like a TCP/IP address and port because software programs can use it to access the network and to communicate with other software programs that are distributed throughout the enterprise. Unlike TCP/IP connections, logical units must be defined prior to use. Figure 5-1 shows the CRM using APPC to establish communication with a back-end application.

Figure 5-1 CRM Using APPC

In order for software programs such as the CRM to communicate via APPC, each peer program must have access to a logical unit. The software programs then allocate a session between the two logical units to communicate and collaborate.

A session is a pipeline between two logical units that manages the exchange of data between the logical units. The two peer programs send data back and forth over the logical unit pair using a session. This exchange of data is called a conversation. The number of sessions that can exist simultaneously over a given logical unit pair is configured in the SNA network. The number of sessions that are configured between an LU-LU pair, determine how many concurrent conversations can occur simultaneously. Establishing WebLogic JAM connectivity involves allocating logical units and sessions in your SNA network, and recording this configuration in WebLogic JAM.

The WebLogic Administration Console allows you to define where WebLogic JAM components will run within your enterprise, and the network connections that they will establish. Once entered into the console, this configuration is persisted and distributed to WebLogic JAM components upon start-up.

Getting Started with WebLogic JAM Connectivity

The overall task of establishing WebLogic JAM connectivity involves asking administration personnel to allocate SNA network resources (logical units, sessions) and then recording these resources in WebLogic JAM configuration via the WebLogic Administration Console. This task has been organized into six primary steps:

- Step 1: Define Where the CRM Will Run

- Step 2: Connecting VTAM and Your Local Stack

Note: Please refer to the "Configuring WebLogic Connectivity" topic in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide for instructions on performing steps 3, 4, 5, and 6.

- Step 3: Connect the CRM to Back-End System on the Mainframe

- Step 4: Enter Connectivity Information into WebLogic Administration Console

- Step 5: Define a WebLogic JAM Gateway

- Step 6: Verify Your WebLogic JAM Connectivity Configuration

Your system administrators will configure your mainframe to communicate using SNA and then establish the actual connection to the CRM using the parameter information provided in the steps of this section.

When you have all of the appropriate parameters, you are ready to configure connectivity by entering them into the WebLogic Administration Console. Use the steps in this section to help you and your system administrators connect your systems correctly and to get the correct configuration information into the WebLogic Administration Console. Instructions are also provided to help you verify your configuration.

Note: The Mainframe Connectivity Worksheet is provided to help you prepare to configure connectivity between your mainframe system and your BEA WebLogic Server system. For a copy of the worksheet, refer to the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

Step 1: Define Where the CRM Will Run

The CRM can run on Solaris 7 or 8 with a DCL SNAP-IX stack.

For this step, you need to determine where you want the CRM to run and then gather the configuration information that you will input into the WebLogic Administration Console in a later step. Table 5-1 provides a list of the parameters that you will use to configure connectivity with the CRM in the WebLogic Administration Console.

Table 5-1 CRM Definition Parameter in the WebLogic Administration Console

WebLogic Administration Console Parameters | Description | Parameter Syntax
--- | --- | ---
Name | The arbitrary name of the CRM. The CRM process uses this name to ensure the correct configuration between the WebLogic JAM Gateway and the CRM process. | Alpha-numeric string Ex. CRM1
Listen Address | The host name of the machine where the CRM runs, or the TCP/IP address of the machine where the CRM runs. | Alpha-numeric string or dotted IP address Ex. myhost or 123.4.5.678
Listen Port | The TCP/IP port that is used by the CRM to listen for connecting WebLogic JAM components. Ask your network administrator for an unused TCP/IP port on the machine where the CRM runs. | Numeric value Ex. 8002
Stack Type | The predefined name for the SNA network software. If the CRM is running on Solaris 7 or 8 with the DCL SNAP-IX stack, this entry is the abbreviation spx70. | Supported stack available in drop-down list. Ex. spx70

Step 2: Connecting VTAM and Your Local Stack

Connecting VTAM to your local stack consist of the following two steps:

- Creating a VTAM Switched Major Node Definition

- Establishing a DCL SNAP-IX Stack Configuration

Creating a VTAM Switched Major Node Definition

VTAM Switched Major Node (SWNET) definitions define and link together physical units (PU) and logical units (LU). Each workstation connected to a network must be represented on the network as a PU and each PU can have one or more LUs. The VTAM SWNET definition defines how the PUs and LUs communicate with a server. An example of a SWNET definition is listed below.

Listing 5-1 Sample VTAM SWNET Definition

>     SWNEBEA  VBUILD  TYPE=SWNET, MAXNO=3, MAXGRP=3
>     SWNEBEA1 PU  ADDR=03,
>                    IDBLK=021,
>                    IDNUM=10333,
>                    PUTYPE=2,
>                    NETID=BEALAN,
>                    CPNAME=BEASUN,
>                    MAXPATH=3,
>                    DWACT=YES,
>                    CONNTYPE=APPN,
>                    DYNLU=YES,
>                    CPCP=YES
>     PATHDI1  PATH DIALNO=3767,
>                    GRPNM=G1ETH1
>     LUBEA01   LU  LOCADDR=0
>     LUBEA02   LU  LOCADDR=0

The fields that are most relevant to WebLogic JAM and the local stack configuration are listed in the table below.

Table 5-2

Field | Field From Example | Definition and Usage
--- | --- | ---
SWNET Definition Name | SWNEBEA1 | The name of the SWNET definition that must be varied active before the stack will connect to your mainframe.
PU Name | SWNEBEA1 | The PU name of the link station expecting to connect to the mainframe. This field appears as a link station in your local stack configuration.
IDBLK | IDBLK=021 | Must be unique.
IDNUM | IDNUM=10333 | Must be unique.
DIALNO | DIALNO=1874560398634502 | The MAC address of the Solaris 7 or 8 machine where the DCL SNAP-IX stack will run.
NETID | NETID=BEALAN | The network ID which is also the first half of the control point name for your DCL SNAP-IX node.
CPNAME | CPNAME=BEASUN | The control point name which appears as the second half of the control point name for your DCL SNAP-IX node.
LU Name | LUBEA01 | Name of the LU that is defined on your local stack configuration. It is also used as the netname in the session definition within your CICS region.

VTAM SWNET Field Definitions

Establishing a DCL SNAP-IX Stack Configuration

A DCL SNAP-IX stack configuration can be set up using stack-specific configuration utilities or by manually creating a configuration file with any text editor. The following listing shows an example of an SNA node configuration file. The configuration file is divided into sections for various components of the configuration. Each section defines a component using parameters (or keywords) and values. Some of these keywords and values will affect how your WebLogic JAM configuration is defined.

Consult with your VTAM administrator to obtain key parameters in the VTAM SWNET definition that must be included in the SNA stack configuration.

Listing 5-2 Example of a sna_node.cfg File

>     [define_node_config_file]
>     major_version = 5
>     minor_version = 1
>     update_release = 1
>     revision_level = 57

>     [define_node]
>     cp_alias = dalsun8
>     description = ""
>     fqcp_name = BEALAN.BEASUN
>     node_type = LEN_NODE
>     mode_to_cos_map_supp = YES
>     mds_supported = YES
>     node_id = <bea89476>
>     max_locates = 1500
>     dir_cache_size = 255
>     max_dir_entries = 0
>     locate_timeout = 0
>     reg_with_nn = YES
>     reg_with_cds = YES
>     mds_send_alert_q_size = 100
>     cos_cache_size = 24
>     tree_cache_size = 40
>     tree_cache_use_limit = 40
>     max_tdm_nodes = 0
>     max_tdm_tgs = 0
>     max_isr_sessions = 1000
>     isr_sessions_upper_threshold = 900
>     isr_sessions_lower_threshold = 800
>     isr_max_ru_size = 16384
>     isr_rcv_pac_window = 8
>     store_endpt_rscvs = NO
>     store_isr_rscvs = NO
>     store_dlur_rscvs = NO
>     cos_table_version = VERSION_0_COS_TABLES
>     send_term_self = NO
>     disable_branch_awareness = NO
>     cplu_syncpt_support = NO
>     cplu_attributes = NONE
>     dlur_support = NO
>     pu_conc_support = YES
>     nn_rar = 128
>     max_ls_exception_events = 0
>     ptf_flags = NONE

>     [define_ethernet_dlc]
>     dlc_name = ETHER0
>     description = ""
>     neg_ls_supp = YES
>     initially_active = NO
>     adapter_number = 0
>     lan_type = 802_3_DIX

>     [define_ethernet_port]
>     port_name = ETSAP0
>     description = ""
>     dlc_name = ETHER0
>     port_type = PORT_SATF
>     port_number = 0
>     max_rcv_btu_size = 1033
>     tot_link_act_lim = 64
>     inb_link_act_lim = 0
>     out_link_act_lim = 0
>     ls_role = LS_NEG
>     implicit_dspu_services = NONE
>     implicit_dspu_template = ""
>     implicit_ls_limit = 0
>     act_xid_exchange_limit = 9
>     nonact_xid_exchange_limit = 5
>     ls_xmit_rcv_cap = LS_TWS
>     max_ifrm_rcvd = 7
>     target_pacing_count = 7
>     max_send_btu_size = 1033
>     mac_address = <937694760285>
>     lsap_address = 0x04
>     implicit_cp_cp_sess_support = NO
>     implicit_limited_resource = NO
>     implicit_deact_timer = 30
>     implicit_hpr_support = NO
>     implicit_link_lvl_error = NO
>     implicit_uplink_to_en = NO
>     effect_cap = 3993600
>     connect_cost = 0
>     byte_cost = 0
>     security = SEC_NONSECURE
>     prop_delay = PROP_DELAY_LAN
>     user_def_parm_1 = 128
>     user_def_parm_2 = 128
>     user_def_parm_3 = 128
>     initially_active = YES
>     window_inc_threshold = 1
>     test_timeout = 10
>     test_timer_retry = 5
>     xid_timer = 10
>     xid_timer_retry = 5
>     ack_timeout = 5000
>     p_bit_timeout = 5000
>     t2_timeout = 100
>     rej_timeout = 10
>     busy_state_timeout = 30
>     idle_timeout = 30
>     max_retry = 3

>     [define_ethernet_ls]
>     ls_name = SWNEBEA1
>     description = ""
>     port_name = ETSAP0
>     adj_cp_name = P390.MVSREGION
>     adj_cp_type = END_NODE
>     mac_address = <197459563870>
>     lsap_address = 0x04
>     auto_act_supp = NO
>     tg_number = 0
>     limited_resource = NO
>     solicit_sscp_sessions = YES
>     pu_name = BEASUN1
>     disable_remote_act = NO
>     default_nn_server = NO
>     dspu_services = NONE
>     dspu_name = <0000000000000000>
>     dlus_name = <0000000000000000000000000000000000>
>     bkup_dlus_name = <0000000000000000000000000000000000>
>     hpr_supported = NO
>     hpr_link_lvl_error = NO
>     link_deact_timer = 30
>     use_default_tg_chars = YES
>     ls_attributes = SNA
>     adj_node_id = <00000000>
>     local_node_id = <00000000>
>     cp_cp_sess_support = NO
>     effect_cap = 3993600
>     connect_cost = 0
>     byte_cost = 0
>     security = SEC_NONSECURE
>     prop_delay = PROP_DELAY_LAN
>     user_def_parm_1 = 128
>     user_def_parm_2 = 128
>     user_def_parm_3 = 128
>     target_pacing_count = 7
>     max_send_btu_size = 1033
>     ls_role = USE_PORT_DEFAULTS
>     max_ifrm_rcvd = 0
>     dlus_retry_timeout = 0
>     dlus_retry_limit = 0
>     branch_link_type = NONE
>     adj_brnn_cp_support = ALLOWED
>     dddlu_offline_supported = NO
>     initially_active = NO
>     restart_on_normal_deact = NO
>     react_timer = 30
>     react_timer_retry = 65535
>     test_timeout = 10
>     test_timer_retry = 5
>     xid_timer = 10
>     xid_timer_retry = 5
>     ack_timeout = 5000
>     p_bit_timeout = 5000
>     t2_timeout = 100
>     rej_timeout = 10
>     busy_state_timeout = 30
>     idle_timeout = 30
>     max_retry = 3

>     [define_partner_lu]
>     plu_alias = CICS1
>     description = ""
>     fqplu_name = P390.CICSREGN
>     plu_un_name = CICSREGN
>     parallel_sess_supp = YES
>     max_mc_ll_send_size = 0
>     conv_security_ver = NO

>     [define_local_lu]
>     lu_alias = LUBEA01
>     list_name = ""
>     description = ""
>     lu_name = LUBEA01
>     lu_session_limit = 0
>     pu_name = <0000000000000000>
>     nau_address = 0
>     default_pool = NO
>     syncpt_support = YES
>     lu_attributes = NONE
>     sscp_id = 0
>     disable = NO
>     sys_name = ""
>     timeout = 60
>     back_level = NO

>     [define_mode]
>     mode_name = SMSNA100
>     description = ""
>     max_neg_sess_lim = 32767
>     plu_mode_session_limit = 12
>     min_conwin_src = 5
>     min_conloser_src = 5
>     auto_act = 5
>     receive_pacing_win = 4
>     max_receive_pacing_win = 0
>     default_ru_size = YES
>     max_ru_size_upp = 1024
>     max_ru_size_low = 0
>     cos_name = #CONNECT

>     [define_directory_entry]
>     resource_name = P390.MVSREGN
>     resource_type = ENCP_RESOURCE
>     description = (Auto defined - remote node)
>     parent_name = <0000000000000000000000000000000000>
>     parent_type = ENCP_RESOURCE

>     [define_directory_entry]
>     resource_name = P390.CICSREGN
>     resource_type = LU_RESOURCE
>     description = ""
>     parent_name = P390.MVSREGN
>     parent_type = ENCP_RESOURCE

>     [define_defaults]
>     description = ""
>     mode_name = SMSNA100
>     implicit_plu_forbidden = NO
>     specific_security_codes = NO
>     limited_timeout = 20

The fields that are most relevant to WebLogic JAM configuration and the VTAM SWNET definitions are listed in the table below.

Table 5-3 SNA Node Configuration Fields

Component Name | Field Within Component | Description
--- | --- | ---
[define_node] | fqcp_name=BEALAN.BEASUN1 | Fully Qualified Control Point name. Must match the NETID and CPNAME as specified in the VTAM SWNET definition.
[define_ethernet_ls] | ls_name=SWNEBEA1 | Link Station name. Must match the PU name as specified in the VTAM SWNET definition.
[define_partner_lu] | plu_alias=CICSREGN | Partner Logical Unit name. Name of CICS region or IMS region that will communicate with your applications. This is used in the logical unit field in a Batch, CICS, or IMS region definition in the WebLogic Administration Console.
[define_local_lu] | lu_alias=LUBEA01 | Logical Unit name. Name of the logical unit specified in your JAM CRM definition in the WebLogic Administration Console, in your session definitions in your CICS region, and in your VTAM SWNET definition.
[define_local_lu] | syncpt_support=YES | Syncpoint Support. Must be set to Yes to enable transactions to work.
[define_mode] | mode_name=SMSNA100 | Mode name. This is used in the mode name field in a CRM link definition in the WebLogic Administration Console.