![]() |
![]() |
|
|
Understanding the UDMCONFIG File
Before you configure BEA eLink OSI TP and set up the gateway configuration, it is helpful to understand the UDMCONFIG file.
This section covers the following topics:
For detailed instructions on how to configure eLink OSI TP by modifying the UDMCONFIG file, refer to Configuring BEA eLink OSI TP.
Overview of the UDMCONFIG File
The configuration specified in the UDMCONFIG file controls much of the operation of the eLink OSI TP gateway. A sample of this file is provided in the installation directory of your eLink OSI TP product software.
UDMCONFIG is the ASCII version of a Tuxedo System/Domain domain configuration file. The UDMCONFIG file is parsed and loaded into two binary versions by the udmloadcf utility. The binary configuration files, called the BDMCONFIG and BUDMCONFIG files, contain information used by domain gateways to initialize the context required for communications with other domains. In its monitoring activity, dmadmin uses the binary file (or a copy of it). There is one BDMCONFIG file for each Tuxedo System/Domain application that uses the /Domain feature. Refer to Processing a Configuration File with the Udmloadcf Utility for more information about the binary configuration files.
A UDMCONFIG file, and its binary BDMCONFIG counterpart, are analogous to the UBBCONFIG and TUXCONFIG files of a non-/Domain System/T application. The UDMCONFIG file extends the definition of a non-/Domain System/T application so that the application becomes a domain.
OSI TP Application Addresses Used in the UDMCONFIG File
OSI TP application address information is used for several parameters in the UDMCONFIG file. The address of a Tuxedo application using OSI TP consists of a collection of the names of each of the components described in the following table. These names must be coordinated with the remote domain OSI TP implementation.
Table 3-1 OSI TP Application Components
Creating an Application Entity Title The Application Entity Title equals the APT (application process title) plus the AEQ (application entity qualifier). Each OSI TP node in your network must have a unique AET. If your site is participating in a global OSI network, you need to contact the OSI registration authority for a valid OSI Object-ID, otherwise, create your own unique AET as described below. If your site is in a closed network, create an Object ID with at least 3 "arcs" as shown in Figure 3-1. Each arc of the dotted integer (1.3.192.59.192.213 in the example below) represents an identifier for the Object ID. A valid OSI TP Object ID has either 0 or 1 for the first arc, and 0, 1, 2, 3 for the second arc. It is recommended to use 1.3 (IP address) for the first and second arcs respectively. Figure 3-1 Example of an Application Entity Title
UDMCONFIG File Format
The format of a domain configuration file is as follows:
Caution: Enter all parameters on separate lines. The NWADDR parameter is the only exception; it may list multiple network address values in a single line.
DEFAULT: { KEYWORD1 = value1 { KEYWORD2 = value2 {...}}}
The values set on this line remain in effect until reset by another DEFAULT: line, or until the end of the section is reached. These values can also be overridden by specifying another value for the parameter on a non-DEFAULT: line. The override parameter setting is valid for that line only; lines that follow revert to the default setting. If DEFAULT: appears on a line by itself, all previously set defaults are cleared and their values revert to the system defaults.
UDMCONFIG File Sections
The UDMCONFIG file consists of the following sections and parameters that define new gateway configurations.
Note: The DM_LOCAL_DOMAINS section must precede the DM_REMOTE_DOMAINS section.
Following is a sample configuration file and detailed descriptions of the UDMCONFIG file sections and the parameters applicable to each section.
Sample Configuration File
Listing 3-1 Sample UDMCONFIG File
*DM_LOCAL_DOMAINS
dalnt8
GWGRP = OSIGRP
TYPE = OSITPX
DOMAINID = "dalnt8"
BLOCKTIME = 30
DMTLOGDEV = "D:\tuxedo\log\DMLOG"
SECURITY = DM_PW # turns link layer security on
< BR >
*DM_REMOTE_DOMAINS
dal2200 TYPE=OSITPX DOMAINID="dal2200"
openti TYPE=OSITPX DOMAINID="openti"
icl2 TYPE=OSITPX DOMAINID="icl2"
aseries1 TYPE=OSITPX DOMAINID="aseries1"
*DM_OSITPX
dalnt8
AET="{1.3.132.61.146},{3}"
TAILOR_PATH="d:\tuxedo\configs\tailor.txt"
NWADDR="//dalnt8:102"
DNS_RESOLUTION=STARTUP # this is the default
dal2200
AET="{1.3.132.61.46},{3}"
XATMI_ENCODING="OLTP_TM2200"
NWADDR="132.61.146.3";"132.61.147.1" #redundant IP addresses
T_SEL="OSITP"
openti
AET="{1.3.122.62.103},{209}"
NWADDR="122.62.103.209:2001"
OPTIONS=SECURITY_SUPPORTED
icl2
AET="{1.3.142.60.203},{4}"
NWADDR="142.60.203.4"
T_SEL="ICLTP"
S_SEL="SSEL"
P_SEL="PSEL"
aseries1
AET="{1.3.123.55.222},{51}"
NWADDR="123.55.222.51"
XATMI_ENCODING="PRELIMINARY"
T_SEL="0x5453"
S_SEL="0x3F5C3F"
*DM_ACCESS_CONTROL
mylist ACLIST = dalnt8, dal2200
*DM_LOCAL_SERVICES
TOUPPERF
INRECTYPE="VIEW:view10"
OUTBUFTYPE="FML:"
COUPLING=LOOSE #this is the default
TOUPPERF32
INRECTYPE="VIEW:view10a"
OUTBUFTYPE="FML32:"
COUPLING=TIGHT
TOUPPERV
INBUFTYPE="X_C_TYPE:v10"
INRECTYPE="VIEW:upper"
COUPLING=LOOSE
TOUPPERC OUTRECTYPE="X_OCTET" OUTBUFTYPE="CARRAY"
INRECTYPE="X_OCTET"
COUPLING=TIGHT
TOUPPERS OUTRECTYPE="X_OCTET" OUTBUFTYPE="STRING"
INRECTYPE="X_OCTET"
TOUPPERX OUTRECTYPE="STRING" OUTBUFTYPE="STRING"
INRECTYPE="X_OCTET"
*DM_REMOTE_SERVICES
DEFAULT: TRANTIME=300
ECHOXOCT RNAME="ECHOSRVR" OUTBUFTYPE="X_COMMON:ECHOVIEW" RDOM=dal2200 LDOM=dalnt8
ECHOXCOM RNAME="ECHOSRVR" RDOM=openti LDOM=dalnt8 AUTOPREPARE=Y
ECHOXCTYPE RNAME="ECHOSRVR"
INBUFTYPE="X_C_TYPE:ECHOVIEW"
INRECTYPE="X_COMMON:ECHOVIEW"
OUTBUFTYPE="X_C_TYPE:ECHOVIEW"
OUTRECTYPE="X_COMMON:ECHOVIEW"
RDOM=aseries1
LDOM=dalnt8
CONV=Y
ECHOVIEW RNAME="ECHOSRVR"
INBUFTYPE="VIEW:ECHOVIEW"
INRECTYPE="X_COMMON:ECHOVIEW"
OUTBUFTYPE="VIEW:ECHOVIEW"
OUTRECTYPE="X_COMMON:ECHOVIEW"
RDOM=icl2
LDOM=dalnt8
REM_TPSUT="tpmvs"
*DM_ROUTING
ACCOUNT FIELD = branchid BUFTYPE = "View:account"
RANGE = "MIN - 1000:aseries1, 1001-3000:openti, *:dal2200"
DM_LOCAL_DOMAINS Section
This section identifies local domains and their associated gateway groups. The section must have an entry for each gateway group (Local Domain). Each entry specifies the parameters required for the domain gateway processes running in that group.
Format
DM_LOCAL_DOMAINS entries have the following format. LDOM required parameters [optional parameters] where LDOM is an identifier value used to name each local domain. LDOM must be unique within a particular configuration. As described in the
DM_LOCAL_SERVICES section, LDOM is the
identifier that connects local services with a particular gateway
group. Valid Parameters Following is a list of valid parameters for the DM_LOCAL_DOMAINS section:
Parameter Definitions Following is more detailed information about each of the
DM_LOCAL_DOMAINS section
parameters:
Note: This parameter must appear AFTER the TYPE=OSITPX parameter.
DM_REMOTE_DOMAINS Section
This section identifies the known set of remote domains and their characteristics.
Format
DM_REMOTE_DOMAINS entries have the following format:
RDOM required parameters
where
RDOM is an identifier value used to identify each remote domain known to this configuration.
RDOM must be unique within the configuration.
Valid Parameters
Following is a list of valid parameters for the DM_REMOTE_DOMAINS section:
Parameter |
Required/Optional |
Description |
---|---|---|
DOMAINID |
Required |
ID of remote domain. |
TYPE |
Required |
Class of remote domain |
Parameter Definitions Following is more detailed information about each of the
DM_REMOTE_DOMAINS section
parameters:
DM_OSITPX Section
This section defines the addressing information required by domains of type OSITPX. This section should have at least one entry per gateway group (local domain), and at least one entry per remote domain of type OSITPX. The bridged configuration can have multiple gateways in a local domain.
Format
DM_OSITPX entries have the following format:
DOM required parameters [optional parameters]
where
DOM is an identifier value used to identify a local domain (LDOM) or a remote domain (RDOM) in the DM_LOCAL_DOMAINS section or in the DM_REMOTE_DOMAINS section.
The DOM identifier must match a previously defined LDOM in the DM_LOCAL_DOMAINS sections or RDOM in the DM_REMOTE_DOMAINS section.
Valid Parameters
Following is a list of valid parameters for the DM_OSITPX section:
Parameter Definitions Following is more detailed information about each of the
DM_OSITPX section
parameters:
Note: The braces are part of the syntax and must be included within the quotes.
DM_ACCESS_CONTROL Section
This section specifies the access control lists used by local domain.
Format
DM_ACCESS_CONTROL entries have the following format:
ACL_NAME required parameters
where
ACL_NAME is a (identifier) name used to identify a particular access control list; it must be 15 characters or less in length.
Following is a list of valid parameters for the DM_ACCESS_CONTROL section:
Parameter |
Required/Optional |
Description |
---|---|---|
ACLIST |
Required |
List of remote domain names |
Parameter Definitions Following is more detailed information about the DM_ACCESS_CONTROL section
parameter:
DM_LOCAL_SERVICES Section
This section provides information on the services exported by each local domain. This section is optional and if it is not specified then all local domains defined in the DM_LOCAL_DOMAINS section accept requests to all of the services advertised by the Tuxedo System/Domain application. If this section is defined then it should be used to restrict the set of local services that can be requested from a remote domain.
Format
DM_LOCAL_SERVICES entries have the following format:
service [optional parameters]
where
service is the (identifier) local name of the exported service, and it must be 15 characters or fewer in length.
This name corresponds to a name advertised by one or more servers running with the local Tuxedo System/Domain application. Notice that exported services inherit the default or special properties specified for the service in an entry in the SERVICES section of the TUXCONFIG file. Some of these parameters are: LOAD, PRIO, AUTOTRAN, ROUTING, BUFTYPE, and TRANTIME.
Valid Parameters
Following is a list of valid parameters for the DM_LOCAL_SEVICES section:
Parameter Definitions Following is more detailed information about the DM_LOCAL_SEVICES section
parameters:
DM_REMOTE_SERVICES Section
This section provides information on services "imported" and available on remote domains.
Format
DM_REMOTE_SERVICES entries have the following format.
service [optional parameters]
where
service is the (identifier) name used by the local Tuxedo System/Domain application for a particular remote service.
Remote services are associated with a particular remote domain.
Valid Parameters
Following is a list of valid parameters for the DM_REMOTE_SERVICES section:
Parameter Definitions Following is more detailed information about the DM_REMOTE_SERVICES section
parameters:
DM_ROUTING Section
This section provides information for data-dependent routing of service requests using FML, VIEW, X_C_TYPE, and X_COMMON typed buffers.
Format
DM_ROUTING entries have the following format:
CRITERION_NAME required parameters
where
CRITERION_NAME is the (identifier) name of the routing entry that was specified on the services entry. CRITERION_NAME must be 15 characters or less in length.
Valid Parameters
Following is a list of valid parameters for the DM_ROUTING section:
Parameter Definitions Following is more detailed information about the DM_ROUTING section parameters:
![]() |
![]() |
![]() |
|
Copyright
© 2000 BEA Systems, Inc. All rights reserved. |