[Top] [Previous] [Next] [End of Book]

# Chapter 3 . Configuring BEA Connect OSI TP

Once the installation of Connect OSI TP is complete, you will want to configure Connect OSI TP. The proper configuration of Connect OSI TP sets up the gateway configuration. Configuring the Connect OSI TP gateway includes:

- Defining new gateway configurations or modifying existing gateway configuration.

- Defining the Connect OSI TP administrative and gateway servers to the BEA TUXEDO system.

- Verifying the configuration of Connect OSI TP.

## Defining New Gateway Configurations

To define a new gateway configuration, complete the following steps.

1. Edit the DMCONFIG file.

2. Process the DMCONFIG file by running the `dmloadcf` utility.

### Editing the DMCONFIG File

The configuration specified in the DMCONFIG file controls much of the operation of the BEA Connect OSI TP gateway. A sample of this file is provided in the installation directory of your BEA Connect OSI TP product software.

DMCONFIG is the ASCII version of a TUXEDO System/Domain domain configuration file. The DMCONFIG file is parsed and loaded into a binary version by the `dmloadcf` utility. The binary configuration file, called the BDMCONFIG file, contains information used by domain gateways to initialize the context required for communications with other domains `dmadmin` uses the binary file (or a copy of it) in its monitoring activity. There will be one BDMCONFIG file for each TUXEDO System/Domain application that uses the /Domain feature.

A DMCONFIG file, and its binary BDMCONFIG counterpart, are analogous to the UBBCONFIG and TUXCONFIG files of a non-/Domain System/T application. The DMCONFIG file extends the definition of a non-/Domain System/T application so that the application becomes a domain.

#### Prerequisites

The BEA Connect OSI TP product software must be installed and accessible to your text editor. You must have file permission to access the `install` directory and modify the sample DMCONFIG file. In addition, the following prerequisites must be met to successfully complete the editing procedure:

- The `$TUXDIR/udataobj/DMTYPE` file defining the valid domain types must exist. Refer to the Appendix B, "Reference Pages," for information on the `dmloadcf` command.

- The effective user identifier of the person running `dmloadcf` must match the UID in the RESOURCES section of the TUXCONFIG file. Refer to the `dmloadcf` reference page in Appendix B, "Reference Pages".

#### Configuration File Format

The format of a domain configuration file is as follows:

- The file is made up of eight possible specification sections. Lines beginning with an asterisk (*) indicate the beginning of a specification section. Each such line contains the name of the section immediately following the *. Allowable section names are: DM_LOCAL_DOMAINS, DM_REMOTE_DOMAINS, DM_LOCAL_SERVICES, DM_REMOTE_SERVICES, DM_ROUTING, DM_ACCESS_CONTROL and DM_domtype, where domtype is OSITP or TDOMAIN. The DM_LOCAL_DOMAINS section must precede the DM_REMOTE_DOMAINS section.

- Parameters are generally specified by: KEYWORD = value. This sets KEYWORD to value. Valid keywords are described in the following sections. KEYWORDs are reserved; they cannot be used as values unless they are quoted.

- Lines beginning with the reserved word, DEFAULT:, contain parameter specifications that apply to any lines that follow them in the section in which they appear. Default specifications can be used in all sections. They can appear more than once in the same section. The format for these lines is:

  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 on non-DEFAULT: lines by placing the optional parameter setting on the line. If on a non-DEFAULT: line, the 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.

- If a value is numeric, standard C notation is used to denote the base (that is, 0x prefix for base 16 (hexadecimal), 0 prefix for base 8 (octal), and no prefix for base 10 (decimal)). The range of values acceptable for a numeric parameter are given under the description of that parameter.

- If a value is an identifier, standard C rules are used. An identifier must start with an alphabetic character or underscore and contain only alphanumeric characters or underscores. The maximum allowable length of an identifier is 30 (not including the terminating null). An identifier cannot be the same as any KEYWORD.

- A value that is neither an integer number nor an identifier must be enclosed in double quotes. Certain special characters can be escaped inside a string using a backslash. ``\\'' translates to a single backslash. ``\"'' translates to a double quote. ``\n'' translates to a new line. ``\t'' translates to a tab. ``\f'' translates to a form feed. ``\x'' (where 'x' is any character other than one of the previously mentioned special characters) translates to 'x'.

