In a remote configuration service (RCS, aka supervisor), the supervising JobScheduler contains a central configuration directory (generally named remote) for transport (push) JobScheduler object files to the workload schedulers (JWS). The objects, which has to be deployed, are stored in the subfolders of the folder named remote of the config folder of the supervising JobScheduler. There is a subfolder named "_all" which content will be pushed to all connected JWS and another subfolder which name is created in the form <servername>#<portnumber>, which content is pushed to the JWS running on <servername> and listening on <portnumber>. For every JWS a subfolder is expected and must be created.
In the configuration of a JWS the adress of the RCS has to be customized. Once a workload scheduler is started, it send a register message to the RCS via TCP/IP. The RCS then sends the actual configuration objects from the RCS's remote directory with an internal scheduler command via TCP/IP to the JWS. The RCS tehn transfer the objects to the folder cache in the config folder of the JWS.
Whenever a configuration file is changed in the remote directory of the RCS, it sends a message via UDP to all JWS's to signal them that the configuration has changed.
Sometimes the signalling to the JWS's does not work, because the UDP port (or UDP in general) is blocked by the firewall of the server, where the JWS is running. In JobScheduler versions older than 1.3.9 this is not noted in the scheduler log file.
With releases 1.3.9 and newer a warning message is shown in the scheduler log, if it is not possible for the RCS to send the 'configuration is changed' signal via UDP to a JWS:
- SCHEDULER-474 Workload scheduler is not responding to UDP message since 2010-09-09 14:28:50.000 UTC (72s). Workload scheduler's configuration can not be updated.]
There is a panel in JOC where all the connected JWS are listed.
See also
- [Remote Configuration Service Docu/scheduler.doc/central_configuration.xml]