Deployment scenarios

This topic illustrates typical scenarios for deploying BladeLogic Portal.

The number of concurrent end users determines how many BladeLogic Portal components you must actually deploy. To determine what size deployment is appropriate for your needs, see this sizing matrix, which also provides minimum hardware requirements for the servers where you are installing additional components. 

The portal's installation program can install a single BladeLogic Portal server or a single DCA Index Server or it can install both on the same machine (known as a compact deployment). Larger organizations should segregate the BladeLogic Portal server and the DCA Index Server onto separate nodes. If additional capacity is necessary, you can install additional instances of the BladeLogic Portal server and DCA Index Server.

This topic includes the following sections:

• • Large deployment
  • Medium deployment
  • Small deployment
  • Compact deployment

Large deployment

A large deployment of BladeLogic Portal allows up to six instances of BladeLogic Portal servers to integrate with up to six instances of DCA Index Servers. The portal servers employ a single database and rely on one or more BMC BladeLogic Server Automation and BMC BladeLogic Network Automation Application Servers.

Medium deployment

A medium deployment consists of two BladeLogic Portal servers and two DCA Index Server, all installed on separate hosts. This type of deployment employs a single database and relies on at least one BMC BladeLogic Server Automation or BMC BladeLogic Network Automation Application Server, although you can potentially access many different Application Servers.

Compact deployment

The BladeLogic Portal installation program creates a compact deployment. A BladeLogic Portal server and a DCA Index Server are both installed on the same machine, although each runs in a separate Java virtual machine (JVM).

A compact deployment employs a single database and relies on at least one BMC BladeLogic Server Automation Application Server, although you can potentially access many different Application Servers.

Typically, a compact deployment is used for testing and demonstration rather than production purposes.