|
A transaction to a remote site is completed
successfully when all Tivoli Problem Management related computers, software, and networks
in your enterprise are operating properly. A transaction can be a problem transfer to a
remote site, attaching a call to a problem at a remote site, viewing all current
information about a problem at a remote site, and so on. For more information about the
remote transaction types, see the appropriate help topic. Distributed Data Manager
completes transactions to remote sites in the following manner:
- Site A packages the data and sends it to Site B.
- Site B unpackages the transactions data.
- Site B sends an acknowledgement of the completed transaction to Site A. This
acknowledgement can represent a successful or failed transaction to Site B.
- Site A performs additional tasks based on the success or failure of the remote
transaction.
Transactions to remote sites are performed by the Distributed Data Manager application
servers in your enterprise using control tables. Control tables are database
records that contain the data required to initiate and process transactions to remote
sites, as shown in the following table.
Control Table |
Description |
REMOTE_WORK |
Each record stores the specific data required to perform a particular
remote transaction. A REMOTE_WORK record is similar to an Tivoli Problem Management
PROBLEM_CLOSURE record. |
REMOTE_TASKS |
A record that is created for each site where a particular REMOTE_WORK
transaction is to be performed. |
LOCAL_WORK |
A record that is created by the remote site when it begins the remote
transaction. When the remote transaction is completed, the local site is notified. If the
local site cannot be notified for some reason, the LOCAL_WORK record is used to notify the
local site at a later time. |
|