[IBM i]

Adding installation packages of previous versions to the centralized installation manager (CIM) repository using the Installation Factory

Use IBM® WebSphere® Installation Factory Version 7.0.0.15 or later to add WebSphere Application Server Network Deployment Version 7.0 installation packages to the repository. From the administrative console, you can then use the centralized installation manager to install your added components from the repository to the nodes. Each WebSphere Application Server installation has only one associated repository. The repository is shared among all the deployment managers of the installation.

Before you begin

To populate the repository, ensure you have write permission to the specified repository directory. To configure the WebSphere Application Server installation to associate with the repository, ensure you have write permission to the app_server_root/properties directory.

[IBM i] Supported configurations Supported configurations:
  • The centralized installation manager repository location is stored in <WAS_HOME>/properties/cimgr.props. The default value is "${WAS_INSTALL_ROOT}/cimrepos". The default location is /QIBM/ProdData/WebSphere/AppServer/cimrepos. If you are using two different users to install and run WebSphere Application Server, the user that runs WebSphere Application Server must have write permission to create the cimrepos directory and its content. Otherwise, some functions in the centralized installation manager such as downloading new descriptors or Update Installer will not work. You might see an error in the SystemOut.log that is similar to the following:
    XCIM0903E: Cannot download file 7.0.0.13-WS-UPDI-i5OsPPC.zip.part to /QIBM/ProdData/WebSphere/AppServer/cimrepos/UPDI70.  
    Reason: /QIBM/ProdData/WebSphere/AppServer/cimrepos/UPDI70/7.0.0.13-WS-UPDI-i5OsPPC.zip.part (A file or directory in the path name does not exist.) 
    If the user that runs WebSphere Application Server does not have write permission to the <WAS_HOME>, you can relocate the repository location outside of <WAS_HOME> by modifying the value in cimgr.props.
  • When you install WebSphere Application Server version 7.0 to a node using centralized installation manager and you encounter a time out error that is similar to the following,
    XCIM0203E: The installation command [install -silent -OPT silentInstallLicenseAcceptance="true" -OPT installType="installNew" 
    -OPT installLocation="/QIBM/ProdData/WebSphere/AppServer" -OPT disableOSPrereqChecking="false" -OPT profileType="none" 
    -OPT feature="languagepack.console.all" -OPT feature="languagepack.server.all" -OPT defaultProfileLocation="/QIBM/UserData/WebSphere/AppServer"] timed out.
    You can modify the default time out value in the descriptor file InstallPackageND70X.xml. This file is located at <WAS_HOME>/properties/cim. Open InstallPackageND70X.xml in a text editor and locate the <InstallCmd TimeoutInSecs="1800"> tag. The default time out value is 1,800 seconds (30 mins). For installation WebSphere Application Server version 7.0 on IBM i nodes, you may change the time out value to 5,400 seconds (90 mins). Save the changes and restart deployment manager.
sptcfg

Procedure

  1. Launch the Installation Factory from the following location, where if_root is the Installation Factory root directory.
    • Click Manage Repository for Centralized Installation Manager.
    • On the WebSphere Application Server installation directory page, you can optionally enter the directory path to a WebSphere Application Server installation to associate the repository with the installation. Click Next.
    • On the Repository and Installation Package page, enter the directory path to the repository, and enter the directory path to an installation package. Click Next.

      The specified installation package is populated to the repository when the procedure is complete. If you only want to configure the WebSphere Application Server installation to associate the repository, then enter the directory path to the WebSphere Application Server installation on the previous page and leave the directory path to installation package to empty.

      To change your selections, click Back.

    • Review the preview page, and click Finish to begin the procedure on the repository.
    • Optional: You can also add a CIP to the repository from the Installation Factory command line interface. Run the ifcli command using the options in table.
        Table 1. ifcli command-line options for centralized installation manager .

        This table describes command-line options for centralized installation manager.

        Option Description
        -wasPath wasInstallationPath Specifies the directory path of the WebSphere Application Server installation.
        -repositoryPath repositoryPath Specifies the directory path of the repository.
        -installationPackagePath installationPackagePath Specifies the directory path of the installation package.
        -overwrite Overwrites the existing installation package in the repository.

      Results

      The centralized installation manager repository you specified now contains one or more WebSphere Application Server installation packages. Alternatively, you can add the installation package to the repository as you install the installation package on the deployment manager workstation. Read the "Adding the current installation package during installation" topic for more information.

      Example

      Task topic    

      Terms and conditions for information centers | Feedback

      Last updated: April 20, 2014 09:55 PM CDT
      http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=tins_cim_package_add_if
      File name: tins_cim_package_add_if.html