Problems installing on Linux

The following problems could occur:

• An InstallShield wizard installation fails on Linux with an error installing the bundled JRE
• A non-English installation on Linux finishes correctly, but the start of Tivoli Workload Scheduler gives one or more errors
• Java Virtual Machine (JVM) failure when installing the Dynamic Workload Console on a Red Hat Enterprise Linux (RHEL) Version 5 or a Suse Linux system Version 11
• On Red Hat Enterprise Linux 6.0 installation fails.

An InstallShield wizard installation fails on Linux with an error installing the bundled JRE

You are installing on Linux where the required level of JRE is not installed. The installation wizard tries to install the bundled JRE but fails. The following message is received:

This application requires a Java Run Time Environment (JRE)
to run. Searching for one on your computer was not successful.
Please use the command line switch -is:javahome to specify
a valid JRE.  For more help use the option -is:help.

Cause and solution

The probable cause is that the bc utility is a prerequisite of the InstallShield wizard, but is not installed by default on all Linux platforms (on Red Hat Linux, version 2.1, for example, it is included only in Service Pack 2).

To check for the existence of the utility run this query on the rpm registry: rpm -q bc

If the utility is missing, consult your operating system's support resources to determine how to obtain it. When it is successfully installed, rerun the installation.

A non-English installation on Linux finishes correctly, but the start of Tivoli Workload Scheduler gives one or more errors

You installed a non-English version of Tivoli Workload Scheduler on Linux, but when the product starts errors are given.

Cause and solution

The problem might be the code page of the workstation. To support languages other than English, Tivoli Workload Scheduler requires the code page to be UTF8. Reset the code page and restart the product and you should have no reoccurrence of this problem.

|Java Virtual |Machine (JVM) failure when installing on a Red Hat Enterprise Linux (RHEL) Version 5 or a Suse Linux system Version 11|

Problem description:

When working with Tivoli Workload Scheduler on a Red Hat Enterprise Linux Version 5 or a Suse Linux system Version 11, you might receive the error |"Failed to find VM - aborting".

Cause and solution

Linux systems have a new |security feature named 'Security Enhanced Linux', or SELinux for short. |A weaker version of SELinux was included in Red Hat Enterprise Linux Version 4, and was disabled |by default. On these versions of Red Hat Enterprise Linux and Suse Linux, |this security feature is enabled by default. SELinux helps to keep |the host secure from certain types of malicious attacks. However, |the default settings have been known in many cases to prevent Java from running properly.

To fix this issue, choose one of the following options:

|
• Configure SELinux so that it knows that the Tivoli Workload Scheduler Java related processes are acceptable |to run.
|
• Change the mode of SELinux to Permissive by |entering setenforce 0 on the command line. SELinux will |be fully enabled again the next time the system is rebooted or if setenforce |1 is entered on the command line. For the Dynamic Workload Console to function, |you must set setenforce 0. For more information about setenforce, |see the documentation for your operating system.

On Red Hat Enterprise Linux 6.0 installation fails

On Red Hat Enterprise Linux 6.0, you launched the installation, but it fails with the following error message written in the twsismp.log file:

AWSJIS138E The specified instance name "instance_name"
does not exist on the DB2 server.

Cause and solution

The problem occurs because the db2idefs file cannot be found by the installation program.

To solve the problem, perform the following steps:

1. Add to the PATH environment variable the path where the db2idefs file is located, for example /opt/ibm/db2/V9.7/instance.
2. Launch the installation again.