Tuxedo
0

File Formats, Data Descriptions, MIBs, and System Processes Reference

 Previous Next Contents View as PDF  

DMCONFIG for GWTOPEND(5) Additional Information

Files

The BDMCONFIG environment variable is used to find the BDMCONFIG configuration file.

Example

The following Domains configuration file example is based on Example 1 in the core BEA Tuxedo DMCONFIG(5) reference page. The example has been extended to include a TOP END domain gateway with a single connection to a BEA TOP END system. In this scenario the BEA TOP END system is also running a banking application that offers services needed by users of a BEA Tuxedo application. Conversely, certain BEA Tuxedo services need to be available to the BEA TOP END system for use by modified client programs. A simple queuing example is also included.

The DMCONFIG file for this configuration is shown below. Changes from the original example in the core DMCONFIG(5) file are shown in bold.

# Tuxedo Domains Configuration File for the Central Bank
#
#
*DM_LOCAL
#
DEFAULT: SECURITY = NONE


c01 GWGRP = bankg1
TYPE = TDOMAIN
ACCESSPOINTID = "BA.CENTRAL01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C01"

c02 GWGRP = bankg2
TYPE = OSITP
ACCESSPOINTID = "BA.CENTRAL02"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C02"

c03  GWGRP = bankg3
 TYPE = TOPEND
 ACCESSPOINTID = "CENTRALBKGW"
 DMTLOGDEV = "/usr/apps/bank/DMTLOG"
 DMTLOGNAME = "DMTLG_C03"
 SECURITY = CLEAR

#
*DM_REMOTE
#
b01 TYPE = TDOMAIN
ACCESSPOINTID = "BA.BANK01"

b02 TYPE = TDOMAIN
ACCESSPOINTID = "BA.BANK02"

b03 TYPE = TDOMAIN
ACCESSPOINTID = "BA.BANK03"

b04 TYPE = OSITP
ACCESSPOINTID = "BA.BANK04"

b05  TYPE = TOPEND
 ACCESSPOINTID = "BANK05"

*DM_TDOMAIN
#
# Local network addresses
c01 NWADDR = "//newyork.acme.com:65432" NWDEVICE ="/dev/tcp"

# Remote network addresses
b01 NWADDR = "//192.11.109.5:1025" NWDEVICE = "/dev/tcp"
b02 NWADDR = "//dallas.acme.com:65432" NWDEVICE = "/dev/tcp"
b03 NWADDR = "//192.11.109.156:4244" NWDEVICE = "/dev/tcp"

*DM_OSITP
#
c02 APT = "BA.CENTRAL02"
AEQ = "TUXEDO.R.4.2.1"
AET = "{1.3.15.0.3},{1}"
ACN = "XATMI"
b04 APT = "BA.BANK04"
AEQ = "TUXEDO.R.4.2.1"
AET = "{1.3.15.0.4},{1}"
ACN = "XATMI"

*DM_TOPEND
#
#Local network addresses
c03 NWADDR = "//newyork.acme.com:65434"
TP_SYSTEM = "BANKSYS"
#Remote network addresses
b05 NWADDR = "//sandiego.acme.com:65434"
TP_SYSTEM = "BANKSYS"

*DM_EXPORT
#
#Not available to TOP END, no mapping
open_act ACL = branch LACCESSPOINT = c01
close_act ACL = branch LACCESSPOINT = c01
credit LACCESSPOINT = c01
debit LACCESSPOINT = c01
loan LACCESSPOINT = c02 ACL = loans

#Services exported to TOP END and other domains
balance TYPE=SERVICE TE_PRODUCT="TUX" TE_FUNCTION="BALANCE" LACCESSPOINT=c03

#Queues available to TOP END
qspace TYPE=QSPACE TE_RTQGROUP="TUXQUEUE" TE_RTQNAME="TUXQ" LACCESSPOINT=c03
qname TYPE=QNAME TE_PRODUCT="TUX" TE_FUNCTION="QSERV" LACCESSPOINT=c03

*DM_IMPORT
#
tlr_add LACCESSPOINT = c01 ROUTING = ACCOUNT
tlr_bal LACCESSPOINT = c01 ROUTING = ACCOUNT
tlr_add RACCESSPOINT = b04 LACCESSPOINT = c02 RNAME ="TPSU002"
tlr_bal RACCESSPOINT = b04 LACCESSPOINT = c02 RNAME ="TPSU003"

