Distributed Data Manager Bulk Problem Transfer Transaction


Overview

Included with

Tivoli Problem Management administration

Overview

Bulk problem transfer transaction The following table lists the tasks for a bulk problem transfer to a remote site.

Task System Process
1 Client A For each problem in the Bulk Transfer:
  • Create REMOTE_WORK record:
    RW_BULK_PROBLEM_TRANSFER
  • Create REMOTE_TASKS record for Site A for each REMOTE_WORK record created above. The CONTROL_TIME is set to 1, so the application server will process each of these tasks as "missed" tasks.
  • Set the problem's CURRENT_SITE to (PEND)
2 Client A Post Message to A's application server: ES_MSG_TA_OUTGOING_WORK
3 Application Sever A Read REMOTE_WORK and REMOTE_TASKS records
4 Application Sever A Create "Sent" Audit Trail record
5 Application Sever A Package problem ticket data
6 Application Sever A Post Message to B's application server: ES_MSG_TA_PROBLEM_TRANSFER
7 Application Server B Create LOCAL_WORK record
8 Application Server B Unpackage problem ticket data
9 Application Server B Create problem transfer data
10 Application Server B Notify recipient if appropriate
11 Application Server B 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
12 Application Server B Begin problem escalation
13 Application Server B Send acknowledgment to Site A. Post Message to A's application server: ES_MSG_TA_REMOTE_COMPLETION
14 Application Server B Remove LOCAL_WORK record
15 Application Sever A Update problem's CURRENT_SITE to Site B
16 Application Sever A Update Audit Trail to reflect successful transfer
17 Application Sever A End problem escalation "Update owner on Problem Transfer in on
18 Application Sever A Remove REMOTE_WORK and REMOTE_TASKS records