Platform Agent High Availability

on-site-related topic

Note: This topic describes configuring Platform Agents for high availability in SaaS installations. For on-premises installations, see Configuring Platform Agents for High Availability.

To integrate Platform Agents into high-availability clusters:

  • Install the Platform Agent on a SAN drive.
  • Make sure all failover servers use the same port, shared secret, and hostname.

Note: When you update Platform Agents on Microsoft Windows, you may have to adapt the binary paths in your cluster software, depending on the solution you are using. On UNIX, this is solved with the latest symbolic link.

Note: For Microsoft Cluster Service implementations, see Configuring Web Application Clusters for High Availability.

Procedure

The procedures below describe setting up High Availability Platform Agents in a clustered environment.

UNIX

Warning: Make sure only one of the Platform Agents is running at any given time. If not, multiple Platform Agents may try to connect to the Process Server at the same, potentially causing issues.

  1. Install the Platform Agent on node 0 of a shared SAN file system.
  2. On node 1, configure the system to start the Platform Agent using the platform-specific startup mechanism. You can use the same script as used for node 0.
  3. Optionally, configure cluster software to control the startup script of the Platform Agent.
  4. Make sure the following files are the same on both nodes:
    • <installdir>/net/instance/<instance>server_acl
    • <installdir>/net/instance/<instance>/agent_initiated_url
  5. Adapt the RemoteHostNameWhitelist Process Server Parameter so that the hostnames and IP addresses from both nodes are included.
  6. Keep in mind that failover on the RunMyJobs side happens after a five-minute delay.

Windows Using MSCS

Warning: Make sure only one of the Platform Agents is running at any given time. If not, multiple Platform Agents may try to connect to the Process Server at the same, potentially causing issues.

  1. Install the Platform Agent on node 0 of a shared SAN file system.
  2. On node 1, is start servicemanager.exe and create a service for the Platform Agent.
  3. Optionally, configure cluster software to control the startup script of the Platform Agent.
  4. Adapt the RemoteHostNameWhitelist Process Server Parameter so that the hostnames and IP addresses from both nodes are included.
  5. Control Platform Agent services from within the MS Cluster.
  6. Keep in mind that failover on the RunMyJobs side happens after a five-minute delay. During this time, the Process Server is in status Bonded. To speed up this process, restart the Process Server.