#
# New TOP END services available to BEA Tuxedo
DEFAULT: LACCESSPOINT = c03 RACCESSPOINT = b05
TYPE = SERVICE TE_PRODUCT = "EBANK"
te_start TE_FUNCTION = "START"
te_end TE_FUNCTION = "END"
te_login TE_FUNCTION = "LOGIN"
te_listacct TE_FUNCTION = "LISTACCT"
te_getpayees TE_FUNCTION = "GETPAYES"
te_elecpay TE_FUNCTION = "ELECPAY"
te_bal TE_FUNCTION = "BAL"
te_transfer TE_FUNCTION = "TRANSFER"
te_withdrawl TE_FUNCTION = "WITHDRAW"
te_deposit TE_FUNCTION = "DEPOSIT"

#
#TOP END RTQ queues available to Tuxedo
DEFAULT: LACCESSPOINT = c03 RACCESSPOINT = b05 TYPE = QSPACE
tuxqspace TE_RTQGROUP = "TEQGROUP" TE_RTQNAME = "TEQNAME"

#
#TOP END services available to Tuxedo via tpenqueue and RTQ
DEFAULT: LACCESSPOINT = c03 RACCESSPOINT = b05 TYPE = QNAME
te_report TE_PRODUCT = "EBANK" TE_FUNCTION = "REPORT"
te_update TE_PRODUCT = "EBANK" TE_FUNCTION = "UPDATE"

*DM_ROUTING
#
ACCOUNT FIELD = branchid BUFTYPE = "VIEW:account"
RANGES = "MIN-1000:b01,1001-3000:b02,*:b03"

*DM_ACCESS_CONTROL
#
branch ACLIST = "b01,b02,b03"
loans ACLIST = b04

Network Addresses

Suppose the local machine on which a TEDG is being run is using TCP/IP addressing and is named backus.company.com. The address of the machine is 155.2.193.18. Further suppose that the port number at which the TEDG should accept requests is 2334. Assume that the port number 2334 has been added to the network services database under the name bankapp-gwaddr. The complete address of this port can be represented in the following ways:

//155.2.193.18:bankapp-gwaddr
//155.2.193.18:2334
//backus.company.com:bankapp-gwaddr
//backus.company.com:2334
0x0002091E9B02C112

The last of these representations is written in hexadecimal format. The string 0002 is the first part of a TCP/IP address. 091E is the port number 2334 translated into a hexadecimal number. The rest of the address (9B02C112) consists of hexadecimal translations of each element of the IP address (155.2.193.12): 9B is translated from 155, 02 is translated from 2, and so on.

See Also

dmadmin(1), dmloadcf(1), dmunloadcf(1), tmboot(1), tmshutdown(1), DMADM(5), GWADM(5), GWTOPEND(5)

BEA TOP END Programmer's Reference Manual: tp_intro(3T), ni_config(4T), nm_config(4T), nm_script(4T)

Administering a BEA Tuxedo Application at Run Time

Setting Up a BEA Tuxedo Application

Programming a BEA Tuxedo ATMI Application Using C

Using the BEA Tuxedo Domains Component

Using the BEA Tuxedo TOP END Domain Gateway with ATMI Applications

 


DM_MIB(5)

Name

DM_MIB—Management Information Base for Domains

Synopsis

#include <fml32.h>
#include <tpadm.h> /* MIB Header, includes DOMAINS */

Domains Terminology Improvements

For BEA Tuxedo release 7.1 or later, the Domains MIB uses improved class and attribute terminology to describe the interaction between local and remote domains. This improved terminology has also been applied to DMCONFIG file syntax.

These terminology improvements eliminate multiple uses of the term "domain" and introduce terms that more clearly describe the actions that occur. For example, the term access point defines an object through which you gain access to another object. Therefore, you access a remote domain through a remote domain access point, and remote domains gain access to a local domain through a local domain access point. The following table reflects the DMCONFIG section name changes that result from eliminating multiple uses of the term "domain."

This DMCONFIG section name. . .

Has changed to. . .

DM_LOCAL_DOMAINS

DM_LOCAL

DM_REMOTE_DOMAINS

DM_REMOTE


 

Within these sections, the following parameter names have changed.

This parameter name. . .

Has changed to. . .

DOMAINID

ACCESSPOINTID

MAXRDOM

MAXACCESSPOINT

MAXRDTRAN

MAXRAPTRAN


 

The equivalent DM_MIB classes for these DMCONFIG sections are T_DM_LOCAL and T_DM_REMOTE, respectively.

In certain configurations, both available services and resources, such as queue spaces and queue names, need to be imported and exported. As such, the DMCONFIG section names DM_LOCAL_SERVICES and DM_REMOTE_SERVICES no longer accurately describe the necessary activity. Replacing these section names with DM_EXPORT and DM_IMPORT, respectively, clearly describes the actions that occur; that is, from the perspective of a single BEA Tuxedo domain, resources are exported from the domain through local access points and imported into the domain through remote domain access points. These DMCONFIG section name changes are shown in the following table.

