This section, also known as the DM_LOCAL_SERVICES section, defines the mapping information required to make BEA Tuxedo services and /Q queue spaces available to BEA TOP END systems. This section is required for TOP END domain gateways.

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

Entries within the DM_EXPORT 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 name of an exported BEA Tuxedo service, qspace is the name of an exported BEA Tuxedo queue space, and qname is the name of a queue name defined within a BEA Tuxedo queue space. 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.

SERVICE entries in the DM_EXPORT section define BEA Tuxedo services that are advertised to the BEA TOP END system by the TEDG. Entries for BEA Tuxedo services that are advertised to a BEA TOP END system include a mapping from BEA Tuxedo service names to BEA TOP END service identifiers (product, function, target, qualifier). These service identifiers are used with the BEA TOP END tp_client_send(3T) and tp_client_signon(3T) routine calls.

QSPACE entries in the DM_EXPORT section define BEA Tuxedo queue spaces that are made available to BEA TOP END as RTQ queues (limitations apply). RTQ queues are made available in BEA TOP END by advertising the RTQ Group name, RTQ Queue name, and target name as a BEA TOP END service name. The BEA TOP END gateway handles tp_rtq_put(3T) requests sent to its RTQ queue names in a manner similar to that used by the RTQ server. Each request is then mapped to the BEA Tuxedo queue space identified in this QSPACE entry. Both QSPACE entries and QNAME entries are required for message queuing.

QNAME entries in the DM_EXPORT section define the mapping of a BEA TOP END service request to a BEA Tuxedo queue name for requests enqueued to the BEA Tuxedo system via RTQ. QNAME entries are not advertised as services to the BEA TOP END system. QSPACE and QNAME entries are independent. Any combination of QSPACE and QNAME identifiers may be used by an application by supplying the associated BEA TOP END identifiers with a tp_rtq_put(3T) routine call. A run-time error results if the combination does not exist in the local BEA Tuxedo application.

QNAME entries should be unique with respect to their product, function, target, and qualifier combination for a particular local domain access point specified using the LACCESSPOINT parameter. If multiple entries of the same combination 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 all local domain access points of type TOPEND if the entry is not configured for a particular local domain access point via the LACCESSPOINT parameter. Entries configured for a specific local domain access point are applicable only to the domain gateway associated with that access point.

Because SERVICE and QSPACE entries configure BEA TOP END service identifiers that are advertised as BEA TOP END services, these identifiers must not overlap for a particular local domain access point. For a SERVICE entry, the TE_PRODUCT, TE_FUNCTION, and TE_TARGET are advertised. For a QSPACE entry, the TE_RTQGROUP, TE_RTQNAME, and TE_TARGET are advertised as product, function, and target identifiers. Therefore if a SERVICE entry product, function, and target match a QSPACE entry RTQ Group, RTQ Queue name and target, the TEDG cannot route the request. Note that, as in the BEA TOP END system, the default for the target is the truncated node name.

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 local resource entry in the DM_EXPORT section. Mixed configurations that do not specify local domain access points should not be created; they may prevent a gateway from initializing properly. If in doubt, explicitly set LACCESSPOINT.

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

Required and optional TEDG parameters for DM_EXPORT section