Installing from the command-line interface

Install IBM Workload Scheduler from the command-line interface based on a typical installation scenario. Variations to the typical scenario are described in the FAQ sections.

Before you get started, download the installation images and verify the prerequisites, as described in sections Downloading installation images and Prerequisites.

Downloading installation images

Steps to take when downloading images on your workstation.

You can download installation images from IBM Fix Central.

Ensure that your workstation has sufficient space to store the compressed file containing the installation images. For more information about system requirements, see Exigences système détaillées d'IBM Workload Scheduler.
From IBM Fix Central, download the compressed file, containing the latest product image, to a temporary directory.
Extract the installation image from the downloaded file and verify that the installation image is complete.
Extract the content of the ZIP files into a directory, using one of the extraction tools available on your system or that can be downloaded from the internet. The tool you use must be able to keep the file permissions on the extracted files, for example, infozip.
On Windows™ systems, ensure that you extract the image into a path that is not very long, otherwise, the file name might be truncated. The maximum length allowed is 255 characters.
If you are installing on a UNIX™ operating system, run the following command:
```
 chmod -R 755 <imagesDir>  
```
Note: To extract the .zip file onto a Windows 64-bit system, ensure that the image is not located on the desktop because the Windows operating system extract tool might encounter a problem. Choose another directory into which to extract the product image.
On z/OS systems, to install the Dynamic Workload Console perform the following steps:
1. Transfer the 10.x.x-IBM-DWC-Zsystem.pax file using the FTP protocol in binary to your USS environment.
2. Restore the code by issuing the following command:
```
pax -rf 10.x.x-IBM-DWC-Zsystem.pax
```
Note: DB2 is available for download from IBM Passport Advantage only. The latest versions of WebSphere Application Server Liberty Base can be downloaded from Recommended updates for WebSphere Application Server Liberty. For further details, see the 10.2.4 Quick Start Guide available from IBM Fix Central.

Prerequisites

When installing IBM Workload Scheduler components, consider the following prerequisites.

To produce a dynamic report that lists the supported operating systems, click Supported operating systems.

For a complete list of the correct prerequisite versions to install, open the Related software report and click on the Prerequisites tab.

For a complete list of system requirements (disk spaces, temporary spaces and RAM usage), see Exigences système détaillées d'IBM Workload Scheduler.

WebSphere Application Server Liberty Base: The latest versions of WebSphere Application Server Liberty Base can be downloaded from Recommended updates for WebSphere Application Server Liberty. For information about WebSphere Application Server Liberty Base issues and restrictions, see Runtime environment known issues and restrictions.

Before you install IBM Workload Scheduler for the first time, you must have one of the following databases installed. The following requirements apply to the RDBMS systems:

DB2

DB2® Enterprise Server Edition

A version of DB2 is bundled with the installation image.

You can install DB2 Server and the master domain manager or Dynamic Workload Console on the same workstation, then configure the database drivers from any workstation in your environment.

You can install DB2 manually.

Oracle and Amazon RDS for Oracle

You can install Oracle in the following ways:

Oracle Enterprise Edition: The advantage of choosing Oracle Enterprise Edition is that you can implement the Oracle Partitioning feature to improve the performance of event-driven workload automation. This improves rule management performance, in particular the following queries: event_rule_instance, action_run, and operator_messages. For information about event-driven workload automation, see Exécution de l'automatisation de la charge de travail gérée par événements.
Oracle Standard Edition: Oracle Standard Edition does not include the Oracle Partitioning feature. Installing this edition does not improve the performance of event-driven workload automation.
Amazon RDS for Oracle: Amazon RDS for Oracle is a robust and convenient option for managing Oracle databases in the cloud. It handles routine database tasks such as provisioning, patching, backup, recovery, and scaling, allowing you to focus on application development.

For supported versions, see the IBM Workload Scheduler System Requirements Document at Exigences système détaillées d'IBM Workload Scheduler.

Note:

When installing the product on a 64-bit library operating system, use an Oracle database on a 64-bit library.
When upgrading:
- If you already have an RDBMS installed and you want to upgrade it, you must upgrade it after you upgrade IBM Workload Scheduler.
- Use an Oracle database on a 64-bit library when installing the product on a 64-bit library.

For information about upgrading the RDBMS, see Data maintenance.

MSSQL

Before you create the IBM Workload Scheduler schema on the database, you must have created the directory where the IBM Workload Scheduler table spaces will be placed when the IBM Workload Scheduler schema is created. The default is C:\MSSQL.

Azure SQL: A family of managed, secure, and intelligent products that use the SQL Server database engine in the Azure cloud
Google Cloud SQL for SQL server: A fully-managed database service that helps you set up, maintain, manage, and administer your relational databases on Google Cloud Platform.
Amazon RDS for MSSQL: Amazon RDS for MSSQL offers a powerful and user-friendly solution for managing MSSQL databases in the cloud. It takes care of routine tasks like provisioning, patching, backups, recovery, and scaling, so you can concentrate on developing your applications.

PostgreSQL

A powerful, open source object-relational database system, which provides reliability, feature robustness, and performance.

Local user

The installation of IBM Workload Scheduler requires the creation of a local user. For more information, see Creating the IBM Workload Scheduler administrative user.

Scanning system prerequisites for IBM Workload Scheduler

Before installing or upgrading the product, IBM Workload Scheduler automatically runs a scan on your system.

When installing IBM Workload Scheduler using the serverinst script, the script first runs the scanner to verify system prerequisites.

Note: To ensure that the prerequisite scan process does not fail, verify that the bc executable is present on the local system and that it is set in the PATH environment variable. If you do not want to install the bc executable, you can skip the prerequisites check by using the skipcheckprereq parameter when running the serverinst and twsinst parameters. For more information about the bc executable, see bc, an arbitrary precision calculator language. For more information about installation commands, see Server components installation - serverinst script and Agent installation parameters - twsinst script.

Having an environment that meets the product system requirements ensures that an installation or upgrade succeeds without any delays or complications.

The scan verifies that:

The operating system is supported for the product.
On UNIX operating systems, the necessary product libraries are installed.
There is enough permanent and temporary disk space to install both the product and its prerequisites.
There is enough memory and virtual memory.

Note: The scan verifies only that the environment meets the requirements of IBM Workload Scheduler. It does not check the requirements for other components, such as DB2.

If any of these checks fails, IBM Workload Scheduler returns an error message.

The log files for the server components are located in:

On Windows operating systems:: <TWA_home>\logs\serverinst<version_number>.log
On UNIX and Linux™ operating systems:: <TWA_DATA_DIR>/installation/logs/serverinst<version_number>.log

The log files for the Dynamic Workload Console are located in:

On Windows operating systems:: <DWC_home>\logs\dwcinst<version_number>.log
On UNIX and Linux operating systems:: <DWC_DATA_dir>/installation/logs/dwcinst<version_number>.log

The log files for the agents are located in:

On Windows operating systems:: <TWA_home>\logs\twsinst<interp><user_name><version_number>.log
On UNIX and Linux operating systems:: <TWA_DATA_DIR>/installation/logs/twsinst<interp><user_name><version_number>.log

You can decide to rerun the installation or upgrade without executing the prerequisite scan. If you set the -skipcheckprereq parameter to true when performing the installation, the installation script does not execute the prerequisite scan. If a problem occurs, an error is displayed, the component is installed or upgraded, but might not work. For more information about the -skipcheckprereq parameter in all installation scripts, see Reference.