Home
Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
z/OS considerations for DevOps Deploy
HCL DevOps Deploy (Deploy) includes support for the z/OS platform. Although the articles in this Knowledge Center for using Deploy to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
Upgrading z/OS® agents
You can upgrade IBM® z/OS® agents. However, you must upgrade the server before you upgrade the agents.
Migrating data from versions before 6.1.1
Upgrade the server, agents, and agent relays before upgrading the IBM® z/OS® deployment tools.

Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
- Integrating with DevOps Test Performance
  When you use HCL DevOps Test Performance (Test Performance), you can create tests and run those tests in HCL DevOps Deploy (Deploy) by using the Test Performance Deploy plug-in.
- z/OS considerations for DevOps Deploy
  HCL DevOps Deploy (Deploy) includes support for the z/OS platform. Although the articles in this Knowledge Center for using Deploy to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
  - Installing the z/OS® agent
    Before you deploy to the IBM® z/OS® platform, you must install the z/OS agent and configure the z/OS server for communication with HCL DevOps Deploy (Deploy). If the build process runs on a different logical partition (LPAR), then you must additionally install the agent on the build LPAR. You can install the z/OS agent and deployment tools by using the IBM System Modification Program Extended (SMP/E) or by extracting archive files to the z/OS UNIX™ file system.
  - Upgrading z/OS® agents
    You can upgrade IBM® z/OS® agents. However, you must upgrade the server before you upgrade the agents.
    - IBM® z/OS® agent changes in version 6.2.4
    - Migrating data from versions before 6.1.1
      Upgrade the server, agents, and agent relays before upgrading the IBM® z/OS® deployment tools.
  - Starting z/OS agents from the z/OS UNIX command line
    The z/OS agent can be started from ISPF as a started task or from the z/OS UNIX command line. To start an agent from ISPF as a started task refer to install/topics/run_agent.html. To start the z/OS agent from the z/OS UNIX command line, follow this procedure.
  - Installing the z/OS® agent and deployment tools by using SMP/E
    IBM® System Modification Program/Extended (SMP/E) is a tool for installing and maintaining software on z/OS® systems. SMP/E controls software changes at the element level. Job Control Language (JCL) is submitted by using 3270 emulation.
  - Job Monitor customization
    The Job Monitor binary is installed with the IBM® z/OS® deployment tools in the hlq.SBUZAUTH data set. You need the assistance of a security administrator and a TCP/IP administrator to complete this customization task.
  - Planning storage
    You can store the versions in CodeStation or in Artifactory/Nexus. To store versions in Artifactory or Nexus, the artifactory details must be passed to the buztool.sh. Every z/OS agent that is used to deploy projects, stores backups of old artifacts so that a rollback can be done when required. Plan the agent directory to ensure there is sufficient space for backup.
  - Customizing and verifying the TSO-ISPF client gateway
    HCL DevOps Deploy (Deploy) uses the IBM® z/OS® Time Sharing Option-Interactive System Productivity Facility (TSO-ISPF) gateway when it imports and deploys component versions.
- Deploying components to the z/OS® platform
  Use the toolkit to deploy to the IBM® z/OS® platform.

Migrating data from versions before 6.1.1

Upgrade the server, agents, and agent relays before upgrading the IBM® z/OS® deployment tools.

About this task

If you have version data and deployment results that were created by a version of the z/OS® agent and deployment tools before version 6.1.1, complete these migration steps.

Procedure

Determine the repository directory and deployment base directory in the current installation of the product. The repository directory is the value of the ucd.repository property in the profile data set. The location of the profile data set is recorded in the ISPF.conf file. The deployment base directory is typically set in the deploy.base.path environment property.
Install a new agent or upgrade the current agent. Then, copy files to the new repository and deployment directories.
- For version 6.2.4, the repository directory and the deploy directory are as follows:
  - agent install dir/var/repository
  - agent install dir/var/deploy
- For versions from 6.1.1 to 6.2.3, you can find the the repository directory and the deployment directory locations in the profile data set.
Verify the migration by deploying a current version of a component, and then by rolling back version.