Editing the DM_REMOTE_SERVICES Section


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| TOP END Domain Gateway \| Topic List \| Previous \| Next \| Contents

Using the BEA Tuxedo TOP END Domain Gateway

The DM_REMOTE_SERVICES section defines the mapping information required to make BEA TOP END services, RTQ queues, and services accessed via RTQ available to a BEA Tuxedo application. This section is required for TOP END Domain Gateways.

In DMCONFIG files written for domain gateways other than the TEDG, the purpose of entries in the DM_REMOTE_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:

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

For BEA Tuxedo and BEA TOP END 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

The 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 BEA Tuxedo service assigned to the BEA TOP END service (default).
qspace is the name of the BEA Tuxedo queue space assigned to the RTQ queue.
qname is the name of the BEA Tuxedo queue assigned to a BEA TOP END service accessed through RTQ.

Configuration Guidelines for the DM_REMOTE_SERVICES

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

Because SERVICE and QSPACE entries define service identifiers and qspace identifiers that are advertised as BEA Tuxedo services, these identifiers must be unique for a particular LDOM. However, multiple entries of the same type and identifier are permitted for load balancing. All entries for a single service identifier must have the same value for the CONV parameter.
If they do not define a particular local domain (with the LDOM parameter), the following types of entries apply to each local domain of type TOPEND:
- Any SERVICE and QNAME entry that includes the TE_PRODUCT parameter
- Any QSPACE entry that includes the TE_RTQGROUP parameter
For SERVICE and QSPACE entries, the BEA TOP END service or RTQ queue is assumed to be available on the remote BEA TOP END node specified with the RDOM parameter or obtained through specified routing criteria. Services specified in a QNAME entry are assumed to be available via the BEA TOP END node to which they are enqueued.
Entries in which multiple remote domains are specified with the RDOM parameter use the Domains Failover feature that enables this service request to be routed to the alternate RDOM if the primary RDOM is not connected, or to the second alternate if the primary and first alternate are not connected. This feature may also be used in conjunction with the load balancing feature in which multiple remote service entries are configured for the same service or queue space identifier.
If a configuration includes LDOMs for more than one BEA TOP END system, or includes multiple gateway types (such as TDOMAIN and TOPEND), the LDOM parameter should be specified in the remote service entry. If an RDOM is specified on the entry or in a referenced routing entry, it should match the LDOM type (TOPEND) and TP_SYSTEM. Mixed configurations that do not specify LDOM, or reference RDOMs of mixed types or mixed TP_SYSTEMs should not be created and may prevent a gateway from initializing properly. If in doubt, explicitly set LDOM and a remote domain (via the RDOM parameter or ROUTING). "Wildcard" specifications for remote domains should be used only when a single gateway type is defined.

Defining the Service Type Parameters

A SERVICE entry defines BEA TOP END services that are accessible from a BEA Tuxedo domain via the TEDG. These BEA TOP END services are made accessible by mapping BEA Tuxedo service names to BEA TOP END service identifiers. These service names are used with two BEA Tuxedo functions: tpcall(3c) and tpacall(3c).

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

Parameters of SERVICE Type Entries in DM_REMOTE_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 define the parameters available when mapping a BEA TOP END service to a local BEA Tuxedo service.

No

LDOM

The name of the local domain importing this 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

RDOM

The name of the remote domain providing this service. The remote domain must be of type TOPEND and it must belong to the TP_SYSTEM to which the local domain (that is, the domain to which this entry applies) belongs. If you do not specify the RDOM parameter and routing criteria, the local domain assumes that any remote domain of type TOPEND with the same TP_SYSTEM value as the local domain provides the service.

To configure alternate remote domains using this parameter, you must specify ON_STARTUP as the value of the CONNECTION_POLICY parameter 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

CONV

Request/Response or conversational service mapping. If this value is set to Y, the BEA TOP END server application must manage a pseudo-conversation that may or may not maintain application context. The default is N.

No

TRANTIME

The default timeout value, in seconds, for a transaction automatically started for the associated service.

No

ROUTING

The name of the criteria used by a local domain for data-dependent routing when more than one remote domain offers the same service. If you do not specify this parameter, data-dependent routing is not done for this service.

