Post-installation configuration

The most common configuration steps to be performed after completing the installation.

After successfully installing IBM Workload Scheduler, there are a number of recommended configuration steps to be performed that are described in more detail in this section. Also consider the FAQs listed below.

FAQ - Security configurations

A list of questions and answers related to security configurations:

When installing the IBM Workload Scheduler, you might have the need to customize some parameters to suit your environment.

Can I install any IBM Workload Scheduler components without setting up the SSL configuration?: No, starting from version 10.2.1, certificates, either default or custom, are required when installing IBM® Workload Scheduler. You can no longer install IBM Workload Scheduler without securing your environment with certificates.
Q:How do I set up SSL communication using custom certificates for master domain manager and dynamic agent?: See the detailed explanation in Customizing certificates for master domain manager and dynamic agent communication.
Q:How do I set up SSL communication using custom certificates for master domain manager and Dynamic Workload Console?: See the detailed explanation in Customizing certificates for master domain manager and Dynamic Workload Console communication.
Q: How do I set up SSL communication using custom certificates for agents?: You can use the -sslkeysfolder and --sslpassword parameters when installing fault-tolerant agents and dynamic agents with the twsinst command. For more information, see Agent installation parameters - twsinst script.
How do I configure master domain manager and dynamic domain manager in SSL mode?: See the detailed explanation in Configuring your master domain manager and dynamic domain manager in SSL mode.
Q: Is FIPS supported?: FIPS compliance is not supported in the current product version. This is because OpenSSL 3.0 libraries do not provide a FIPS-compliant validation algorithm for P12 certificates. Development is in progress with the aim of supporting FIPS in upcoming releases.
How do I configure Single Sign-On?: Single Sign-On (SSO) is a method of access control that allows a user to authenticate once and gain access to the resources of multiple applications sharing the same user registry. For more information, see Configuring the Dynamic Workload Console for Single Sign-On.