- Input fields are separated by at least one space (or tab) character.

- "#" introduces a comment. A new line ends a comment.

- Blank lines and comments are ignored.

- Comments can be freely attached to the end of any line.

- Lines are continued by placing at least one tab after the new line. Comments cannot be continued.

#### Editing Procedure

The following steps will assist you in editing the DMCONFIG file.

Note: Because BEA Connect OSI TP may be installed on a variety of platforms, the procedures in this section make only general references to command entries. Many steps show UNIX command examples. Be sure to use the proper syntax for your platform when making command-line entries.

1. Enter the platform command to gain access to the `install` directory, for example:

    cd install

2. Gain access to the `examples` subdirectory, for example:

    cd examples

3. Enter the command to invoke the text editor and gain access to the DMCONFIG file, for example:

    edit DMCONFIG

4. Edit the DMCONFIG file as necessary. Refer to the parameter descriptions in this section for details about defining your BEA Connect OSI TP configuration.

5. When editing is complete, save and exit the DMCONFIG file. For example, type the following command.

       $exit

6. Load the file with the `dmloadcf` utility. This parses and loads a binary BDMCONFIG configuration file (refer to `dmloadcf` reference page in Appendix B, "Reference Pages").

### DMCONFIG Parameters

The following paragraphs describe the significant parameters within specific sections of the DMCONFIG file that define new gateway configurations.

#### *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 you will see in the description of the *DM_LOCAL_SERVICES section, LDOM is the identifier that connects local services with a particular gateway group.

##### Required Parameters

The following parameters are required.

GWGRP = identifier
  specifies the name of the gateway server group (the name provided in the TUXCONFIG file) representing this local domain. There is a one-to-one relationship between a DOMAINID and the name of the gateway server group, that is, each GWGRP must have its own, unique DOMAINID.

TYPE = identifier
  is used for grouping local domain into classes. TYPE can be set to one of the following values: TDOMAIN or OSITP. The TDOMAIN value indicates that this local domain can only communicate with another TUXEDO System/Domain. The OSITP value indicates that this local domain communicates with another TP Domain via the OSI-TP protocol. Domain types must be defined in the $TUXDIR/udataobj/DMTYPE file.

DOMAINID = string
  is used to identify the local domain. DOMAINID must be unique across both local and remote domains. The value of string can be a sequence of characters (for example, "BA.CENTRAL01"), or a sequence of hexadecimal digits preceded by "0x" (for example, "0x0002FF98C0000B9D6"). DOMAINID must be 32 octets or fewer in length. If the value is a string, it must be 31 characters or fewer.

DMTLOGDEV = string
  specifies the TUXEDO file system that contains the Domain transaction log (DMTLOG) for this machine. The DMTLOG is stored as a TUXEDO System VTOC table on the device. If this parameter is not specified, the domain gateway group is not allowed to process requests in transaction mode. Local domains running on the same machine can share the same DMTLOGDEV file system, but each local domain must have its own log (a table in the DMTLOGDEV) named as specified by the DMTLOGNAME keyword.

##### Optional Parameters

The following optional parameters describe resources and limits used in the operation of domain gateways:

AUDITLOG = string
  specifies the name of the audit log file for this local domain. The audit log feature is activated from the dmadmin command and records all the operations within this local domain. If the audit log feature is active and this parameter is not specified, the file DMmmddyy.LOG (where mm=month, dd=day, and yy=year) is created in the directory specified by the $APPDIR environment variable or the APPDIR keyword of the *MACHINES section of the TUXCONFIG file.

BLOCKTIME = numeric
  specifies the maximum wait time allowed for a blocking call. The value sets a multiplier of the SCANUNIT parameters specified in the TUXCONFIG file. The value SCANUNIT * BLOCKTIME must be greater than or equal to SCANUNIT and less than 32,768 seconds. If this parameter is not specified, the default value is set to the value of the BLOCKTIME parameter specified in the TUXCONFIG file. A timeout always implies a failure of the affected request. Notice that the timeout specified for transactions in the TUXCONFIG will always be used when the request is issued within a transaction.

