Multiple server deployment

You can implement a multiple server deployment by reusing existing components or by installing all new components.

You can simplify the deployment by installing all new components with the Control Desk middleware and product installation programs. If you plan to reuse or migrate resources that exist in your network, adjust your rollout plan to allow time for additional tasks. For example, you must bring the existing resources to version levels that are compatible with Control Desk.

The required components for Control Desk are all installed on different servers.

Important: In certain cases, you must avoid the sharing of resources. For example, do not share one DB2® database instance between Control Desk and IBM® Security Directory Server. During installation, the database instance is restarted, which can disrupt the availability of IBM Security Directory Server for your enterprise.

In a disparate environment, the collection of servers can be a combination of Windows and UNIX servers.

You can create deployment managers that provide centralized administration of managed application servers. Basic caching support is provided, which includes work balancing, performance optimization, and centralized management and monitoring.

With WebSphere® Application Server Network Deployment, you can manage nodes as a single cell. WebSphere Application Server Network Deployment also provides clustering support and automated performance optimization. A cluster groups similar functions on two or more Java™ virtual machines (JVMs) to process a single function, such as scheduled cron tasks. Clusters connect to the same database but operate independently. For example, if the cron task cluster fails, users can still connect to the user interface cluster.

Feedback