Detailed system requirements for IBM Workload Scheduler, version 9.4

To view the IBM Workload Scheduler Release Notes, go to the Release Notes page.

To view the IBM Dynamic Workload Console, go to the Dynamic Workload Console System Requirements page.

To access the IBM Workload Scheduler documentation, see the online Knowledge Center.

Acronyms and abbreviations used in the tables in this section

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

Supported operating systems for the engine

To obtain the latest information about the required versions for each supported operating system, run the related report:

• AIX
• HP
• IBMi
• Linux
• Solaris
• Windows
• z/OS

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:

• libstdc++.so.5 (with the exclusion of Linux Red Hat, version 8)
• libstdc++.so.6
• libgcc_s.so.1

On AIX OS version 7.2.5.0, ensure you have installed APAR IJ30808. For more information, see https://www.ibm.com/support/pages/apar/IJ30808.

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 (i.e. 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.

This section contains the following sub-sections:

• Software requirements for IBM Workload Scheduler
• Plug-ins and Access Methods
• Software requirements for WebSphere Application Server
• Supported operating systems and software requirements for the Integration Workbench
• Supported operating systems and software requirements for the Job Brokering Definition Console
• Supported LDAP Servers
• Support for Internet Protocol version 6

Software requirements for IBM Workload Scheduler

To obtain the latest information about the following requirements, run the Software Requirements report and browse to the relevant section:

• Application Servers
• Databases
• Integration Middleware
• Java
• Web Browsers

Notes:

DB2

For a complete list of supported operating systems for DB2, run the Software Requirements dynamic report.

Bundled DB2

IBM Workload Scheduler 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 IBM Workload Scheduler (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 IBM Workload Scheduler 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 IBM Workload Scheduler; you must use your own version of the Oracle database software. For a complete list of supported operating systems for Oracle run the Software Requirements dynamic report.

Plug-ins and Access Methods

To obtain the latest information about plug-ins and access methods, run the Data Integration report and select the Supported Software tab.

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.

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. Refer to SAP note 1025361 for details.

SAP Notes

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

9

• Note 399449 resolve print parameter issues. Notes 357924 and 517672 are release-independent.
• Note 758829 resolves job step management problems.
• Notes 602683, 604496, and 612564 are required if you want to use the BC-XBP 2.0 interface.
• Notes 684106 applies only to Windows operating systems.
• Server groups are supported by IBM Workload Scheduler on the following versions of SAP Basis:
  • 6.10 with support package 40
  • 6.20 with support package 41
  • 6.40 with support package 30
  • 6.40 with support package 30
  • 7.00 with support package 27
  • 7.01 with support package 11
  • 7.02 with support package 11
  • 7.10 with support package 15
  • 7.11 with support package 09
  • 7.20 with support package 07
  • 7.30 with support package 07
  • 7.31 with support package 03
  For a list of functions and limitations for SAP R/3 server groups, refer to the following SAP Notes:
  • 786412
  • 729317
  • 612838
  • 1658978
  • 1402400

Prerequisite SAP Notes for r3batch

• Modify job header, Job class missing (SAP Note 1447880)
  • 7.00 with support package 26
  • 7.01 with support package 11
  • 7.02 with support package 10
  • 7.10 with support package 13
  • 7.11 with support package 08
  • 7.20 with support package 06
  • 7.30 with support package 05
  • 7.31 with support package 01
• Modify SAP variant, Variant type missing (SAP Note 1461421)
  • 7.00 with support package 22
  • 7.01 with support package 07
  • 7.02 with support package 05
  • 7.10 with support package 11
  • 7.11 with support package 06
  • 7.20 with support package 04
• Modify SAP variant, Variant attributes overwritten (SAP Note 1639210)
  • 7.00 with support package 26
  • 7.01 with support package 11
  • 7.02 with support package 11
  • 7.10 with support package 14
  • 7.11 with support package 09
  • 7.20 with support package 07
  • 7.30 with support package 07
  • 7.31 with support package 02

SAP Business Warehouse

• InfoPackages are supported by Tivoli Workload Scheduler for Applications on SAP Business Warehouse systems 3.0B, or later.
• Process chains are supported on SAP Business Warehouse systems version 3.0B, or later.
• The Support Package 9 (SAPKW31009) for SAP Business Warehouse version 3.1 is required so that the extended agent is able to launch Process Chains.

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

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 scheduler
3. 2164341: URL checking

z/OS

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

Software requirements for WebSphere Application Server

IBM Workload Scheduler 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 operating systems and software requirements for the Integration Workbench

The IBM Workload Scheduler Integration Workbench is available on the following platforms:

• Linux on x86-64
• Microsoft Windows on x86-64

It requires Eclipse, version 4.2.2

The version of the Java Development Kit used to develop all application programming interfaces and plug-ins is 1.7.

Supported operating systems and software requirements for Job Brokering Definition Console

The Job Brokering Definition Console is available on the following platforms:

• Linux on x86-64
• Microsoft Windows on x86-64

Supported LDAP Servers

For a list of the LDAP servers supported by IBM Workload Scheduler, 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

IBM Workload Scheduler 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, IBM Workload Scheduler provides IP dual-stack support. The product communicates using both IPv4 and IPv6 protocols simultaneously with other applications using IPv4 or IPv6.

This section contains the following sub-sections:

• Permanent disk space requirements
• Temporary space requirements
• Virtual memory swap space requirements
• Memory requirements
• Memory requirements for Installation Manager

Permanent disk space requirements when installing the product

To obtain the latest information about permanent disk space requirements when installing IBM Workload Scheduler on supported operating systems, run the Hardware requirements report and and click on the relevant operating system link.

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 IBM Workload Scheduler (without scheduling data), which is 2 GB.

2. Space requirements for operating IBM Workload Scheduler: The disk space requirements listed in the report does not include the space required to operate IBM Workload Scheduler. For this you must consider the additional space required for the following:
   • Database data
   • Symphony file
   • Archive files (and their retention period)
   • Log files (and their retention period)
   • Temporary files that are placed on the local hard drive
   • Files associated with the jobs managed by IBM Workload Scheduler

   The space required is very subjective and depends on how you use IBM Workload Scheduler. 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, run the Requirements report, click on the Hardware tab, and scroll to the relevant operating system.

Virtual memory swap space requirements

IBM Workload Scheduler 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 requirements for Installation Manager

IBM Workload Scheduler 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)

Note:

• To run the Installation Manager GUI on Red Hat Enterprise Linux Server 6 (64-bit), the following operating system libraries are required:
  • libXtst+
  • compat-libstdc+
• To run the Installation Manager GUI on AIX, ensure that the operating system has the required operating system libraries listed in the Required gtk libraries for Installation Manager on AIX technote.

Top

© Copyright International Business Machines Corporation 2006, 2016. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

© Copyright HCL Technologies Limited 2016.