Consider the following information when using the centralized installation manager (CIM) with customized installation packages (CIPs).
You can install WebSphere Application Server Version 7.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, you must 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 WebSphere Application Server Version 7.0 that was installed using a CIP, you can select either the WebSphere Application Server Network Deployment Version 7.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 Version 7.0 from workstations that are part of the Network Deployment cell.
Centralized installation manager does not support the installation of WebSphere Application Server Version 6.1 CIPs. Instead, use the fix packs to upgrade your WebSphere Application Server.
Installing a CIP from the CIM
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.
<InstallCmd TimeoutInSecs="1800">This specifies a timeout value of 1800 seconds.
<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 you 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 deployment manager'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.