i b m w o r kl o a d s c h e d ul e r ibm€¦ · installing a master domain manager or its backup...

IBM Workload Scheduler

Planning and InstallationVersion 9 Release 4

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 441.

This edition applies to version 9, release 4, modification level 0 of IBM Workload Scheduler (program number5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 1999, 2016. © Copyright HCL Technologies Limited 2016, 2018

Contents

Figures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

About this publication . . . . . . . . xiWhat is new in this release . . . . . . . . . xiWho should read this publication . . . . . . . xiAccessibility . . . . . . . . . . . . . . xiTechnical training . . . . . . . . . . . . xiiSupport information . . . . . . . . . . . xii

Part 1. Planning . . . . . . . . . . 1

Chapter 1. Known problems andlimitations . . . . . . . . . . . . . . 3

Chapter 2. Network planning . . . . . . 5IBM Workload Scheduler environment. . . . . . 5

IBM Workload Scheduler interfaces . . . . . 10Planning the environment . . . . . . . . . 11

Distributed workload environment with staticscheduling capabilities . . . . . . . . . . 11Distributed workload environment with dynamicscheduling capabilities. . . . . . . . . . 12Distributed workload environment with staticand dynamic scheduling capabilities . . . . . 15End-to-end workload environment . . . . . 16Workload environment integrated with externalsystems. . . . . . . . . . . . . . . 17Distributed-driven workload environment forz/OS . . . . . . . . . . . . . . . 18

Planning domains . . . . . . . . . . . . 20Localized processing in your domain . . . . . 20Considerations in planning domains . . . . . 20Single domain network . . . . . . . . . 22Multiple domain network . . . . . . . . 23

Workstation classes . . . . . . . . . . . . 25Time zone considerations . . . . . . . . . . 25

Part 2. IBM Workload Scheduler . . 27

Chapter 3. Preparing for installation . . 29Installation overview . . . . . . . . . . . 29Installation method . . . . . . . . . . . . 30

Installation wizard . . . . . . . . . . . 30Silent mode . . . . . . . . . . . . . 30The twsinst script for agents. . . . . . . . 30

Downloading installation images on yourworkstation . . . . . . . . . . . . . . 31Creating a network repository . . . . . . . . 31Accessing the installation media . . . . . . . 33

Installation media . . . . . . . . . . . 33Installation considerations . . . . . . . . . 34

Directories created outside of TWA_home atinstallation time . . . . . . . . . . . . 35Windows services . . . . . . . . . . . 36

Chapter 4. Prerequisites . . . . . . . 37Supported operating systems . . . . . . . . 37Relational database management systems . . . . 37

Installing DB2 . . . . . . . . . . . . 38Installing Oracle . . . . . . . . . . . . 38Installing Informix Dynamic Server . . . . . 39Installing Microsoft SQL Server . . . . . . . 40

IBM Workload Scheduler user . . . . . . . . 40Windows user domain rights and structure . . . 41Considerations for Windows domain controllersrunning Microsoft Active Directory . . . . . 42Checking environment settings for WindowsVista users. . . . . . . . . . . . . . 43Umask settings for UNIX root user . . . . . 43

Scanning system prerequisites for IBM WorkloadScheduler . . . . . . . . . . . . . . . 44

Scanning system prerequisites for InstallationManager . . . . . . . . . . . . . . 45

Chapter 5. Creating or upgrading theIBM Workload Scheduler databasetables before installing or upgrading . . 47Creating or upgrading the database schema if youare using DB2 . . . . . . . . . . . . . 48

Creating the database tables if you are using DB2 49Upgrading the database tables if you are usingDB2 . . . . . . . . . . . . . . . . 57

Creating or upgrading the database tables if you areusing Oracle . . . . . . . . . . . . . . 59

Creating the database tables if you are usingOracle . . . . . . . . . . . . . . . 61Upgrading the database tables if you are usingOracle . . . . . . . . . . . . . . . 71

Creating or upgrading the database schema if youare using Informix Dynamic Server . . . . . . 74

Customizing the properties file for InformixDynamic Server . . . . . . . . . . . . 74Generating the SQL files on Informix . . . . . 76Running scripts to create or upgrade the SQLschema on Informix . . . . . . . . . . 76

Creating or upgrading the database schema if youare using Microsoft SQL Server . . . . . . . . 82

Customizing the properties file for Microsoft SQLServer . . . . . . . . . . . . . . . 82Generating the SQL files on Microsoft SQL Server 84Running scripts to create or upgrade the SQLschema on Microsoft SQL Server . . . . . . 84

Chapter 6. Installing . . . . . . . . . 93Changing temporary directory when installing usingInstallation Manager . . . . . . . . . . . 93

iii

||

|||||||||||

Installing main components . . . . . . . . . 93Selecting installation methods . . . . . . . 93Installing a master domain manager or itsbackup . . . . . . . . . . . . . . . 94Installing a dynamic domain manager or itsbackup . . . . . . . . . . . . . . 122Installing agents . . . . . . . . . . . 139Discovering installed components . . . . . 156

Installing additional components . . . . . . . 156Installing the Job Brokering Definition Console 157Installing IBM Workload Scheduler IntegrationWorkbench . . . . . . . . . . . . . 158

Chapter 7. Upgrading . . . . . . . . 163Before upgrading . . . . . . . . . . . . 164


Files and folders changed during the upgrade . . 166Files not changed during upgrade . . . . . . 167Upgrading single components . . . . . . . . 168

Performing a safe upgrade . . . . . . . . 169Upgrading a master domain manager instanceor its backup . . . . . . . . . . . . 169Upgrading a dynamic domain manager instanceor its backup . . . . . . . . . . . . 192Upgrading agents and domain managers . . . 204

Upgrading when there are corrupt registry files 226Re-creating registry files using twsinst . . . . 226

Chapter 8. Centralized agent update 227Centralized agent update by using DynamicWorkload Console . . . . . . . . . . . . 227

Scheduling the centralized agent update . . . 229Updating fault-tolerant agent and dynamicagent instances . . . . . . . . . . . . 231

Troubleshooting scenarios . . . . . . . . . 232Prerequisite scan detects missing prerequisitesand the centralized agent update fails . . . . 233Centralized agent update fails because thetemporary backup directory is too small . . . 233Manually restore agent instances when theautomatic restore fails . . . . . . . . . 234Centralized agent update does not complete andno operator message is displayed. . . . . . 235Centralized update fails on agents in paralleldue to WebSphere Application Server wrongmemory management . . . . . . . . . 236

Chapter 9. Configuring . . . . . . . 237Setting the environment variables . . . . . . 237Configuring a master domain manager . . . . . 238Configuration steps for a master domain managerconfigured as backup. . . . . . . . . . . 239Configuring a domain manager . . . . . . . 240Configuring a backup domain manager . . . . 241Configuring a dynamic domain manager . . . . 241Configuration steps for a dynamic domainmanager configured as backup . . . . . . . 242Configuring a fault-tolerant agent . . . . . . 242Configuring a dynamic agent . . . . . . . . 243

Automatically register agents to pools . . . . 244Configuring a remote command-line client . . . 246

Configuring SSL connection between remotecommand-line client and master domainmanager . . . . . . . . . . . . . . 247

Configuring a z-centric agent on Windowsoperating systems . . . . . . . . . . . . 248Adding a feature . . . . . . . . . . . . 249

Procedure . . . . . . . . . . . . . 249Configuring WebSphere Application Server . . . 251Enabling dynamic scheduling after installation . . 251

Chapter 10. Uninstalling . . . . . . . 255Uninstalling the main components . . . . . . 255

Selecting uninstallation methods . . . . . . 255Uninstalling a master domain manager or itsbackup . . . . . . . . . . . . . . 256Uninstalling a dynamic domain manager or itsbackup . . . . . . . . . . . . . . 257Performing a silent uninstallation . . . . . 258Uninstalling agents using the twsinst script . . 259

Chapter 11. Troubleshootinginstallation, migration, anduninstallation . . . . . . . . . . . 263Installation log files . . . . . . . . . . . 263

Installation Manager wizard, silent installationand uninstallation log files . . . . . . . . 263WebSphere Application Server profile log files 265DB2 installation log files. . . . . . . . . 266The twsinst log files . . . . . . . . . . 266

Packaging log files for support . . . . . . . 267Analyzing return codes for agent installation,upgrade, restore, and uninstallation . . . . . . 267Problem scenarios: install, reinstall, upgrade,migrate, and uninstall . . . . . . . . . . 269

Problems installing on Windows operatingsystems . . . . . . . . . . . . . . 269Other installation problems. . . . . . . . 272Reinstallation problems . . . . . . . . . 292Upgrade problems. . . . . . . . . . . 293Uninstallation problems . . . . . . . . . 308Fix pack installation problems . . . . . . . 308

Uninstalling IBM Workload Scheduler manually 309Uninstalling manually on Windows operatingsystems . . . . . . . . . . . . . . 309Uninstalling manually on UNIX operatingsystems . . . . . . . . . . . . . . 311Problems during manual uninstall . . . . . 313

Part 3. IBM Workload Scheduleron IBM i systems . . . . . . . . . 315

Chapter 12. Prerequisites . . . . . . 317Scanning system prerequisites on IBM i systems 317

Chapter 13. Installing agents on IBM isystems. . . . . . . . . . . . . . 319Agent installation parameters on IBM i systems 321

iv IBM Workload Scheduler: Planning and Installation

||||||||||||

|||||||||||||||***||||||||||

--

Example installation of an agent on IBM i systems 324The twsinst script log files on IBM i systems. . . 324Analyzing return codes for agent installation,upgrade, restore, and uninstallation . . . . . . 325

Chapter 14. Configuring a dynamicagent . . . . . . . . . . . . . . . 329

Chapter 15. Upgrading agents on IBMi systems . . . . . . . . . . . . . 331Agent upgrade parameters on IBM i systems . . . 332Example upgrade of an agent on IBM i systems 334The twsinst script log files on IBM i systems. . . 334Analyzing return codes for agent installation,upgrade, restore, and uninstallation . . . . . . 335

Chapter 16. Uninstalling agents onIBM i systems . . . . . . . . . . . 339The twsinst script log files on IBM i systems. . . 339

Part 4. Dynamic Workload Console 341

Chapter 17. Overview of the DynamicWorkload Console . . . . . . . . . 343

Chapter 18. Preparing . . . . . . . . 345Directories created outside of TWA_home atinstallation time . . . . . . . . . . . . 345Downloading installation images on yourworkstation . . . . . . . . . . . . . . 346Creating a network repository . . . . . . . . 346Accessing the installation media . . . . . . . 347

Installation media . . . . . . . . . . . 348

Chapter 19. Dynamic WorkloadConsole prerequisites. . . . . . . . 351Supported operating systems . . . . . . . . 351Scanning system prerequisites for IBM WorkloadScheduler. . . . . . . . . . . . . . . 352


Chapter 20. Installing . . . . . . . . 355Selecting your installation method . . . . . . 355Changing temporary directory when installingusing Installation Manager . . . . . . . . . 355Installation procedure for Dynamic WorkloadConsole . . . . . . . . . . . . . . . 356

WebSphere Application Server profileconfiguration . . . . . . . . . . . . 358z/OS connector configuration . . . . . . . 359

Silent installation . . . . . . . . . . . . 360Checking system prerequisites for the DynamicWorkload Console . . . . . . . . . . . 361Performing a Dynamic Workload Console silentinstallation . . . . . . . . . . . . . 362Performing a Dynamic Workload Console andits prerequisites silent installation . . . . . 364

Encrypting user passwords for response files 366Accessing the Dynamic Workload Console . . . 368

Quick steps to define an IBM WorkloadScheduler engine connection . . . . . . . 369Quick steps to define an dynamic workloadbroker connection . . . . . . . . . . . 370

Starting and stopping the Dynamic WorkloadConsole . . . . . . . . . . . . . . . 371

Chapter 21. Configuring . . . . . . . 373Post-installation steps to configure the use ofLightweight Third-Party Authentication (LDAP). . 374

Chapter 22. Navigating the DynamicWorkload Console . . . . . . . . . 375First actions . . . . . . . . . . . . . . 375

Chapter 23. Upgrading . . . . . . . 377Upgrading overview . . . . . . . . . . . 377Upgrading Dynamic Workload Console V8.6 singleinstance . . . . . . . . . . . . . . . 378

Upgrading Dynamic Workload Console V8.6single instance on the same workstation . . . 378Upgrading Dynamic Workload Console V8.6single instance on a new workstation . . . . 381

Upgrading Dynamic Workload Console V8.6installed with one or more components in the samedirectory . . . . . . . . . . . . . . . 385Upgrading Dynamic Workload Console V9.1 andlater . . . . . . . . . . . . . . . . 385

Upgrading Dynamic Workload Console V9.1 orlater . . . . . . . . . . . . . . . 386Upgrading Dynamic Workload Console V9.1 orlater with silent upgrade . . . . . . . . 386Upgrading Dynamic Workload Console as anon-root user . . . . . . . . . . . . 387Upgrading Dynamic Workload Console as anon-root user with silent upgrade . . . . . 388

Chapter 24. Uninstalling . . . . . . . 391Uninstalling using the Installation Manager wizard 391Uninstalling in silent mode . . . . . . . . . 391

Chapter 25. Troubleshooting theinstallation, upgrade, anduninstallation . . . . . . . . . . . 393Installation and uninstallation log and trace files 393Manually uninstall the Dynamic Workload Consoleand the zConnector on Windows systems . . . . 393Manually uninstall the Dynamic Workload Consoleand the zConnector on UNIX systems . . . . . 394Troubleshooting scenarios . . . . . . . . . 396

Installation log files . . . . . . . . . . 396Problems with the interactive installation . . . 398Problems with the silent installation . . . . . 399

Part 5. Tutorials . . . . . . . . . 401

Contents v

|||

|||||

||

Chapter 26. Using the IBM WorkloadScheduler tutorial utility . . . . . . . 403Populating your IBM Workload Scheduler database 403

Objects used by the IBM Workload Schedulertutorial scenarios . . . . . . . . . . . 404

Overview of the scheduling scenarios . . . . . 405Creating and working with the production plan 405

Scenario 1: Creating the production plan andviewing its contents . . . . . . . . . . 406

Running the scheduling scenarios . . . . . . 406Scenario 2: Starting and stopping IBM WorkloadScheduler processes . . . . . . . . . . 406Scenario 3: Scheduling basics, how jobs arescheduled, and run order of jobs . . . . . . 407Scenario 4: Advanced scheduling, dependenciesfrom prompts, files, and resources . . . . . 407Scenario 5: Time dependencies and run cycles 408Scenario 6: Manual submission of jobs, jobstreams, and commands . . . . . . . . . 408Scenario 7: Recovery options and recovery jobs 408Scenario 8: Event-driven scheduling . . . . . 409Scenario 9: Using variable tables . . . . . . 409

Removing tutorial objects from the database . . . 410

Part 6. Appendixes . . . . . . . . 411

Appendix A. Registry file . . . . . . 413

Appendix B. The IBM WorkloadScheduler response file properties . . 415

Appendix C. The Dynamic WorkloadConsole response file properties . . . 431

Appendix D. The Job BrokeringDefinition Console response fileproperties . . . . . . . . . . . . . 437

Appendix E. DB2 tablespace relativepaths . . . . . . . . . . . . . . . 439

Notices . . . . . . . . . . . . . . 441Trademarks . . . . . . . . . . . . . . 443Terms and conditions for product documentation 443

Index . . . . . . . . . . . . . . . 445

vi IBM Workload Scheduler: Planning and Installation

Figures

1. Graphical overview of IBM Workload Schedulerenvironment to run static workload . . . . . 6

2. Graphical overview of IBM Workload Schedulerdynamic environment . . . . . . . . . 8

3. Distributed workload environment with staticscheduling capabilities . . . . . . . . . 12

4. Distributed workload environment withdynamic scheduling capabilities. . . . . . 14

5. Distributed workload environment with staticand dynamic scheduling capabilities . . . . 16

6. Workload environment integrated withexternal systems . . . . . . . . . . . 18

7. Distributed-driven workload environment forz/OS. . . . . . . . . . . . . . . 19

8. Single domain topology . . . . . . . . 229. Single domain topology on multiple sites 23

10. Multiple domain topology . . . . . . . 2411. Parallel upgrade procedure flowchart from a

V8.6. . . . . . . . . . . . . . . 17112. Parallel upgrade procedure flowchart from

V9.x. . . . . . . . . . . . . . . 172

vii

======

viii IBM Workload Scheduler: Planning and Installation

Tables

1. Features partially or not supported fordynamic scheduling. . . . . . . . . . 15

2. Required eImages . . . . . . . . . . 313. Symbolic link options . . . . . . . . . 354. DB2 Setup files . . . . . . . . . . . 385. Properties for DB2 upgrade procedure . . . 586. Upgrade script parameters . . . . . . . 597. Properties for Oracle upgrade procedure 728. Upgrade script parameters . . . . . . . 739. Installation response files . . . . . . . 117

10. Global installation response files . . . . . 12011. Installation response files . . . . . . . 13412. Global installation response files . . . . . 13713. Valid values for -lang and LANG parameter 14614. Installation syntax for agent installation with

agents in the same network zone . . . . . 15315. Installation syntax for agent installation with

agents in different network zones . . . . . 15416. Global installation response files . . . . . 16117. Upgrade deployment model for IBM

Workload Scheduler single componentinstance . . . . . . . . . . . . . 168

18. Upgrade response files . . . . . . . . 18519. Upgrade response files . . . . . . . . 20220. Required and optional attributes for the

definition of a centralized agent update job . 23021. Uninstallation response files . . . . . . 25922. Windows operating system agent return

codes . . . . . . . . . . . . . . 26723. UNIX or Linux operating system agent return

codes . . . . . . . . . . . . . . 26824. Valid values for -lang and LANG parameter 322

25. Windows operating system agent returncodes . . . . . . . . . . . . . . 325

26. UNIX or Linux operating system agent returncodes . . . . . . . . . . . . . . 326

27. Windows operating system agent returncodes . . . . . . . . . . . . . . 335

28. UNIX or Linux operating system agent returncodes . . . . . . . . . . . . . . 336

29. Required eImages . . . . . . . . . . 34630. Installation response files . . . . . . . 36431. Upgrade response files . . . . . . . . 36432. Global installation response files . . . . . 36633. Uninstallation response files . . . . . . 39234. Objects downloaded by the tutorial utility 40435. List of scheduling scenarios . . . . . . . 40536. Registry file attributes . . . . . . . . 41337. General information . . . . . . . . . 41538. User information . . . . . . . . . . 41639. Upgrade configuration (only for upgrade) 41640. Master configuration . . . . . . . . . 41641. Dynamic domain manager configuration 41842. Database configuration . . . . . . . . 42043. WebSphere configuration . . . . . . . 42744. Offering and features to install . . . . . . 42845. General information . . . . . . . . . 43146. WebSphere configuration . . . . . . . 43247. z/OS connector configuration . . . . . . 43348. Offering and features to install . . . . . . 43349. Upgrade settings . . . . . . . . . . 43450. Job Brokering Definition Console response file

properties . . . . . . . . . . . . . 437

ix

|||

|||||||||||

x IBM Workload Scheduler: Planning and Installation

About this publication

About this task

This IBM Workload Scheduler Planning and Installation provides information forplanning, installing, migrating, and configuring an IBM Workload Schedulernetwork.

What is new in this releaseLearn what is new in this release.

For information about the new or changed functions in this release, see IBMWorkload Automation: Overview, section Summary of enhancements.

For information about the APARs that this release addresses, see the IBM WorkloadScheduler Release Notes at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048863 and the Dynamic Workload Console Release Notes athttp://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048864.

New or changed content is marked with revision bars. For the PDF format, new orchanged V9.4 content is marked in the left margin with a pipe (|) character andnew or changed V9.4FP1 content is marked with an equal sign (=).

Who should read this publicationLearn the audience of this publication.

About this task

This guide is intended for the following audience:v IBM Workload Scheduler IT administrators who plan for and install the networkv Dynamic Workload Console IT administrators who plan for and install the

productv Specialists who plan the network topologyv IT administrators who install the networkv System architects

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully.

With this product, you can use assistive technologies to hear and navigate theinterface. You can also use the keyboard instead of the mouse to operate allfeatures of the graphical user interface.

For full information, see the Accessibility Appendix in the IBM Workload SchedulerUser's Guide and Reference.

xi

===

http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048863http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048863http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048864

Technical trainingCloud & Smarter Infrastructure provides technical training.

For Cloud & Smarter Infrastructure technical training information, see:http://www.ibm.com/software/tivoli/education

Support informationIBM provides several ways for you to obtain support when you encounter aproblem.

If you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:v Searching knowledge bases: You can search across a large collection of known

problems and workarounds, Technotes, and other information.v Obtaining fixes: You can locate the latest fixes that are already available for your

product.v Contacting IBM Software Support: If you still cannot solve your problem, and

you need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.

For more information about these three ways of resolving problems, see theappendix about support information in IBM Workload Scheduler: TroubleshootingGuide.

xii IBM Workload Scheduler: Planning and Installation

http://www.ibm.com/software/tivoli/education

Part 1. Planning

An overview of the IBM Workload Automation environment and describes how toplan for the installation.

1

2 IBM Workload Scheduler: Planning and Installation

Chapter 1. Known problems and limitations

For information about installation limitations, problems, and their workarounds seethe IBM Workload Scheduler release notes: http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048863 and the Dynamic Workload Console releasenotes: http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048864.

3


Chapter 2. Network planning

Network planning on IBM Workload Automation.

About this task

How to plan your IBM Workload Scheduler network.

IBM Workload Scheduler environmentA IBM Workload Scheduler network consists of a set of linked workstations onwhich you perform job processing. A network is composed of one or moredomains, each having a domain manager workstation acting as a management hub,and one or more agent workstations.

About this task

Using IBM Workload Scheduler you can run your workload in one of thefollowing ways:

StaticallyTo run existing job types, for example docommand and scripts on specificworkstations of fault-tolerant agent or standard agent type.

DynamicallyTo run existing job types and job types with advanced options, allowingthe product to assign it to the workstation that best meets both thehardware and software requirements needed to run it.

Job types with advanced options are both those supplied with the productand the additional types implemented through the custom plug-ins. Forexample, those supplied with the product are DB2®, file transfer, and webservices. Those implemented through the custom plug-ins are the ones youdeveloped using the Integration Workbench of the Software DevelopmentKit (SDK).

Depending on how you want to run your workload you have to install andconfigure different components in your network.

Figure 1 on page 6 gives a graphical overview of a typical IBM WorkloadScheduler environment to run static workload:

5

In Figure 1 the master domain is shown with the principle components to runworkload statically, and two levels of subdomain. The available user interfaces arealso indicated. An example is provided of the basic domain hierarchical structure,where each domain is named "D1", "D2, and so on. All of these concepts areexplained in the following section:

To run your workload statically install the following components:

Master domain managerThe master domain manager is the highest level workstation of a IBMWorkload Scheduler network. It contains or connects to the relationaldatabase that stores scheduling object definitions. It creates or updates aproduction file when the plan is created or extended and then distributesthe file to the network. It performs all logging and reporting for thenetwork. It can perform the role of event processing server for theevent-driven workload automation feature.

Backup master domain manager

Child domain(Dn) - and so on

MD

D1 D2

D3 D4 D5

User Interfaces

Master Domain(MD)

Example domain hierarchyFault-toleant

Agents

Database

Master domainmanager

Dynamic Workload

Console

Command-line

client (remote)

Backup masterdomain manager

(agent)Fault-toleant

Agents

Child domainmanager(agent)

Child domainmanager(agent)

Command

line

Web browser

D6

Backup domainmanager (agent)

Figure 1. Graphical overview of IBM Workload Scheduler environment to run static workload


Define a backup master domain manager at installation to point to eitherthe database being used by the master domain manager or to a mirror ofthat database. In this way the backup master domain manager has thelatest data available to it at all times.

Domain managerInstall this component if you need a multi-domain network and you wantto manage workload by assigning it to a predefined workstation that is torun your workload statically. In a multi-domain network all domainsbelow the master domain have fault-tolerant agents configured to be adomain manager to manage the workstations in its domain. A domainmanager can manage fault-tolerant, standard, and extended agents. Eachdomain manager is a fault-tolerant agent in the domain of the next higherlevel. To define a domain manager, install a fault-tolerant agent on yourworkstation and then define it as manager in the workstation definition.

Backup domain managerInstall this component if you want a backup to your domain manager. Ifyour domain manager experiences problems, you can configure anyfault-tolerant agent as the domain manager and switch to it with a simpleprocedure.

Agent An agent is a workstation in the network that runs the jobs which arecontrolled by the IBM Workload Scheduler master domain manager. Afterinstalling an agent, you define its type by using the workstation definition.

Fault-tolerant agentAn fault-tolerant agent can resolve local dependencies and launchjobs in the absence of a domain manager. It has a copy of theproduction control file. This allows fault-tolerant agents to continueprocessing even if the dynamic domain manager or the networkconnection is down. With a simple reconfiguration, they can serveas subordinate domain managers. To define a fault-tolerant agent,install a fault-tolerant agent on your workstation and then define itas fault-tolerant in the workstation definition.

Standard agentAn agent that launches jobs only under the direction of its domainmanager. It is not fault-tolerant. To define a standard agent, installa fault-tolerant agent on your workstation and then define it as astandard agent in the workstation definition.

Extended agentExtended agents are logical definitions (hosted by a physical workstation)used to extend job processing to selected applications (SAP R/3,PeopleSoft, and z/OS®). For information about installing an extendedagent, see IBM Workload Automation: Scheduling Applications with IBMWorkload Automation.

Note: All agents with special roles (master domain manager, backup masterdomain manager, domain manager, backup domain manager) can also work asfault-tolerant agents with jobs scheduled on them.

Figure 2 on page 8 gives a graphical overview of a typical IBM WorkloadScheduler environment to run dynamic workload:

Chapter 2. Network planning 7

In Figure 2 the master domain is shown with the principle components to runworkload dynamically, and two levels of dynamic subdomain. The available userinterfaces are also indicated. An example is provided of the basic domainhierarchical structure, where each domain is named "D1", "D2, and so on. All ofthese concepts are explained in the following section.

If you want to run your workload dynamically install the following components:

Master domain managerThe master domain manager is the highest level workstation of a IBMWorkload Scheduler network. It contains or connects to the relationaldatabase that stores scheduling object definitions. It creates or updates aproduction file when the plan is created or extended and then distributesthe file to the network. It performs all logging and reporting for thenetwork. It can perform the role of event processing server for theevent-driven workload automation feature.

Backup master domain manager

Child domain(Dn) - and so on

MD

D1 D2

D3 D4 D5

User Interfaces

Master Domain(MD)

Example domain hierarchy

Database

Master domainmanager

Dynamic Workload

Console

Command-line

client (remote)

Backup masterdomain manager

(agent)Dynamic

agents

Child dynamicdomain

manager

Child dynamicdomain

manager

Command

line

Web browser

D6

Backup dynamicdomain

manager

Dynamic

agents

Figure 2. Graphical overview of IBM Workload Scheduler dynamic environment


Define a backup master domain manager at installation to point to eitherthe database being used by the master domain manager or to a mirror ofthat database. In this way the backup master domain manager has thelatest data available to it at all times.

Dynamic Domain managerInstall this component if you need a multi-domain network and you wantto manage your workload both statically that dynamically. All domainsbelow the master domain have dynamic domain managers to manage theworkstations in its domain. Each dynamic domain manager is an agent inthe domain of the next higher level. To define a dynamic domain manager,install a dynamic domain manager and then perform the “Configuring adynamic domain manager” on page 241 procedure.

Backup dynamic domain managerInstall this component if you want a backup to your dynamic domainmanager. If your dynamic domain manager experiences problems, you canswitch to it with a simple procedure.

Agent An agent is a workstation in the network that runs the jobs which arecontrolled by the IBM Workload Scheduler master domain manager.

Dynamic agentAn agent that has the following capabilities:

Run workload dynamicallyIt communicates with the server the status of its resources.In this way the product is able to dynamically run yourworkload to the best available resources by:v Automatically discovering scheduling environment

resources.v Automatically following resource changesv Requesting additional resources when neededv Matching job requirements to available resourcesv Controlling and optimizing use of resources

The characteristics listed above provide high availabilityand load balancing potentialities to your environment andwell suit virtualized environments.

When a job is submitted, either as part of a job stream inthe plan or through ad hoc submission, IBM WorkloadScheduler checks the job requirements, the availableresources and the related characteristics and submits thejob to the resource that best meets the requirements to runit.

Run both existing job types and job types with advancedoptions

It can run:v Existing job types. For example docommand and scripts.v Job types with advanced options, both those supplied

with the product and the additional types implementedthrough the custom plug-ins. For example, thosesupplied with the product are DB2, file transfer, and webservices. Those implemented through the customplug-ins are the ones you developed using the


Integration Workbench of the Software Development Kit(SDK). To run these job types you must also install theJava™ run time.

Manage dynamic workload broker logical resourceIt can remotely run, from the agent, the dynamic workloadbroker resource command on the server. To manage theresource command you must also install the Java run time.

After installing the agent, you define its type by using“Configuring a dynamic agent” on page 243.

In a simple configuration, dynamic agents connect directly to themaster domain manager or to the dynamic domain manager.However, in more complex network topologies, if the networkconfiguration prevents the master domain manager or the dynamicdomain manager from directly communicating with the dynamicagent, for example, if the agents are behind a firewall and need tocommunicate through the internet, or if they need to communicatewith a Network Address Translation (NAT) process, then you canconfigure your dynamic agents to use a local or remote gateway. Inthis way, communication is concentrated in a single connection,reducing the number of connections to the master domain manageror to the dynamic domain manager. For more information aboutthe gateway parameters specified when installing a dynamic agent,see “Agent installation parameters - twsinst script” on page 143.For more information about gateway configuration, see thenetwork communications information in the Administration Guide.

Extended agentExtended agents are logical definitions (hosted by a physicalworkstation) used to extend job processing to selected applications(SAP R/3, PeopleSoft, and z/OS). For information about installingan extended agent, see IBM Workload Automation: SchedulingApplications with IBM Workload Automation.

IBM Workload Scheduler interfacesThe IBM Workload Scheduler has user interfaces from which you can manage yourproduction environment.

About this task

You can manage your production environment from the following user interfaces:

Master domain manager command linesThe master domain manager command lines are installed automaticallywhen you install the master domain manager. This command linesinterface are run only from the workstation serving as the master domainmanager. From the command lines, you can administer the master specificbinaries and options. A backup master domain manager command linesalso exist on the master domain manager configured as backup instance.

Dynamic Workload ConsoleThe web-based interface for creating, modifying, monitoring, controlling,and deleting IBM Workload Scheduler objects. You can interface with theconsole from any system in the network where a supported web browser isinstalled. When you install a Dynamic Workload Console also the z/OS


Connector is installed, which is a component that connects IBM WorkloadScheduler for z/OS and the Dynamic Workload Console. For moreinformation, see IBM Workload Scheduler for z/OS: Planning and InstallationGuide.

Command-line clientA component of IBM Workload Scheduler installed only with afault-tolerant agent that allows you to implement the following commandson the master domain manager from another workstation: The commandsyou can use are the following:v Composerv Optmanv Planman showinfo and unlock (the other planman commands must be

run locally on the master domain manager)

dynamic workload broker command lineInstalled and configured automatically when you install a master domainmanager. It includes commands to directly submit and manage jobs fordynamic scheduling, manage job JSDL definitions and resources, and more.See IBM Workload Scheduler: Scheduling Workload Dynamically for reference.

Job Brokering Definition ConsoleA structured editing tool that you use to create and modify Job SubmissionDescription Language (JSDL) files. These files are saved in the JobRepository as job definitions and become available for submission. TheJSDL files adhere to the XML syntax and semantics as defined in the JSDLschema. For more information, see the IBM Workload Scheduler: User's Guideand Reference, SC32-1274.

For a more detailed description of the IBM Workload Scheduler components, seeIBM Workload Automation: Overview.

Planning the environmentTypical installation scenarios for products and components.

These typical scenarios for IBM Workload Automation show how to deployspecific solutions on the minimum possible system resources.

Distributed workload environment with static schedulingcapabilities

Configuration to run workload statically across your distributed network.

Use this configuration to run workload statically across your distributed network.Figure 3 on page 12 shows the system resources needed to install a fully-workingIBM Workload Scheduler environment for managing your distributed workload.


Distributed workload environment with dynamic schedulingcapabilities

Use this configuration to run workload dynamically across your distributednetwork.

MasterDomainManager

DBserver

ServerSystem

Components share infrastructure

DWCserver

Workload Scheduler instance

Workload Scheduler agentnetwork

FTA FTA

Figure 3. Distributed workload environment with static scheduling capabilities


The run time environment is used to:v Run on the agent job types with advanced options, both those supplied with the

product and the additional types implemented through the custom plug-ins.v Enable the capability to remotely run, from the agent, the dynamic workload

broker resource command on the server.

For information about dynamic scheduling, how to run application job plug-insand the dynamic workload broker resource command on the server, see IBMWorkload Scheduler: Scheduling Workload Dynamically.

In this configuration, you can choose whether or not to add the run timeenvironment for Java jobs to the agent.

Figure 4 on page 14 shows the system resources required to install a fully workingIBM Workload Scheduler environment for running your distributed workloaddynamically.

Note: A dynamic agent can be directly connected to its master domain manager orthrough a dynamic domain manager as shown in “Distributed workloadenvironment with static and dynamic scheduling capabilities” on page 15. In morecomplex network topologies where the master domain manager or the dynamicdomain manager cannot directly communicate with the dynamic agent, you canconfigure your dynamic agents to use a local or remote gateway. For moreinformation about the gateway parameters specified when installing a dynamicagent, see “Agent installation parameters - twsinst script” on page 143. For moreinformation about the gateway parameters specified when installing a dynamicagent, see “Agent installation parameters - twsinst script” on page 143.

For more information about gateway configuration, see the networkcommunications information in the Administration Guide.


Dynamic scheduling supports most of the IBM Workload Scheduler features forstatic scheduling. The Table 1 on page 15 lists some features or properties that arepartially or not supported.

MasterDomainManager

DBserver

ServerSystem


TDWCserver


Workload Scheduler agentnetwork

DynamicAgent

JavaRuntime

DynamicAgent

DWCserver

DynamicAgent

Gateway

Figure 4. Distributed workload environment with dynamic scheduling capabilities


Table 1. Features partially or not supported for dynamic scheduling

Featureagent and IBM Workload Scheduler for z/OSagent

Event-driven workload automation.Note: For more details about the eventstype, see IBM Workload Scheduler User'sGuide and Reference: Appendixes -Event-driven workload automation event andaction definitions

TivoliWorkloadSchedulerObjectMonitorevents supported.

FileMonitor events supported, except for IBMi systems.

TivoliWorkloadSchedulerApplicationMonitorevents not supported.

Utility commands (datecalc, jobinfo, and soon).

Not supported.

Distributed workload environment with static and dynamicscheduling capabilities

Use this configuration to run workload both statically and dynamically across yourdistributed network.

The run time environment is used to:v Run on the agent job types with advanced options, both those supplied with the

product and the additional types implemented through the custom plug-ins.v Enable the capability to remotely run, from the agent, the dynamic workload

broker resource command on the server.

For information about dynamic scheduling, how to run application job plug-insand the dynamic workload broker resource command on the server, see IBMWorkload Scheduler: Scheduling Workload Dynamically.

In this configuration, you can choose whether or not to add the run timeenvironment for Java jobs to the agent.

Figure 5 on page 16 shows the system resources required to install a fully workingIBM Workload Scheduler environment for running your distributed workload bothstatically and dynamically. IBM Workload Scheduler requires a fault-tolerant agentand a dynamic agent to be installed on every system where jobs are to scheduledstatically or dynamically.

Note: A dynamic agent can be directly connected to its master domain manager orthrough a dynamic domain manager as shown in Figure 5 on page 16. In morecomplex network topologies where the master domain manager or the dynamicdomain manager cannot directly communicate with the dynamic agent, you canconfigure your dynamic agents to use a local or remote gateway. For moreinformation about the gateway parameters specified when installing a dynamicagent, see “Agent installation parameters - twsinst script” on page 143.

For more information about gateway configuration, see the networkcommunications information in the Administration Guide.


||

|||

||||||

||

||

||

|||

|

|

For a list of features partially or not supported in a mixed environment, see Table 1on page 15.

End-to-end workload environmentIn an End-to-end workload environment (agent connected to the z/OS system),you can define the types of configurations.

You can define the following types of configurations:

To run your workload statically:

MasterDomainManager

DBserver

ServerSystem


DWCserver


Workload Scheduleragent network

DomainManager

DynamicDomainManager

FTA

FTA

FTA

DynamicAgent

DynamicAgent

DynamicAgent

DBserver

JavaRuntime

DynamicAgent

Gateway

Figure 5. Distributed workload environment with static and dynamic scheduling capabilities


Using fault-tolerant agentsUse the fault-tolerant end-to-end scheduling environment toschedule and control static workload from the mainframe todistributed systems. On the distributed system, you installfault-tolerant agents and connect them to the z/OS server. See IBMWorkload Scheduler for z/OS: Scheduling End-to-end with FaultTolerance Capabilities for more details.

Using IBM Workload Scheduler for z/OS Agents (z-centric)Use the z-centric end-to-end scheduling environment to scheduleand control static workload from the mainframe to distributedsystems with a low cost of ownership. On the distributed system,you install IBM Workload Scheduler for z/OS Agents and connectthem to the z/OS controller. For information about how to install itsee IBM Workload Scheduler for z/OS: Planning and Installation Guidefor information about how to use it see IBM Workload Scheduler forz/OS: Scheduling End-to-end with z-centric Capabilities for moredetails.

To run your workload dynamically:

Using IBM Workload Scheduler for z/OS Agents (z-centric) withdynamic capabilities

Use the z-centric end-to-end scheduling environment to scheduleand control dynamic workload from the mainframe to distributedsystems with a low cost of ownership. On the distributed system,you install IBM Workload Scheduler for z/OS Agents , adddynamic scheduling capabilities and connect them to a dynamicdomain manager that must be connected to the z/OS controller.For information about how to:v Install a dynamic domain manager see “Installing a dynamic

domain manager or its backup” on page 122v Install IBM Workload Scheduler for z/OS agents see IBM

Workload Scheduler for z/OS: Planning and Installation Guide

v Use IBM Workload Scheduler for z/OS agents seeIBM WorkloadScheduler for z/OS: Scheduling End-to-end with z-centric Capabilitiesfor more details.

Workload environment integrated with external systemsConfiguration to extend IBM Workload Scheduler capabilities for scheduling onexternal applications.

Use this configuration to extend IBM Workload Scheduler capabilities forscheduling on external applications, such as SAP R/3 and PeopleSoft using IBMWorkload Scheduler.

Figure 6 on page 18 shows a sample environment including the agents needed toextend IBM Workload Scheduler scheduling capabilities on one or more externalapplications using IBM Workload Scheduler. You can install IBM WorkloadScheduler on the master domain manager, on a fault-tolerant agents, on dynamicagents, and on IBM Workload Scheduler for z/OS Agents.

For information about IBM Workload Scheduler, see the IBM Workload Scheduler:User's Guide documentation.


Note: Installing IBM Workload Scheduler on an agent (master domain manager,domain manager, fault-tolerant agent, standard agent, dynamic agent, IBMWorkload Scheduler for z/OS Agent ) is the correct deployment scenario in anend-to-end environment.

Distributed-driven workload environment for z/OSConfiguration used when submitting from the IBM Workload Scheduler.

Use this configuration to submit from the IBM Workload Scheduler (using thedynamic workload broker component installed with the master domain manageror the dynamic domain manager) workload to be processed by JES2, withouthaving to define the workload on the z/OS system.

Figure 6 shows the minimum system resources needed to install adistributed-driven environment, where the IBM Workload Scheduler

Workload Scheduleragent

network

WSFTA

z/OS

Oracle

PeopleSoft

SAP R/3

WSfor

Applications

Applications

WSfor

Applications

WSfor

Applications

Workload SchedulerServer system

WSDynamic

Agent

WSfor Z/OS

Agent

JavaRuntime

Figure 6. Workload environment integrated with external systems


distributed-Agent for z/OS represents a lightweight end-to-end schedulingsolution where you define and manage on the distributed side the workload that isto be processed by JES2.

For information about IBM Workload Scheduler distributed-Agent for z/OS, seethe IBM Workload Scheduler: Scheduling with the Agent for z/OS documentation.

DBserver

ServerSystem

DWCserver



MDM

z/OSSystem

Distributed-Agentfor z/OS

Figure 7. Distributed-driven workload environment for z/OS


Planning domainsA IBM Workload Scheduler network contains at least one master domain managerthat acts as a management hub for the product. Additional domains can be used todivide a widely-distributed network into locally-managed groups of workstations.

In a single domain configuration, the master domain manager maintainscommunications with all of the workstations in the network.

In a multiple domain configuration, the master domain manager communicateswith the workstations in its domain and all immediately subordinate domainmanagers. The subordinate domain managers communicate with the workstationsin their domains and their immediately subordinate domain managers, and so on.Domain managers report all of the activities of the domain to the master. Usingmultiple domains reduces network traffic and the load on the master by reducingthe number of direct communications between the master domain manager andworkstations. Multiple domains also provide fault-tolerance by limiting the outagecaused by losing a domain manager in a single domain. To limit the effects further,you can designate backup domain managers to take over if domain managers fail.

When you define a new domain, you must identify the parent domain and thedomain manager. The parent domain is the domain directly above the new domainin the domain hierarchy. All communications to and from a domain are routedthrough the parent domain manager.

Localized processing in your domainLocalized processing is separating your scheduling needs based on a common setof characteristics, such as geographical locations, business functions, andapplication groupings.

Group related processing can limit the amount of interdependency informationthat needs to be communicated between domains. The benefits of localizeddomains are:

Decreased network trafficKeeping processing localized to domains eliminates the need for frequentinter-domain communication.

Tighter security and simplified administrationSecurity and administration can be defined at and limited to the domainlevel. Instead of network-wide or workstation-specific administration, youcan have domain administration.

Optimized network and workstation fault-toleranceIn a multiple domain network, you can define backups for each domainmanager so that problems in one domain do not disrupt operations inother domains.

Considerations in planning domainsThere are a number of considerations that are to be taken into account whenplanning domains.

In planning your IBM Workload Scheduler network, consider the following:

Number of workstations, applications, and jobsConsider the number of workstations that comprise the network and the


number of applications and jobs that the network runs. If you have a smallnumber of workstations, or a small number of applications to control, youdo not need multiple domains.

Number of geographic locationsConsider the number of geographic locations covered by your network andthe reliability and efficiency of communication between the locations.Multiple geographic locations is one of the primary reasons for choosing amultiple domain architecture. One domain for each geographical location isa common configuration. A single domain architecture relies on thenetwork maintaining continuous processing.

Time zonesWhen your network is spread across multiple geographic locations indifferent time zones, decide whether to activate the time zone feature. See“Time zone considerations” on page 25.

Centralized or decentralized managementYou can manage single or multiple domain networks from a single masterdomain manager. If you want to manage multiple locations separately, youcan consider the installation of a separate IBM Workload Schedulernetwork at each location. Some decentralized management is possible in astand-alone IBM Workload Scheduler network by mounting or sharing filesystems.

Types of applicationsConsider the types of applications that are run by IBM WorkloadScheduler. If you have multiple applications that are distinctly separatefrom each other, you might choose to put them in separate domains.

Windows networkWhen you have a Windows network, you might want your IBM WorkloadScheduler domains to mirror your Windows domains.

System performance and other criteriaYou can define multiple domains to localize systems based on performanceor operating system type.

Amount of network trafficIf your network traffic is manageable, having multiple domains is lessimportant.

Dependencies between jobsConsider if you need to plan for job dependencies that cross systemboundaries, geographical boundaries, or application boundaries. Forexample, does the start of Job1 on workstation1 depend on the completionof Job2 running on workstation2. The degree of interdependence betweenjobs is an important consideration when planning your network. If you usemultiple domains, try to keep interdependent objects in the same domainto decrease network traffic and improve the use of the domain architecture.See User's Guide and Reference.

Level of fault-tolerance requiredA disadvantage of the single domain configuration is the reliance on asingle domain manager. In a multi-domain network, the loss of a singledomain manager affects only the agents in its domain.

FirewallsWhen your network contains firewalls, plan the structure of your domainsaround the firewalls. See Administration Guide.


Secure Sockets Layer (SSL) or IBM® Global Security Kit (GSKit) encryptionIf you want to use SSL or GSKit encryption in your network, plan yourdomains in accordance with the protocol.

Note: If you want to be compliant with Federal Information ProcessingStandards (FIPS), you must use GSKit. See Administration Guide.

Single domain networkA single domain network consists of a master domain manager and any number ofagents.

Figure 8 shows an example of a single domain network. A single domain networkis well-suited to companies that have few locations and business functions. Allcommunication in the network is routed through the master domain manager.With a single location, you are concerned only with the reliability of your localnetwork and the amount of traffic it can handle.

Single domain networks can be combined with other networks, single or multipledomain, to meet multiple site requirements. IBM Workload Scheduler supportsinternetwork dependencies between jobs running on different networks.

MasterDomainManager

Agents

Figure 8. Single domain topology


Example 1 shows a single domain network. The master domain manager is locatedin Atlanta, along with several agents. There are also agents located in Denver. Theagents in Denver depend on the master domain manager in Atlanta to resolve allinteragent dependencies, even though the dependencies might be on jobs that runin Denver. An alternative would be to create separate single domain networks inAtlanta and Denver, as shown in example 2.

Multiple domain networkMultiple domain networks are especially suited to companies that span multiplelocations, departments, or business functions.

DynamicWorkload Console

MasterDomainManager

Atlanta

Denver

Atlanta Denver

Agent

Backup MasterDomain Manager

Or:

MasterDomainManager

MasterDomainManager

Agent Agent

Agent

Agent Agent Agent

Example 1

Example 2

BackupMasterDomainManager

Agent

Figure 9. Single domain topology on multiple sites


A multiple domain network consists of a master domain manager, any number oflower tier domain managers, and any number of agents in each domain. Agentscommunicate only with their domain managers, and domain managerscommunicate with their parent domain managers. The hierarchy of domains cango down to any number of levels.

As Figure 10 illustrates, the master domain manager is located in Atlanta. Themaster domain manager contains the database files used to document thescheduling objects, and distributes the Symphony file to its agents and the domainmanagers in Denver and Los Angeles. The Denver and Los Angeles domainmanagers then distribute the Symphony file to their agents and subordinate

DynamicWorkload Console

MasterDomainManager

Master domain

Denver

Backup MasterDomain Manager

Agent

DomainManager

Agent Agent Agent

Second-leveldomains

LosAngeles

DomainManager

Agent

Agent

NewYork

DomainManager

Agent Agent

AuroraDomainManager

Agent Agent

Burbank

DomainManager

Agent Agent

Third-leveldomains

Atlanta

Figure 10. Multiple domain topology


domain managers in New York, Aurora, and Burbank. The master domainmanager in Atlanta is responsible for broadcasting inter-domain informationthroughout the network.

All communication to and from the New York domain manager is routed throughits parent domain manager in Denver. If there are schedules or jobs in the NewYork domain that are dependent on schedules or jobs in the Aurora domain, thosedependencies are resolved by the Denver domain manager. Most inter-agentdependencies are handled locally by the lower tier domain managers, greatlyreducing traffic on the network.

Workstation classesWorkstations are organized into domains to make your network managementeasier and more efficient. However, the domain name is not one of the selectioncriteria when choosing where to run a job or job stream.

If you want to group workstations together because they have similar jobscheduling characteristics, use a workstation class. Any number of workstationscan be grouped in a class, and a workstation can be in many classes. Jobs and jobstreams can be assigned to run on a specific workstation class.

For example, you could set up workstation classes to group workstations accordingto:v Your internal departmental structure, so that you could define a job that would

be run on all the workstations in a departmentv The software installed on them, so that you could define a job that would be run

on all the workstations that had a particular application installedv The role of the user, so that you could define a job that would be run on all the

workstations belonging to, for example, managers

In this example, an individual workstation could be in one workstation class for itsdepartment, another for its user, and several others for the software installed on it.

Time zone considerationsTime zone support is an optional feature that is enabled by default.

It allows you to manage workloads at a global level. For information about how toset the time zone, see IBM Workload Scheduler: Administration Guide.

Time zone implementation also enables easy scheduling across multiple timezones. For a description of how the time zone works, see the IBM WorkloadScheduler: User's Guide and Reference.


Part 2. IBM Workload Scheduler

How to create or upgrade the IBM Workload Scheduler database tables beforeinstalling or upgrading IBM Workload Scheduler, and how to install, upgrade,configure, uninstall and troubleshoot IBM Workload Scheduler.

27

Chapter 3. Preparing for installation

An overview on preparing for installation.

About this task

A brief overview of an installation and some specific environment considerations.

Installation overviewSteps to prepare your environment to install and configure IBM WorkloadScheduler.

About this task

Perform the following steps to prepare your environment to install and configureIBM Workload Scheduler:1. Plan your IBM Workload Scheduler network to determine what type of

workstation you need to install. See Chapter 2, “Network planning,” on page5.

2. Check the available installation media, see “Accessing the installation media”on page 33.

3. Check the installation prerequisites, see Chapter 4, “Prerequisites,” on page 37.4. If you are installing a component that needs a Relational Database, decide if

you want to use a DB2 database, an Oracle database, an Informix® DynamicServer database, or a Microsoft SQL Server database, and install it.

5. Optional, create or upgrade the IBM Workload Scheduler database tablesbefore installing or upgrading, see Chapter 5, “Creating or upgrading the IBMWorkload Scheduler database tables before installing or upgrading,” on page47. The database administrator runs this procedure only if the ITadministrator who installs the product does not know all the confidentialinformation related to the database. If instead the IT administrator canprovide the database administrator user ID and password during theinstallation, the database administrator does not need to run these proceduresbecause the installation automatically creates and upgrades the databasetables.

6. Choose the available method that you want to use for installing or upgrading.For information about the available installation methods, see “Installationmethod” on page 30.

7. Collect the information necessary to type in the required fields during theinstallation.

8. Manage the IBM Workload Scheduler user for the instance that you areinstalling, see “IBM Workload Scheduler user” on page 40.

9. Install IBM Workload Scheduler by following the instructions provided inChapter 6, “Installing,” on page 93.

10. Perform any configuration required for the workstation type that youinstalled, see Chapter 9, “Configuring,” on page 237.

29

Installation methodInstallation methods

About this task

You can install IBM Workload Scheduler using several different methods, eitherstarting the wizard or starting a silent installation. Both methods use InstallationManager.

Before you run Installation Manager, ensure you have checked the relatedprerequisites, as described in “Scanning system prerequisites for InstallationManager” on page 45.

Installation wizardInstallation wizard method for master domain manager or its backup, dynamicdomain manager or its backup.

About this task

Install IBM Workload Scheduler master domain manager or its backup, dynamicdomain manager or its backup, by using the Installation Manager wizard for eachsupported platform.

You can use the installation wizard in interactive or silent mode. In interactivemode, the wizard guides you through the installation steps. In silent mode, aresponse file provides the information relevant to the installation process, which isrun in background.

Silent modeSilent method for master domain manager or its backup, dynamic domainmanager or its backup..

About this task

Install IBM Workload Scheduler master domain manager or its backup, dynamicdomain manager or its backup, and the Dynamic Workload Console by using acustomized response file by adding all the configuration settings to be used duringinstallation.

From the command line, run the Installation Manager command to install in silentmode. Using this method you can run the installation unattended and in thebackground. For more information, see “Performing a silent installation” on page113.

The twsinst script for agentsThe twsinst script to install agents.

About this task

To install IBM Workload Scheduler agents you can use only the twsinst script.


|||

The twsinst command is a very simple command that you can use both on UNIXand Windows operating systems. It saves disk space and RAM because it is notJava based.

For information about the twsinst script, see “Installing agents” on page 139.

Downloading installation images on your workstationSteps to take when downloading images on your workstation.

About this task

You can download installation images by performing the following steps:1. Ensure that your workstation has sufficient space to store both the files you

download from IBM Passport Advantage and the extracted installation image.For more information about Systems requirements, see IBM WorkloadScheduler System Requirements Document at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858.

2. From IBM Passport Advantage, download all the required parts for the productimage listed in Table 2 to a temporary directory.

Table 2. Required eImages

IBM Workload Scheduler components toinstall eImages to download

v A dynamic agentv A fault-tolerant agent with remote

command line

Agent eImage.

v A master domain manager or its backupv A dynamic domain manager or its backup

v IBM Workload Scheduler eImage.v WebSphere Application Server eImage.v DB2 eImage if you want to install and use

the DB2 relational database.

Dynamic Workload Console v IBM Workload Scheduler eImage.v WebSphere Application Server eImage.

Integration Workbench Integration Workbench eImages.

Batch reports IBM Workload Scheduler eImage.

Job Brokering Definition Console IBM Workload Scheduler eImage.

3. Extract the installation image from the downloaded file and verify that theinstallation image is complete.

For more information about eImages, see the Download Document athttp://www-01.ibm.com/support/docview.wss?rs=672&uid=swg24042843.

Creating a network repositoryAbout this task

This scenario is valid only for master domain manager or dynamic domainmanager and their backups, or Dynamic Workload Console that are installed byusing the Installation Manager infrastructure.

Chapter 3. Preparing for installation 31


Use the Installation Manager Package Utility to create the IBM WorkloadScheduler eImages in network repository format. For more information about thePackage Utility wizard, see Installation Manager > Installing> Managing packageswith Packaging Utility in the Installation Manager Information centerhttps://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html.

After you use the Packaging Utility to create a repository from the ESD images,you can use the Installation Manager to define this location as a repository. Youcan save the repository on a UNC drive on Windows operating systems or on aweb server to make the directories and files available over HTTP.

To create an IBM Workload Scheduler network repository, perform the followingprocedure:1. Download the eImages as described in “Downloading installation images on

your workstation” on page 31.2. Install Installation Manager on your workstation.3. Install the Package Utility using Installation Manager on your workstation.4. To create the ESD images in network format, run the following steps:

a. Start the Package Utility.b. Click Point to the ESD image.c. Run the wizard. For more information about the Package Utility wizard,

see Installation Manager > Installing> Managing packages with Packaging Utility.

After you created a repository in network format, define this location asanInstallation Manager repository. To add a repository, run the following steps:1. Open the Installation Manager wizard.2. Select File > Preferences. The Repositories page is displayed and shows

available repositories, repository locations, and the connection status for therepositories.

3. Select Add Repository. The Add Repository page is displayed.4. Enter the repository location or select Browse.5. Go to the repository location where you saved the eImages content in network

format and select the URL related to the product that you want to install.6. Click OK. If you provided an HTTPS or restricted FTP repository location, you

are prompted to enter a user ID and password. The new repository location isadded to the list. If the repository is not connected, a red box is shown in theConnection column.

7. Click OK.

After you defined an Installation Manager repository, install the product:

IBM Workload SchedulerSee “Installing main components” on page 93 in IBM Workload Scheduler:Planning and Installation.

Dynamic Workload ConsoleSee Chapter 20, “Installing,” on page 355.


https://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.htmlhttps://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html

Accessing the installation mediaAccessing the installation media

Access the installation media to download the installation files

Installation mediaContent of the installation media.

About this task

The content of the installation media depends on the image that you downloaded.

Agents image

Depending on the operating system, the installation image contains someor all of the following directories:

TWS Contains the files required to install a IBM Workload Schedulerdynamic agent or a fault-tolerant agent with remote command line.

JavaExtensionContains the files to install Java extension or to add Java extensionto an installed IBM Workload Scheduler instance.

IBM Workload Scheduler Server image

Depending on the operating system, the installation image contains someor all of the following directories:

dbtoolsContains the files required to create or update the IBM WorkloadScheduler database before installing or upgrading the product. Formore information about managing IBM Workload Schedulerdatabase before the installation process, see Chapter 5, “Creating orupgrading the IBM Workload Scheduler database tables beforeinstalling or upgrading,” on page 47.

FULL Contains the repository required to install the product by usingInstallation Manager.

iim Contains the files required to install Installation Manager manually.

response_filesContains the response files that install the IBM Workload Schedulermaster domain manager, the backup master domain manager, thedynamic domain manager, the backup dynamic domain manager,or the Dynamic Workload Console.

DWC Contains the files required to install the Dynamic WorkloadConsole.

TWS Contains the files required to install the IBM Workload Schedulermaster domain manager or its backup, the dynamic domainmanager or its backup.

PrerequisitesContains the files needed to scan your system to verify that yourenvironment has all the product system requirements necessary toperform a successful installation.


Integration WorkbenchContains the files required to install IBM Workload SchedulerIntegration Workbench.

DB2 imagesContains the files required to install DB2.

WebSphere Application Server imagesContains the files required to install WebSphere Application Server.

Jazz for Service Management extension for WebSphere imagesContains the files required to install Jazz for Service Management extensionfor WebSphere.

Installation considerationsSome considerations that need to be taken into account before installation.

About this task

Before you begin the installation using the installation wizard, consider thefollowing items that might apply to your specific environment.

Installing on Windows operating systems

If you are installing on Windows, consider the following items.v If you are using Windows Terminal Services, set the install user with the

command: change user /installv If is a domain user, Microsoft Computer Browser Service

must be active. This is required for IBM WebSphere Application Serverauthentication.

v If is a domain user, the user performing the installationmust be a domain administrator.

Choosing language settings and national charactersIf you want to use characters of a specific language locale, the languageyou choose for the installation wizard must match the language localesettings of the workstation on which you are installing. You cannot usenational characters in the installation path of a master domain manager orbackup master domain manager. Additionally, you cannot add adistributed connector to an agent that has national characters in itsinstallation path.

Performing silent installationsWhen you install the latest version of IBM Workload Scheduler, you cancreate a response file based on the parameters of the initial installation.You can then use this customized response file to run silent installationsusing the same parameters. Before running the initial installation, youmight want to consider this feature. For more information, see “Performinga silent installation” on page 113.

Mapped drivesWhen you copy the image of a specific operating system onto theworkstation for installation using the wizard, you must copy the completecontents of the DVD to the drive from where you run your installation.When the drive is a UNC mapped drive, the remote path must be mappedto a drive on the installation workstation. For a complete list of thesupported operating systems and their prerequisites, see the IBM Workload


Scheduler System Requirements Document at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858.

Remote installationYou cannot install IBM Workload Scheduler on a Windows workstationfrom a remote Samba-mounted file system.

Installing for end-to-end scheduling

If you are installing IBM Workload Scheduler on a workstation used as adistributed agent (that is either a standard agent, fault-tolerant agent, ordomain manager) for end-to-end scheduling, specify OPCMASTER as thename of the master domain manager during the installation process. Forfurther information about installing for end-to-end scheduling, seeScheduling End-to-end with Fault Tolerance Capabilities.

Create symbolic linksUNIX and Linux. The installation wizard installs all executable files in itsown .bin directory. Before running any IBM Workload Schedulercommands, you run a script that sets the command-line environment toaccess these files. To avoid having to set the environment each time youwant to run any of the commands from within a script, you can select aninstallation option to create symbolic links to those commands or utilitiesmost frequently used from within scripts. Table 3 shows the binary pathsand the symbolic links.

Table 3. Symbolic link options

TWS binary path Symbolic link

/bin/at usr/bin/mat

/bin/batch usr/bin/mbatch

/bin/datecalc usr/bin/datecalc

/bin/jobstdl usr/bin/jobstdl

/bin/maestro usr/bin/maestro

/bin/mdemon usr/bin/mdemon

/bin/morestdl usr/bin/morestdl

/bin/muser usr/bin/muser

/bin/parms usr/bin/parms

Directories created outside of TWA_home at installation timeThe following list shows the directories that are created outside of TWA_homewhen you install IBM Workload Scheduler.

Windows operating systems%WINDIR%\TWA%WINDIR%\TWS%WINDIR%\system32\TWSRegistry.dat (32 bits)%WINDIR%\sysWOW64\TWSRegistry.dat (32 bits on 64 bits)%WINDIR%\TWSRegistry.dat (64 bits on 64 bits)%WINDIR%teb%WINDiR%\cit%ProgramFiles%\tivoli\cit (or the path specified by %WINDiR%\cit\cit.ini)

UNIX/etc/TWA/etc/TWS/etc/teb


http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858

/etc/cit/etc/init.d/tebclt-tws_cpa_agent_/usr/Tivoli/TWS/usr/ibm/tivoli/common/CIT/logs/opt/tivoli/cit (or the path specified by /etc/tivoli/cit/cit.ini)

Windows servicesWhen installing on the Windows operating system the Windows Service ControlManager registers services.

About this task

An installation on Windows operating systems registers the following services onthe Windows Service Control Manager:v IBM Workload Scheduler (for )v Netman (for )v Token Service (for ) - includes the In-Flight Tracing facility servicev IBM Workload Scheduler SSM Agent (for )v WebSphere Application Server (for )v IBM Common Platform Agent: tws_cpa_agent_ (for )

You can optionally create a Windows service for Jazz for Service Management. Formore information, see the section about creating a Windows service for Jazz forService Management in IBM Workload Scheduler: Administration Guide.

Note: An existing service that has the same name as the new service will beoverwritten during installation.

The Service Control Manager maintains its own user password database. If the password is changed after installation, you must use the Servicesapplet in the Control Panel to assign the new password for the Token Service andIBM Workload Scheduler (for ). For more information, see the sectionabout changing the password of the TWS_User in IBM Workload Scheduler:Administration Guide.


Chapter 4. Prerequisites

When installing a master domain manager or a dynamic domain manager considerthe following prerequisites.

The master domain manager or a dynamic domain manager installation have thefollowing prerequisites:

Relational DatabaseSee “Relational database management systems.”

WebSphere Application ServerIf you do not have this product installed, the installation processautomatically installs it.

WebSphere SDK Java Technology EditionIf you do not have this product installed, the installation processautomatically installs it.

For a complete list of the correct versions to install, see the System RequirementsDocument at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858.

Supported operating systemsHow to obtain information about the supported operating systems.

About this task

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

For a complete list of system requirements (disk spaces, temporary spaces andRAM usage), see System Requirements Document at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858.

Relational database management systemsA relational database management system (RDBMS) is a prerequisite of the masterdomain manager and dynamic domain manager and its backups.

About this task

You must install the RDBMS before installing IBM Workload Scheduler.

The RDBMS can be one of the following:

DB2 For more information, see “Installing DB2” on page 38.

Oracle For more information, see “Installing Oracle” on page 38.

Informix Dynamic ServerFor more information, see “Installing Informix Dynamic Server” on page39.

37

|||

http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/osForProduct?deliverableId=0CC24A00294211E880086ABC559AD03E&osPlatforms=AIX|HP|IBM%20i|Linux|Solaris|Windows|z/OS&duComponentIds=S004|S005|A001|A003|A002http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858

Microsoft SQL ServerFor more information, see “Installing Microsoft SQL Server” on page 40.

Installing DB2Before installing a master domain manager or a dynamic domain manager youmust install a database.

About this task

You can install DB2 in the following ways:

DB2 Enterprise Server Edition

A version of DB2 is bundled with the installation image. You can installDB2 in the following ways:

Server Install DB2 Server and the master domain manager on the sameworkstation.

Client Install DB2 Server on one workstation. DB2 client and the masterdomain manager or the dynamic domain manager on a differentworkstation. The advantage of this configuration is that you caneasily switch between your master domain manager and its backupor switch between your dynamic domain manager or its backup, ifnecessary.

You can install DB2 manually.

To install DB2 manually, run the DB2 server or client installation program on theproduct image. The setup files for DB2 are on the product images as follows:

Table 4. DB2 Setup files

Operating System Setup file

AIX®, HP-UX/IA64, SunOS/SPARC,SunOS/SPARC64, all Linux operatingsystems

DB2/server/db2setup

SunOS/AMD64 DB2/wse/db2setup

Windows/x86 and Windows/AMD64 DB2\SERVER\setup.exe

Installing OracleBefore installing a master domain manager or a dynamic domain manager youmust install a database.

About this task

You can install Oracle in the following ways:

Oracle Enterprise EditionThe advantage of choosing Oracle Enterprise Edition is that you canimplement the Oracle Partitioning feature to improve the performance ofevent-driven workload automation. This improves rule managementperformance, in particular the following queries: event_rule_instance,action_run, and operator_messages. For information about event-drivenworkload automation, see Overview.


||

|

Oracle Standard EditionOracle Standard Edition does not include the Oracle Partitioning feature.Installing this edition does not improve the performance of event-drivenworkload automation.

For supported versions, see the IBM Workload Scheduler System RequirementsDocument at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858.

Note:

v When installing the product on a 64-bit library operating system, use an Oracledatabase on a 64-bit library otherwise you receive a warning during theinstallation and you cannot use the product unless you run the procedure“Master domain manager or dynamic domain manager installation completeswith warning AWSJIM976W” on page 280.

v 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.– If you are performing a parallel upgrade, use an Oracle database on a 64-bit

library when installing the product on a 64-bit library, otherwise you receive awarning during the installation and you cannot use the product unless yourun the procedure “Master domain manager or dynamic domain managerinstallation completes with warning AWSJIM976W” on page 280.

– If you are performing a direct upgrade, use an Oracle database on a 64-bitlibrary operating system when upgrading the product on a 64-bit libraryoperating system, otherwise you receive a warning during the upgrade andyou cannot use the product unless you run the procedure “After upgrading amaster domain manager or a dynamic domain manager you cannot performany operation” on page 296.

For information about upgrading the RDBMS, see the data maintenance chapter inthe IBM Workload Scheduler: Administration Guide.

Installing Informix Dynamic ServerBefore installing a master domain manager or a dynamic domain manager youmust install a database.

About this task

You must have Informix Dynamic Server installed already before you install IBMWorkload Scheduler for the first time. Also, before you create the IBM WorkloadScheduler schema on the database, you must have created the following db and sbspaces:v A db space sized 100 MB and with a page size of 8K or greater, referred to as

DBSPNAME in the properties file customization steps.v A db space space sized 20 MB, referred to as TWS_DBSP_LOG in the properties

file customization steps.v An sb space for blob and clob data, sized 100 MB, referred to as TWS_SBSP in

the properties file customization steps.

To have a working IBM Workload Scheduler schema on your Informix DynamicServer database, you must follow these steps:1. Run the procedures described in “Creating or upgrading the database schema if

you are using Informix Dynamic Server” on page 74.

Chapter 4. Prerequisites 39

|

||

|

||||

||

||

||

||

||

http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048858

2. Install a master domain manager, a dynamic domain manager, or their backups.3. Configure the master domain manager, dynamic domain manager, or their

backups to connect with the database as described in “Installing for anInformix Dynamic Server” on page 109.

Installing Microsoft SQL ServerAbout this task

Before you install IBM Workload Scheduler for the first time, you must haveMicrosoft SQL Server installed. Ensure you downloaded the JDBC driver forMicrosoft SQL Server, including the following prerequisites libraries and classlibrary files :v sqljdbc_auth.dllv sqljdbc4.jarv sqljdbc.jar

Also, before you create the IBM Workload Scheduler schema on the database, youmust ha

i b m w o r kl o a d s c h e d ul e r ibm€¦ · installing a master domain manager or its backup...

Documents