Deployment scenarios
Deployment scenarios are summaries of product deployment tasks.
- Scenario 1: Deploying with automatic middleware configuration
- Scenario 2: Deploying automatically reusing existing middleware
- Scenario 3: Deploying manually reusing existing middleware
- Scenario 4: Deploying automatically in a cluster environment.
In scenarios 2 and 3, you reuse existing middleware installations as Control Desk components. For example, you might have an existing instance of a database. This instance might be hosted in an existing database server farm. Corporate access policies, redundancy measures, and backup plans might affect how you deploy software in your organization.
If you plan to reuse existing middleware, ensure that they are at the level supported by Control Desk. The installation program does not provide a mechanism for updating servers with unsupported versions of middleware. The installation program does not provide remote prerequisite checks to ensure that they are at the correct level. Use the prerequisite checking tool provided with the product.
Scenario 1: Deploying with automatic middleware configuration
In this scenario, you deploy this product in a new environment. You use the Control Desk installation programs and tools to install and automatically configure new installations of middleware and the product.
Oracle WebLogic Server must still be configured manually.
You can use the Control Desk installation program to install DB2®, for example, and use the Control Desk configuration program to automatically configure it.
This scenario is useful for setting up a demonstration environment.
Scenario 2: Deploying automatically reusing existing middleware
In this scenario, you deploy this product with middleware that exists in your enterprise. You use the product installation programs and tools to automatically configure your middleware. This scenario is applicable in situations where you already have existing middleware resources established in your enterprise.
Oracle WebLogic Server must be configured manually, but you can use the Control Desk installation program to automatically configure an existing database, for example.
This scenario is intended for experienced database and application server administrators only.
Scenario 3: Deploying manually reusing existing middleware
In this scenario, you deploy Control Desk with middleware that exists in your enterprise, and you manually configure that middleware. This scenario is applicable to those situations in which you have existing middleware resources. You might have particular company-sanctioned processes and regulations that restrict your use of automated configuration tools when you are deploying a new application. All manual middleware configuration information is contained in this scenario.
This scenario is intended for experienced database and application server administrators only.
Scenario 4: Deploying automatically in a cluster environment
In this scenario, you deploy Control Desk into a clustered environment that you configure. You use the product installation programs and tools to automatically configure your middleware.
This scenario is intended for knowledgeable application server administrators with experience planning and creating cluster environments in IBM® WebSphere® Application Server.