No

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 define the parameters available when mapping a BEA TOP END service to a local BEA Tuxedo service.	No
LDOM	The name of the local domain importing this 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
RDOM	The name of the remote domain providing this service. The remote domain must be of type TOPEND and it must belong to the TP_SYSTEM to which the local domain (that is, the domain to which this entry applies) belongs. If you do not specify the RDOM parameter and routing criteria, the local domain assumes that any remote domain of type TOPEND with the same TP_SYSTEM value as the local domain provides the service. To configure alternate remote domains using this parameter, you must specify ON_STARTUP as the value of the CONNECTION_POLICY parameter 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
CONV	Request/Response or conversational service mapping. If this value is set to Y, the BEA TOP END server application must manage a pseudo-conversation that may or may not maintain application context. The default is N.	No
TRANTIME	The default timeout value, in seconds, for a transaction automatically started for the associated service.	No
ROUTING	The name of the criteria used by a local domain for data-dependent routing when more than one remote domain offers the same service. If you do not specify this parameter, data-dependent routing is not done for this service.	No

Defining QSPACE Type Parameters

A QSPACE entry defines a BEA TOP END RTQ queue that is made available in the BEA Tuxedo domain by the TEDG as if it were a BEA Tuxedo queue space. Queue spaces are made available in a BEA Tuxedo application by advertising the queue space name as a BEA Tuxedo service name. In a manner similar to that used by the TMQUEUE server, the TEDG handles tpenqueue requests sent to its queue space names. Each request is mapped to the RTQ queue 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_REMOTE_SERVICES section. Some parameters are required; others are optional.

Parameters of QSPACE Type Entries in DM_REMOTE_SERVICES

This Parameter . . .
Defines . . .
Required?

TYPE

A type for this entry. The value QSPACE means that the purpose of this entry is to define the parameters available when mapping a BEA TOP END RTQ queue to a local BEA Tuxedo queue space.

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

LDOM

The name of the local domain importing this RTQ queue. 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

RDOM

The name of the remote domain providing this RTQ queue. The remote domain must be of type TOPEND and it must belong to the same TP_SYSTEM to which the local domain (that is, the domain to which this entry applies) belongs. If you do not specify the RDOM parameter and routing criteria, the local domain assumes that any remote domain of type TOPEND with the same TP_SYSTEM value as the local domain provides the service.

To configure alternate remote domains using this parameter, you must specify ON_STARTUP as the value of the CONNECTION_POLICY parameter in the DM_LOCAL_DOMAINS section.

No

TRANTIME

The default timeout value, in seconds, for a transaction automatically started for the associated service.

No

ROUTING

The name of the criteria used by a local domain for data-dependent routing when more than one remote domain offers the same service. If you do not specify this parameter, data-dependent routing is not done for this service.

No

This Parameter . . .	Defines . . .	Required?
TYPE	A type for this entry. The value QSPACE means that the purpose of this entry is to define the parameters available when mapping a BEA TOP END RTQ queue to a local BEA Tuxedo queue space.	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
LDOM	The name of the local domain importing this RTQ queue. 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
RDOM	The name of the remote domain providing this RTQ queue. The remote domain must be of type TOPEND and it must belong to the same TP_SYSTEM to which the local domain (that is, the domain to which this entry applies) belongs. If you do not specify the RDOM parameter and routing criteria, the local domain assumes that any remote domain of type TOPEND with the same TP_SYSTEM value as the local domain provides the service. To configure alternate remote domains using this parameter, you must specify ON_STARTUP as the value of the CONNECTION_POLICY parameter in the DM_LOCAL_DOMAINS section.	No
TRANTIME	The default timeout value, in seconds, for a transaction automatically started for the associated service.	No
ROUTING	The name of the criteria used by a local domain for data-dependent routing when more than one remote domain offers the same service. If you do not specify this parameter, data-dependent routing is not done for this service.	No

Defining QNAME Type Parameters

A QNAME entry maps a BEA Tuxedo queue name to a BEA TOP END service (product and function) for requests enqueued to a BEA TOP END system. QNAME entries are not advertised as services to a BEA Tuxedo application.

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

Parameters of QNAME Type Entries in DM_REMOTE_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 available when mapping a BEA Tuxedo queue name to a BEA TOP END service name for requests enqueued to a BEA TOP END system via /Q.

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 the queue name 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

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 available when mapping a BEA Tuxedo queue name to a BEA TOP END service name for requests enqueued to a BEA TOP END system via /Q.	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 the queue name 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