This DMCONFIG section name. . .

Has changed to. . .

DM_LOCAL_SERVICES

DM_EXPORT

DM_REMOTE_SERVICES

DM_IMPORT


 

Within these sections, the following parameter names have changed.

This parameter name. . .

Has changed to. . .

LDOM

LACCESSPOINT

RDOM

RACCESSPOINT


 

The equivalent DM_MIB classes for these DMCONFIG sections are T_DM_EXPORT and T_DM_IMPORT, respectively.

Backwards Compatibility

The improved Domains terminology introduced in BEA Tuxedo release 7.1 has been applied to the DM_MIB reference page, classes, and error messages, and to the DMCONFIG reference page, section names, parameter names, and error messages.

For backwards compatibility, aliases are provided between the DMCONFIG terminology used prior to BEA Tuxedo 7.1 and the improved Domains MIB terminology. For BEA Tuxedo release 7.1 or later, dmloadcf accepts both versions of the DMCONFIG terminology. dmunloadcf, however, generates a DMCONFIG file that uses the improved domains terminology by default. Use the -c option of dmunloadcf to generate a DMCONFIG file that uses the previous domains terminology.

Description

The Domains MIB defines the set of classes through which a domain may import or export services using domain gateways and domain gateway administrative servers. This reference page assumes the reader is familiar with the BEA Tuxedo System Domains component, which is described in Using the BEA Tuxedo Domains Component.

Use DM_MIB(5) in combination with the generic MIB reference page MIB(5) to format administrative requests and interpret administrative replies.

Requests formatted as described in MIB(5) using classes and attributes described in DM_MIB may be used to request an administrative service using existing ATMI interfaces in an active application. For additional information pertaining to all DM_MIB(5) class definitions, see DM_MIB(5) Additional Information.

DM_MIB(5) consists of the following classes:

Table 11 DM_MIB Classes

Class Name

Attributes

T_DM_ACL

Domain access control list

T_DM_CONNECTION

Connection status between two domains

T_DM_EXPORT

Exported resource

T_DM_IMPORT

Imported resource

T_DM_LOCAL

Local access point

T_DM_OSITP

OSI TP 1.3 specific configuration for an access point

T_DM_OSITPX

OSI TP 4.0 or later specific configuration for an access point

T_DM_PASSWORD

Domain password entry

T_DM_PRINCIPAL_MAP

Principal mapping entry

T_DM_REMOTE

Remote access point

T_DM_RESOURCES

Global Domains configuration information

T_DM_ROUTING

Access point routing criteria

T_DM_RPRINCIPAL

Remote principal entry

T_DM_SNACRM

SNA-CRM-specific configuration for a local access point

T_DM_SNALINK

SNAX-specific configuration for a remote domain access point

T_DM_SNASTACK

SNA stack to be used by a specific SNA CRM

T_DM_TDOMAIN

TDomain-specific configuration for an access point

T_DM_TOPEND

BEA TOP END-specific configuration for an access point

T_DM_TRANSACTION

Transaction entry associated with a local access point


 

Each class description consists of four sections:

Attribute Table Format

The attribute table is a reference guide to the attributes within a class and how they may used by administrators, operators, and general users to interface with an application.

There are five components to each attribute description in an attribute table: name, type, permissions, values, and default. Each of these components is discussed in MIB(5).

TA_FLAGS Values

MIB(5) defines the generic TA_FLAGS attribute which is a long-valued field containing both generic and component MIB-specific flag values. At this time, there are no DM_MIB-specific flag values defined.

FML32 Field Tables

The field tables for the attributes described in this reference page are found in the file udataobj/tpadm relative to the root directory of the BEA Tuxedo System software installed on the system. The directory ${TUXDIR}/udataobj should be included by the application in the colon-separated list specified by the FLDTBLDIR environment variable. The field table name tpadm should be included in the comma-separated list specified by the FIELDTBLS environment variable.

Interoperability

Access to the header files and field tables for this MIB is provided only on BEA Tuxedo release 7.1 sites and later, both native and Workstation. If a release 5.0 or earlier site is active in the application, global information updates ("SET" operations) are not allowed to gateway groups on those sites.

Local information access for release 5.0 and earlier sites is not available. If the class accessed also has global information, only the global information is returned. Otherwise, an error is returned.

Portability

The existing FML32 and ATMI functions necessary to support administrative interaction with BEA Tuxedo System MIBs, as well as the header file and field tables defined in this reference page, are available on all supported native and Workstation platforms.

 

Back to Top Previous Next
Contact e-docsContact BEAwebmasterprivacy