Home
HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
Planning and Installation
Installing Dynamic Workload Console and Z connector
Installing the Dynamic Workload Console
Install the Dynamic Workload Console to manage your static and dynamic workload both in distributed and end-to-end environments using a web interface.
Installation log files
The type of log files you find on your system depends on the type of installation you performed.

HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
- Program Directory
- Dynamic Workload Console Readmes
  For the latest information about a Dynamic Workload Console fix pack, see the appropriate Readme File.
- Planning and Installation
  - About this publication
  - Planning
  - Installing HCL Workload Automation for Z
  - Installing Dynamic Workload Console and Z connector
    - Preparing the installation
      An overview about how to install and use the Dynamic Workload Console.
    - Installing the Dynamic Workload Console
      Install the Dynamic Workload Console to manage your static and dynamic workload both in distributed and end-to-end environments using a web interface.
      - Installing WebSphere Application Server Liberty Base
        WebSphere Application Server Liberty Base is required on all workstations where you plan to install the master components and the Dynamic Workload Console.
      - Encrypting passwords (optional)
        How to encrypt passwords required by the installation, upgrade, and management processes.
      - Creating and populating the database
        By default, the installation script is configured to install and use a Derby database. Alternatively, you can also choose to use any one of the supported databases.
      - Installing a Dynamic Workload Console server
        Procedure for installing a Dynamic Workload Console server.
      - Defining a z/OS engine in the Z connector
        To define a z/OS engine, perform the following steps.
      - Defining a z/OS engine in the Dynamic Workload Console
        Steps to create a z/OS engine connection in the Dynamic Workload Console
      - Encrypting the connection between the Z connector and the server started task
        An overview of encrypting the connection between the Z connector and the server started task.
      - Navigating the Dynamic Workload Console
        An overview to the Dynamic Workload Console.
      - Starting and stopping the WebSphere Application Server Liberty Base
      - Installation log files
        The type of log files you find on your system depends on the type of installation you performed.
    - Configuring the Dynamic Workload Console
      Some links and pointers on configuration tasks that are needed for the Dynamic Workload Console.
    - Upgrading the Dynamic Workload Console
      This section describes how to upgrade the Dynamic Workload Console from v 9.5.x to 10.1.0.x.
    - Uninstalling the Dynamic Workload Console
      How to encrypt passwords required by the installation, upgrade, and management processes.
  - Deploying with containers
    Getting started with containers
  - Deploying AI Data Advisor
    You can deploy AI Data Advisor (AIDA) by using Docker or Kubernetes.
  - Installing HCL Workload Automation Agent (z-centric)
    How to install, migrate, and uninstall the HCL Workload Automation Agent (also known as z-centric agent).
  - Installing HCL Workload Automation Agent on IBM i systems
    Installing HCL Workload Automation Agent on IBM i systems
  - Integrating Workload Automation with Zowe™
    Zowe™ is an open source project that enables you to interact with z/OS through modern interfaces. You can issue Workload Automation commands through the Zowe command-line interface (CLI), and access Workload Automation REST APIs through the Zowe API Mediation Layer (ML).
  - Sample library (SEQQSAMP)
    The SEQQSAMP library contains samples to help you install and customize HCL Workload Automation for Z.
  - Configuration examples
  - Invoking the EQQEXIT macro
  - Invoking the EQQLSENT macro
- Customization and Tuning
- Managing the Workload
  You can plan when and how your workload runs and manage it as part of a plan.
- Scheduling End-to-end with z-centric Capabilities
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Installation log files

The type of log files you find on your system depends on the type of installation you performed.

About this task

To simplify administration, configuration, and backup and recovery, a new default behavior has been implemented with regard to the storage of product data and data generated by HCL Workload Automation, such as logs and configuration information. On UNIX operating systems, these files are now stored by default in the DATA_DIR directory, which you can optionally customize at installation time. By default, this directory is INST_DIR/TWSDATA for the server and agent components, and INST_DIR/DWC_DATA for the Dynamic Workload Console. The product binaries are stored instead, in the installation directory.

Note: If you deployed the product components using Docker containers, this is the default behavior and it cannot be modified. However, if you installed the product components using the command-line installation, the --data_dir parameter can be used to change the path.

Dynamic Workload Console: INST_DIR/DWC_DATA/installation/logs

On Windows operating systems, installation log files for the Dynamic Workload Console are stored in INST_DIR\logs.

On z/OS operating system, installation log files for the Dynamic Workload Console are stored in INST_DIR/DWC_DATA.