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.
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.
Installing binary and config to different directories
By default, the agent installer installs the binary and config files into the same directory. You can customize the installation so that these files are installed into different directories. Also, multiple agent configurations can share the same copy of binary files which makes security control and product upgrading easier.

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.
    - Deploying by using the Job Monitor
      You use the Job Monitor to submit jobs and to monitor the job status in your deployment. You must ensure that you have a Job Monitor task running and that you run the HCL DevOps Deploy (Deploy) process to submit or to monitor the job. Then, you must set up Job Monitor connection properties in your HCL DevOps Deploy (Deploy) environment.
    - Installing binary and config to different directories
      By default, the agent installer installs the binary and config files into the same directory. You can customize the installation so that these files are installed into different directories. Also, multiple agent configurations can share the same copy of binary files which makes security control and product upgrading easier.
  - Upgrading z/OS® agents
    You can upgrade IBM® z/OS® agents. However, you must upgrade the server before you upgrade the agents.
  - 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.

Installing the binary and config files to different directories

By default, the agent installer installs the binary and config files into the same directory. You can customize the installation so that these files are installed into different directories. Also, multiple agent configurations can share the same copy of binary files which makes security control and product upgrading easier.

Installing agent binary files

Agent binary files are installed by running the install-agent.sh script with the -binary parameter. Note that all agent data sets are considered binary files. Depending on the installation method, agent data sets are either installed by the SMP/E process or by submitting the BUZEXPD job.

After the binary files are installed, they can be used by multiple agents. Typically, they are installed to a shared volume and made accessible by multiple systems in read-only mode.

Installing agent config files

Agent config files are installed by running the install-agent.sh script with the -config parameter. The installation program prompts you to specify the directory of the agent binary before installation the process can start. You should specify a different directory for the agent config.

The backup directory is also located in the agent config directory. The storage space calculation described in the Planning storage topic applies to the agent config directory.

Upgrading agent

In the binary and config installation mode, only the agent binary needs to be upgraded. When needed the agent config is automatically upgraded, when you start the agent or run the buztool.sh script.

Limitations

The following are limitations related to the binary and config installation mode.

Upgrading agents from the Web user interface is not supported for agents installed using the binary and config mode.
The binary and config installation mode can only be used when installing new agents.
Silent mode installation using install-agent-from-file.sh does not support binary and config mode.
Config files must be installed using the install-agent.sh script. It is not supported to copy files or data sets to other locations.