DMTLOGNAME = identifier
  specifies the name of the domain transaction log for this domain. This name must be unique when the same DMTLOGDEV is used for several local domains. If not specified, the default is the string ``DMTLOG''. The name must be 30 characters or less.

DMTLOGSIZE = numeric
  specifies the numeric size, in pages, of the Domain transaction log for this machine. It must be greater than 0 and less than the amount of available space on the TUXEDO file system. If not specified, the default is 100 pages.

MAXDATALEN = numeric
  specifies a maximum amount of data (in bytes) that can be sent to or from any services advertised by this local domain. There is no limit if this parameter is not specified.

MAXRDOM = numeric
  specifies the maximum number of connections (or dialogues if the domain is of type OSITP) allowed per gateway. There is no limit if this parameter is not specified.

MAXRDTRAN = numeric
  specifies the maximum number of domains that can be involved in a transaction. It must be greater than 0 and less than 32,768. If not specified, the default is 16.

MAXTRAN = numeric
  specifies the maximum number of simultaneous global transactions allowed on this local domain. It must be greater than or equal to 0 and less than or equal to the MAXGTT parameter specified in the TUXCONFIG file. If not specified, the default is the value of MAXGTT.

MAXSENDLEN = numeric
  specifies the maximum length (in bytes) of messages sent or received by this local domain. If this parameter is set all messages sent or received will be broken up into packets of no more than MAXSENDLEN bytes. There is no limit if this parameter is not specified.

#### *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.

##### Required Parameters

The following parameters are required.

TYPE = identifier
  is used for grouping remote domain into classes. TYPE can be set to one of the following values: TDOMAIN or OSITP. The TDOMAIN value indicates that this remote domain can only communicate with another TUXEDO System/Domain Domain. The OSITP value indicates that this remote domain communicates with another TP domain via the OSI-TP protocol.

DOMAINID = string
  is used to identify a remote domain. DOMAINID must be 32 octets or fewer in length. If the value is a string, it must be 31 characters or fewer. DOMAINID must be unique across remote domains. The value of string can be a sequence of characters or a sequence of hexadecimal digits preceded by "0x".

##### Optional Parameters

There are no optional parameters for this section.

#### *DM_TDOMAIN Section

This section defines the addressing information required by domains of type TDOMAIN. This section should have an entry per local domain if requests from remote domains to local services are accepted on that local domain (gateway group), and an entry per remote domain accessible by the defined local domains.

##### Format

*DM_TDOMAIN entries have the following format.

DOM required parameters [optional parameters]

where:

DOM is an identifier value used to identify either 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.

##### Required Parameters

The following parameter is required.

NWADDR = string
  This parameter specifies the network address used by a local or a remote domain to accept connections from other TUXEDO System/Domain Domains. If string has the form ``0xhex-digits'', it must contain an even number of valid hexadecimal digits.

##### Optional Parameters

The following parameter is optional:

NWDEVICE = string
  Specifies the device file name to be used when binding to the listening address of a local or a remote domain. If the networking functionality is TLI-based, the device name must be an absolute path name. If the networking functionality is Sockets-based, this parameter does not need to be specified.

Notice that multiple entries for a particular domain may be defined in this table. Currently, only the first address is used and the remaining entries are ignored.

#### *DM_OSITP Section

This section defines the addressing information required by domains of type OSITP. This section should have one entry per gateway group (local domain), and one entry per remote domain of type OSITP.

##### Format

*DM_OSITP 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.

##### Required Parameters

The following are required parameters.

APT = string
  This parameter specifies an OSI Application Process Title (APT). An APT may be a name (i.e., the Directory Name of an Application Process Title) or an object identifier (i.e., a sequence of integer values separated by periods).

AEQ = string
  This parameter specifies an OSI Application Entity Qualifier (AEQ). An AEQ is an integer.

NWDEVICE = string
  Specifies the device name to be used when binding to an XAP dialogue instance. It may be an absolute path name of a device file name or just an identifier of a device. The value of the string is specific to the XAP-TP provider.

