Installing and configuring IBM z/OS Package Manager 1.0.x

Before importing

Go to Importing operator collections to create an endpoint, import the IBM z/OS Package Manager Operator collection, map the z/OS endpoint, and map the namespace.

You need to complete the prerequisites within that page, which includes ensuring that an SSH key has been generated and that the public key has been copied to the z/OS endpoint. The SSH key is used to authenticate connections to the specified endpoints.

When you import the IBM z/OS Package Manager Operator collection through the Ansible® galaxy collection installation URL or manual upload, you must have either a local copy of the operator collection to be imported by z/OS Cloud Broker or the Ansible galaxy URL of the operator collection.

Importing an operator collection

The following steps are to be completed on the IBM z/OS Cloud Broker Web User Interface (UI).

1. In the left navigation, click Operator Collections > Import.

2. In the Import Operator Collection section, use the following methods to upload an operator collection:

   a. Search for zos_package_manager in Galaxy.

   b. Selected the card that you want to import.

   c. Select the version from the drop-down list.

   d. Click Import Collection button.

Select the Operator collection overview tab to verify whether the collection is successfully imported. The suboperator collection card is placed under imported row.

Associating the operator collection with a z/OS endpoint

This step ensures that the tasks that are defined in an operator collection are performed against the specified z/OS environment. The following steps are to be completed on the IBM z/OS Cloud Broker Web UI.

1. In the Operator collection overview tab, click the suboperator collection card that you want to configure to enter the Configure Collection view.

2. In the z/OS Endpoint selection panel, select the target z/OS endpoint from the list available.

3. In the SSH key panel, click Add file button to upload the SSH Key.

4. Enter a name in the SSH Key username field.

5. Click the Test SSH button to test the connection.

6. Click the Submit button.

7. Click Complete.

After you complete this step, the suboperator collection card should be shown under the Mapped Collection row, which means it is successfully mapped to a z/OS endpoint. IBM z/OS Cloud Broker has also generated a z/OS Package Manager operator for you in Red Hat® OpenShift®.

To see the installation status of the operator, open the Red Hat OpenShift Container Platform web console. Then, click Operators > Installed Operators, search for the operator, and check the Status column for the operator.

Before creating the operator instance

As part of the IBM z/OS Package Manager installation process, a product-related OCI artifact is pulled from a specified registry. By default, the z/OS Package Manager pulls software from the IBM container registry. If you want to use your own enterprise registry instead, enter the registry and namespace during the installation of the IBM z/OS Package Manager.

You can also set up a registry proxy server if needed, to pull and install the OCI artifacts. You can specify the proxy server details during the installation of IBM z/OS Package Manager on the z/OS endpoint.

If authentication is required into either the registry or registry proxy, specific key/value pairs must be manually added in the z/OS Cloud Broker web UI to any z/OS endpoint to which IBM z/OS Package Manager will be deployed. For more information, see Importing operator collections.

Install product on z/OS

Take the following steps to create an IBM z/OS Package Manager instance. These steps are to be completed on the Red Hat OpenShift Container Platform web console.

The steps in this task are also shown in the following video:

1. In the Installation Operators view, navigate to IBM Z® and Cloud Modernization Stack- IBM z/OS Package Manager and click its name.

2. Click Create instance in the IBM z/OS Package Manager section from the Details tab.

3. You can configure the instance with Form view option selected.

   a. Enter the instance name, which is required.

   b. Optional: fill the box under Labels. Labels can be used to view all of your resources by a specific label or name when on the Red Hat OpenShift Platform web console.

   c. Check Accept under License.

   d. Enter the z/OS endpoint to be used. This is the endpoints that you want to install the IBM z/OS Package Manager on to.

   e. If different than the default, enter the directory where you want to install IBM z/OS Package manager on the z/OS endpoint. The default is /usr/lpp/IBM/zpm.

   f. If different than the default, enter the directory where you want to save configuration and state data for the IBM z/OS Package manager on the z/OS endpoint. The default is /var/zpm.

   g. If different than the default, enter the directory path for the Java™ 8 (64-bit) SDK on the z/OS endpoint. The default is /usr/lpp/java/J8.0_64.

   h. If different than the default, enter the high-level qualifier for any product data sets that are created during product installations. The default is ZPM.

   i. If different than the default, enter the registry that you want the IBM z/OS Package Manager to use to pull software to install on the z/OS endpoint. The default is icr.io/zpm.

   j. Optional: If you require proxy access to a registry, the hostname of the proxy.

   k. Optional: If you require proxy access to a registry, the port of the proxy.

   l. Click Create to create the IBM z/OS Package Manager instance.

You can return to Details tab to check the instance creation status under Conditions section.

When the Status turns to Succeeded, the IBM z/OS Package Manager instance is successfully installed.