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

Download package descriptors and binary files for previous versions to the centralized installation manager (CIM) repository

To enhance your product environment, download additional installation packages and maintenance files to the centralized installation manager (CIM) repository to install later on the remote workstations. Use this topic to manage the installation packages and maintenance files that are located in your CIM repository.

We must first create the CIM repository and add one or more product packages to the repository on the host workstation. For more information, see Adding installation packages of previous versions to the centralized installation manager (CIM) repository using the Installation Factory.

If you do not have direct access to the Internet, then you can set up an FTP gateway and perform the download indirectly through the gateway. Read the "Using CIM download function when the dmgr does not have direct Internet access" topic for more information.

Alternatively, if we have no access to the Internet whatsoever, you can manually add the packages to the repository. Read the "Manually adding package files to the repository" topic for more information.

From the Installation Packages panel in the administrative console, download the descriptor files and any associated binary files of new or additional installation packages to the CIM repository. We can selectively download only the binary files of the platforms that you might need from the IBM support website. The following list describes the four types of installation packages:

• Product installation

  This package type includes WebSphere Application Server Network Deployment v7.0. The descriptor and binary files for this installation type are not available to download because the files are included during the installation of the WebSphere Application Server product on the dmgr host.

• Refresh packs or fix packs

  We can download the binary files for this package type based on specific platforms. When a fix pack for the application server is released, it usually comes with a fix pack for the application server and a fix pack for the Java SDK. CIM requires having both fix packs in the repository, and CIM will install both fix packs to all selected targets.

• Interim fix

  We can search for an interim fix using its identifying Authorized Program Analysis Report (APAR) number. Specify the APAR number of the interim fix and click Search to display a list of files associated with the interim fix and optionally download the binary files.

Complete the following steps to download fix pack descriptors and binary files for fix packs or interim fixes to your CIM repository.

Procedure

1. In the admin console, click System administration > Centralized Installation Manager > Installation Packages.

2. Click Add Packages to download a new installation package descriptor to the centralized installation manager repository if the descriptor is not included in the table displayed from the previous step. The Download Descriptors page is then displayed.

   Best practice: Ensure that the descriptor file for the type of package that you choose is not included as part of the product installation. The installation package descriptors that are included during the product installation are provided in the following list:

   • Maintenance for WAS Network Deployment 7.0
   • WAS Network Deployment 7.0

   bprac

3. Select one or more descriptor files from the list, and click Download.

   After we have confirmed to download the selected descriptor files, they are displayed in the table on the Installation Packages panel with the following text:

   Download filename
   

   Click the refresh icon to refresh the contents of the table. After the descriptor file is downloaded, the package name is displayed as a hyperlink.

   To download the binary files for the installation packages in the preceding list, click the name of the descriptor, and proceed to the next step. To download additional package descriptors from the IBM support website, click Add packages.

4. Download the binary files from the Installation Packages panel.

   We can download the associated binary files of the specific descriptor file that you just downloaded, or you can also download the binary files for the Interim fix package type.

   Determine the type of installation package to download by the viewing the descriptions of each type in the table. The steps to download the binary files differ, depending on the package type.

   • To download the binary files for a refresh pack, fix pack, or maintenance tool package type...

     1. Click the name of the package in the table. A new page is then displayed.

     2. Select one or more platforms in the table, and click Download.

     3. Click Download on the confirmation page to start downloading the binaries. After the download process begins, the previous page is then displayed, from which you can check the download status of the files in the third column of the table. Click the refresh icon to refresh the contents of the table, if necessary.

     4. When all the required files have been downloaded, the download status column displays a Completed status.

     If one or more files are missing, the download status column displays an Incomplete status. In this case, you can try to download again. If your status is Incomplete, check for error messages in the $PROFILE_ROOT/logs/dmgr/SystemOut.log file where PROFILE_ROOT is the profile location of the dmgr.

     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:

   • To download the binary files for an interim fix package type, complete the following steps:

     1. Click the name of the package in the table. A new page is then displayed.

     2. Click Add Files to go to the Download Files page.
     3. We can type the specific APAR name (For example, PK55555), and click Search to navigate directly to the corresponding FTP location. We can also specify the FTP URL directly, and click Go from the Download Options section.

     4. Click the APAR number, select the individual maintenance files that are contained in the directory, and click Download. The binary files are then downloaded to the CIM repository.

     5. Click Download on the confirmation page to start downloading the binaries.

        After the download process begins, the previous page is then displayed, where you can check the download status of the files in third column of the table. Click the refresh icon to refresh the contents of the table, if necessary.

        If your status is Incomplete, check for error messages in the $PROFILE_ROOT/logs/dmgr/SystemOut.log file where PROFILE_ROOT is the profile location of the dmgr.

Results

The CIM repository now contains maintenance files to install later on the remote workstations.
Use the v6.1.x and 7.x centralized installation manager (CIM) download function when the dmgr does not have direct Internet access
Manually adding package files for previous versions to the centralized installation manager (CIM) repository
Add installation packages of previous versions to the centralized installation manager (CIM) repository using the Installation Factory
Use the centralized installation manager (CIM) to manage v6.1.x and 7.x

+

Search Tips   |   Advanced Search