Gateway User Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Get Adobe Reader |
The BEA Tuxedo Mainframe Adapter for TCP Gateway (hereafter referenced as TMA TCP Gateway) product is a domains-based gateway connectivity feature that allows application programs on BEA Tuxedo systems to perform non-transactional tasks with application programs in other OLTP systems that support TMA TCP Gateway gateways. These include:
The TMA TCP Gateway gateway is designed to provide transparent access to services that reside outside a BEA Tuxedo region. In addition, TMA TCP Gateway can provide remote application programs with access to local services.
This document provides information about the following topics:
A BEA Tuxedo region consists of client and server programs that operate across a network of BEA Tuxedo systems or compatible systems. Any client program can request services that are offered by any server program running on any computer in the region. The location of server programs is kept transparent through use of a directory that maps services to servers.
As Figure 1-1 shows, TMA TCP Gateway extends this transparent access by sending requests to and receiving requests from remote regions and systems through TCP/IP network software.
Figure 1-1 Routing Service Calls through BEA TMA TCP Gateway
As Figure 1-1 illustrates, inside a single region, TMA TCP Gateway fits between the BEA Tuxedo software and TCP/IP.
The TMA TCP Gateway product is implemented as a Tuxedo domain gateway. It accepts standard BEA Tuxedo service requests and returns standard replies.
One TMA TCP Gateway gateway connects to multiple communications targets, also referred to as gateways. Each communications target, or gateway, is a unique network endpoint.
Although remote systems are identified in the TMA TCP Gateway configuration, they remain unknown to BEA Tuxedo software. For example, remote systems that are accessible through TMA TCP Gateway are not identified in the MACHINES
section of the UBBCONFIG
file.
The TMA TCP Gateway gateway maintains its own control information in shared memory, in much the same way that BEA Tuxedo software itself maintains the Bulletin Board. Although TMA TCP Gateway accesses the BEA Tuxedo Bulletin Board, BEA Tuxedo does not access TMA TCP Gateway control information.
Operational considerations are permanent limitations on using a feature. The following operational considerations apply to TMA TCP Gateway:
Note: In the following discussion, a local application program is one that resides within the immediate BEA Tuxedo administrative region. A remote application program is one that resides outside the immediate BEA Tuxedo administrative region.
tpsprio()
function set the priority where service requests are dequeued by TMA TCP Gateway. This process does not affect any prioritization on the remote system.tpbroadcast()
function to send unsolicited messages to remote client programs (and the reverse).tpbroadcast()
or tpnotify()
functions to send messages to remote client programs (and the reverse).tpgprio()
function to determine the priority of a remote service, the priority of a local TMA TCP Gateway requester is returned.For background information about these operational considerations, see Understanding How BEA TMA TCP Gateway Works.
The following functionality is available in this version of TMA TCP.
The TMA TCP product has a domains-based architecture supporting bidirectional communications, request/response support, and support for MVS Open Transaction Manager Access (OTMA) interfaces.
The TMA TCP Gateway product grants access to BEA Tuxedo services based on a user name that the remote gateway supplies.
The TMA TCP for CICS product can initiate transactions or link to programs. BEA Tuxedo security provides the user ID value to the TMA TCP product to test for appropriate security prior to initiating the transactions.
The TMA TCP for IMS product has an OTMA interface that supports enhanced security. This interface allows a BEA Tuxedo requester to pass a user ID through the OTMA server interface for authorization through a third-party security package, such as RACF.
The TMA TCP Gateway allows multiple requests to process simultaneously over a single connection. This feature is known as connection multiplexing. Two connecting gateways determine a multiplex count that is acceptable to both sides at connection time. After establishing the connection, clients can send multiple requests (up to the number in the multiplex count) to the server gateway. Connection multiplexing allows for more efficient use of sockets and other system resources by the TMA TCP gateways.
Note: Each connection is one-directional, which means clients on opposing platforms cannot use the same connection to communicate with remote servers.
The TMA TCP product supports domain name server (DNS) resolution of IP addresses. This support allows you to change the IP address at the Domain Name Server to implement address changes without reconfiguring the TMA TCP gateway.
The TMA TCP product consists of a single component, the GWIDOMAIN
gateway. This gateway is responsible for the mediating both incoming and outgoing requests. It also maintains connections with all remote gateways.
The TMA TCP Gateway product preserves the high degree of location transparency that BEA Tuxedo software provides. In fact, in virtually all cases, programmers do not need to know that particular services are provided by remote systems.
The TMA TCP Gateway product supports the main BEA Tuxedo communication paradigm: request/reply communications (either synchronous or asynchronous).
All BEA Tuxedo buffer types can be employed for data exchange. These include:
Each of the three X/Open buffer types is equivalent to a BEA Tuxedo ATMI buffer type. The following information provides these equivalencies.
X_OCTET
is equivalent to CARRAY
X_C_TYPE
is equivalent to VIEW
X_COMMON
is equivalent to VIEW
, but represents only the subset of field types that are common to both the C and COBOL languagesIn some circumstances, you must convert typed buffers to formats that are acceptable to target systems. The standard BEA Tuxedo system VIEW
definition mechanism is employed for this purpose.
VIEW
definitions make it possible to map input data and output data between different programming environments (such as C and COBOL). They also enable TMA TCP Gateway to convert data representations automatically between different systems.
VIEW
definitions can be created by programmers or system administrators. See the Configuring BEA TMA TCP Gateway for Data Mapping section for details. For more detailed information about programming considerations, see the Understanding How BEA TMA TCP Gateway Workssection.
When communicating with systems or regions that do not support FML buffers directly, the TMA TCP Gateway can convert FML buffers to or from user-defined record layouts in a manner transparent to the FML application. Thus, once a VIEW
definition that describes the remote application's record layout is created, it can be used to convert the record to or from an FML buffer. The GWICONFIG
(TMA TCP Gateway configuration file) and DMCONFIG
files contain VIEW
specifications as part of the service description.
Through this conversion between ATMI buffers and record structures, TMA TCP Gateway supports sending fielded buffers containing FML data between regions. The TMA TCP Gateway software converts the data from FML buffers to user-defined records using the VIEW
definitions and field descriptions at the originating region.
You can use an alternate data mapping tool to map FML buffers to formats that mainframe applications can use. For more information about how to configure TMA TCP Gateway to work with an alternate data mapping tool, see the Configuring BEA TMA TCP Gateway for Data Mapping and Configuring BEA TMA TCP Gateway sections.
The TMA TCP Gateway administration tools and features are thoroughly integrated with BEA Tuxedo administration tools and features. Here are some specific examples:
DMCONFIG
) specifies how local BEA Tuxedo service names are mapped to remote service names. Also, the GWICONFIG
file identifies VIEW
definitions that TMA TCP Gateway uses to convert and translate input and output data.For more detailed information about configuring TMA TCP Gateway, see the Configuring BEA TMA TCP Gateway section. For detailed information about commands for administering TMA TCP Gateway,see the BEA Tuxedo Administrator's Guide and the BEA Tuxedo Domain User Guide.
![]() ![]() |
![]() |
![]() |