XATMI_ENCODING = {CAE | PRELIMINARY | OLTP_TM2200}
  This parameter specifies the version of the XATMI protocol used to communicate with a remote application. Valid values are:
  CAE
  PRELIMINARY
  OLTP_TM2200

##### Optional Parameters

The following are optional parameters.

AET = string
  This parameter specifies an OSI Application Entity Title (AET). An AET is formed from an Application Process Title (APT) and an Application Entity Qualifier (AEQ), i.e. in ASN.1 AET is defined as a SEQUENCE {APT, AEQ} where APT and AET are of type ANY. Three main formats are accepted for the value of string:

{object identifier}, {integer}
  The first element represents the APT defined as an object identifier (i.e., a sequence of integer values separated by periods) and the second element represents an AEQ defined as an integer constant, e.g., AET = "{1.3.15.0.3},{1}".

ACN = {XATMI | UDT}
  This parameter specifies the object identifier of the Application Context Name (ACN) used by this domain. Current allowed application contexts are: the XATMI-ASE (XATMI) and the UDT-ASE (UDT). If this parameter is not specified, the ACN is set to the object identifier of the XATMI-ASE Application Context.

APID = integer
  This parameter specifies an OSI Application Process Invocation Identifier (APID).

AEID = integer
  This parameter specifies an OSI Application Entity Invocation Identifier (AEID).

PROFILE = identifier
  This parameter specifies the OSI TP profile used by this domain and is used to determine the required OSI TP functional units. PROFILE can be set to one of the following values: ATP11, ATP21, ATP31, ATP12, ATP22, and ATP32. The UDT ASE application context allows the use of any of these profiles. The XATMI-ASE application context only allows profiles ATP11, ATP21 and ATP31. Profiles ATP11, ATP21 and ATP31 use the Dialogue, Polarized Control and Handshake functional units. Profiles ATP12, ATP22 and ATP32 use the Dialogue, Shared Control, and Handshake functional units. Profiles ATP11 and ATP12 do not use OSI TP transactions (the Commit functional unit is not used). Profiles ATP21 and ATP22 require the Commit, Unchained Transactions, and Recovery functional units. Profiles ATP31 and ATP32 require the Commit, Chained Transactions, and Recovery functional units. By default, the ATP21 profile is always selected.

URCH = string
  This parameter specifies the user portion of the OSITP Recovery Context Handle. It may be required by the XAP-TP provider in order to perform recovery of distributed transactions after a communications line or system failure.

MAX_LISTENING_EP = integer
  This parameter specifies the number of endpoints currently waiting for incoming connections. The default is three (3).

#### *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.

##### Required Parameters

The following parameter is required.

ACLIST = identifier [,identifier]
  where an ACLIST is composed of one or more remote domain names (RDOM) separated by commas. The wildcard character (*) can be used to specify that all the remote domains defined in the *DM_REMOTE_DOMAINS section can access a local domain.

#### *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.

##### Required Parameters

There are no required parameters for *DM_LOCAL_SERVICES.

##### Optional Parameters

The following parameters are optional.

ACL = identifier
  specifies the name of the access control list (ACL) to be used by the local domain to restrict requests made to this service by remote domains. The name of the ACL is defined in the *DM_ACCESS_CONTROL section. If this parameter is not specified then access control will not be performed for requests to this service.

LDOM = identifier
  specifies the name identifying the local domain exporting this service. If this keyword is not specified then all the local domains defined in the *DM_LOCAL_DOMAINS section will accept requests to this local service.

RNAME = string
  specifies the name exported to remote domains. This name will be used by the remote domains for request to this service. If this parameter is not specified, the local service name is supposed to be the name used by any remote domain. For OSI TP, this maps to the TPSUT on the remote system.

#### *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.

##### Required Parameters

There are no required parameters for the *DM_REMOTE_SERVICES section.

##### Optional Parameters

The following parameters are optional.

CONV = {Y | N}
  specifies whether or not the remote service is a conversational service. Use Y to specify the remote service is a conversational service. Use N to specify the remote service is not a conversational service. The default value is N.

LDOM = identifier
  specifies the name of a local domain in charge of routing requests to this remote service. The gateway group associated with the local domain advertises service in the TUXEDO System/Domain Bulletin Board. If this parameter is not specified then all the local domains will be able to accept requests to this remote service. The service request will be then redirected to a remote domain of the same type (see the following definition for RDOM keyword).

