Introduction

• Initial Operation is performed after installation of JS7 Controller, Agent and JOC Cockpit, see JS7 - Initial Operation
• In case there are issues while registering the Controllers then the Controller cannot orchestrate the job-related configuration to Agents. Also, the Controller is used for the execution of workflows that include jobs running on a number of Agents as switching of Agents during workflow execution is performed by the customer.

• , it throws the error 021-09-21T11:21:49,764 ERROR js7.common.system.startup.JavaMain - No license for js7.controller.cluster 
  js7.base.problem.ProblemException$NoStackTrace: No license for js7.controller.cluster in the controller log file. 

Troubleshooting

On registering the Controller the status of the Controller can be checked either from the JOC Cockpit Dashboard. While registering a Controller the following issues can be faced:

1. When the same Controller is used as Standalone Controller and as a member of Controller Cluster:
   1. Problem: The JOC Cockpit has a Controller registered as a Standalone Controller in the JOC Cockpit. The same Controller is used to be registered as a Controller Cluster member then the JOC Cockpit throws an error as JocObjectAlradyExistException: com.sos.joc.exceptions.JocObjectAlreadyExistException: Controller(s) with id 'controller' already exists in the $JETTY_BASE/logs/joc.log file.
   2. Solution: This is not possible as the same Controller cannot be registered twice, as a Standalone or as a Controller cluster.
      
      
2. Controller with different Controller Id's are used as a Controller Cluster:
   1. Problem: : If the Controller with different controller ID's are registered as Controller Cluster then then the registering of Controller will not be successful and will throw an error in  is a error in $JETTY_BASE/logs/joc.log file as joc.log ControllerInvalidResponseDataException:  
      com.sos.joc.exceptions.ControllerInvalidResponseDataException: The cluster members must have the same Controller Id: http://<host1>:<port1> -> controller_ID1, HTTP://<host2>:<port2> -> controller_ID2.
   2. Solution:  It is not possible to register Controllers with different Controller ID's to work as a Controller Cluster.
      
      
3. While configuring the Controller Cluster if the license is not added:
   1. Problem: Configuring a Controller Cluster requires a license. It is not possible to have a Cluster configured without the license. In case the license is missing from the controller while configuring then the $SCHEDULER_DATA/logs/controller.log will throw error as js7.common.system.startup.JavaMain - No license for js7.controller.cluster js7.base.problem.ProblemException$NoStackTrace: No license for js7.controller.cluster.
   2. Solution: If the license is not added at the time of installation then it is possible to add the license after the installation also. Stop the services of the Controller and follow the article JS7 - FAQ - How to apply a JS7 License Key to add a license to a Controller.