Procédure de traitement des cibles d'un opérateur › Exemple de reprise automatique des opérateurs

Exemple de reprise automatique des opérateurs

Si la récupération automatique des opérateurs est sélectionnée (par défaut), vous ne devez pas lancer la récupération. Chaque orchestrateur dans l'environnement détecte si l'agent ou l'orchestrateur est actif et lance la récupération. Chaque orchestrateur lance la récupération sur tous les points de contact, groupes d'hôtes ou orchestrateurs activés et mappés vers l'agent ou l'orchestrateur dans l'environnement.

Si un agent est mappé vers plusieurs points de contact, les orchestrateurs lancent la récupération sur tous les points de contact activés qui sont mappés vers l'agent. Lorsqu'un agent ou un orchestrateur devient actif, l'orchestrateur de domaine diffuse les changements aux autres orchestrateurs. Dans le cas d'une installation en cluster, seul le noeud principal exécute la récupération.

Exemple : Récupération automatique

Envisagez le scénario suivant, dans lequel un agent est mappé vers les points de contact et les groupes d'hôtes suivants dans un environnement :

• TP_user01-w500,
• TP_user01-w500_2
• TP_user01-w500_3
• TP_manyagents
• HG_user01-w500

Supposez que tous les points de contact et les groupes d'hôtes sont activés et que seuls les points de contact et les groupes d'hôtes suivants sont définis sur la récupération automatique des opérateurs :

• TP_user01-w500
• TP_user01-w500_3
• HG_user01-w500

Lorsque l'agent est actif, chaque orchestrateur dans l'environnement tente d'exécuter la récupération automatique sur les trois points de contact.

Supposez que deux orchestrateurs se trouvent dans l'environnement :

Contenu du fichier journal Orchestrator1 :

• Message signalant que l'agent est de nouveau actif :

  2010-06-28 19:22:59,984 DEBUG 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Checking whether to initiate Touchpoint/Orchestrator Recovery of 'System_Error' operators in 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set), that ran against Agent/Server ID: f3492322-5517-4a21-8a19-92838ccb3f65
  

• L'orchestrateur a mappé l'agent sur HG_user01-w500 :

  2011-03-28 19:22:59,984 INFO 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Initiating Touchpoint/Orchestrator: HG_user01-w500 Recovery... Recovering 'System_Error' Operators that ran against: HG_user01-w500 and belong to 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set).
  2011-03-28 19:22:59,984 DEBUG 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieve the processes (with enabled auto recovery flag) that are in 'Waiting' or ‘Running’ or 'Blocked' states and contain operators in 'System Error' when ran against: HG_user01-w500
  

• L'orchestrateur signale 0 processus à reprendre pour HG_user01-w500 :

  2011-03-28 19:23:00,000 WARN  
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 0 processes to recover for HG_user01-w500 recovery.
  2011-03-28 19:23:00,000 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Found no Processes to recover for Touchpoint/Orchestrator: HG_user01-w500 Recovery.
  

• L'orchestrateur a mappé l'agent sur TP_user01-w500 :

  2011-03-28 19:23:00,000 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Initiating Touchpoint/Orchestrator: TP_user01-w500 Recovery... Recovering 'System_Error' Operators that ran against: TP_user01-w500 and belong to 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set).
  2011-03-28 19:23:00,000 DEBUG 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieve the processes (with enabled auto recovery flag) that are in 'Waiting' or ‘Running’ or 'Blocked' states and contain operators in 'System Error' when ran against: TP_user01-w500.
  

• L'orchestrateur signale 1 processus à reprendre pour TP_user01-w500 :

  2011-03-28 19:23:00,015 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 1 processes to recover for TP_user01-w500 recovery.
  

• L'orchestrateur met en attente la demande de reprise du processus (ROID : 2889) pour TP_user01-w500 :

  2011-03-28 19:23:00,015 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Queueing recovery of process with ROID - 2889 for TP_user01-w500 recovery.
  2011-03-28 19:23:00,015 DEBUG 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Special Response for process recovery. ROID is 2889 UUID is 3fe95f08-a347-4d6d-a0a3-b3639836e130
  2011-03-28 19:23:00,015 DEBUG 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Special Response for process recovery was posted. ROID is 2889 UUID is 3fe95f08-a347-4d6d-a0a3-b3639836e130
  2011-03-28 19:23:00,015 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Queued requests for Touchpoint: TP_user01-w500 Recovery... Recovering Processes with the following ROIDs: 2889
  