RDOM = identifier
  specifies the name of the remote domain responsible for the actual execution of this service. If this parameter is not specified and a routing criteria (see the following definition for ROUTING keyword) is not specified, then the local domain assumes that any remote domain of the same type accepts this service and it selects a known domain (a domain to which a connection already exists) or remote domain from the \**DM_REMOTE_DOMAINS section.

RNAME = string
  specifies the actual service name expected by the remote domain. If this parameter is not specified, the remote service name is the same as the name specified in service. For OSI TP, this maps to the TPSUT on the remote system.

ROUTING = identifier
  when more than one remote domain offers the same service, a local domain can perform data-dependent routing if this optional parameter is specified. The identifier specifies the name of the routing criteria used for this data-dependent routing. If not specified, data-dependent routing is not done for this service. identifier must be 15 characters or less in length. If multiple entries exist for the same service name but with different RDOM parameters, the ROUTING parameter should be the same for all of these entries.

TRANTIME = integer
  specifies the default time-out value in seconds for a transaction automatically started for the associated service. The value must be greater than or equal to 0 and less than 2147483648. The default is 30 seconds. A value of 0 implies the maximum time-out value for the machine.

#### *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.

##### Required Parameters

The following parameters are required.

FIELD = identifier
  specifies the name of the routing field. It must be 30 characters or less. This field is assumed to be a field name that is identified in an FML field table (for FML buffers) or an FML view table (for VIEW, X_C_TYPE, or X_COMMON buffers). The FLDTBLDIR and FIELDTBLS environment variables are used to locate FML field tables, and the VIEWDIR and VIEWFILES environment variables are used to locate FML view tables.

RANGES = string
  specifies the ranges and associated remote domain names (RDOM) for the routing field. string must be enclosed in double quotes. The format of string is a comma-separated ordered list of range/RDOM pairs (see the following "Sample Configuration Files" section).

A range is either a single value (signed numeric value or character string in single quotes), or a range of the form ``lower - upper'' (where lower and upper are both signed numeric values or character strings in single quotes). Note that ``lower'' must be less than or equal to ``upper.'' To embed a single quote in a character string value (as in O'Brien, for example), it must be preceded by two backslashes ('O\\'Brien').

The value MIN can be used to indicate the minimum value for the data type of the associated FIELD; for strings and arrays, it is the null string; for character fields, it is 0; for numeric values, it is the minimum numeric value that can be stored in the field.

The value MAX can be used to indicate the maximum value for the data type of the associated FIELD; for strings and arrays, it is effectively an unlimited string of octal-255 characters; for a character field, it is a single octal-255 character; for numeric values, it is the maximum numeric value that can be stored in the field.

Thus, ``MIN - -5'' is all numbers less than or equal to -5 and ``6 - MAX'' is all numbers greater than or equal to 6. The meta-character ``*'' (wildcard) in the position of a range indicates any values not covered by the other ranges previously seen in the entry; only one wildcard range is allowed per entry and it should be last (ranges following it will be ignored).

The routing field can be of any data type supported in FML. A numeric routing field must have numeric range values and a string routing field must have string range values.

String range values for string, array, and character field types must be placed inside a pair of single quotes and cannot be preceded by a sign. Short and long integer values are a string of digits, optionally preceded by a plus or minus sign. Floating point numbers are of the form accepted by the C compiler or `atof():` an optional sign, then a string of digits optionally containing a decimal point, then an optional e or E followed by an optional sign or space, followed by an integer.

When a field value matches a range, the associated RDOM value specifies the remote domain to which the request should be routed. A RDOM value of ``*'' indicates that the request can go to any remote domain known by the gateway group.

Within a range/RDOM pair, the range is separated from the RDOM by a ``:''.

