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 Domains Component   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

To integrate the Domains component with an existing BEA Tuxedo application, add entries for domain gateway groups and gateway servers to the TUXCONFIG file. You can use either the tmconfig(1) (see tmconfig, wtmconfig(1)) or tmadmin(1) command to add a multiple-domain configuration to a running BEA Tuxedo application. You can also use tmadmin to list the information available in the bulletin board for Domain gateway groups and individual gateways.

Domains offers the following administrative commands:

• dmadmin(1) command, a generic administrative service—enables administrators to configure, monitor, and tune domain gateway groups dynamically, and to update the Domains configuration file (BDMCONFIG) while the BEA Tuxedo application is running. The command acts as a front-end process that translates administrative commands into service requests which it then sends to the DMADMIN service, a generic administrative service advertised by the DMADM server. The DMADMIN service invokes the validation, retrieval, or update of functions provided in the DMADM server to maintain the BDMCONFIG file.

• DMADM(5), the gateway group administrative server—provides the administrative processing required for updating the Domains configuration. This server acts as a back-end to the dmadmin command. It provides a registration service to gateway groups. This registration service is requested by GWADM servers as part of their initialization procedure. The registration service downloads the configuration information required by the requesting gateway group. The DMADM server maintains a list of registered gateway groups, and propagates to these groups any changes made to the configuration.

• GWADM(5), the gateway process—the GWADM server registers with the DMADM server to obtain the configuration information used by the corresponding gateway group. The GWADM accepts queries from DMADM to obtain run-time statistics or to change the run-time options of the corresponding gateway group. Periodically, the GWADM server sends an "I-am-alive" message to the DMADM server. If no reply is received from the DMADM server, the GWADM server registers again. This mechanism makes sure the GWADM server always has the latest copy of the Domains configuration for its group.

• GWTDOMAIN(5)—the gateway process, GWTDOMAIN, which provides connectivity to remote gateway processes, focuses on throughput of messages between BEA Tuxedo domains. Clients and servers send and receive messages across BEA Tuxedo domains via the GWTDOMAIN process.

  Note: For a gateway type other than GWTDOMAIN, an executable other than GWTDOMAIN must be used. Refer to the BEA eLink Adapter for Mainframe documentation and Using the BEA Tuxedo TOP END Domain Gateway with ATMI Applications for additional information.

• BDMCONFIG—the binary version of the Domains configuration file, which contains all the configuration parameters that the BEA Tuxedo software interprets to create a viable application.

1. Copy DMCONFIG to the new machine and run dmloadcf.

2. Shut down all domain gateway groups (GWADM and a domain gateway, for example, GWTDOMAIN).

   Note: If the domain gateway groups are not shut down, they will continue to function, but after DMADM has been migrated, all MIB requests for them will fail.

3. Migrate the DMADM group to the new machine.

1. In the DMCONFIG file, add multiple listening addresses, in the following format, to the DM_TDOMAIN section:

   *DM_TDOMAIN
   LDOM NWADDR="//primary:port"
   LDOM NWADDR="//backup:port"

   Note: This step is unnecessary if third-party IP failover solutions are used.

2. If you are using transactions, you must copy the Domains transaction log manually to the backup machine.

3. The DMCONFIG files for the remote domains should include both network addresses as specified in step 1.

4. Migrate the domain gateway group to the new machine.