Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Problem: Assume that the JOC Cockpit uses a Controller registered as a Standalone Controller. If the same Controller is registered as a Controller Cluster member then the JOC Cockpit throws an error such as
    • JocObjectAlradyExistException: com.sos.joc.exceptions.JocObjectAlreadyExistExceptionJocObjectAlreadyExistException: Controller(s) with id 'controller' already exists exists 
    • This error message is available from the JOC Cockpit's log file too, e.g. from the JS7_JOC_DATA/logs/joc.log file, see JS7 - Log Files and Locations.
  • SolutionIt is not possible to register the same Controller twice, as a Standalone Controller and as a Controller cluster.

...

  • Check that you have a license key ready as the clustering for Controllers is available for a commercial license, see JS7 - LicensingLicense.
  • Verify that execution of workflows is completed with the Standalone Controller and that no orders are running.
  • Remove the Standalone Controller from the JOC Cockpit GUI.
  • Shutdown the Standalone Controller and remove the Controller's journal files in its JS7_OONTROLLER_DATA/Statestate directory.
  • Follow the steps from the JS7 - Initial Operation for Controller Cluster article.
  • Redeploy the scheduling objects such as workflows from JOC Cockpit to the Controller Cluster.

...

...