Using the Gateway Administrative Server, GWADM(5)


	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 \| Administration \| Topic List \| Previous \| Next \| Contents

Using the BEA Tuxedo Domains Component

The gateway administrative server, GWADM(5), is a BEA Tuxedo-supplied server that provides administrative functions for a Domains gateway group. The main functions of the GWADM server include the following:

To get Domains configuration information from the DMADM server, and to accept queries from dmadmin. The GWADM server gets the gateway group configuration information by registering with the DMADM server. The GWADM server then makes the configuration available to gateways by storing the information in shared memory.
To provide administrative functionality for a gateway group, for example, to accept queries from dmadmin for run-time statistics or to change the run-time parameters of the gateway group.
To provide transaction logging functionality for a gateway group. The GWADM server determines which transactions need to be logged by reading information stored in shared memory. When the GWADM server is booted; scans the log to see whether any transactions need to be recovered; it then reconstructs the transaction information in shared memory. The gateway server scans the information in shared memory and performs recovery for the corresponding transactions. The recovery procedure is performed asynchronously with new incoming or outgoing requests received by the gateway group.

The GWADM server advertises a service name based on the local domain name (the value of the LDOM keyword in the BDMCONFIG). The dmadmin command uses this service to retrieve information from all active gateway groups or from a specific gateway group.

The GWADM server must be defined in the SERVERS section of the TUXCONFIG file. It should not be part of the MSSQ used by the gateways associated with the group and it must not have a reply queue, that is, REPLYQ=N must be specified. It must be the first server booted within the gateway group; that is, either (a) it must have a SEQUENCE number, or (b) it must be defined ahead of the gateway servers.

The GWADM server requires the existence of a DMADM server. Specifically, a DMADM server must be booted before that GWADM is booted.

The GWADM server must create the shared memory required by the gateway group to populate the configuration tables with information received from the DMADM server. The GWADM server uses IPC_PRIVATE with shmget and stores the ipckey returned in the shmid field of its registry entry in the bulletin board. Gateways can obtain the ipckey by retrieving the GWADM registry entry and checking the shmid field.