WAS v8.0 > Install the application serving environment > Distributed operating systems > Centralized installation manager (CIM) > Use the centralized installation manager (CIM) to manage v6.1.x and 7.x > Install packages using the centralized installation manager (CIM) for previous versions
Install v6.1.x and 7.x customized installation packages (CIPs) using the centralized installation manager (CIM)
Consider the following information when using the centralized installation manager (CIM) with customized installation packages (CIPs).
Supported configurations: This topic applies to WAS v6.1.x and 7.x only. For information about using centralized
installation manager (CIM) for v8.0, see Submit Installation Manager jobs.
WAS v7.0 customized installation packages
We can install WAS v7.0 CIPs using centralized installation manager. For a new installation, you can either click the Install button or the Install with response file button on the Available Installation page.
A slip installation of a CIP means that you are installing a CIP on top of an existing product or component. For a slip installation of a CIP, use a response file. Click the Install with response file button on the Available Installations page. After you complete a slip installation, you cannot use centralized installation manager to roll back the slip installation.
To uninstall WAS Version 7.0 that was installed using a CIP, you can select either the WebSphere Application Server Network Deployment v7.0 package or the WebSphere Application Server CIP as the installation package. Clear all features under Select optional features. Click the Show Uninstallation Targets button. Select one or more targets from the table, and click Uninstall to launch the wizard. Any CIP can be used to uninstall all platforms of WebSphere Application Server v7.0 from workstations that are part of the Network Deployment cell.
New feature: Beginning in WAS v8.0 you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.New feature:
WAS v6.1 customized installation packages
Centralized installation manager does not support the installation of WAS Version 6.1 CIPs. Instead, use the fix packs to upgrade your WAS.
Troubleshoot
You might experience a timeout situation when attempting to install a CIP with customized scripts from the CIM. For example, consider a CIP that consists of WAS v7.0 and a large custom tar file with associated custom scripts. We must first add the CIP to the CIM repository. At this point you can install the CIP to a remote server. However, the installation might fail with the following error:
XCIM0203E: The installation command [install -silent -OPT ...............] timed out.It appears that the custom script that runs at the end of the installation takes a long time to complete its tasks which causes the timeout. There is a way to change the timeout value used by CIM for the CIP.
The installation timeout value used by CIM for the CIP is specified in the CIM descriptor for the CIP. When you add the CIP to the CIM repository using the IBM WebSphere Installation Factory, a copy of the descriptor file is placed in the <CIM_repository_root>/descriptors directory. The descriptor file controls how CIM is to handle the remote installation of the CIP including the timeout value to use for different commands. Each CIP has its own descriptor file with a name that identifies the CIP. For example, if the CIP directory name is com.ibm.torolab.ND70_AIX_PPC32_1.0.0.0, then the descriptor file for the CIP is named InstallPackageND70X_com.ibm.torolab.ND70_AIX_PPC32_1.0.0.0.xml. The timeout value that CIM uses for the installation command is specified by the TimeoutInSecs attribute of the InstallCmd element. For example:
<InstallCmd TimeoutInSecs="1800">This specifies a timeout value of 1800 seconds.
To force CIM to use a larger timeout value, update the value within the quotes, save the file, and retry the installation. It is strongly recommended that you make a copy of the descriptor file in a separate place and do not attempt any other changes. There is no need to restart the dmgr to make the change effective. If you are using a response file to install the CIP using CIM, you may want to verify that the preset timeout value for installation with a response file is sufficient for this CIP. The timeout value that CIM will use for the installation of the CIP using a response file is specified by the TimeoutInSecs attribute of the InstallWithRespFileCmd element. For example:
<InstallWithRespFileCmd TimeoutInSecs="7200" .......>This specifies a timeout value of 7200 seconds.
The preset timeout
value for installation with response file is longer because installation with response file could potentially include creation of profiles
and federation of the node to a cell in a single invocation of the install command to the remote server. This larger timeout value may
be sufficient for the CIP without modification. If you no longer see the CIP in the CIM's Available Installations panel after making
the above change, it means we have likely made a mistake in your editing and the descriptor file has become invalid. Compare the changed file with the original copy you saved to make sure that is the only change you made or check the dmgr's SystemOut.log for any error messages. Correct the error and retry. Note that if you populate the CIP to another CIM repository using the IBM WebSphere Installation Factory, then the same change has to be made to the CIM descriptor for the CIP in the descriptors directory of that other repository.
Get started with the centralized installation manager (CIM) for previous versions
Add installation packages of previous versions to the centralized installation manager (CIM) repository using the Installation Factory