BUFTYPE = ~type1[:subtype1[,subtype2 . . . ]][;type2[:subtype3[, . . . ]]] . . .~
  is a list of types and subtypes of data buffers for which this routing entry is valid. The types are restricted to be either FML, VIEW, X_C_TYPE, or X_COMMON. No subtype can be specified for type FML and subtypes are required for the other types (``*'' is not allowed). Duplicate type/subtype pairs cannot be specified for the same routing criterion name; more than one routing entry can have the same criterion name as long as the type/subtype pairs are unique. This parameter is required. If multiple buffer types are specified for a single routing entry, the data types of the routing field for each buffer type must be the same.

If the field value is not set (for FML buffers), or does not match any specific range and a wildcard range has not been specified, an error is returned to the application process that requested the execution of the remote service.

##### Optional Parameters

There are no optional parameters for the *DM_ROUTING section.

### Sample Configuration Files

The following configuration file defines a 5-site domain configuration. The example shows 4 Bank Branch domains communicating with a Central Bank Branch. Three of the Bank Branches run within other TUXEDO System/Domain domains. The fourth Branch runs under the control of another TP Domain and OSI TP is used in the communication with that domain.

The example shows the TUXEDO System/Domain Domain configuration file from the Central Bank point of view.

> Listing 3-1 `Sample Configuration File at Central Bank`

`# TUXEDO DOMAIN CONFIGURATION FILE FOR THE CENTRAL BANK
#
#
*DM_LOCAL_DOMAINS
# <local domain name> <Gateway Group name> <domain type> <domain id> <log device>
# [<audit log>] [<blocktime>]
# [<log name>] [<log offset>] [<log size>]
# [<maxrdom>] [<maxrdtran>] [<maxtran>]
# [<maxdatalen>] [<security>]
# [<tuxconfig>] [<tuxoffset>]
#
#
DEFAULT: SECURITY = NONE
`

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

`c02 GWGRP = bankg2
TYPE = OSITP
DOMAINID = "BA.CENTRAL01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C02"
NWDEVICE = "OSITP"
URCH = "ABCD"
#
*DM_REMOTE_DOMAINS
#<remote domain name> <domain type> <domain id>
#
b01 TYPE = TDOMAIN
DOMAINID = "BA.BANK01"
`

`b02 TYPE = TDOMAIN
DOMAINID = "BA.BANK02"
`

`b03 TYPE = TDOMAIN
DOMAINID = "BA.BANK03"
`

`b04 TYPE = OSITP
DOMAINID = "BA.BANK04"
NWDEVICE = "/dev/osi"
URCH = "ABCD"
`

`*DM_TDOMAIN
#
# <local or remote domain name> <network address> [<nwdevice>]
#
# Local network addresses
c01 NWADDR = "0x0002ff98c00b9d6d" NWDEVICE ="/dev/tcp"
c01 NWADDR = "newyork01.65432" NWDEVICE ="/dev/starlan"
# Remote network addresses
b01 NWADDR = "0x00020401c00b6d05" NWDEVICE = "/dev/tcp"
b02 NWADDR = "dallas.65432" NWDEVICE = "/dev/starlan"
b03 NWADDR = "0x00021094c00b6d9c" NWDEVICE = "/dev/tcp"
`

`*DM_OSITP
#
#<local or remote domain name> <apt> <aeq>
# [<aet>] [<acn>] [<apid>] [<aeid>]
# [<profile>]
#
c02 APT = "BA.CENTRAL01"
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_LOCAL_SERVICES
#<service_name> [<Local Domain name>] [<access control>] [<exported svcname>]
#
#
open_act ACL = branch
close_act ACL = branch
credit
debit
balance
loan LDOM = c02 ACL = loans
`

`*DM_REMOTE_SERVICES
#<service_name> [<Remote domain name>] [<local domain name>]
# [<remote svcname>] [<routing>] [<conv>] [<trantime>]
#
#
tlr_add LDOM = c01 ROUTING = ACCOUNT
tlr_bal LDOM = c01 ROUTING = ACCOUNT
tlr_add RDOM = b04 LDOM = c02 RNAME ="TPSU002"
tlr_bal RDOM = b04 LDOM = c02 RNAME ="TPSU003"
`

`*DM_ROUTING
# <routing criteria> <field> <typed buffer> <ranges>
#
ACCOUNT FIELD = branchid BUFTYPE ="VIEW:account"
RANGES ="MIN - 1000:b01, 1001-3000:b02, *:b03"
`

