Creating a repository on an HTTP server

The product repository on an HTTP server is used to install the product on your local computer and on additional computers.

Before you begin

Install Installation Manager on the local computer to use a repository created by IBM® Packaging Utility.

Procedure

Download the DevOps product from IBM Passport Advantage®. Download the IBM Installation Manager and Packaging Utility; see technote 609575.
- For information about Installation Manager updates, see Installation Manager updates.
- For information about how updates for installed products and Installation Manager are found, see Check for updates for Installation Manager and installed products.
Extract the installation files for the DevOps product, Installation Manager, and the Packaging Utility to a local computer. The extracted installation files contain the product repository.
The following examples show directories on the local computer that contain the extracted installation files:
Windows™ systems
```
C:\installation_files\DevOps_product
C:\installation_files\EnterpriseCD-platform\InstallationManager
C:\installation_files\EnterpriseCD-platform\PackagingUtility
```
Linux or UNIX systems
```
/installation_files/DevOps_product
/installation_files/EnterpriseCD-platform/InstallationManager
/installation_files/EnterpriseCD-platform/PackagingUtility
```
Locate the file agent.installer.platform-version.zip in the InstallationManager directory, and extract the file to the InstallationManager directory.
Locate the file pu.disk_platform-version.zip in the PackagingUtility directory, and extract the file to the PackagingUtility directory.
Use the following commands to install the Packaging Utility. Installation Manager is automatically installed when you install Packaging Utility.
Windows™ systems
```
<installation_files>\InstallationManager\install.exe 
<installation_files>\PackagingUtility\disk_platform\InstallerImage_platform\install.exe
```
Note: On Windows™, use install.exe for installations that use the GUI. Use installc.exe for silent installs.
Linux or UNIX systems
```
/installation_files/InstallationManager/install
/installation_files/PackagingUtility/disk_platform/InstallerImage_platform/install
```
Create the repository in Packaging Utility.
1. Check that the computer that has Packaging Utility installed can access the HTTP server. Access includes FTP access or mapping a writable, shared drive to the document directory on the HTTP server.
2. Start the Packaging Utility.
3. Click Copy Packages.
4. Click Open Repository.
5. Click Browse and navigate to the directory containing the DevOps product installation files. For example:
  Windows™ systems:
```
C:\<installation_files>\<DevOps_product>\disk1\diskTag.inf
```
  Linux or UNIX systems
```
 /installation_files/DevOps_product/disk1/diskTag.inf
```
  Note: If your repository contains both diskTag.inf and a repository.config directories, select the diskTag.inf directory. If the repository.config directory is selected, the copy process fails.
  Note: After selecting Copy Packages, the following message is displayed:
```
Download zips from IBM Web site to hard drive. Unzip each into a common root directory.
```
  After selecting Open Repository, the following message is displayed:
  You can open the repository.config file, a directory that contains the repository.config file, a .zip file, or a JAR file. For enterprise CD images, open the diskTag.inf file in the root of the CD.
  Compressed files that contain a diskTag.inf or are larger than 2.2 GB must be extracted. Both the DevOps Code ClearCase® and installation files contain a diskTag.inf file.
  Note these differences between repository.config and diskTag.inf. Repository.config is a file that can be created using the Packaging Utility or obtained from the installation files. This file is typically in the <installation_files>\<Rational_Product> directory.
  diskTag.inf indicates to Installation Manager that the files are from a disk image. diskTag.inf can be across multiple disks. You cannot create a diskTag.inf with Packaging Utility but you can select a diskTag.inf in Packaging Utility. diskTag.inf cannot be used from an HTTP server. Fix packs do not contain a diskTag.inf.
6. The default value for the repository name is the location of the selected repository. To enter a different repository name, clear the option Use the location as the name of the target repository. For example:
  Windows™ systems:
```
C:\<installation_files>\<Rational_Product>\disk1\diskTag.inf
```
  Linux or UNIX systems:
```
/installation_files/DevOps_product/disk1/diskTag.inf
```
Click OK.
In the Source window, verify that the DevOps product repository is selected. Expand the repository name to see the files located in the repository.
Click Next > Accept License Agreement.
Click Browse to select the directory on the HTTP server that will contain the repository. You must select an existing directory. For example, for Windows™: \\HTTPServer\<Rational_product> or for Linux or UNIX systems: /HTTPServer/<Rational_product>.
Click Next.
Click Copy to copy the selected repositories into a repository located on the HTTP server.
For example, on Windows™ systems, files in the DevOps product repository, C:\installation_files\<Rational_product>\disk1\diskTag.inf, are copied to the repository on the HTTP server, \\HTTPServer\<Rational_product>.
On Linux or UNIX systems, files in the DevOps product repository, installation_files/<Rational_product>/disk1/diskTag.inf, are copied to the repository on the HTTP server, /HTTPServer/<Rational_product>.
Close the Packaging Utility.
Copy the Installation Manager files to the HTTP server. You cannot add Installation Manager files to the repository created by the Packaging Utility. For example:
Windows™ systems:
```
\\HTTPServer\InstallationManager
```
Linux or UNIX systems:
```
/HTTPServer/InstallationManager
```
Note: You can add an Installation Manager fix pack, com.ibm.cic.agent.offering.zip, to the repository created by Packaging Utility.