Deployment topologies

Determine the most suitable deployment option for your environment and business needs.

Deployment types

Control Desk works with various databases and J2EE server software, as listed in the system requirements information.

You use the Control Desk installation program to install IBM® middleware products. You can also reuse existing resources in your environment, which can include supported versions of both IBM and non-IBM middleware.

Although IBM middleware is included with Control Desk, you can deploy Control Desk with non-IBM middleware exclusively.

There are two primary strategies to deploying Control Desk in your enterprise.

Single-server

The single-server topology consists of loading all Control Desk components, including all Control Desk middleware, the Control Desk administrative workstation, process managers, and other components, onto one server. This deployment is typical for proof-of-concept purposes, as a demonstration, or to create a learning environment. For managing enterprise assets and processes, you would typically implement a multi-server topology.

Multi-server

The multi-server topology consists of splitting Control Desk components across several different servers. This method is beneficial, as it optimizes resource use and decreases the workload for each system. This type of deployment would be typical for production use within an enterprise.

In a disparate environment, the collection of computers in this deployment can be a mixture of Windows and UNIX computers.

In IBM WebSphere® Application Server Network Deployment, you can create deployment managers that provide centralized administration of managed application server nodes and custom nodes as a single cell. IBM WebSphere Application Server Network Deployment provides basic clustering and caching support, including work balancing, automated performance optimization, and centralized management and monitoring.

The Oracle WebLogic Server configuration requires, at a minimum, a single administration server on a single computer.

A typical deployment lifecycle can begin with a single-server topology and progress to a multi-server topology. This progression can occur if you start with a demonstration phase and then move onward to a functional proof-of-concept. Next, you test the integration in the existing environment and move toward a pilot multi-server environment. Finally, you move to a multi-server production deployment in the enterprise.

Control Desk is built upon the process automation engine. The process automation engine is a core set of functions used by Integrated Service Management (ISM) products. It serves as a common base for shared services and applications inherited by all Control Desk based products. Process managers are workflow-based applications that you can use to create executable process flows.

Process managers provide a user interface that can be used to:

Perform process procedures
Gather information from various sources
Interact with external tools
Use and update information in a database
Provide information to monitoring, analysis, and reporting tools

In addition, you can track execution metrics and use dashboards and reports to identify bottlenecks and improve organizational productivity.

Administrative workstation

You install Control Desk on an administrative workstation that is running a UNIX or Windows operating system. The administrative workstation is where the product EAR files are built and later deployed to the application server.

The administrative workstation is used in all phases of the product life cycle. It is required for the initial installation and configuration of Control Desk. You also use the administrative workstation to install program fixes, product upgrades, new applications, new process managers, and additional language packs.