Planning HAC Nodes and HAC Users

Use

High Availability Controller (HAC)

High Availability Controller (HAC) manages and controls the BCM system where the actual software packages are installed in virtual units on different servers. Each server requires a HAC node, and do not have more than one HAC node on one server. Each HAC node can belong to one system model only.

To acquire maximum safety:

  • Define HAC Server Connection Certificates for HAC nodes. Acquire the appropriate certificates and configure them in the IA tool when installing HAC nodes.

  • Define User Connection Security Certificate for the administrative workstation. Acquire the appropriate certificate and configure it in the IA tool when installing HAC nodes.

  • Define Windows user accounts without any rights to be used as HAC Administrators and HAC View-Only Users. Each user must have a specific user account, otherwise it is not possible to trace who did what changes. As of SP09, you can enter also Active Directory user groups.

  • Do not allow the communication between HAC nodes (HAC-HAC communication) to be reached from outside the server network, and separate this communication from the administration communication (HAC-IA communication).

Procedure

  1. Plan how the virtual units that include the actual software packages are distributed on servers.

  2. Plan users with different using rights:

    • HAC Administrators with rights to create, edit, start and stop system model.

    • HAC View-Only Users that can create and edit system model but cannot start or stop it.