• L'orchestrateur indique que le point de contact TP_user01-w500_2 est mappé vers l'agent, mais qu'il n'est pas défini sur la récupération automatique :

  2011-03-28 19:23:00,015 DEBUG 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Touchpoint: TP_user01-w500_2 mapped to Agent: f3492322-5517-4a21-8a19-92838ccb3f65 is not set to Automatic Recovery of 'System_Error' operators in 'Waiting' or ‘Running’ or 'Blocked' Processes.
  

• L'orchestrateur a mappé l'agent sur TP_user01-w500_3 :

  2011-03-28 19:23:00,015 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Initiating Touchpoint/Orchestrator: TP_user01-w500_3 Recovery. Recovering 'System_Error' Operators that ran against: TP_user01-w500_3 and belong to 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set).
  2011-03-28 19:23:00,015 DEBUG 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieve the processes (with enabled auto recovery flag) that are in 'Waiting' or ‘Running’ or 'Blocked' states and contain operators in 'System Error' when ran against:: TP_user01-w500_3
  

• L'orchestrateur signale 0 processus à reprendre pour TP_user01-w500_3 :

  2011-03-28 19:23:00,015 WARN  
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 0 processes to recover for TP_user01-w500_3 recovery.
  2011-03-28 19:23:00,031 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Found no Processes to recover for Touchpoint/Orchestrator: TP_user01-w500_3 Recovery.
  

• L'orchestrateur indique que le point de contact TP_manyAgents est mappé vers l'agent, mais qu'il n'est pas défini sur la récupération automatique :

  2011-03-28 19:23:00,031 DEBUG 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Touchpoint: TP_manyAgents mapped to Agent: f3492322-5517-4a21-8a19-92838ccb3f65 is not set to Automatic Recovery  of 'System_Error' operators in 'Waiting' or ‘Running’ or 'Blocked' Processes 
  

• L'orchestrateur retire la demande de reprise de la file d'attente pour le processus 2889 :

  2011-03-28 19:23:30,015 INFO  
  [com.optinuity.c2o.workflowengine.FlowManagerCache] [onPool Worker-3] Registering flow manager: 2889
  2011-03-28 19:23:30,015 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Handling Response: [$$TouchpointRecovery&&]. flow id is 2889
  2011-03-28 19:23:30,171 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Start Recovery of Process with ROID:2889, for TP_user01-w500 Recovery.
  

• L'orchestrateur redéfinit les opérateurs avec System_Error lors d'une exécution pour TP_user01-w500 dans le processus 2889 :

  2011-03-28 19:23:30,171 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Resetting System_Error Operators in Process with ROID: 2889 for TP_user01-w500 Recovery.
  2011-03-28 19:23:30,203 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Resetting Operator with ROID: 2912 in Process with ROID: 2889 for TP_user01-w500 Recovery.
  

• L'orchestrateur reprend la totalité du processus 2889 après avoir réinitialisé les opérateurs appropriés :

  2011-03-28 19:23:30,343 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Resuming Process with ROID: 2889 for TP_user01-w500 Recovery.
  2011-03-28 19:23:30,343 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Resuming WorkFlow - ROID is 2889
  2011-03-28 19:23:30,703 INFO  
  [com.optinuity.c2o.workflowengine.WorkflowManager] [onPool Worker-3] Done resuming Process with ROID: 2889 for TP_user01-w500 Recovery.
  

  Le processus 2889 est terminé. La récupération ayant été lancée automatiquement, les journaux de processus indiquent que le moteur a initialisé le processus. Si la reprise est manuelle, les journaux incluent le nom de l'utilisateur qui a lancé l'opération.

Le fichier journal Orchestrator2 (OrchestratorD610b) contient :

