Configuration program overview

Use the configuration program to configure Control Desk and associated middleware.

Note: In this documentation, the configuration program referred to is Tivoli's Process Automation Suite Configuration program.
The configuration program is used to perform the following configuration tasks:
  • Prepare IBM® WebSphere® Application Server for configuration of your product
  • Configure Control Desk deployment
  • Configure Control Desk to point to an existing Maximo configuration
  • Update database access credentials
  • Change the Control Desk security model
  • Change the database server host
  • Update IBM WebSphere Application Server access credentials
  • Change IBM WebSphere Application Server host
  • Update database and build and deploy application EAR files
  • Install product help information in another language
  • Remove IBM WebSphere Application Server configuration
  • Remove Control Desk configuration

The Control Desk configuration program records configuration choices that you make about your Control Desk deployment and then deploys Control Desk based on the information that you entered.

Figure 1. Control Desk configuration program

Information that you enter for the configuration program is stored in the maximo.properties and install.properties files. Some of this information is also written to the Maximo® database. These values are displayed in the panel fields of the configuration program during an upgrade or fix pack application.

The configuration program validates the values that you enter in configuration item fields. Some configuration item fields are validated as a pair, for example, user name and password fields.

In most cases, you can run the configuration program locally or remotely. You are required to run the configuration program locally on the IBM WebSphere Application Server server when you are preparing it for Control Desk configuration.

The configuration program cannot automate the configuration of Oracle WebLogic Server.

If you choose not to have the configuration program automatically configure middleware, you must configure that piece of middleware manually before the configuration of Control Desk.
Note: If you are using a directory server to secure Control Desk, be aware of the product-specific syntax rules for using special characters in LDAP strings that you enter. In most cases, special characters must be preceded by an escape character to make them readable by the directory server. 

Many directory server products consider a blank space to be a special character in an LDAP string. If you enter an LDAP string with an unescaped blank character at the end of a field value, you encounter Control Desk errors.

For more information about special character usage in LDAP strings, see the product documentation for your directory server.