Chapter 3. Tivoli Workload Scheduler V8.3: New installation 67
3.2.3 Creating scheduling objects for the new master
After installing the Job Scheduling Console V8.3, the next task is to define the
scheduling objects. In this section, we discuss the definition of a UNIX and a
Windows workstation, defining the final job stream and necessary jobs, and the
Tivoli Workload Scheduler user for the Windows fault-tolerant agent (FTA).
1. To start the Job Scheduling Console, click the Job Scheduling Console
V8.3 icon, as shown in Figure 3-39.
Figure 3-39 The Job Scheduling Console V8.3 icon
68 Getting Started with IBM Tivoli Workload Scheduler V8.3
Alternatively, you can start it from the Programs menu. Select Program
Job Scheduling Console V8.3 Job Scheduling Console V8.3, as shown
in Figure 3-40.
Figure 3-40 Selecting Job Scheduling Console V8.3 icon from programs menu
Chapter 3. Tivoli Workload Scheduler V8.3: New installation 69
Figure 3-41 shows the Job Scheduling Console V8.3 banner.
Figure 3-41 The Job Scheduling Console splash window
2. The next window prompts for a Preferences file or an Engines file (see
Figure 3-42). This allows you to load a predefined file that has either
standardized or customized views. Because this is a new installation of the
application, click Cancel to proceed with the Job Scheduling Console
initialization.
Figure 3-42 The load preferences files window
70 Getting Started with IBM Tivoli Workload Scheduler V8.3
3. Figure 3-43 shows the welcome window, select Dismiss this window and
work on my own and click OK.
Figure 3-43 The Job Scheduling Console welcome window
4. A warning is shown stating that the Job Scheduling Console did not find any
defined engines, as shown in Figure 3-44. This is a normal message after the
Job Scheduling Console is started for the first time after the initial installation.
Click OK to proceed.
Figure 3-44 Warning window stating the engine does not exist
Chapter 3. Tivoli Workload Scheduler V8.3: New installation 71
5. Figure 3-45 shows the default engine definition window.
Figure 3-45 The default engine definition window
Note: The port number shown in the new engine definition window is not
the netman port used to link workstations. The requested port is one of the
six new ports that was part of the Tivoli Workload Scheduler V8.3
installation, see Figure 3-11 on page 45. The port name is Bootstrap/RMI
and by default is port 31117. Each engine instance on the same
workstation must use a different port number.
You can determine the Tivoli Workload Scheduler ports that are used by
the instance by viewing the file serverindex.xml in
TWSuser_home/appserver/profiles/twsprofile/config/cells/DefaultNode/
nodes/DefaultNode and searching for BOOTSTRAP_ADDRESS. The line
contains the port number assigned to BOOTSTRAP.

Get Getting Started with IBM Tivoli Workload Scheduler V8.3 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.