Editing the DM_LOCAL_SERVICES Section


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Using the BEA Tuxedo TOP END Domain Gateway \| Local Topics \| Previous Topic \| Next Topic \| Contents

The DM_LOCAL_SERVICES section defines the mapping required to make BEA Tuxedo services and /Q queue spaces available to a BEA TOP END system.

In DMCONFIG files written for domain gateways other than the TEDG, the purpose of entries in the DM_LOCAL_SERVICES section is to map local services to remote names for those services. In a DMCONFIG file written for the TEDG, however, the purpose of entries in this section is to map BEA Tuxedo names to BEA TOP END names for the following:

Request/reply and conversational services
BEA Tuxedo queue spaces and queue names

For BEA TOP END and BEA Tuxedo systems to exchange queue messages, there must be a mapping of the queue addresses on both systems. The address of a BEA Tuxedo /Q queue consists of a combination of queue space (QSPACE) and queue name (QNAME).

Defining Service and Queue Mapping Entries

Entries in this section must adhere to the following form.

service [TYPE=SERVICE] required_parameters [optional_parameters]
qspace  TYPE=QSPACE    required_parameters [optional_parameters]
qname   TYPE=QNAME     required_parameters [optional_parameters]

Here:

service is the name of an exported BEA Tuxedo service (TYPE=SERVICE is the default).
qspace is the name of an exported BEA Tuxedo queue space.
qname is the name of a queue defined in a BEA Tuxedo queue space and used in tpenqueue(3c) requests.

Configuration Guidelines for DM_LOCAL_SERVICES

Observe the following guidelines when editing the DM_LOCAL_SERVICES section of the DMCONFIG file.

For SERVICE and QSPACE entries, the BEA Tuxedo service or queue space is assumed to be available in the local BEA Tuxedo domain. A queue name specified in a QNAME entry is assumed to be defined in the queue space associated with that queue.
If the configuration includes LDOMs for more than one BEA TOP END system, or if it includes multiple gateway types, specify the LDOM parameter in the local service entry. Do not specify a mixed configuration that does not specify an LDOM; such a configuration may prevent a gateway from initializing properly. If in doubt, explicitly set LDOM.
Entries configured for a specific LDOM are advertised by the gateway for that LDOM. Additionally, any local SERVICE entry that is not configured for a particular local domain using the LDOM parameter, and that has the required TE_PRODUCT parameter, is advertised to the BEA TOP END system by each local domain of type TOPEND.
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 LDOM. For example, do not specify both a SERVICE entry and a QSPACE entry such that the TE_PRODUCT and TE_FUNCTION parameters of the SERVICE entry match the TE_RTQGROUP and TE_RTQNAME of the QSPACE entry, respectively.
QSPACE and QNAME entries are independent. Any combination of QSPACE and QNAME entries may be used by an application by supplying the associated BEA TOP END identifiers in the tp_rtq_put(3T) routine call. A run-time error will occur if the specified combination does not exist in the local BEA Tuxedo domain.

Defining Service Type Parameters

A SERVICE entry defines BEA Tuxedo services that are accessible from a BEA TOP END system via the TEDG. These services are made accessible by mapping the BEA TOP END service identifiers to BEA Tuxedo service names. These service identifiers are used with the BEA TOP END tp_client_send(3T) and tp_client_signon(3T) routine calls. RTQ service requests are not mapped in SERVICE entries.

The following table lists the parameters available for mapping in entries of type SERVICE in the DM_LOCAL_SERVICES section. Some parameters are required; others are optional.

Parameters of SERVICE Type Entries in DM_LOCAL_SERVICES