• Messages identiques à l'orchestrateur pour OrchestratorD610b :

  2011-03-28 19:23:41,444 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Initiating Touchpoint/Orchestrator: HG_user01-w500 Recovery. Recovering 'System_Error' Operators that ran against: HG_user01-w500 and belong to 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set).
  2011-03-28 19:23:41,444 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 0 processes to recover for HG_user01-w500 recovery.
  2011-03-28 19:23:41,444 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Found no Processes to recover for Touchpoint/Orchestrator: HG_user01-w500 Recovery...
  2011-03-28 19:23:41,444 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Initiating Touchpoint/Orchestrator: TP_user01-w500 Recovery... Recovering 'System_Error' Operators that ran against: TP_user01-w500 and belong to 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set).
  2011-03-28 19:23:41,444 WARN  
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 0 processes to recover for TP_user01-w500 recovery.
  2011-03-28 19:23:41,444 INFO 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Found no Processes to recover for Touchpoint/Orchestrator: TP_user01-w500 Recovery...
  2011-03-28 19:23:41,444 INFO 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Initiating Touchpoint/Orchestrator: TP_user01-w500_3 Recovery... Recovering 'System_Error' Operators that ran against: TP_user01-w500_3 and belong to 'Waiting' or 'Running' or 'Blocked' Processes (with auto recovery flag set).
  

• OrchestratorD610b trouve 1 processus à reprendre pour TP_user01-W500_3 (ROID : 541) et met la demande correspondante dans la file d'attente :

  2011-03-28 19:23:41,444 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 1 processes to recover for TP_user01-w500_3 recovery.
  2011-03-28 19:23:41,444 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Queueing recovery of process with ROID - 541 for TP_user01-w500_3 recovery.
  2011-03-28 19:23:41,444 INFO  
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Queued requests for Touchpoint: TP_user01-w500_3 Recovery... Recovering Processes with the following ROIDs: 541
  2011-03-28 19:23:41,444 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Retrieved - 1 processes to recover for TP_user01-w500_3 recovery.
  2011-03-28 19:23:41,444 WARN 
  [com.optinuity.c2o.workflowengine.C2oWorkFlowEngine] [aListenerThread] recoverSystemErrorProcesses: Queueing recovery of process with ROID - 541 for TP_user01-w500_3 recovery.
  2011-03-28 19:23:41,444 INFO 
  [com.optinuity.c2o.c2oserver.ServerManager] [aListenerThread] Queued requests for Touchpoint: TP_user01-w500_3 Recovery... Recovering Processes with the following ROIDs: 541
  

• OrchestratorD610b récupère la demande de récupération, réinitialise les opérateurs avec System_Error, qui ont été exécutés pour TP_user01-w500_3, dans le processus, puis reprend le processus :

  2011-03-28 19:24:11,461 INFO 
  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Handling Response: [$$TouchpointRecovery&&]. flow id is 541
  2011-03-28 19:24:11,804 INFO 
  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Start Recovery of Process with ROID:541, for TP_user01-w500_3 Recovery.
  2011-03-28 19:24:11,820 INFO 
  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Resetting System_Error Operators in Process with ROID: 541 for TP_user01-w500_3 Recovery.
  2011-03-28 19:24:11,883 INFO 
  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Resetting Operator with ROID: 564 in Process with ROID: 541 for TP_user01-w500_3 Recovery.
  2011-03-28 19:24:12,039 INFO 
  [com.optinuity.c2o.workflowengine.C2OSvcIconInstanceRefObject] [nPool Worker-63] Inside Update ConnectorTraversed, Current/destination is Start_System_Process_1 Source is Start_1
  2011-03-28 19:24:12,117 INFO 
  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Resuming Process with ROID: 541 for TP_user01-w500_3 Recovery.
  2011-03-28 19:24:12,117 INFO 
  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Resuming WorkFlow - ROID is 541
  2011-03-28 19:24:12,133 INFO 
  [com.optinuity.c2o.workflowengine.C2OSvcIconInstanceRefObject] [nPool Worker-63] Inside Update ConnectorTraversed, Current/destination is Start_System_Process_1 Source is Start_1
  2011-03-28 19:24:12,648 INFO  [com.optinuity.c2o.workflowengine.WorkflowManager] [nPool Worker-63] Done resuming Process with ROID: 541 for TP_user01-w500_3 Recovery.