Distributed Data Manager Retrieve Problem Update Transaction


Overview

Included with

Tivoli Problem Management administration

Overview

Retrieve problem update transaction The following table lists the tasks to retrieve a problem update from a remote site.

Task System Process
1 Client A Create REMOTE_WORK record: RW_REQUEST_PROBLEM_UPDATE
2 Client A Create REMOTE_TASKS record for problem's CURRENT_SITE
3 Client A Post message to A's application server: ES_MSG_TA_OUTGOING_WORK
4 Application Server A Read the REMOTE_WORK and REMOTE_TASKS records
5 Application Server A Package update request data
6 Application Server A Post message to B's application server: ES_MSG_TA_PROBLEM_UPDATE_REQ
7 Application Server B Create LOCAL_WORK record
8 Application Server B Create REMOTE_WORK record: RW_SEND_PROBLEM_UPDATE
9 Application Server B Create REMOTE_TASKS record for Site A
10 Application Server B Post message to B's application server: ES_MsgNetNAgentAsClientRelay
11 Application Server B Send acknowledgement to Site A. Post Message to A's application server: ES_MSG_TA_REMOTE_COMPLETION
11a Application Server A Remove REMOTE_WORK and REMOTE_TASKS records
12 Application Server B Remove LOCAL_WORK record
13 Application Server B Read REMOTE_WORK and REMOTE_TASKS records
14 Application Server B Package problem ticket data that has been changed or added since the last time Site A was updated
15 Application Server B Post message to A's application server: ES_MSG_TA_PROBLEM_UPDATE
16 Application Server A Create LOCAL_WORK record
17 Application Server A Update or create problem ticket data
18 Application Server A Post message to Client: ES_MSG_TA_PROBLEM_AVAILABLE
18a Client A Display Problem Status Notebook
19 Application Server A Send acknowledgment to Site B. Post message to B's application server: ES_MSG_TA_REMOTE_COMPLETION
19a Application Server B Remove REMOTE_WORK and REMOTE_TASKS records
20 Application Server A Remove LOCAL_WORK record