zato create scheduler

Overview

Creates a new scheduler instance and makes it join a Zato cluster.

If the scheduler is to run in the same Linux instance as one of the servers, only server path option is required on input.

• --server-path

If the scheduler is to run on a Linux instance that is not shared with a Zato server, the options below should be used.

• --server-host
• --server-port
• --odb-type
• --odb-host
• --odb-port
• --odb-db-name
• --odb-user
• --odb-password
• --secret-key

Note that, within the same cluster, the --secret-key parameter must be the same as one used with the create server command. In other words, all the servers and the scheduler must use the same secret key.

Use the zato start command to start the schedule afterwards.

Usage examples

In the first example, the scheduler is being installed in the same Linux system as one of the servers which means that it suffices to provide a path to the server on input. The "create scheduler" command will then reuse the connection parameters that the server already keeps in its configuration files.

$ zato create scheduler \
    ~/prod3/scheduler \
    --server-path /path/to/server
OK
$

In the second example, the scheduler will run in its own Linux instance which means that all the connection parameters and details need to be provided explicitly on input.

Note that the address to a server can be provided using a DNS entry, rather than IP, which means that it is possible for servers in a cluster to be added or removed dynamically in runtime and the scheduler will know how to find one through DNS.

The server does not need to be running at the time when the "create scheduler" commands runs.

$ zato create scheduler \
    ~/prod4/scheduler \
    --server-host my.server.consul \
    --server-port 17010 \
    --odb-type mysql
    --odb-host 10.151.17.19 \
    --odb-port 3306 \
    --odb-db-name mydb \
    --odb-user myuser \
    --odb-password ... \
    --secret-key ...
OK
$