`*DM_ACCESS_CONTROL
#<acl name> <Remote domain list>
#
branch ACLIST = b01, b02, b03
loans ACLIST = b04`

This example shows the TUXEDO System/Domain Domain Configuration file required at one of the Bank Branches (BANK01).

> Listing 3-2 `Sample Configuration File at Branch Bank`

`#TUXEDO DOMAIN CONFIGURATION FILE FOR A BANK BRANCH
#
#
*DM_LOCAL_DOMAINS
#
b01 GWGRP = auth
TYPE = TDOMAIN
DOMAINID = "BA.BANK01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
`

`*DM_REMOTE_DOMAINS
#
c01 TYPE = TDOMAIN
DOMAINID = "BA.CENTRAL01"
`

`*DM_TDOMAIN
#
b01 NWADDR = "0x00021094c00b689c" NWDEVICE = "/dev/tcp"
c01 NWADDR = "0x0002ff98c00b9d6d" NWDEVICE = "/dev/tcp"
*DM_LOCAL_SERVICES
#
tlr_add ACL = central
tlr_bal ACL = central
`

`*DM_REMOTE_SERVICES
#
OPA001 RNAME = "open_act"
CLA001 RNAME = "close_act"
CRD001 RNAME = "credit"
DBT001 RNAME = "debit"
BAL001 RNAME = "balance"
`

`*DM_ACCESS_CONTROL
#
central ACLIST = c01`

## Modifying an Existing Gateway Configuration

To modify an existing gateway configuration, complete the following steps.

1. Use the `dmadmin` command to access the binary BDMCONFIG file.

2. Process the DMCONFIG file by running the `dmloadcf` utility.

### Using the dmadmin Command

You can use the `dmadmin` command or the BEA TUXEDO graphical user interface to administer Connect OSI TP.

You can administer domain gateway groups defined for a BEA TUXEDO System/T application using `dmadmin`, an interactive command interpreter. The `dmadmin` command can operate in two modes: administration mode and configuration mode. Configuration mode allows the administrator to change a configuration while the application is running. Refer to the BEA TUXEDO/T Domain Manual for information about the `dmadmin` command.

## Defining Connect OSI TP Servers to BEA TUXEDO

To establish a gateway configuration, the BEA TUXEDO system must recognize the Connect OSI TP administrative and gateway servers. To define the Connect OSI TP servers for BEA TUXEDO, edit the UBBCONFIG file to define the Connect OSI TP administrative and gateway servers to the BEA TUXEDO system.

### Sample UBBCONFIG File

The following file is a sample UBBCONFIG file that defines Connect OSI TP administrative and gateway servers to the BEA TUXEDO system.

> Listing 3-3 Sample UBBCONFIG File for Connect OSI TP

>     ### Sample ubbconfig file showing Connect OSI TP modifications

>     *RESOURCES
>     	# No OSI TP entries in the RESOURCES section.
>     *MACHINES
>     	# No OSI TP entries in the MACHINES section.
>     *GROUPS

>     ### A group must exist for each OSI TP Gateway.
>     #
>     OSIGRP			# Name the group as you wish
>     	GRPNO=1		# Choose a free group number
>     	LMID=MACHINE		# Specify the machine hosting the gateway.
>     	TMSNAME="TMS"		# Two or more TMS servers are required.
>     	TMSCOUNT=2
>     *SERVERS

>     ### One DMADM server must be configured.
>     #
>     DMADM
>     	SRVID=1		# Choose a unique server id.
>     	SRVGRP=OSIGRP		# Place in any convenient group.

>     ### One GWADM server must be configured for each gateway.
>     #

>     GWADM
>           SRVID=2		     # Choose a unique server id.
>           SRVGRP=OSIGRP		# Place into the group created for this gateway.

>     ### One GWOSITP server must be configured for each gateway.

>     GWOSITP
>           SRVID=3		     # Choose a unique server id.
>           SRVGRP=OSIGRP		# Place into the group created for this gateway.

>     *SERVICES

>     	# No OSI TP entries in the SERVICES section.

Refer to the BEA TUXEDO Reference Manual.

[Top] [Previous] [Next] [End of Book]