| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Deployment
- In a remote configuration service (RCS
...
- )
...
- the supervising JobScheduler
...
- manages a central configuration directory (generally named remote) for transport (push) of JobScheduler object files to the
...
- Workload JobSchedulers (JWS).
- The objects
...
- that have 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
...
- the content of which
...
- will be pushed to all connected JWS
...
- .
- Tehre could be other subfolders with a name that is created from <servername>#<portnumber> the content of which is pushed to the JWS running on <servername> and listening on <portnumber>. For every JWS a subfolder is expected and
...
- has to be created.
- In the configuration of a JWS the
...
- address of the RCS has to be customized.
- Once a
...
- Workload JobScheduler is started, it
...
- sends a
...
- registration message to the RCS via TCP/IP.
- The RCS then sends the
...
- current configuration objects from the RCS's remote directory with an internal
...
- command via TCP/IP to the JWS.
- The RCS
...
- then transfers 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
...
- to signal
...
- that the configuration has changed.
- Sometimes the signalling to the JWS
...
- might not work
...
- due to the UDP port (or UDP in general)
...
- being blocked by
...
- a firewall of the server, where the JWS is running.
- In JobScheduler versions older than 1.3.9 this is not
- a firewall of the server, where the JWS is running.
...
- logged to the
...
- JobScheduler log file.
- With releases 1.3.9 and newer a warning message is
...
- added to 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.]
- added to scheduler.log, if it is not possible for the RCS to send the 'configuration is changed' signal via UDP to a JWS:
- There is a panel in JOC where all the connected JWS are listed.
See also
- [Remote Configuration Service Docu/scheduler.doc/central_configuration.xml]