Detailed System Requirements for HCL Workload Automation, version 9.4

Detailed System Requirements

Abstract

This document details the system requirements for HCL Workload Automation, version 9.4.

Content

This document provides details of the system requirements for all HCL Workload Automation components on all supported operating systems.

The topics included are:


Acronyms and abbreviations used in the tables in this section

Top

Acronyms and abbreviations used in the tables in this section

The following acronyms and abbreviations are used in the tables on this page

+
BDDM HCL Workload Automation backup dynamic domain manager
BKM HCL Workload Automation backup master domain manager
CLI Command-line Client
CONN HCL Workload Automation Connector
DA Dynamic agent
DDM HCL Workload Automation dynamic domain manager
DM HCL Workload Automation domain manager
DWC Dynamic Workload Console
FP Fix Pack
FTA HCL Workload Automation fault-tolerant agent
MDM HCL Workload Automation master domain manager
SDK Eclipse-based Integration Workbench
TWS HCL Workload Automation
TWS for z/OS Agent HCL Workload Automation for z/OS Agent
WAS WebSphere Application Server

Supported operating systems for the engine

The following operating systems are supported for the engine:

To obtain information about the required versions for each supported operating system, see the Operating Systems document.

Notes:
On LINUX operating systems, you only need to check for the 32-bit libraries. On 64-bit machines if 32-bit libraries are installed then by default the 64-bit libs are also there.

On IBM i systems the JDK V1.8 must be installed in the /QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit/jre directory.

The following libraries are required on Linux:

Dynamic Workload Console installation fails on Windows 10 (166339)

Dynamic Workload Console installation fails on Windows 10 if JazzSm is installed in a virtual directory (for example, C:\Program Files) and a pop-up message is displayed asking for credentials. To circumvent the problem, provide the JazzSm credentials or install both Dynamic Workload Console and JazzSm in a non-virtual directory.


Software requirements

Top

This section contains the following sub-sections:

Software requirements for HCL Workload Automation

To obtain information about the following requirements, see the Supported Software document.

Notes:

DB2
For a complete list of supported operating systems for DB2, see the Supported Software document.
Bundled DB2
HCL Workload Automation is supplied with a version of the DB2 server and client for the supported operating systems. This version can be installed by you separately before the product installation.

Note: The bundled version of DB2 is provided solely for use with HCL Workload (see the product license for details).

Non-Bundled DB2
If you are using a supported version of DB2 for which you have purchased a license (a non-bundled DB2), then HCL Workload Automation will support it provided that the product edition is the same as the Bundled DB2 product edition or is a product edition with higher entitlements.
Oracle
The Oracle database software is not supplied with HCL Workload Automation; you must use your own version of the Oracle database software. For a complete list of supported operating systems for Oracle, see the Supported Software document.



Plug-ins and Access Methods

To obtain the latest information about plug-ins and access methods, see the Supported Software document.

PeopleSoft

You must have access to the psjoa.jar file located in the ps_home\class directory of the indicated version.

SAP R/3

You must have one of the following installed, configured, and working: SAP R/3 version 6.10, 6.20, 6.30, 6.40, 7.00, 7.01, 7.02, 7.10, 7.11, 7.20, 7.30, 7.31, or 7.40.

To understand if a SAP system is compatible with IBM Workload Scheduler, check if your system exposes the following interfaces:

If the above interfaces are exposed, IBM Workload Scheduler supports the SAP system.

SAP R/3 Access Method Requirements

