Installation program tasks
The Control Desk installation program performs a series of configuration and deployment tasks when you instruct it to automatically configure middleware.
The following list details the steps taken by the Control Desk installation program during a typical installation. This information is provided so it can be reviewed in order to ensure that the Control Desk installation program is compliant with your corporate application deployment policy.
For applicable tasks, links are provided to manual configuration instructions if you plan to opt out of the automatic middleware configuration provided by the Control Desk installation program. In this case, these tasks must be completed before running the Control Desk installation program
| Task Category | Automated Installation Action | Description | Manual Instructions |
|---|---|---|---|
| Access | Database user created for DB2® | A system user named maximo by default is created on the DB2 server that are used to access the Maximo® database. This default value can be modified. | You can manually create this system user on the DB2 server before running the Control Desk installation program using the methods prescribed by your organization. |
| WebSphere® Application Server thin client | WebSphere Application Server thin client configuration | The keystore file is copied from the WebSphere Domain Manager to the Control Desk administrative system in order to establish communications between the two systems. | Instructions for manually copying the keystore
file from the WebSphere Domain
Manager can be found in the product installation information. Ensure that the SOAP port for the WebSphere Domain Manager is accessible by the Control Desk administrative system. By default, this port is 8879. |
| Database | Create a database instance | A new database instance is created for Control Desk on DB2 if one does not exist. | You can either reuse an existing database instance or create a database instance. Instructions for manually creating a database instance for DB2 can be found in the product installation information. |
| Database | Create a database instance | A new database instance is created for Control Desk on Oracle if one does not exist. | You can either reuse an existing database instance or create a database instance. Instructions for manually creating a database instance for Oracle can be found in the product installation information. |
| Create a database | A new database is created for Control Desk for DB2. | Instructions for manually creating a database for DB2 can be found in the product installation information. | |
| Create a database | A new database is created for Control Desk for Microsoft SQL Server. | Instructions for manually creating a database for Microsoft SQL Server can be found in the product installation information. | |
| Database user created for Oracle. | A database user named maximo by default is created for Oracle that is used to access the Maximo database. This default value can be modified. | You can manually create this system user on Oracle before
running the Control Desk installation
program using the methods prescribed by your organization. Information on granting permissions to the user for Oracle can found in the product installation information. |
|
| Database user created for Microsoft SQL Server. | A database user named maximo by default is created for Microsoft SQL Server that is used to access the Maximo database. This default value can be modified. | You can manually create this system user on Microsoft SQL Server before
running the Control Desk installation
program using the methods prescribed by your organization. For Microsoft SQL Server, this user must be the owner of the database. |
|
| Create table spaces | Table spaces are created for the new DB2 database. | Instructions for manually creating table spaces for DB2 can be found in the product installation information. | |
| Create table spaces | Table spaces are created for the new Oracle database. | Instructions for manually creating table spaces for Oracle can be found in the product installation information. | |
| Deploy the Maximo database schema | The Maximo database schema is deployed into the newly created database. | The name of the database schema is required to be the same value as the owner of the table spaces defined. | |
| The maxinst command is run | maxinst deploys database tables and required data. | ||
| WebSphere Application Server Network Deployment | Create a database instance and user ID | If you opt to persist JMS messages in a database, a new DB2 database instance is created. A database instance user ID is also created. | A new database instance for persisting JMS messages
can be manually created using the standard procedures of your organization. If you are using Oracle or Microsoft SQL Server, and assuming that you do not intend to reuse existing resources, you must manually create a database instance and user ID for message persistence. |
| Create a database | If you opt to persist JMS messages in a database, a new database is created on DB2. |
A new database for persisting JMS messages can
be manually created using the standard procedures of your organization. If you are using Oracle, and assuming that you do not intend to reuse existing resources, you must manually create a database for message persistence. If you are using Microsoft SQL Server, and assuming that you do not intend to reuse existing resources, you must manually create a database for message persistence. |
|
| Create a data source | If you opt to persist JMS messages in a database, a data source is created. | Instructions for manually creating the data source for persisting messages can be found in the product installation information.. | |
| Create an application server. | A new application server named MXServer is
created if it does not already exist. This value is the default value. Right after the application server is created, the JVM heap size is set for it. If the application server has been previously created, then this step consists only of setting the JVM heap size for it. |
Instructions for manually creating an application server can be found in the product installation information. | |
| Set JVM heap size on the WebSphere Deployment Manager. | The JVM heap size is set to 1536 for Initial Heap Size and Maximum Heap Size on the WebSphere Deployment Manager for 32-bit platforms. For 64-bit platforms, this value is 4096. | You can manually set the heap size on the WebSphere Deployment Manager using the standard procedures of your organization. | |
| Create system integration buses and system integration bus destinations | System integration buses and system integration bus destinations are created for messaging purposes. | Instructions for manually creating system integration buses and system integration bus destinations can be found in the product installation information. | |
| Create JMS queues | JMS queues are created for messaging purposes. | Instructions for manually creating JMS queues can be found in the product installation information. | |
| Modify web.xml files | The web.xml files located on the deployment manager are modified to include Control Desk deployment information, including letting the deployment manager know how the Control Desk application handles its authentication needs. | ||
| Launch-in-context configured. | Launch-in-context function between Control Desk and TADDM is configured. This is achieved by deploying two EAR files (wim.ear and IBMESSAuthnSvc.ear), and configuring authentication services by generating an LTPA Key. | More information can be found in the product installation information. | |
| Integration Framework Adapter is enabled. | |||
| Users created within the LDAP repository. | The following default users and groups created
in the LDAP repository.
|
More information found in the product installation information. | |
| Process managers deployed. | The Control Desk components are deployed using the Process Solution installation program. | ||
| Groups created for process managers. | Groups are created for each of the main
components of Control Desk
|
||
| Applications deployed | The maximo and maximohelp applications are deployed to the MXServer application server. | ||
| updatedb command run | The updatedb command is run to update the Maximo database. | ||
| The VMMSYNC crontask. is modified. | The VMMSYNC crontask is used to schedule the synchronization between Virtual Member Manager and the LDAP repository you configure for authentication. | More information can be found in the product installation information. |
You have the option of manually completing these tasks. You would then select the option to not automatically configure middleware servers Control Desk installation program.