Versions Compared

Key

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

...

The Agent Batch/Update solution comes with a job chain in JobScheduler. It is available starting with release 1.3.10.

The Job AgentBatchInstaller reads a xml configuration file and creates orders for the job chain to setup/update agents. For each agent there is an entry in the configuration file.

The job chain for update/installation of one agent has the four nodes:

  • TransferInstallaionSetup: To transfer the setup jar file to the host
  • TransferInstallationFile: To transfer the generated xml setup file to the host
  • ShutdownScheduler: To shutdown Job Scheduler if running using ssh.
  • PerformInstall: To start the installation using ssh.

You will find the xsd-schema for the configuration in config/scheduler_agent_installations.xsd

...

The global sections have the following entries:

  
serviceId

...

The

...

JobScheduler ID of the agent. This ID must be unique. You get a unique value by adding host and port to the value of the

...

ID.
licence

...

The license key for the agent. Use the same key as you have used for your main JobScheduler. If you are using the GPL license

...

, copy your default license key from the main JobScheduler sos.ini file into the sos.ini file

...

for the agent.
servicePort

...

The port, the agent is listening. For example 4445. You can use the same port for each agent on different hosts.
serviceAllowedHost

...

The IP address or the host name of the

...

Master JobScheduler.
installPath

...

The path to install the agent. Recommended value

...

: /opt/sos-berlin.com/jobscheduler.
UserPathPanelElement

...

The path with the configuration files of the agent. Recommended value

...

: /home/

...

<user>/sos-berlin.com/jobscheduler
ftp

...

Specifies the ftp

...

file transfer protocol.
ftp.user

...

The user for the ftp login.
ftp.password

...

The password for the ftp login.
ftp.localDir

...

The location of the setup files.This is scheduler_agent.jar and the generated xml installation files.
ftp.remoteDir

...

The location on the server where the setup files should be transferred.
ftp.port

...

The port for the ftp connection. Default

...

value: 21.
ssh

...

Specifies the ssh connection.
ssh.user

...

The user for the ssh login.
ssh.password

...

The password if using password authentication.
ssh.sudoPassword

...

The password for the sudo user. This can be used in the command to enable the sudo login.
ssh.authMethod

...

The authentication method can be password or publickey.
ssh.authFile

...

The authorization file with the key if authMethod is publickey.
ssh.port

...

The port for the ssh connection.

...

Default value: 22.
ssh.command

...

The command to perform the installation. The recommended command is:

 echo ${sudo_password} | sudo -S java -jar ${ftp_remote_dir}/scheduler_linux32_agent.jar ${ftp_remote_dir}/${installation_file}

 

Example for xml configuration file:

...