BMC Virtual Agent deployment

The following diagrams provide a starting point for planning your installations.

For more information about BSM deployment scenarios and recommendations, see Deployment architecture and Performance benchmarks in the BMC Remedy IT Service Management online documentation.

Typical deployment (non-server group)

The following diagram illustrates a small, medium, or large deployment that does not use AR System server groups. You need to install BMC Virtual Agent twice, as shown in the following diagram:

• On the Mid Tier server 
• On the BMC Remedy AR System server

Server group deployment 

An AR System server group consists of two or more AR System servers that share the same database and are designated to be part of a server group. AR System server groups can be used to provide scalability, load balancing, and fail-over operations.

You need to install BMC Virtual Agent at least three times, as shown in the following diagram:

• On all BMC Remedy Mid Tier servers
  If you have multiple Mid Tier servers, you have to install BMC Virtual Agent on each. 
• On the primary BMC Remedy AR System server
• On any secondary BMC Remedy AR System server

Proof-of-concept deployment 

The following diagram illustrates a generic, proof-of-concept (POC) deployment suitable for a small number of users. This is not a typical deployment scenario for production use. BMC Remedy AR System, BMC Remedy Mid Tier, BMC Atrium Core, and BMC Remedy IT Service Management are installed on the same server. You need to install BMC Virtual Agent on the Mid Tier/BMC Remedy AR System server, as shown in the following diagram.