IBM Quick Deployer run Install Applications process

Authors: ThomasPiccoli, KennethThomson, JenniferLiu, KenTessier, ClareCarty
Build basis: CLM 6.0, CLM 6.0.x, CE 6.0.x

This topic leads you through running the Install Applications process to install IBM Rational solution for Collaborative Lifecycle Management (CLM) or IoT Continuous Engineering (CE) solution applications onto your server system.

Prepare the target system

Before you run the UrbanCode Deploy Install Applications application process, you must set the default LDAP, user, and database parameters. You can set these parameters when you run the installer by entering the values in the ldap.properties, userCreds.properties, and database.properties files, which are included in the Quick Deployer package. Alternatively, you can set the parameters by running the following application processes:

• Change Default LDAP Parameters application process - Change the default LDAP parameters
• Change Default User Parameters application process - Change the default user parameters
• Change Default DB2 Database Parameters application process - Change default DB2 database parameters
• Change Default Oracle Database Parameters application process - Change default Oracle database parameters
• Change Default SQL Server Database Parameters application process - Change default SQL Server database parameters

Quick Deployer stores the LDAP, user, and database parameter values in the Rational_QD_SystemPre-Requisite_60x component. To permanently store an updated set of these parameter values in the Rational_QD_SystemPre-Requisite_60x component, see IBM Quick Deployer updating Rational_QD_SystemPre-Requisite_60x* component parameters.

Install the applications

1. This process cannot be restarted; therefore, create a snapshot of the target VMs before proceeding.
2. Open application Rational_QD_60x and click Run Process against the target environment.
   
   
   
   
3. When the Run Process window opens:
   1. Select process Install Applications.
   2. Set Admin user name and Admin user password to the credentials of the administrator account defined on the LDAP Server.
   3. Set enableIFIX to TRUE if you want to install a fix pack.
   4. Set RUN_JTS_SCRIPTED_SETUP to Y if you want Jazz Team Server setup to be run by the automation.
   5. Set IMPORT_LDAP_USERS to Y if you want the users defined on the LDAP server to be imported into Jazz Team Server by the automation. (RUN_JTS_SCRIPTED_SETUP must be set to Y)
   6. Set MTM_SAMPLE to Y if you want the Money That Matters (MTM) sample deployed by the automation. (RUN_JTS_SCRIPTED_SETUP must be set to Y)
   7. Set AppServer to was or liberty
   8. Set EnableCM to TRUE if you want to activate Configuration Management. If you set this to TRUE, you must also enter a value for CMActivationKey.
   9. Set EnableNTPclock to TRUE to connect to the clock specified during configuration. If you set this to TRUE, you must also enter a value for *NTPclock".
   10. If you use a prefix to LDAP user names to form the distinguished name (DN), set Prefix_LDAP.
   11. Set DBVendor to db2, oracle, or sqlserver.
   12. Set appMediaRoot to match the version of CLM or CE you wish to install.
   13. If enableIFIX is TRUE, set CLMiFixVersion to match the CLM version and fix pack that you want to install. Make sure that the appMediaRoot version and the iFixVersion match.
       
   14. If enableIFIX is TRUE, set DMiFixVersion and / or DMMSiFixVersion to match the DM version and fix pack that you want to install. Make sure that the appMediaRoot version and the iFixVersions match. If you select DM, and DMMS fix packs make sure that you specify the same version for the DMiFixVersion and DMMSiFixVersion fix packs.
   15. If AppServer is was then set wasJavaSDKVersion to bundled6, 7.1 or bundled8
   16. If DBVendor is oracle then set oracleVersion to 12.1 or 12.2
       
       
       
       
4. Wait for the process to complete
   
   
   
   

Post install

If the process was successful, you can access the Jazz applications by using the fully qualified domain name of the IHS server on port 9443 followed by the context root and page name of the application. For example:

https://<ihs.server.fully.qualified.domain.name>:9443/jts/admin
https://<ihs.server.fully.qualified.domain.name>:9443/ccm/admin
https://<ihs.server.fully.qualified.domain.name>:9443/ccm/web
https://<ihs.server.fully.qualified.domain.name>:9443/qm/admin
...

Miscellaneous

Notes:

• Throughout the IBM Quick Deployer wiki the screen captures are for reference only.
  In some cases if the functionality they display has not changed in the latest release they will be from a previous release

Related topics:

• Quick Deployer
• Quick Deployer setup and run

External links:

• Collaborative Lifecycle Management
• Continuous Engineering
• UrbanCode Deploy

Additional contributors: MichelleCrane, NathanBak, ChristianLopez