Distributed Data Manager Pull Problem Back (Retrieve Problem) Transaction


Overview

Included with

Tivoli Problem Management administration

Overview

Pull problem back transaction The following table lists the tasks to retrieve a problem from a remote site.

Task System Process
1 Client A Create REMOTE_WORK record: RW_REQUEST_TRANSFER_PROB_BACK
2 Client A Create REMOTE_TASKS record for problem's CURRENT_SITE
3 Client A Set problem's CURRENT_SITE to (PEND)
4 Client A Post Message to A's application server: ES_MSG_TA_OUTGOING_WORK
5 Application Server A Read the REMOTE_WORK and REMOTE_TASKS records
6 Application Server A Package request data
7 Application Server A Post Message to B's application server: ES_MSG_TA_TRANSFER_BACK_REQ
8 Application Server B Create LOCAL_WORK record
9 Application Server B Create REMOTE_WORK record: RW_AUTO_PROBLEM_TRANSFER
10 Application Server B Create REMOTE_TASKS record for Site A
11 Application Server B Create "Sent" Audit Trail record
12 Application Server B Post Message to B's application server: ES_MsgNetNAgentAsClientRelay
13 Application Server B Send acknowledgment to Site A. Post Message to A's application server: ES_MSG_TA_REMOTE_COMPLETION
13a Application Server A Remove REMOTE_WORK and REMOTE_TASKS records
14 Application Server B Remove LOCAL_WORK record
15 Application Server B Read REMOTE_WORK and REMOTE_TASKS records
16 Application Server B Package problem ticket data that has been changed or added since the last time Site A was updated
17 Application Server B Notify current owner that problem has been "taken"
18 Application Server B Set problem's CURRENT_SITE to (PEND)
19 Application Server B Post Message to A's application server: ES_MSG_TA_PROBLEM_TRANSFER
20 Application Server A Create LOCAL_WORK record
21 Application Server A Update/create problem ticket data
22 Application Server A Create PROB_TRANSFER record
23 Application Server A Notify requester of problem's arrival
24 Application Server A Notify all remote sites which have ever owned the problem of the new CURRENT_SITE, OWNER and PROBLEM_RESULT (status) by performing a Problem Change Broadcast
25 Application Server A Begin problem escalation
26 Application Server A Send acknowledgment to Site B. Post Message to B's application server: ES_MSG_TA_REMOTE_COMPLETION
27 Application Server A Remove LOCAL_WORK record
28 Application Server B Update the problem's CURRENT_SITE to Site A
29 Application Server B Update Audit Trail to reflect successful transfer
30 Application Server B End problem escalation
31 Application Server B Remove REMOTE_WORK and REMOTE_TASKS records