Introduction

The Controller ID is a unique identifier for a Standalone Controller or Controller Cluster.

The identifier is specified during installation and cannot be modified. Therefore the procedure to modify a Controller ID for an existing installation implies a number of steps.

Modifying Controller ID

Prerequisites

Check that no jobs are running. Orders should be completed, workflows will not pick up from a given job step when applying the procedure.

Controller

If a Controller Cluster is used then the following steps apply to both Controller instances.

  • Shutdown the Controller.
  • Drop the Controller's journal by deleting the contents of the <controller-data>/state directory.
  • Modify the Controller's <controller-home>/bin/controller_instance.sh|.cmd instance start script.
    • Modify the following environment variable to hold the new Controller ID:
    • JS7_CONTROLLER_ID=<controller-id>
  • Start the Controller.

JOC Cockpit

Navigate to the Manage Controllers/Agents page:

  • Delete the existing Controller configuration. This will delete the configuration of a Controller and any Agents assigned.
  • Add the Controller as explained with chapter Initial Operation of the following articles:
  • Add Standalone Agents and/or Cluster Agents.
  • Deploy Agents using the Deploy operation of the related Agent's action menu or select Agents and apply the related bulk operation.
  • Initialize Agents using the Reset Forced operation of the related Agent's action menu or select Agents and apply the related bulk operation.
    • This will force Agents to restart and to drop their journal in the related <agent-data>/state directory.
    • It can take the Controller approx. 60-120s to reconnect to Agents. 

Navigate to the Configuration view:

  • Re-deploy Controller objects such as Job Resources, Workflows etc.
    • The Deploy operation is available from any folder level in the inventory.
    • It is not required to re-release automation objects such as calendars, schedules etc.

Navigate to the Daily Plan view:

  • Cancel any orders in the submitted state. Orders will assume the planned state.
    • The GUI allows to filter display to submitted orders.
    • The operation can be performed day by day using the calendar widget in the view.
    • The operation can be performed by use of the Advanced Filter for a number of days: search for submitted orders for some longer future, select all orders and apply the cancel bulk operation.
  • Submit planned orders.
    • It is required to re-submit orders for the current day and for the next day. For further days orders will be submitted automatically by the JS7 - Daily Plan Service.



  • No labels