If I make changes to a system that is a component of an ISM product deployment, do I need to do anything before I apply a fix pack or otherwise upgrade my ISM product?
When you install a fix pack or otherwise upgrade an existing ISM product, the installation program uses values recorded from the previous deployment. These values are stored on the administrative workstation in the install.properties and maximo.properties files. If you have made any environmental changes to any of the systems used for the original deployment, such as changing a host name or updating a password. For example, they must be recorded in the install.properties and maximo.properties files.
When the product installation program is run for an upgrade task, it will attempt to use values found in the install.properties and maximo.properties files to complete the upgrade. During the upgrade operation, if you have not updated the user name or password for a system used in the previous deployment, the installation program will use the credentials found in the properties files, and, pending successful use of these credentials, you will not be prompted to provide them again. If the installation program is unsuccessful in its attempt to log into a system using the credentials found in the properties files, you will be prompted to supply the correct information. These values will then be written to the appropriate property file.
This method of updating credential information in property files has one exception. Database connection and credential information must always be current before you attempt an upgrade operation. Database connection and credential information is stored in the maximo.properties file. Any changes to this information from the time of the original deployment must be manually recorded in the maximo.properties file before you upgrade.
1. Complete the following steps to update database properties within the maximo.properties file:
a. Change directory to <Product_Home>\maximo\applications\maximo\properties\
b. Make a backup of the maximo.properties file.
c. Delete the maximo.properties file.
d. Change directory to <Product_Home>\etc
e. Make a backup of the maximo.properties_orig found in the directory. This backup should be a permanent backup that can be copied from when you need to update properties in the future.
f. Rename the unencrypted file named maximo.properties_orig to maximo.properties
g. Copy the maximo.properties file to <Product_Home>\maximo\applications\maximo\properties\
h. Edit the maximo.properties file and update the credential or connection information for the database server.
i. Save the file.
j. Run the encryptproperties.bat file located in <Product_Home>\maximo\tools\maximo\ directory against the file to encrypt it.
2. Complete the following steps to update properties within the install.properties file: The install.properties file contains the majority of properties used by the installation program, including non-connection related properties for the database. These values must be up to date before you apply a fix pack or other upgrade operation. If these values have changed from the previous deployment, you must first manually update them.
a. Change directory to <Product_Home>\etc\
b. Edit the install.properties file and make updates. Do not make changes to encrypted properties (prefixed by [enc]). You will be prompted for updated values during the update operation. These values will then be written to the install.properties file.
c. Save the file.
There is one important exception to this procedure. When changing the value of the WebSphere® Application Server Network Deployment host name (WAS.DeploymentManagerHostName), in addition to updating this property value in the install.properties file, you must also update a property for the WebSphere Application Server Network Deployment thin client in the thinwasadmin.bat file and then run that file.
3. To update the WebSphere Application Server Network Deployment host name that was used in the previous deployment, complete the following steps:
a. Update the WAS.DeploymentManagerHostName value in the install.properties file, as described in the previous procedure.
b. Edit the C:\IBM\SMP\WASClient\thinwasadmin.bat file.
c. Update the following line of the file with the new, fully-qualified, host name of the WebSphere Application Server Network Deployment server.
set wsadminHost=-Dcom.ibm.ws.scripting.host=<fully-qualified host name>
d. Run thinwasadmin.
thinwsadmin.bat -username <domain manager user name> -password <password>
e. When prompted, indicate that you do want to download the truststore file.
After you have completed these updates, you will be able to upgrade, install a fix pack, or install another ISM product using the corrected values.
|Systems and Asset Management||IBM Maximo Asset Management||AIX, Linux, Windows||7.1, 7.5|
|Systems and Asset Management||Tivoli Release Process Manager||AIX, Linux, Windows||7.1.1|
|Systems and Asset Management||Tivoli Service Request Manager||AIX, Linux, Windows 2003 server||7.1, 7.2, 7.2.1|
|Systems and Asset Management||Tivoli Asset Management for IT||AIX, Linux, Windows||7.1, 7.2, 7.2.1, 7.2.2|
|Systems and Asset Management||Tivoli Provisioning Manager||AIX, Linux, Windows||7.1|
|Systems and Asset Management||IBM Maximo for Government|
|Systems and Asset Management||IBM Maximo for Utilities|
|Systems and Asset Management||IBM Maximo for Oil and Gas|
|Systems and Asset Management||IBM Maximo Asset Configuration Manager|
|Systems and Asset Management||IBM Maximo Calibration|
|Systems and Asset Management||IBM Maximo for Life Sciences|
|Systems and Asset Management||IBM Maximo for Nuclear Power|
|Systems and Asset Management||IBM Maximo for Transportation|
|Systems and Asset Management||IBM Maximo for Service Providers|
|Systems and Asset Management||IBM Maximo Adapter for Primavera|
|Systems and Asset Management||Maximo Spatial Asset Management|
|Systems and Asset Management||IBM SmartCloud Control Desk||7.5, 7.5.1|