To have the SAP R/3 access method work correctly, ensure that you have installed the SAP NetWeaver RFC Library. At least SDK 7.20 Support Package SP000 patch level 000028 is required. You must download these libraries from the SAP Service Marketplace (visit http://service.sap.com/connectors) and copy them to the TWS_home\methods directory. For details, refer to SAP note 1025361.

SAP Notes

The following is a list of the SAP Notes to apply:

9
SAP Basis Version SAP Notes
6.10 357924, 399449, 435111, 453135, 517672, 602683, 604496, 610480, 612564, 635095, 684106, 758829, 784446, 790615, 792767, 833777
6.20 602683, 604496, 612564, 635095, 684106, 758829, 792767, 833777, 1079601, 1257432, 1299738
6.30 602683, 604496, 612564, 684106, 758829, 792767, 833777, 1299738
6.40 602683, 604496, 612564, 635095, 684106, 758829, 784446, 790615, 792767, 833777, 1079601, 1257432, 1299738
7.00 684106, 792767, 833777, 862989, 1257432, 1299738
7.01 1658978, 1402400, 1447880, 1461421, 1639210
7.02 786412, 1658978, 1402400, 1447880, 1461421, 1639210
7.10 729317, 1257432, 1299738
7.20 786412, 1658978, 1402400, 1447880, 1461421, 1639210
7.30 1658978, 1447880, 1639210
7.31 1658978, 1447880, 1639210
7.40 None

Prerequisite SAP Notes for r3batch

SAP Business Warehouse

Ensure that you have the required SAP Business Warehouse Support Package as follows:

SAP Business Warehouse Versions SAP Notes
3.0B, 3.50 786748, 786749, 795858, 826878, 1059049
3.10 786748, 786749, 795858, 826878
7.0 826878, 1059049, 1049735, 1100457, 1130034, 1723482
7.01 1723482
7.02 1723482
7.10 1723482
7.11 1723482
7.20 1723482
7.30 1723482
7.31 1723482
7.40 None

SAP Solution Manager

To start Dynamic Workload Console from SAP Solution Manager, install the following SAP notes in the specified order:

  1. 1999878: Several SMSE extensions
  2. 2029063: Job Management creates incorrection permalink URLs for external HCL Workload Automation
  3. 2164341: URL checking

z/OS

You must have the following software installed, configured, and working:

Software requirements Versions
TCP/IP One of the following:
  • IBM V3.1, or later
  • Interlink V3.1, or later
  • Open Connect V2.3, or later
Job Scheduling Interface
  • JES2 or JES3.
    Note: In a z/OS Parallel Sysplex® environment, a JES job must be run on the LPAR where it is submitted.
  • OPCinterface: IBM Tivoli Workload Scheduler for z/OS.

Software requirements for WebSphere Application Server

HCL Workload Automation no longer includes an embedded version of WebSphere Application Server, which must therefore be installed as a separate entity. The supported version of WebSphere Application Server is V8.5.5.9 and subsequent fixpacks. For more information, see the WebSphere Application Server Detailed System Requirements website, browse to the relevant version and follow the appropriate links.

Supported LDAP Servers

For a list of the LDAP servers supported by HCL Workload Automation, go to the WebSphere Application Server Detailed System Requirements website, browse to the relevant version and follow the appropriate links.

Support for Internet Protocol version 6

HCL Workload Automation supports Internet Protocol version 6 (IPv6) in addition to IPv4. To help you in the transition from an IPv4 environment to a complete IPv6 environment, HCL Workload Automation provides IP dual-stack support. The product communicates using both IPv4 and IPv6 protocols simultaneously with other applications using IPv4 or IPv6.


Hardware requirements

Top

This section contains the following sub-sections:

Permanent disk space requirements when installing the product

To obtain the latest information about permanent disk space requirements when installing HCL Workload Automation on supported operating systems, see the Supported Hardware document.

Notes:
  1. Space for RDBMS: The disk space requirements listed in the report do not include the space required for the RDBMS software you have chosen, details of which can be obtained from their support documentation.

    Nor do they include the additional space requirement for the base support of HCL Workload Automation (without scheduling data), which is 2 GB.

  2. Space requirements for operating HCL Workload Automation: The disk space requirements listed in the report does not include the space required to operate HCL Workload Automation. For this you must consider the additional space required for the following:

    The space required is very subjective and depends on how you use HCL Workload Automation. If you are already a user of the product, you will have an idea of how much space it currently occupies. However, you should bear in mind that each version of the system uses more disk space than the previous one. If you are a new user you will probably set up a test system to help you grow familiar with the product and you should be able to scale up the operating space requirements of the test system to give you an indication of how much space you will be using in a fully functional live system.

Temporary space requirements

To obtain the latest information about temporary space requirements, see the Supported Hardware document.

Virtual memory swap space requirements

HCL Workload Automation requires a minimum of 2 GB of virtual memory swap space on the file system of any operating system.

Memory requirements

Table 2: Memory (MB) summarizes the memory requirements for the various components, on all operating systems:

Table 2: Memory (MB)
Memory MDM or BKM or
DDM or BDDM
Dynamic agent
or
z-centric agent
Fault-tolerant agent
CLI
Recommended 2560 512 1024 512
Required 2048 512 512 512

Memory requirements for Installation Manager

HCL Workload Automation and its components are installed using IBM Installation Manager. Table 3: Memory Requirements to run the Installation Manager (MB) summarizes the memory requirements indicated for running the Installation Manager in interactive or in silent mode.

Table 3: Memory Requirements to run the Installation Manager (MB)
Operating system Physical memory Temporary space
Windows 200 200
Solaris 200 200
Linux 200 200
AIX 200 200

Note:


© Copyright HCL Technologies Limited 2016, 2018.

Original Publication Date

2018/03/30