HOME | SEARCH | CONTACT | PDF FILES | WHAT'S NEW
TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX
|
|
|
BEA eLink TCP for CICS 3.0 Information Center |
|
HOME | SEARCH | CONTACT | PDF FILES | WHAT'S NEW |
||
|
TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX |
||
It is the responsibility of the BEA TUXEDO administrator to set up the configuration file, but close coordination with the BEA TUXEDO application developer and the CICS programmer is necessary.
The following subsections describe the BEA eLink for Mainframe TCP for CICS (hereafter referenced as eLink TCP for CICS) Maintenance System. The BEA eLink TCP for CICS Maintenance System is an online CICS application for use in configuring, maintaining, and administering the BEA eLink TCP for CICS gateway. The following topics explain the Maintenance System:
To start the administration system, enter the transaction code as defined to CICS in the installation procedure.
You can access any of the following five groups of menus for maintaining connections, requesters, outbound services, the user connection account, and inbound services. The following table describes how you can use each group of menus.
Each of these topics is discussed in more detail in the following sections.
The Main menu gives you access to all the maintenance screens.
Use the Main menu to access the screens that make up the maintenance system. To move from the Main menu to a sub-menu, enter the appropriate two-character code. The first character in the code denotes the area in which you want to operate and the second character denotes the operation you want to perform on that area.
The following are the codes for the areas of operation:
Menu Navigation
The Main Menu
Usage
The following are the codes for the allowable operations:
Because some operations are not available in all three areas, the following table lists the valid combinations.
You can use the maintenance system screens to view and alter a connection, but not to insert (create) or delete a connection. Connections are created and deleted by BEA eLink TCP for CICS in its normal operation.
The maintenance system will check the two-character selection code that you enter and will display the appropriate screen if the code is valid. If the code you enter is not valid you will receive an error message.
Note:
The maintenance screens use the field name LOGICAL MACHINE NAME. The logical machine name corresponds to a eLink TCP for TUXEDO gateway ID.
The three screens available for maintaining connection instances are labeled Update, Inquiry and Browse. The screens allow you to make an inquiry concerning a specific connection, to browse a list of all connections, or to disable/enable a connection.
A connection instance is an established TCP/IP connection between a remote endpoint and either a Requester or a Handler. For the purposes of BEA eLink TCP for CICS, a remote endpoint is a BEA eLink TCP for TUXEDO Handler executing within a remote BEA TUXEDO domain.
The following function keys are available on various connection screens.
The Connections Screens
PF Keys
ENTER
PF3
PF5
PF7
PF8
Use the UPDATE CONNECTION screen to update a record from the Connection file. When the screen initially displays, the LOGICAL MACHINE NAME and TYPE fields are unprotected. Enter a valid Gateway ID (GWID) and TYPE and press ENTER. The screen redisplays showing the data from the record you specified and the STATUS field is unprotected. The message RECORD READY FOR UPDATE displays. You can now make changes to the record.
Use this screen to inquire about a record from the Connection file. When the screen is initially displayed, the LOGICAL MACHINE NAME and TYPE fields are unprotected. Enter a valid GWID and TYPE and press ENTER. The screen is redisplayed with the data from the record you specified and the LOGICAL MACHINE NAME and TYPE fields are unprotected.
Use this screen to browse records in the Connection file and to select individual records for further processing. If you access this screen from the Main menu, the first record on file is displayed at the top of the screen. If you access this screen from the Connection Update screen or the Inquire screen, the list starts with the key received from that screen.
To select a record for processing enter a valid selection code in the SEL CDE field. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used and all others are ignored. After the selection code is validated and processed, the screen for that process is displayed, and the record key appears in the LOGICAL MACHINE NAME field.
A Requester is responsible for collecting request information to be sent to the remote BEA TUXEDO domain. The Requester establishes network connectivity, transmits data to BEA TUXEDO, and receives data from BEA TUXEDO. Each Requester is responsible for one and only one remote endpoint (or one TCP/IP address/port combination). You can configure more than one Requester to point to the same endpoint, but each Requester worries about only one endpoint.
On the following maintenance screens, each instance of the Requester is given a logical machine ID (LMID). You can give a Requester any unique LMID that is meaningful to you. Every service name is associated with one or more LMIDs. That's how the Requester knows which remote machine is responsible for a particular service.
The following function keys are available on various requester screens.
ENTER
PF3
PF5
PF7
PF8
Use this screen to configure a new Requester by inserting a new record into the Requester file.
When the screen is first displayed, all the fields are unprotected. Type the required data as described in the table below, then press ENTER. After the data is validated and processed, the screen is redisplayed and all the fields are unprotected.
Use this screen to update a record from the Requester file.The fields are the same as the ones on the Requester Insert screen, but on this screen you can change the values.
When the screen is first displayed, the LOGICAL MACHINE NAME field is unprotected. Enter a logical machine name and press ENTER. The screen is redisplayed showing the data from the requested record. The HOST ADDRESS, PORT NUMBER, ACCOUNT ID, PASSWORD, MAX MSG SIZE, and CONNECT RETRY LIMIT fields are unprotected. The following message is displayed: RECORD READY FOR UPDATE.
After the changes you entered are validated and processed, the screen is redisplayed and the LOGICAL MACHINE NAME field is unprotected.
Use this screen to make an inquiry about a record from the Requester file. The screen is initially displayed with the LOGICAL MACHINE NAME field unprotected. Enter the logical machine name and press ENTER. The screen is redisplayed with the data from the requested record and the LOGICAL MACHINE NAME field is unprotected.
Use this screen to delete a record from the Requester file.
Warning: Deleting a Requester record can have serious ramifications. Think carefully before performing this operation. If there are any Service records that point to this GWID, any client calls to those services will be rejected because BEA eLink will not know to which remote machine the request should go.
The screen is initially displayed with the LOGICAL MACHINE NAME field unprotected. Enter the logical machine name and press ENTER. The screen is then redisplayed with the data from the requested record and the LOGICAL MACHINE NAME field is protected. The following message is displayed: TO CONFIRM DELETE, PRESS ENTER AGAIN.
Use this screen to browse a list of the records in the Requester file. Additionally, you can select a record for further processing by entering a valid selection code in the first column of that record's row.
If you access this screen from the Main menu the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the key received from that screen determines which records are displayed.
To choose a record, enter a valid selection code in the SEL CDE field next to that record. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used and the others are ignored.
After the entry in the SEL CDE field is validated and processed, the screen for that process is displayed and the record key appears in the LOGICAL MACHINE NAME field.
A service is a name associated with some component of work. That component of work might be a banking transaction, an airline flight reservation, or an order for a dozen widgets. In BEA TUXEDO, a client program that needs work done makes a "service request." A process called a server performs the work described in the service request on behalf of the client, then returns the results of its efforts back to the client. In MVS this would be referred to as a call to a "black box."
In a CICS application that uses BEA eLink TCP for CICS, a service name is passed in the data area in an EXEC CICS LINK command and the results are returned in that same area. The service screens use the terms "service name" and "remote service name". The service name (e.g., CIC01XXYYZZ) is what the service is known as to your CICS environment and the remote service name (e.g., WITHDRAWL) is what the service is known as to BEA TUXEDO. For simplicity, you can make both names the same, but if naming conventions differ, you can use different names.
BEA eLink TCP for CICS uses a "first available" scheme for locating a remote machine on which to satisfy a service request. You can add more than one entry for each service and use a different GWID for each one. BEA eLink will attempt to satisfy a service request using the first record for a particular service. If that remote endpoint is busy or disabled, BEA eLink will try the next LMID configured for that service until all configured LMIDs are exhausted.
The following function keys are available on various outbound service screens.
ENTER
PF3
PF5
PF7
PF8
Use this screen to insert a record into the service name file. The screen is first displayed with all fields unprotected. Enter the required data in the appropriate fields and press ENTER. After the data is validated and processed, the screen is redisplayed and all the fields are unprotected.
Use this screen to update a record from the service name file. When the screen is first displayed, the SERVICE NAME and LOGICAL MACHINE NAME fields are unprotected. Enter the service name and logical machine name, and press ENTER. The screen is then redisplayed with the data from the requested record and the REMOTE SERVICE NAME and SERVICE TIMEOUT(SEC) fields are unprotected.The following message is displayed: RECORD READY FOR UPDATE.
After the changes are validated and processed, the screen is redisplayed and the SERVICE NAME and LOGICAL MACHINE NAME fields are unprotected.
Use this screen to make an inquiry about a record from the Service Name file. The screen is initially displayed with the SERVICE NAME and LOGICAL MACHINE NAME fields unprotected. Enter the service name and logical machine name and press ENTER. The screen is redisplayed with the data from the requested record and the SERVICE NAME and LOGICAL MACHINE NAME fields are unprotected.
Use this screen to delete records from the service name file. The screen is initially displayed with the SERVICE NAME and LOGICAL MACHINE NAME fields unprotected. Type the service name and logical machine name and press ENTER. The screen is redisplayed with the data from the record requested and all the fields protected.
The following message is displayed: TO CONFIRM DELETE, PRESS ENTER: AGAIN. After you press enter to confirm the deletion, the screen is redisplayed and the SERVICE NAME and LOGICAL MACHINE NAME fields are unprotected.
Use this screen to browse the records in the service name file. If you access this screen from the Main menu the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the list starts with the record key received from that screen.
To select a record for processing, enter a valid selection code. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used, and the others are ignored. After the selection code is validated and processed, the screen for that process is displayed and the record key appears in the SERVICE NAME and LOGICAL MACHINE NAME fields.
A Handler is responsible for receiving service requests from the remote BEA TUXEDO domain. The User Connection Account screens allow for dynamic manipulation of the configuration used by all Handler programs in the system.
Note: To apply changes that have been made to the User Connection Account file, you must restart the connection.
The following function keys are available on various user account screens.
ENTER
PF3
Use this screen to update a record from the account file. If a record does not exist, one will be inserted into the account file. When the screen first displays, all fields are unprotected. After the changes are validated and processed, the screen is redisplayed.
Use this screen to make an inquiry about a record from the account file. The screen is displayed with the data from the requested record and all fields are protected.
A service is a name associated with some component of work. That component of work can be a banking transaction, an airline flight reservation, or an order for a dozen widgets. In BEA TUXEDO, a client program that needs work done makes a service request. A server performs the work described in the service request on behalf of the client, then returns the results of its efforts back to the client. In MVS this would be referred to as a call to a "black box."
The service screens use the terms LOCAL SERVICE NAME and REMOTE SERVICE NAME. The LOCAL SERVICE NAME (e.g., CIC01XXYYZZ) is what the service is known as to your CICS environment and the REMOTE SERVICE NAME (e.g., WITHDRAWL) is what the service is known as to BEA TUXEDO. For simplicity, you can make both names the same; however, different names can be used. Changes to the inbound service file will only be picked up when the connection is restarted.
The following function keys are available on various inbound service screens.
ENTER
PF3
PF5
PF7
PF8
Use this screen to insert a record into the service name file. The screen is first displayed with all fields unprotected. Enter the required data in the following fields and press ENTER. After the data is validated and processed, the screen is redisplayed and all the fields are unprotected.
Use this screen to update a record in the inbound service name file. The screen is first displayed with the REMOTE SERVICE NAME field unprotected. Enter the remote service name and press ENTER. The screen is redisplayed with the data from the requested record and the LOCAL SERVICE NAME, TRANSACTION NAME, MAX MESSAGE SIZE, and SECURITY fields unprotected. The following message displays: RECORD READY FOR UPDATE.
After the changes are validated and processed, the screen is redisplayed and the REMOTE SERVICE NAME field is unprotected.
Use this screen to inquire about a record in the inbound service name file. The screen is first displayed with the REMOTE SERVICE NAME field unprotected. Enter the remote service name and press ENTER. The screen is redisplayed with the data from the requested record and the REMOTE SERVICE NAME field unprotected.
Use this screen to delete a record in the inbound service name file. The screen is first displayed with the REMOTE SERVICE NAME field unprotected. Enter the remote service name and press ENTER. The screen is redisplayed with the data from the record requested and all fields protected. The following message displays: TO CONFIRM DELETE, PRESS ENTER AGAIN. After you press ENTER to confirm the deletion, the screen is redisplayed and the REMOTE SERVICE NAME field is unprotected.
Use this screen to browse the records in the inbound service name file. If you access this screen from the Main menu the first record on file is displayed at the top of the screen. If you access this screen from the Insert, Update, Inquire, or Delete screens, the list starts with the record key received from that screen.
To select a record for processing, enter a valid selection code. For example, to make an inquiry about a record, enter "3". If you enter more than one selection code, the first one is used, and the others are ignored. After the selection code is validated and processed, the screen for that process is displayed and the record key appears in the REMOTE SERVICE NAME field.
The eLink TCP product supports a security feature that allows a requester from BEA TUXEDO services to pass a USERID requirement through the CICS server interfaces for verification through a third-party security package.
Figure 3-1 depicts the process flow for security verifications from eLink for Mainframe TCP for CICS on UNIX to a mainframe.
Figure 3-1 Security Checking for UNIX to Mainframe Transactions
tpusr, tpgrp, and tpacl files.
Note:
The userid must match in the TUXEDO and the mainframe environments or a security violation occurs.
Figure 3-2 depicts the process flow for security verifications from a mainframe to eLink for Mainframe TCP for CICS on UNIX.
Figure 3-2 Security Checking for Mainframe to UNIX Transactions
The eLink TCP for CICS product supports enhanced security. This interface allows a requester from BEA TUXEDO services to pass a USERID through the CICS server interface for authorization through your security package.
Complete the following tasks to enable the security feature for each connection:
When SECURITY=Y, eLink TCP for CICS will verify that the ACCOUNT and PASSWORD values from the User Connection Account match the RMTACCT and PASSWORD values in the eLink TCP for TUXEDO GWICONFIG file *FOREIGN section. If these values do not match and SECURITY=Y, a security error occurs.
If SECURITY=N, the gateway allows a connection without any verification.
Complete the following tasks to enable the security feature for each inbound service:
Complete the following tasks to enable the security feature for each outbound connection:
Verify that the parameter values for ACCOUNT and PASSWORD in the Requester screen match the RMTACCT and PASSWORD values in the *FOREIGN section of the eLink TCP for TUXEDO GWICONFIG file.
When SECURITY=Y, the requester program sends the ACCOUNT and PASSWORD to the remote UNIX system on connection initiation. When SECURITY=N, the gateway attempts to make a connection without any verification.
Complete the following tasks to enable the security feature for each outbound connection:
Verify that the parameter values for ACCOUNT and PASSWORD in the Requester screen match the ACCOUNT and PASSWORD values in the User Connection Account screen.
When SECURITY=Y, the requester program sends the ACCOUNT and PASSWORD to the remote CICS system on connection initiation. When SECURITY=N, the gateway attempts to make a connection without any verification.
Complete the following tasks to enable the security feature for each outbound connection:
Verify that the parameter values for ACCOUNT and PASSWORD in the Requester screen match the ACCOUNT and PASSWORD values in the GATEWAY TYPE=REMOTE statement.
When SECURITY=Y, the requester program sends the ACCOUNT and PASSWORD to the remote IMS system on connection initiation. When SECURITY=N, the gateway attempts to make a connection without any verification.
Complete the following tasks to enable the security feature for each outbound service:
BEA TUXEDO has a set of tmadmin and dmadmin commands for the administration of the eLink TCP gateways. For detailed information about these commands, refer to the BEA TUXEDO Administrator's Guide and the BEA TUXEDO Domain User Guide.