← Configuring Web Application Clusters on Microsoft Cluster ServiceConfiguring Platform Agents on Microsoft Cluster Service →

on-site-related topic Configuring Platform Agents for High Availability

Integrating platform agents in high availability clusters is straight forward, in theory:

  • you install the software on a SAN drive
  • all fail-over servers must use the same port/SharedSecret/hostname
note

When you update platform agents on Microsoft Windows, you might 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.

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

Procedure

UNIX

  1. Install the platform agent on the first node on 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. Update process server parameter RemoteHostname to the FQDN of the cluster.
  4. Optionally, configure cluster software to control the startup script of the platform agent.

Windows using MSCS

  1. Install Platform Agent on node 0 as usual on a shared SAN file-system.
  2. On node 1 is start the servicemanager.exe and create a service for the platform agent.
  3. Update process server parameter RemoteHostname to the FQDN of the cluster.
  4. Control platform agent services from within MS Cluster.

See Also

onsiteTopic

← Configuring Web Application Clusters on Microsoft Cluster ServiceConfiguring Platform Agents on Microsoft Cluster Service →