Architecture

There are two distinct architectures for Server Automation. The older Server Automation architecture is based on the BigFix architecture. The only additional component the older architecture required to use Server Automation is the Automation Plan Engine. The older architecture is supported by Server Automation versions upto 9.5.70. The newer Server Automation architecture is supported by Server Automation versions above 9.5.72. The newer architecture has been designed keeping redundancy, reliability, distributive load sharing, performance, and scalability in mind.

Server Automation using Automation Plan Distribution Service & Automation Plan Engine (Multinode) in BigFix

Attention:
  • This architecture is only applicable for versions above Server Automation version 9.5.72. For versions below Server Automation version 9.5.70, only the old architecture is applicable.
  • This performance optimization is entirely server-side. Therefore, to enhance client-side performance, include specific target endpoints in the plan configurations to avoid client serialization.
The following diagram shows the BigFix architecture with the Server Automation component displayed in red. Server Automation is a BigFix application, similar to the other Lifecycle applications. You access and use Server Automation using the BigFix console. Thise new architecture has been designed keeping redundancy, reliability, distributive load sharing, performance, and scalability in mind.
Diagram depicting the new BigFix architecture with Server Automation components Automation Plan Distribution Service and the Automation Plan Engine (Multinode).

In this architecture, you require two different components for Server Automation to function properly. They are the Automation Plan Distribution Service and Automation Plan Engine (Multinode). The Automation Plan Distribution Service and the Automation Plan Engine (Multinode) have a parent-child relationship, with the Automation Plan Distribution Service fulfilling the role of the parent. The Automation Plan Distribution Service plans and distributes all the tasks to the various Automation Plan Engine (Multinode)s for their execution.

Remember: The number of plan engine instances are determined by the plan's batch size. It is recommended to start with 2 nodes, then evaluate the overall performance. Add additional instances only if they are necessary.
Remember: A client machine's hardware configuration (vCPU) for the plan engine instances should be uniform, as the load is equally distributed across the nodes. Each plan engine instance should ideally have a minimum of 8 cores for optimal performance.

In this architecture, if one of the Automation Plan Engine (Multinode) node goes down, its allocated work is distributed equally among the remaining Automation Plan Engine (Multinode) nodes. In this way, the new Server Automation architecture achieves reliability and distributive load sharing. This ensures that there is minimal impact to Server Automation operations and performance.

Lastly, using this architecture, you can achieve scalability by increasing the number of Automation Plan Engine (Multinode)s. You can scale-up or down the Automation Plan Engines depending on the number of endpoints you need to manage.

The BigFix server and the Automation Plan Distribution Service must be installed on the same machines. The Automation Plan Engine (Multinode), on the other hand, can be installed on both root and relay machines.

Server Automation with Automation Plan Engine (Single node) integrated in BigFix

Attention:
  • This architecture is only applicable for versions upto Server Automation version 9.5.70. From Server Automation version 9.5.72 onwards, the new architecture is applicable.
  • Users who choose to remain on the older single-node architecture can still upgrade to the new architecture with a single node to gain the following benefits:
    • The Plan Engine can now be deployed on any client machine, separating it from the root services. This reduces the risk of resource constraints.
    • All future updates, whether functional, security-related, or performance-based will be delivered exclusively on the new architecture.
The following diagram shows the BigFix architecture with the Server Automation component displayed in red. Server Automation is a BigFix application, similar to the other Lifecycle applications. You access and use Server Automation using the BigFix console.
Diagram depicting the BigFix architecture with Server Automation component installed. Server Automation adds the Automation Plan Engine (Single node) and the BigFix server plug-in service is required on the BigFix server.
The Automation Plan Engine (Single node) communicates with the BigFix server via the REST API. The BES server plug-in service is required on the BigFix server. Server Automation requires no additional components. Server Automation can operate with or without relays.

For information about configuring the BES server plug-in service, see Server plugin service configuration.