This Parameter . . .	Defines . . .	Required?
TE_PRODUCT	The BEA TOP END product name.	Yes
TE_FUNCTION	The BEA TOP END function name.	Yes
TE_TARGET	The BEA TOP END MSR target.	No
TE_QUALIFIER	The BEA TOP END function qualifier.	No
TYPE	A type for this entry. The value SERVICE means that the purpose of this entry is to map various parameters for a local BEA Tuxedo service being exported to a BEA TOP END system.	No
ACL	The name of the access control list (ACL) to be used by the TEDG to restrict requests made to the specified SERVICE by BEA TOP END systems. You define the ACL in the DM_ACCESS_CONTROL section of DMCONFIG, as described in Defining Security in the DMCONFIG File.	No
LDOM	The name of the local domain exporting the specified service. If you do not specify this parameter, then the entry applies to all the local domains of type TOPEND that are defined in the DM_LOCAL_DOMAINS section.	No
INBUFTYPE	The input buffer type allowed for this service. You can restrict the input buffer type by setting one of the following values: FML32, CARRAY, or X_OCTET.	No
OUTBUFTYPE	The output buffer type accepted from this service. You can restrict this to one of the following buffer types: FML32, CARRAY, or X_OCTET.	No

Defining QSPACE Type Parameters

A QSPACE entry defines a BEA Tuxedo queue space that is made available to the BEA TOP END system by the TEDG as if it were an RTQ queue (limitations apply). RTQ queues are made available in a BEA TOP END system by advertising the RTQ Group and Queue name as a BEA TOP END service name. In a manner similar to that used by the RTQ server, the TEDG handles tp_rtq_put(3T) requests sent to its RTQ queues. Each request is mapped to the BEA Tuxedo queue space identified in this QSPACE entry. Both QSPACE entries and QNAME entries are required for message queuing.

The following table lists the parameters available for mapping entries of type QSPACE in the DM_LOCAL_SERVICES section. Some parameters are required; others are optional.

Parameters of QSPACE Type Entries in DM_LOCAL_SERVICES

This Parameter . . .	Defines . . .	Required?
TYPE	A type for this entry. The value QSPACE means that the purpose of this entry is to map various parameters to a local BEA Tuxedo queue space being made available to a BEA TOP END system as an RTQ queue.	Yes
TE_RTQGROUP	The BEA TOP END RTQ group name.	Yes
TE_RTQNAME	The BEA TOP END RTQ queue name.	Yes
TE_TARGET	The BEA TOP END MSR target.	No
ACL	The name of the access control list (ACL) to be used by the TEDG to restrict requests made to the specified QSPACE by BEA TOP END systems. You define the ACL in the DM_ACCESS_CONTROL section of DMCONFIG as described in Defining Security in the DMCONFIG File.	No
LDOM	The name of the local domain exporting the specified queue space. If you do not specify this parameter, then the entry applies to all the local domains of type TOPEND that are defined in the DM_LOCAL_DOMAINS section.	No

Defining QNAME Type Parameters

A QNAME entry maps BEA TOP END service names to BEA Tuxedo queue names for requests enqueued to a BEA Tuxedo application via RTQ. The services defined in QNAME entries are not advertised as services to a BEA TOP END system.

The following table lists the parameters available for mapping entries of type QNAME in the DM_LOCAL_SERVICES section. Some parameters are required; others are optional.

Parameters of QNAME Type Entries in DM_LOCAL_SERVICES

This Parameter . . .	Defines . . .	Required?
TYPE	A type for this entry. The value QNAME means that the purpose of this entry is to define the parameters used in mapping a BEA TOP END service name to a BEA Tuxedo queue name for requests enqueued to a BEA Tuxedo application via RTQ.	Yes
TE_PRODUCT	The BEA TOP END product name.	Yes
TE_FUNCTION	The BEA TOP END function name.	Yes
TE_TARGET	The BEA TOP END MSR target.	No
TE_QUALIFIER	The BEA TOP END function qualifier.	No
LDOM	The name of the local domain to which this QNAME entry applies. If you do not specify this parameter, then the entry applies to all the local domains of type TOPEND that are defined in the DM_LOCAL_DOMAINS section.	No