This section, also known as DM_REMOTE_SERVICES, defines the mapping information required to make BEA TOP END services, RTQ queues, and services accessed via RTQ available to BEA Tuxedo applications. This section is required for TOP END domain gateways.

In a DMCONFIG file written for the TEDG, the DM_IMPORT section is used to define the following types of entries:

Entries within the DM_IMPORT section have one of the following forms:

service [TYPE=SERVICE]required_parameters [optional_parameters]

qspace  TYPE=QSPACE   required_parameters [optional_parameters]

qname   TYPE=QNAME    required_parameters [optional_parameters]

where service is the BEA Tuxedo service name assigned to the imported BEA TOP END service, qspace is the BEA Tuxedo queue space name assigned to the imported RTQ Queue, and qname is the BEA Tuxedo queue name assigned to the imported BEA TOP END service accessed through RTQ. Each of these names may contain no more than 15 characters. The setting of the TYPE parameter—SERVICE, QSPACE, or QNAME—determines the entry type.

QSPACE entries in the DM_IMPORT section define BEA TOP END RTQ queues that are made available in the local BEA Tuxedo application by the TEDG as if they were BEA Tuxedo queue spaces (limitations apply). A queue space is made available in a BEA Tuxedo application by advertising the queue space name as a BEA Tuxedo service name. The TEDG handles a tpenqueue(3c) request sent to its queue space name in a manner similar to that used by the TMQUEUE(5) server. The request is then mapped to the RTQ queue identified in this qspace entry. Both QSPACE and QNAME entries are required for message queuing.

QNAME entries should be unique with respect to the queue name identifier for a particular LACCESSPOINT. If multiple entries for the same queue name identifier value are configured, the TEDG uses only the first one.

Any SERVICE or QNAME entry that includes the TE_PRODUCT parameter, or any QSPACE entry that includes the TE_RTQGROUP parameter, is applicable to each local domain access point of type TOPEND if the entry is not configured for a particular local domain access point using the LACCESSPOINT parameter. Entries configured for a specific LACCESSPOINT are only applicable to the gateway (TEDG) for that local domain access point.

Because SERVICE and QSPACE entries configure service identifiers and queue space identifiers that are advertised as BEA Tuxedo services, these identifiers must not overlap for a particular local domain access point. However, multiple entries of the same type and identifier are permitted for load balancing. All entries for the same service identifier must have the same value for the CONV parameter.

If the DMCONFIG file includes local domain access points for more than one BEA TOP END system, or if it includes multiple domain gateway types, the LACCESSPOINT parameter should be specified for the remote resource entry in the DM_IMPORT section. If a remote domain access point is specified for a remote resource entry, or in a referenced routing entry, it should match the value of the local domain access point type (TOPEND) and TP_SYSTEM. Mixed configurations that do not specify local domain access point, or that reference remote domain access points of mixed types or mixed TP_SYSTEMs should not be created; they may prevent gateways from initializing properly. If in doubt, explicitly set the LACCESSPOINT and RACCESSPOINT parameters. A "wildcard" specification for a remote domain access point should be used only when a single gateway type is defined.

The following table identifies the required and optional parameters for each TEDG entry type in the DM_IMPORT section:

Required and optional TEDG parameters for DM_IMPORT section