Allocating the BMC Server Automation infrastructure

Depending on how many infrastructure servers are available to install against, the following describes how you should separate the different components. The Five Server Setup is the most recommended, while the One Server Setup is the least. Any of these servers can be virtual, but note that making either the Application Server or the Database virtual will cause performance degradation.

The following sections discuss how to split up the mid-tier parts of the infrastructure depending on how many servers can be allocated for the infrastructure.

Five Servers

The following is the most ideal scenario, as it separates the infrastructure into five logical areas.

Server Title	Components	Description
Application Server / File Server	BladeLogic Application Server DHCP Network Shell (NSH) RSCD Agent (Application Server management agent) 2nd RSCD Agent (Non-Windows Only / for File Server)	This server is the primary BladeLogic application server.
Provisioning Server	PXE Server TFTP Server Data Store Web Server (Typically Apache or IIS) Network Shell (NSH) RSCD Agent (File Server agent)
Reporting Server	BMC BladeLogic Decision Support for Server Automation RSCD Agent (ETL)
Client Server	RCP Server Automation Console Client	This server is where everyone logs in to BladeLogic.
Database Server	Database (Oracle or SQL Server)

Four Servers

This setup merges the Application Server with the Provisioning Server.

Server Title	Components	Description
Application Server / File Server / Provisioning Server	BladeLogic Application Server DHCP Network Shell (NSH) RSCD Agent (Application Server management agent) 2nd RSCD Agent (Non-Windows Only / for File Server) PXE Server TFTP Server Data Store Web Server (Typically Apache or IIS) Network Shell (NSH) RSCD Agent (File Server agent)	This server is the primary BladeLogic application server, and it also handles provisioning
Reporting Server	BMC BladeLogic Decision Support for Server Automation RSCD Agent (ETL)
Client Server	RCP Server Automation Console Client	This server is where everyone logs in to BladeLogic
Database Server	Database (Oracle or SQL Server)

Three Servers

This setup merges the Client server with the Application / Provisioning server.

Server Title	Components	Description
Application Server / File Server / Provisioning Server / Client Server	BladeLogic Application Server DHCP Network Shell (NSH) RSCD Agent (Application Server management agent) 2nd RSCD Agent (Non-Windows Only / for File Server) PXE Server TFTP Server Data Store Web Server (Typically Apache or IIS) Network Shell (NSH) RSCD Agent (File Server agent) RCP Server Automation Console Client	This server is the primary BladeLogic application server, handles provisioning, and is where everyone logs in to BladeLogic
Reporting Server	BMC BladeLogic Decision Support for Server Automation RSCD Agent (ETL)
Database Server	Database (Oracle or SQL Server)

Two Servers

This setup merges all the components while keeping the database separate. At this point performance will be a big issue, as the reporting server and application server both require a lot of server resources. Going with anything less than two servers is possible but performance will be the biggest issue.

Server Title	Components	Description
Application Server / File Server / Provisioning Server / Client Server / Reporting Server	BladeLogic Application Server DHCP Network Shell (NSH) RSCD Agent (Application Server management agent) 2nd RSCD Agent (Non-Windows Only / for File Server) PXE Server TFTP Server Data Store Web Server (Typically Apache or IIS) Network Shell (NSH) RSCD Agent (File Server agent) RCP Server Automation Console Client BMC BladeLogic Decision Support for Server Automation RSCD Agent (ETL)	This server is the primary BladeLogic application server, handles provisioning, and is where everyone logs in to BladeLogic. It is also used as the reporting server.
Database Server	Database (Oracle or SQL Server)

One Server

While storing all of the components on a single server is possible, you will most likely experience serious performance issues unless you have an extremely powerful physical server. This type of configuration is generally discouraged.