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 > Get started with the centralized installation manager (CIM) for previous versions
Special procedures for IBM i operating systems when running the centralized installation manager (CIM) for previous versions
Special procedures are required if you choose to run centralized installation manager (CIM) on IBM i operating systems. Since IBM WebSphere Installation Factory is not supported on IBM i operating system, create the repository on a Windows operating system and then transfer the repository to the IBM i operating system.
New feature: 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.
Use the Installation Factory v7.0.0.15 or later to create a repository on a Windows system, and then transfer the packages to the repository that resides on the IBM i system.
Use the following procedure to add the installation packages into the CIM repository on the IBM i system using the Windows operating system.
Procedure
- Install WAS Network Deployment v8.0 onto the IBM i operating system.
- Install the Installation Factory onto the Windows operating system.
- Insert the WAS Network Deployment
Version 7.0 installation disk into the drive of the Windows system, or create a customized installation package (CIP) with the Installation Factory on the Windows system.
- Create a repository locally on the Windows operating system with the Installation Factory.
- Change the directory to the repository path.
Run the command zip -r cimrepos.zip * to create a compressed file including all the directories in the repository.
You can also selectively include only the directories you want. If you are including any CIP images, also include the corresponding CIP descriptors that are in the descriptors directory. The CIP descriptor is an XML file whose name contains the CIP directory name. For example, if the CIP directory name is com.ibm.torolab.ND70_AIX_PPC32_1.0.0.0, then the descriptor name is something like InstallPackageND70X_com.ibm.torolab.ND70_AIX_PPC32_1.0.0.0.xml.
- Log onto the IBM i system.
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".
The user that runs WAS must have write permission to create the cimrepos directory and its contents.
Otherwise, errors can occur when CIM downloads new descriptors or runs the Update Installer. You might see an error in the SystemOut.log
that is similar to the following error:
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 WAS does not have write permission to the WAS_HOME directory, you can relocate the repository location to a directory other than WAS_HOME by modifying the value in cimgr.props. - Create the repository directory if it is not already created.
- Transfer cimrepos.zip from the Windows system to the repository directory on the IBM i system. Extract the contents of the cimrepos.zip file onto the repository directory and optionally delete the original zip file.
Results
You have added the installation packages into the CIM repository on the IBM i system.
Instead of creating the repository on the disk drive of the Windows system and transferring the file, alternatively, you can map the IBM i file system of the repository onto the Windows system and use it for populating the installation packages. Using this alternative method eliminates transferring the files to the IBM i system.
What to do next
Use the centralized installation manager to install the components to the nodes and begin managing the environments. In the administrative console, click System administration > Centralized Installation Manager.
Get started with the centralized installation manager (CIM) for previous versions