Tivoli Workload Scheduler

Transcription

1 Tivoli Workload Scheduler Version 8.4 Dynamic Workload Console Installation and Troubleshooting Guide SC

2

3 Tivoli Workload Scheduler Version 8.4 Dynamic Workload Console Installation and Troubleshooting Guide SC

4 Note Before using this information and the product it supports, read the information in Notices on page 193. This edition applies to IBM Tivoli Dynamic Workload Console which is a component of Tivoli Workload Scheduler Version 8, Release 4 Modification Level 0 (program number 5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents About this publication v Intended audience for this publication......v What this publication contains v Publications v Tivoli Workload Scheduler library......vi Prerequisite publications ix Related publications x Accessing terminology online xii Accessing publications online xii Ordering publications xiv Accessibility xiv Tivoli technical training xv Support information xv Conventions used in this publication......xv Typeface conventions xv Operating system-dependent variables and paths xvi Command syntax xvi Chapter 1. Installing Overview Getting started with the installation Installation prerequisites Supported Operating Systems Additional prerequisites for using the launchpad 8 Runtime requirements System runtime requirements Supported client browsers Tivoli Workload Scheduler supported engines..9 Tivoli Dynamic Workload Broker supported servers Before installing Supported installation scenarios Available installation methods Installation media Installing Starting the installation using the launchpad..16 Installing using the graphical wizard Installing in silent mode Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix Pack Accessing the Web console Quick steps to define a Tivoli Workload Scheduler engine connection Quick steps to define a Tivoli Dynamic Workload Broker engine connection Starting and stopping an application server instance 36 Exporting the LTPA token_keys from the Tivoli Workload Scheduler z/os connector version 8.3 Fix Pack Sample Web console configurations using user registry and Single Sign-On Updating the Secure Socket Layer protocol certificates on the Web console Disabling Tivoli Workload Scheduler Version 8.3 Fix Pack 3 workstations from being connected to Web console Chapter 3. Uninstalling Uninstalling using the graphical wizard Uninstalling in silent mode Sample response file for uninstall Uninstalling the Tivoli Workload Scheduler z/os connector Chapter 4. Troubleshooting Log and trace files Activating traces Removing manually the Web console and the embedded version of WebSphere Application Server. 55 Backing up the WebSphere Application Server configuration files Restoring the WebSphere Application Server configuration files Showing the security properties Changing the security properties Setting security properties in the template file for LDAP configuration Backing up the Web console data Creating a core dump of the application server..60 Troubleshooting scenarios Troubleshooting installation scenarios Troubleshooting runtime scenarios Appendix A. Web console messages 77 IBM Tivoli message format Message code Message text Message help List of Web console messages Installation messages Interface messages Server Messages R3Batch Messages Chapter 2. Configuring Managing users and roles Enabling the Web console to use a user registry..39 Enabling the Web console to use the Single Sign-On method with engines Appendix B. Accessibility Navigating the interface using the keyboard Magnifying what is displayed on the screen Appendix C. Support information Using IBM Support Assistant Copyright IBM Corp iii

6 Tivoli Workload Scheduler IBM Support Assistant plug-in version and upgrade issues Searching knowledge bases Searching the local information center Searching the Internet Obtaining fixes Receiving weekly support updates Contacting IBM Software Support Determining the business impact Describing problems and gathering information 190 Submitting problems Notices For the code entitled BIRT For the code entitled Commons-IO TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION For the code entitled Commons File Upload For the code entitled Dojo For INSTALLSHIELD MULTI-PLATFORM 11.5 Code APACHE CODE JXML CODE InfoZip CODE HSQL CODE BROWSERLAUNCHER CODE JTOPEN CODE For the code entitled embedded version of IBM WebSphere Application Server ( embedded WebSphere Application Server ) V APACHE CODE CUP PARSER GENERATOR FOR JAVA EPL CODE JYTHON XML SCHEMAS International Components for Unicode (ICU) OAISIS XML SCHEMAS Trademarks Glossary Index iv IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

7 About this publication IBM Tivoli Dynamic Workload Console Installation and Troubleshooting Guide describes how to install, configure, uninstall, and troubleshoot the Tivoli Dynamic Workload Console component. Intended audience for this publication This publication is for system architects, system administrators, and technical specialists who are responsible for the planning and installing of Tivoli Dynamic Workload Console. Readers need to be familiar with the following topic: v PC and UNIX operating systems What this publication contains This publication contains the following chapters: v Chapter 1, Installing, on page 1 It provides the information about installation prerequisites, supported configurations, different mechanisms to install the Web console. v Chapter 2, Configuring, on page 37 It describes how to configure the Web console v Chapter 3, Uninstalling, on page 49 It provides the information about different mechanisms to uninstall he Web console. v Chapter 4, Troubleshooting, on page 53 It provides information on how to use log and trace files, and contains troubleshooting scenarios. v Appendix A, Web console messages, on page 77 It provides the description of the format and the list of application messages. v Appendix B, Accessibility, on page 183 It provides the information about the accessibility features in this product. v Appendix C, Support information, on page 185 It provides information on how to obtain support for IBM products. Publications The IBM Tivoli Dynamic Workload Console Installation and Troubleshooting guide is part of the IBM Tivoli Workload Scheduler distributed library. This section lists the other publications contained in the IBM Tivoli Workload Scheduler distributed library and related documents. It also describes how to access Tivoli publications online, and how to order Tivoli publications. This section lists publications in the Tivoli Workload Scheduler library and any other related publications. It also describes how to access Tivoli publications online and how to order Tivoli publications. Copyright IBM Corp v

8 Publications Tivoli Workload Scheduler library Tivoli Workload Scheduler comprises several separate products available for a variety of operating systems. The library is divided into: IBM Tivoli Workload Scheduling suite library This library contains all cross-platform and cross-product publications for Tivoli Workload Scheduler. IBM Tivoli Workload Scheduler distributed library This library contains all of the publications that refer to the use of Tivoli Workload Scheduler on operating systems other than z/os. IBM Tivoli Workload Scheduler for z/os library This library contains all publications that apply only to IBM Tivoli Workload Scheduler for z/os. IBM Tivoli Workload Scheduler for Applications library This library contains all publications that apply only to IBM Tivoli Workload Scheduler for Applications. IBM Tivoli Workload Scheduler for Virtualized Data Centers library This library contains all publications that apply only to IBM Tivoli Workload Scheduler for Virtualized Data Centers. IBM Tivoli Workload Scheduling suite library The following publications are available in the IBM Tivoli Workload Scheduling suite library. This library includes publications that are common to all products, operating systems, and components. v Tivoli Workload Scheduling Suite: Overview, SC Provides an overview of all Tivoli Workload Scheduler products, and the way they can be used together to provide workload management solutions for your whole enterprise. Note: This manual used to be called "General Information". v Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide, SC Describes how to work with Tivoli Workload Scheduler, regardless of operating system, using a common Web-based GUI called the Dynamic Workload Console. v Tivoli Dynamic Workload Console Download Document at This provides full information about downloading the product CD images. It also indicates the APARs that have been fixed in this release. v Tivoli Dynamic Workload Console System Requirements Document at This provides full information about the hardware and software prerequisites of the product. v Tivoli Workload Scheduler: Job Scheduling Console User s Guide, SC Describes how to work with Tivoli Workload Scheduler, regardless of operating system, using a common GUI called the Job Scheduling Console. v Tivoli Workload Scheduler, version 8.3: Warehouse Enablement Pack version Implementation Guide for Tivoli Data Warehouse, versions 1.2 and 1.3 Provides information about enabling Tivoli Workload Scheduler for Tivoli Data Warehouse. This publication is only available on the Tivoli Workload Scheduler Engine Installation CD "TWS84_OTHER", in the following path: TDW_enablement_pack/tdw_weps/aws/v8300/doc/itws_for_TDW.doc vi IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

9 Publications You cannot access it online, in the same way that you can the other books (see Accessing publications online on page xii). IBM Tivoli Workload Scheduler distributed library The following publications are available in the IBM Tivoli Workload Scheduler distributed library. This library contains publications that refer to using the product on distributed operating systems (all operating systems except z/os). v Tivoli Workload Scheduler: Quick Start Guide, GC Provides information on how to get started with an installation of Tivoli Workload Scheduler on distributed operating systems. v Tivoli Workload Scheduler Download Document at support/docview.wss?rs=672&uid=swg This provides full information about downloading the product CD images. It also indicates the APARs that have been fixed in this release. v Tivoli Workload Scheduler System Requirements Document at This provides full information about the hardware and software prerequisites of the product. v Tivoli Workload Scheduler: Planning and Installation Guide, SC Describes how to plan for and install IBM Tivoli Workload Scheduler on distributed operating systems, and how to integrate Tivoli Workload Scheduler with NetView, Tivoli Data Warehouse, Tivoli Monitoring, and Tivoli Enterprise Console. v Tivoli Workload Scheduler: Reference Guide, SC Provides an explanation of the concepts of Tivoli Workload Scheduler and describes how the product is used. Also describes the Tivoli Workload Scheduler command line used on distributed operating systems, and how extended and network agents work. v Tivoli Workload Scheduler: Administration and Troubleshooting, SC Provides information about how to administer Tivoli Workload Scheduler on distributed operating systems, and what to do if things go wrong. It includes help on many messages generated by the main components of Tivoli Workload Scheduler. v Tivoli Workload Scheduler: Database Views, SC Provides information about the views of the IBM Tivoli Workload Scheduler database. v Tivoli Workload Scheduler: Using Microsoft Cluster Service on Windows Server 2003, SC Describes how to use Tivoli Workload Scheduler with the Microsoft Cluster service on Windows Server 2003 to achieve high availability. v Tivoli Workload Scheduler: Limited Fault-tolerant Agent for i5/os, SC Describes how to install, configure, and use Tivoli Workload Scheduler limited fault-tolerant agents on i5/os. v Java API documentation. Provides information about using the Java Application Programming Interface (API). This is a set of available classes and methods running in a JAVA environment that you use to create a custom interface to manage scheduling objects in the database and in the plan. They cannot be used to manage the plan or to set global options. About this publication vii

10 Publications Documentation for the API is provided on all distributed product CDs. Mount the CD for your platform and open the following file with your Internet browser: <CD_drive>/API/doc/index.html. See for an introduction to the product. IBM Tivoli Workload Scheduler for z/os library The following publications are available in the Tivoli Workload Scheduler for z/os library: v Tivoli Workload Scheduler for z/os: Getting Started, SC Discusses how to define your installation data for Tivoli Workload Scheduler for z/os and how to create and modify plans. v Tivoli Workload Scheduler for z/os: Installation Guide, SC Describes how to install Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Customization and Tuning, SC Describes how to customize Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Managing the Workload, SC Explains how to plan and schedule the workload and how to control and monitor the current plan. v Tivoli Workload Scheduler for z/os: Quick Reference, SC Provides a quick and easy consultation reference to operate Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Diagnosis Guide and Reference, SC Provides information to help diagnose and correct possible problems when using Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Messages and Codes, SC Explains messages and codes in Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Programming Interfaces, SC Provides information to write application programs for Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Scheduling End-to-end, SC Provides information on how to integrate Tivoli Workload Scheduler for z/os with Tivoli Workload Scheduler, controlling workload in a distributed environment from a z/os master domain manager. v Tivoli Workload Scheduler for z/os: Memo to Users, GI Provides a summary of changes for the current release of the product. v Tivoli Workload Scheduler for z/os: Program Directory, GI Provided with the installation tape for Tivoli Workload Scheduler for z/os, describes all of the installation materials and gives installation instructions specific to the product release level or feature number. See for an introduction to the product. viii IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

11 IBM Tivoli Workload Scheduler for Applications library The following publications are available in the IBM Tivoli Workload Scheduler for Applications library: v Tivoli Workload Scheduler for Applications: User s Guide, SC Provides information on how to install, set up, and use the IBM Tivoli Workload Scheduler access methods that run and control jobs of the following applications: Oracle PeopleSoft R/3 Prerequisite z/os v Tivoli Workload Scheduler for Applications: Quick Start Guide, GC Gives an overview on how to get started with Tivoli Workload Scheduler for Applications. v Tivoli Workload Scheduler for Applications Download Document at This provides full information about downloading the product CD images. It also indicates the APARs that have been fixed in this release. v Tivoli Workload Scheduler for Applications System Requirements Document at This provides full information about the hardware and software prerequisites of the product. See for an introduction to the product. IBM Tivoli Workload Scheduler for Virtualized Data Centers library The following publications are available in the IBM Tivoli Workload Scheduler for Virtualized Data Centers library: v Tivoli Workload Scheduler for Virtualized Data Centers: User s Guide, SC Describes how to extend the scheduling capabilities of Tivoli Workload Scheduler to workload optimization and grid computing by enabling the control of IBM LoadLeveler and IBM Grid Toolbox jobs. v Tivoli Workload Scheduler for Virtualized Data Centers: Release Notes, SC Provides late-breaking information about Tivoli Workload Scheduler for Virtualized Data Centers. See products/ Y614224T20392S50.html for an introduction to the product. publications To use the information in this book effectively, you must have some prerequisite knowledge, which you can obtain from the following publications: In the IBM Tivoli Dynamic Workload Broker publication: v IBM Tivoli Dynamic Workload Broker: User's Guide, SC Publications It explains how to use Tivoli Dynamic Workload Broker to manage your scheduling environment. In the IBM Tivoli Workload Scheduler for z/os publications: v Tivoli Workload Scheduler for z/os: Managing the Workload, SC About this publication ix

12 Prerequisite publications Related It explains how to plan and schedule the workload in a z/os environment and how to control and monitor the current plan. v IBM Redbooks: IBM Tivoli Workload Scheduler for z/os: Best Practices, SG This IBM Redbook describes best practices for installing and using Tivoli Workload Scheduler for z/os. You can find this Redbook in the Redbooks Web site at sg html In the IBM WebSphere Application Server publications: For all types of information about the WebSphere Application Server, go to the WebSphere Application Server Information Center: publications The following publications also provide useful information: In the IBM Tivoli Workload Scheduler distributed publications: v IBM Redbooks: Getting Started with IBM Tivoli Workload Scheduler V8.3: Best Practices and Performance Improvements, SG Abstract: IBM Tivoli Workload Scheduler is an IBM strategic scheduling product that runs on different platforms including the mainframe. The new version of the product, IBM Tivoli Workload Scheduler V8.3, comes with some important enhancements, such as relational database management system support, new advanced planning system, which allows the definition of plans that span more that 24 hours, removal of framework requirements, new application programming interface (API), Job Scheduling Console enhancements, and so on. This IBM Redbook documents the architecture, deployment, best practices, and migration scenarios for IBM Tivoli Workload Scheduler V8.3 in a distributed environment. In addition, it covers IBM Tivoli Workload Scheduler V8.3 security, IBM DB2 and IBM WebSphere considerations, troubleshooting, tuning for performance, application programming interface, and JnextPlan, which has replaced the JnextDay process in this release. Clients and Tivoli professionals who are responsible for installing, administering, maintaining, or using IBM Tivoli Workload Scheduler V8.3 will find this book a major reference. This Redbook can be found on the Redbooks Web site at v IBM Redbooks: Customizing IBM Tivoli Workload Scheduler for z/os V8.2 to Improve Performance, SG Abstract: This IBM Redbook covers the techniques that can be used to improve the performance of Tivoli Workload Scheduler for z/os (including end-to-end scheduling). This Redbook can be found on the Redbooks Web site at v IBM Redbooks: IBM Tivoli Workload Scheduler for z/os: Best Practices, SG Abstract: This IBM Redbook describes best practices for using Tivoli Workload Scheduler for z/os. Topics covered include: Installation best practices Installation verification x IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

13 Related publications Started tasks Communication Initialization statements and parameters Security Exits Restart and cleanup Dataset triggering and event trigger tracking Variables Audit report facility This Redbook can be found on the Redbooks Web site at v IBM Redbooks: Integrating IBM Tivoli Workload Scheduler with Tivoli Products, SG Abstract: This IBM Redbook explains the benefits and technical merits of integrating IBM Tivoli Workload Scheduler Distributed and IBM Tivoli Workload Scheduler for z/os with other IBM products. Scheduling is a mission critical process for any company. However, when you talk about scheduling, you are really talking about an ecosystem. In this ecosystem, each solution is a building block that adds value to the overall solution. With IBM Tivoli Workload Scheduler, you can collect and add data to and from each component. In addition, expanding the scheduling ecosystem to include monitoring, management, help desk, storage, and business systems management provides greater value. This book discusses all these integration points and provides detailed scenarios on how to integrate IBM Tivoli Workload Scheduler with these types of applications. Because workload management is widely considered the nucleus of the data center, there are numerous opportunities for you to integrate IBM Tivoli Workload Scheduler with other products. This book addresses just some of these many opportunities. In terms of integration with IBM Tivoli Workload Scheduler, do not limit yourself to the products that this book discusses. Integration points discussed in this book should give you an idea of the potential value that IBM Tivoli Workload Scheduler integration can provide for your company. This Redbook can be found on the Redbooks Web site at v IBM Redbooks: WebSphere Application Server V6 System Management & Configuration Handbook, SG Abstract: This IBM Redbook provides system administrators, developers, and architects with the knowledge to configure a WebSphere Application Server V6 runtime environment, to package and deploy Web applications, and to perform ongoing management of the WebSphere environment. One in a series of handbooks, the entire series is designed to give you in-depth information about the entire range of WebSphere Application Server products. In this book, we provide a detailed exploration of the WebSphere Application Server V6 runtime environments and administration process. This Redbook can be found on the Redbooks Web site at v Java API documentation. About this publication xi

14 Related publications It explains how to use the Java Application Programming Interface (API). This is a set of available classes and methods running in a JAVA environment that you might want to use to create a custom interface to manage scheduling objects in the database and in the plan. They cannot be used to manage the plan or to set global options. Documentation for the API is provided on all distributed product CDs. Mount the CD for your platform and open the following file with your Internet browser: <CD_drive>/API/doc/index.html. In the IBM Tivoli Workload Scheduler for z/os publications: v Tivoli Workload Scheduler for z/os: Customization and Tuning, SC It explains how to customize Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Diagnosis Guide and Reference, SC It helps diagnose and correct possible problems when using Tivoli Workload Scheduler for z/os. v Tivoli Workload Scheduler for z/os: Messages and Codes, SC It explains messages and codes in Tivoli Workload Scheduler for z/os. In the IBM WebSphere Application Server publications: IBM Redbooks: WebSphere Application Server V6 System Management & Configuration Handbook, SG This IBM Redbook provides system administrators, developers, and architects with the knowledge to configure a WebSphere Application Server V6 runtime environment, to package and deploy Web applications, and to perform ongoing management of the WebSphere environment. This Redbook can be found on the Redbooks Web site at Accessing terminology online The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site: The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: Accessing publications online The Tivoli Workload Scheduler documentation CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. The publications are found within a Tivoli Information Center. Place the CD in the CD drive of a Windows computer and the Information Center automatically opens. If the Information Center does not open automatically, or you require more information, consult the readme.txt file in the root of the CD. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. There are two ways of accessing the Tivoli software information center: xii IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

15 Related publications Directly access the IBM Tivoli Workload Scheduler Information Center Go directly to the Information Center at the following Web address: com.ibm.tivoli.itws.doc/toc.xml Access the IBM Tivoli Workload Scheduler Information Center from the Tivoli Technical Product Documents Web site Access the Tivoli software information center by following these steps: 1. Go to the Tivoli library at the following Web address: 2. Click Tivoli product manuals 3. In the Tivoli Technical Product Documents Alphabetical Listing window, click W (for Workload Scheduler) or scroll down to the W section of the product list 4. Click the appropriate Tivoli Workload Scheduler product link to access your product libraries at the Tivoli software information center. All publications in the Tivoli Workload Scheduler suite library, distributed library, and z/os library can be found under the entry Tivoli Workload Scheduler. The Tivoli software information center page for Tivoli Workload Scheduler is displayed. It gives you access to the publications relating to the latest version of the product. Links are provided to the documentation of prior versions. 5. Click to access the Tivoli Workload Scheduler Information Center. The Information Center is Eclipse-based, and contains full instructions on how to use it to obtain information and search the publications for specific terms. Note: If you print PDF publications on other than letter-sized paper, set the option in the File Print window that enables Adobe Reader to print letter-sized pages on your local paper. For all types of information about DB2, go to the DB2 Information Center: For all types of information about the Embedded Version of the WebSphere Application Server version 6.1, go to the WebSphere Application Server Information Center: index.jsp. Note: The Embedded Version of the WebSphere Application Server version 6.1 is not the same as WebSphere Application Server - Express. It is a runtime version of WebSphere Application Server, version 6.1 which is bundled in and managed by Tivoli Workload Scheduler. For all types of information about the Oracle database, consult the documentation of Oracle Corporation. When this manual was published, the relevant documentation could be found on documentation/index.html. Note: This information has been included as a courtesy, and IBM cannot guarantee that this URL will continue to be correct. About this publication xiii

16 Related publications Tivoli Workload Scheduler online books All the books in the Tivoli Workload Scheduler for z/os library are available in displayable softcopy form on CD in the IBM Online Library: z/os Software Products Collection Kit, SK3T You can read the softcopy books on CD using these IBM licensed programs: v BookManager READ/2 (program number ) v BookManager READ/DOS (program number ) v BookManager READ/6000 (program number ) All the BookManager programs need a personal computer equipped with a CD drive (capable of reading disks formatted in the ISO 9660 standard) and a matching adapter and cable. For additional hardware and software information, refer to the publications for the specific BookManager product you are using. Updates to books between releases are provided in softcopy only. Ordering publications You can order many Tivoli publications online at the following Web site: publications/cgibin/ pbi.cgi You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: v In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative perform the following steps: 1. Go to the following Web site: publications/cgibin/pbi.cgi 2. Select your country from the list and click. The IBM Publications Center page is displayed. 3. Click About this site in the main panel to see an information page which includes the telephone number of your local representative. Accessibility Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface. xiv IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

17 Training Tivoli technical training For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides 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 to contact IBM Software Support. For more information about these three ways of resolving problems, see Appendix C, Support information, on page 185. Conventions used in this publication Typeface This publication uses several conventions for special terms and actions, operating system-dependent commands and paths, command syntax, and margin graphics. conventions This publication uses the following typeface conventions: Bold Italic v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text v Words defined in text v Emphasis of words (words as words) v New terms in text (except in a definition list) v Variables and values you must provide Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text About this publication xv

18 Conventions v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options Operating system-dependent variables and paths This publication uses the UNIX convention for specifying environment variables Command and for directory notation, except where the context or the example path is specifically Windows. When using the Windows command line, replace $variable with % variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables are not always the same in Windows and UNIX environments. For example, %TEMP% in Windows is equivalent to $tmp in UNIX environments. Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions. syntax This publication uses the following syntax wherever it describes commands: Table 1. Command syntax Syntax convention Name of command Brackets ([ ]) Description The first word or set of consecutive characters. The information enclosed in brackets ([ ]) is optional. Anything not enclosed in brackets must be specified. Braces ({ }) Braces ({ }) identify a set of mutually exclusive options, when one option is required. Underscore ( _ ) Vertical bar ( ) An underscore (_) connects multiple words in a variable. Mutually exclusive options are separated by a vertical bar ( ). You can enter one of the options separated by the vertical bar, but you cannot enter multiple options in a single use of the command. Bold Bold text designates literal information that must be entered on the command line exactly as shown. This applies to command names and non-variable options. Italic Italic text is variable and must be replaced by whatever it represents. In the example to the right, the user would replace file_name with the name of the specific file. Example conman [-file definition_file] {-prompts -prompt prompt_name } prompt_name {-prompts -prompt prompt_name } composer add file_name file_name xvi IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

19 Conventions Table 1. Command syntax (continued) Syntax convention Description Ellipsis (...) An ellipsis (...) indicates that the previous option can be repeated multiple times with different values. It can be used inside or outside of brackets. Example [ x file_name]... An ellipsis outside the brackets indicates that x file_name is optional and may be repeated as follows: x file_name1 x file_name2 x file_name3 [ x file_name...] An ellipsis inside the brackets indicates that x file_name is optional, and the file variable can be repeated as follows: x file_name1 file_name2 file_name3 x file_name [ x file_name]... An ellipsis used with this syntax indicates that you must specify x file_name at least once. About this publication xvii

20 Conventions xviii IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

21 Chapter 1. Installing This chapter describes how to install Tivoli Dynamic Workload Console and is divided into the following sections: v Overview v Getting started with the installation on page 2 v Installation prerequisites on page 3 v Runtime requirements on page 8 v Before installing on page 12 v Installing on page 15 v Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix Pack 3 on page 31 v Accessing the Web console on page 32 v Starting and stopping an application server instance on page 36 Overview The Tivoli Dynamic Workload Console, from now on referred to as Web console, is a Web-based user interface for the following set of products: v Tivoli Workload Scheduler v Tivoli Workload Scheduler for z/os v Tivoli Workload Scheduler for Applications v Tivoli Dynamic Workload Broker Starting from Version 8.4 the Web console installs also Tivoli Dynamic Workload Broker web user interface. The Tivoli Dynamic Workload Broker is an on-demand scheduling infrastructure providing dynamic management of your environment. It optimizes the use of the IT infrastructure by constantly analyzing your environment to maintain an up-to-date view of the resources available. You can access Tivoli Workload Scheduler and Tivoli Dynamic Workload Broker environments from any location in your network using one of the supported browsers connected to the Web console. The Web console must reside on a system that can reach either the Tivoli Workload Scheduler or the Tivoli Dynamic Workload Broker nodes using network connections. These are the activities that you can perform from the Web console user interface in your production environments: Tivoli Workload Scheduler v Browse and manage scheduling objects involved in current plan activities. v Create and control connections to Tivoli Workload Scheduler engines. v Submit jobs and job streams in production. v Create trial and forecast plans. v Generate workload and statistics reports from historical data stored in the database. Copyright IBM Corp

22 v Perform event correlation and trigger action in response to stated event conditions Tivoli Workload Scheduler for z/os v Browse and manage scheduling objects involved in current plan activities. v Create and control connections to Tivoli Workload Scheduler engines. v Submit jobs and job streams in production. v Generate workload and statistics reports from historical data stored in the database. Tivoli Workload Scheduler for Applications v Submit SAP jobs and job streams in production. Tivoli Dynamic Workload Broker v Define logical resources. v Edit job definitions. v Submitting and monitoring jobs. Getting started with the installation Follow these steps to install, configure, and prepare your Web console for use: 1. Check the installation prerequisites to verify that your system satisfies the installation requirements. For more information, see Installation prerequisites on page Collect the information necessary to fill in the required fields during the installation, as described in Before installing on page Choose the installation method that best suits your needs as described in Available installation methods on page Install following the instructions provided in Installing on page Perform the post-installation steps described in Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix Pack 3 on page 31 if you plan to communicate with the Tivoli Workload Scheduler or Tivoli Workload Scheduler for z/os connector Version 8.3 Fix Pack3. 6. Log in to the Web console as described in Accessing the Web console on page In the navigation tree on the left, click on Tivoli Workload Scheduler to access the Tivoli Workload Scheduler available functionality, click on Tivoli Dynamic Workload Broker to access the Tivoli Dynamic Workload Broker available functionality. Navigate the tree down these entries, and, if you need help, click on? on the top right corner of the panel, or Help in the menu of the Integrated Solutions Console panel to access to the online help. The online help that is displayed explains the functionality available in the web condole panel. In the online help panel, if you click on More Information, you get more detailed information. To effectively manage the functions available on the Web console, create engine connections to the Tivoli Workload Scheduler and Tivoli Dynamic Workload Broker environments that you want to manage. Without defining engine connections you can use only a limited set of functions, for more information refer to Managing users and roles on page IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

23 Installation prerequisites Installation prerequisites You can install the Web console: On the following existing WebSphere Application Server instances: v WebSphere Application Server version v WebSphere Application Server Network Deployment version in the stand-alone application server profile mode. with the following interim fixes installed: v PK53569 v v PK47675 PK48621 v PK46953 only for HP platforms, both for PA-RISC and Intel Itanium v PK51495 v PK50659 The Web console inherits the WebSphere Application Server installation path. To download the packages containing the required APARs, follow these steps: 1. Access the IBM Support and Download link at software/support. 2. In the Search within all of IBM Software support pane insert as search term the APAR number, for example PK48621, and click Go. 3. Click Go. The Search result page opens. 4. In the Search results panel click the entry related to the selected APAR, for example PK48621: ADMINISTRATIVE CONSOLE CAN HANG ON USER LOGOUT IF INVALID SESSION call is made. The page containing the APAR description opens. 5. In the Problem conclusion section verify which fix pack contains the fix for the APAR, and click on the highlighted link to download it. On its embedded version of WebSphere Application Server version The embedded version of WebSphere Application Server version , is available in the Web console installation CD, and it is installed during the Web console installation. During the installation you can choose in which path to install, from now on referred to as tdwc_install_dir, by default the path is: On On UNIX: %Program Windows: /opt/ibm/tdwc Files%\IBM\TDWC Note: You cannot install the Web console on top of an existing embedded version of WebSphere Application Server version Supported Operating Systems Table 2 on page 4 lists the supported operating systems, with their hardware and software requirements. Chapter 1. Installing 3

24 Installation prerequisites Table 2. Hardware and software requirements for installing the Web console Platform Asset Requirement IBM AIX Processor Power 4 minimum Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System AIX 5L 5.2 with Recommended Maintenance package Install authority Log in as root AIX 5L 5.3 with Service Pack Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB Linux x86 Processor Intel Pentium processor at 1.0 GHz minimum Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System Red Hat Enterprise Linux AS, Version 4 with Update 2 Install authority Log in as root Red Hat Enterprise Linux ES, Version 4 with Update 2 Red Hat Enterprise Linux, Version 5 with: compat-libstdc i386.rpm to install using the graphical wizard: libxp i386.rpm SUSE Linux Enterprise Server, Version 9 with SP 2 or 3 SUSE Linux Enterprise Server, Version 10 Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB 4 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

25 Installation prerequisites Table 2. Hardware and software requirements for installing the Web console (continued) Platform Asset Requirement Linux x86-64 Processor AMD Opteron and Intel EM64T Linux on POWER Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System Red Hat Enterprise Linux AS, Version 4 with Update 2 with: compat-libstdc x86_64.rpm Install authority Log in as root Red Hat Enterprise Linux ES, Version 4 with Update 2 with: compat-libstdc x86_64.rpm Red Hat Enterprise Linux, Version 5 with: compat-libstdc i386.rpm to install using the graphical wizard: libxp i386.rpm libxmu i386.rpm Use the image contained in the CD: IBM Tivoli Dynamic Workload Console 8.4 for Linux on x86 SUSE Linux Enterprise Server, Version 9 with SP 2 or 3 SUSE Linux Enterprise Server, Version 10 Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB Processor System i models that support logical partitioning (LPAR) with minimum of 450 commercial processing workload (CPW) in the Linux partition. Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System Red Hat Enterprise Linux AS, Version 4 with Update 2 with: compat-libstdc ppc.rpm Install authority Log in as root Red Hat Enterprise Linux AS, Version 5 with: compat-libstdc ppc.rpm to install using the graphical wizard: libxp ppc.rpm SUSE Linux Enterprise Server, Version 9 with SP 2 or 3 SUSE Linux Enterprise Server, Version 10 Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB Chapter 1. Installing 5

26 Installation prerequisites Table 2. Hardware and software requirements for installing the Web console (continued) Platform Asset Requirement Linux on IBM System z Microsoft Windows (32-bit) Microsoft Windows (64-bit) Processor System z Memory 1.5 GB available recommended. Swap space should be double the physical memory. Operating System Red Hat Enterprise Linux AS, Version 4 with Update 2 (64 bit kernel support only) with: compat-libstdc s390.rpm Install authority Log in as root Red Hat Enterprise Linux AS, Version 5 (64 bit kernel support only) with: compat-libstdc s390.rpm to install using the graphical wizard: libxp s390.rpm SUSE Linux Enterprise Server, Version 9 with SP 2 or 3 (64 bit kernel support only) SUSE Linux Enterprise Server, Version 10 (64 bit kernel support only) Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB Processor Intel Pentium processor at 1.0 GHz minimum Memory 1.5 GB or more available per processor. Operating System Microsoft Windows Server 2003, Standard with SP1 Microsoft Windows Server 2003, Enterprise with SP1 Microsoft Windows Server 2003, DataCenter with SP1 Install authority Log in as Administrator Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB Processor AMD Opteron or Intel EM64T Memory 1.5 GB or more available per processor. Operating System Microsoft Windows Server 2003 x64 Editions Install authority Log in as Administrator Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB 6 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

27 Installation prerequisites Table 2. Hardware and software requirements for installing the Web console (continued) Platform Asset Requirement Solaris SPARC Processor Power 4 minimum Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System Sun Solaris operating environment, Version 9 with the latest Patch Cluster Install authority Log in as root Sun Solaris operating environment, Version 10 with the latest Patch Cluster Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB Solaris x64 Processor AMD Opteron HP-UX PA-RISC HP-UX Intel Itanium v temporary directory: 350 MB Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System Sun Solaris operating environment, Version 10 with the latest Patch Cluster Install authority Log in as root Disk space The following disk space must be available before proceeding with the installation: Processor v tdwc_install_dir: 900 MB v temporary directory: 350 MB PA_RISC Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System HP-UX 11iv2 (11.23) with Standard Patch Bundles of March 2006 and Sep 2004 Bundle 11i HP-UX 11iv3 (11.31) Install authority Log in as root Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB Processor Intel Itanium 2 v temporary directory: 350 MB Memory 1.5 GB or more available per processor. Swap space should be double the physical memory. Operating System HP-UX 11iv2 (11.23) with Standard Patch Bundles of March 2006 and Sep 2004 Bundle 11i + Java patches PHCO_30476 and PHSS_34201 HP-UX 11iv3 (11.31) Install authority Log in as root Disk space The following disk space must be available before proceeding with the installation: v tdwc_install_dir: 900 MB v temporary directory: 350 MB Chapter 1. Installing 7

28 Installation prerequisites Notes: 1. The WebSphere Application Server installation uses, as temporary directory, the directory specified in the environment variables (%TEMP% for Windows, $TEMP for UNIX). If not specified, the default setting for that operating system is used. 2. For the latest information about required hardware platforms and operating systems refer to the download document available at the following link: Additional prerequisites for using the launchpad If you plan to run the installation using the launchpad, you need to have one of the following browsers installed: v Mozilla Version 1.7, or later v FireFox Version 1.0, or later v Microsoft Internet Explorer (only for Microsoft Windows operating systems) Version 5.5, or later Notes: 1. On UNIX and Linux operating systems make sure you export the browser location to the BROWSER environment variable. 2. Multiple concurrent accesses from the same system using FireFox are not supported. Runtime requirements This section contains the information about what is required to have a supported working environment. It is divided in the following topics: v System runtime requirements v Supported client browsers v Tivoli Workload Scheduler supported engines on page 9 v Tivoli Dynamic Workload Broker supported servers on page 12 System runtime requirements When performing capacity planning on the system where Web console is installed, consider also that additional disk space is used at run time to manage the data displayed in the browse task result table. This additional space depends on: v The number of objects to be displayed. v The number of queries to be run concurrently. v The number of users logged in to the Web console. As an average, one object displayed as the result of one query run by one user, requires 5 KB disk space available in the tdwc_install_dir/appserver profile directory. This disk space is then released when the panel showing the browse task result is closed. Supported client browsers You must use one of the following client browsers to access from the systems across your network, the machine where you installed the Web console: v Microsoft Internet Explorer Version 6.0 SP2 or higher. 8 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

29 Supported client browsers v Microsoft Internet Explorer Version 7.0 v FireFox Version 2.0 Tivoli Workload Scheduler supported engines The Web console supports any of these Tivoli Workload Scheduler distributed configurations: Tivoli Workload Scheduler, Version 8.4 All new functions available on the Web console are accessible. Tivoli Workload Scheduler, Version 8.3 Fix Pack 3 All Tivoli Workload Scheduler, Version 8.3 Fix Pack 3 functions available on the Web console are accessible. Reporting and event management capabilities are not available in this configuration. Note: If you plan to communicate from the Web console version 8.4 to Tivoli Workload Scheduler, Version 8.3 Fix Pack 3 through a firewall, you must install an interim fix on top of Tivoli Workload Scheduler, Version 8.3 Fix Pack 3. For more information, contact IBM Software Support as described in Appendix C, Support information, on page 185. These configurations require that the Tivoli Workload Scheduler connector installed on the engine where you want to connect from the Web console. By default it is installed on the master domain manager. Optionally you can install it on another workstation in the scheduling environments. For information about installing Tivoli Workload Scheduler connector, refer to IBM Tivoli Workload Scheduler Planning and Installation Guide. The Web console supports any of these Tivoli Workload Scheduler for z/os controller configurations: Tivoli Workload Scheduler for z/os, Version 8.3 with APAR PK46302 (Virtual Workstations), and PK41519 (Reporting) All new Tivoli Workload Scheduler for z/os functions available on the Web console are accessible. Tivoli Workload Scheduler for z/os Version 8.3 and PK41611 cumulative APAR All Tivoli Workload Scheduler for z/os Version 8.3 functions available on the Web console are accessible. Reporting capabilities and virtual workstations support are not available in this configuration. Tivoli Workload Scheduler for z/os, Version 8.2 and PK33565 cumulative APAR All Tivoli Workload Scheduler for z/os Version 8.2 functions available on the Web console are accessible. Reporting capabilities and virtual workstations support are not available in this configuration. These configurations require Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 3 installed on a distributed system in your Tivoli Workload Scheduler distributed environment. Installing Tivoli Workload Scheduler z/os connector on page 10 explains how to install the Tivoli Workload Scheduler z/os connector. Note: You must restart the Web console immediately after installation before connecting to either Tivoli Workload Scheduler Version 8.3 Fix Pack 3, or Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 3 engines. Chapter 1. Installing 9

30 Tivoli Workload Scheduler supported engines Installing Tivoli Workload Scheduler z/os connector Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 3 must be installed as an upgrade on top of Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 2. Follow this procedure to install and make operational the Tivoli Workload Scheduler z/os connector in your environment: 1. Before installing the Tivoli Workload Scheduler z/os connector, set up your environment as follows: a. Set up and start the Tivoli Workload Scheduler for z/os server, which is the server address space that runs on z/os and communicates with the Tivoli Workload Scheduler z/os connector installed on the distributed system. b. Modify the SERVER member in the TWS.INSTPARM data set. For example: SYS1.COMPLEX.TWS.INSTPARM(SERVER) SERVOPTS SUBSYS ( TWS ) PROTOCOL ( JSC ) ARM ( YES ) USERMAP ( USERMAP ) PORTNUMBER ( 445 ) 2. Download the Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 2 and Fix Pack 3 from the IBM Software Support Web site at the following link Follow the steps listed in Receiving weekly support updates on page 187 to download the software packages. 3. Install the Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 2 as follows: a. Navigate to the operating system directory. b. Run the setup according to the operating system where you are installing: On Windows: setup.exe On UNIX setup.bin c. Select the language for the installation wizard, and click OK. d. In the welcome panel click Next to proceed. The procedure checks that you have the necessary rights to perform the installation, and that no previous installations of embedded version of WebSphere Application Server and connectors exist. e. Accept the license agreement and click Next, or click Cancel to exit. f. Specify the user name and password of the TWS_user for which you are installing the connector. Click Next. g. Specify the installation directory for Tivoli Workload Scheduler z/os connector. h. Specify the following port numbers: HTTP HTTPS Transport It is the HTTP port used by the Tivoli Workload Scheduler composer command line. The default value is Transport It is the HTTPS port used by the Tivoli Workload Scheduler composer command line. The default value is IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

31 Tivoli Workload Scheduler supported engines Bootstrap/RMI It is the port used when bootstrap or RMI protocol is selected. The default value is SOAP Connector It is the SOAP port used by the Web console to communicate. The default value is Use the defaults unless you are sure those port numbers are already in use. Click Next. i. Configure the Tivoli Workload Scheduler z/os connector connection setting by specifying: Tivoli Workload Scheduler for z/os Engine Name Use the name of the controller agent as the new instance name. Tivoli Workload Scheduler for z/os Remote Host The IP address or host name of the remote z/os system where the controller is installed. Tivoli Workload Scheduler for z/os Remote TCP/IP Port The TCP/IP port number of the remote z/os system. Click Next. j. Review the installation settings and click Next to start the installation. When the installation completes, a panel displays a successful installation message or contains a list of the items that failed to install and the location of the log file. k. Click Finish. You might decide to install Tivoli Workload Scheduler z/os Connector in background using a silent installation. If so, follow these steps to perform the silent installation: a. Make a backup copy of the response file provided for the platform where you are going to install. b. Customize the response file, if needed, to fit with your environment. The following options are available in the response file: v Embedded Version of WebSphere Application Server installation location v Connector instance creation c. Navigate to the directory where the installation setup file is stored and run the installation command as follows: On On Windows: setup.exe -silent -options filename UNIX:./setup.bin -silent -options filename specifying as filename the fully qualified path to the customized response file. Note: The silent installation parameters are described in detail as comments in the response file. 4. After installing the Tivoli Workload Scheduler z/os connector Version 8.3 Fix Pack 2, edit the user-mapping used by the Tivoli Workload Scheduler for z/os server stored in member USERMAP. For example: Chapter 1. Installing 11

32 Tivoli Workload Scheduler supported engines SYS1.COMPLEX.TWS.INSTPARM(USERMAP) USER where: RACFUSER(zosuser) userid Is the user ID specified during the Tivoli Workload Scheduler z/os connector installation. Hostname.domain Is the value specified in the file named TWSConfig.properties stored in the following directory [connector_home]/[userid]/appserver/ profiles/twszconnprofile/properties. zosuser Is an existing z/os user defined in RACF. 5. On the system where the Tivoli Workload Scheduler z/os connector is installed, under the installation path in the wastools directory, run the following command: webui -operation enable -user userid -password password -port port [-server ServerName] where port is the SOAP port of the WebSphere Application Server. This is a mandatory setting when using the enable flag. Its default values are for distributed environments and for z/os environments. 6. Stop and then start the WebSphere Application Server. 7. Upgrade the Tivoli Workload Scheduler z/os connector Version 8.3. to Fix Pack 3. Tivoli Dynamic Workload Broker supported servers The Web console works with Tivoli Dynamic Workload Broker Version 1.2 servers. Before installing This section helps you to quickly choose how to install the Web console in your environment. It is divided into the following topics: v Supported installation scenarios v Available installation methods on page 14 v Installation media on page 14 Supported installation scenarios The installation procedure and the components installed for the Web console might differ according to whether or not you plan to install on an existing WebSphere Application Server version instance. Table 3 lists these different scenarios: Table 3. Components installed during the Web console installation If you select to... The following components are installed... Install on a system where the Integrated Solutions Console Advanced Edition version 7.1 is installed. Tivoli Dynamic Workload Console version IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

33 Supported installation scenarios Table 3. Components installed during the Web console installation (continued) If you select to... The following components are installed... Install on a system where no instance of WebSphere Application Server version is installed. Integrated Solutions Console Advanced Edition version 7.1 Embedded Version of the WebSphere Application Server version Install on a system where WebSphere Application Server version is already installed, but you do not want to integrate the two environments. Tivoli Dynamic Workload Console version 8.4 Integrated Solutions Console Advanced Edition version 7.1 Embedded Version of the WebSphere Application Server version Install on a system where either WebSphere Application Server version or WebSphere Application Server Network Deployment version is already installed. Notes: Tivoli Dynamic Workload Console version 8.4 Integrated Solutions Console Advanced Edition version 7.1 Tivoli Dynamic Workload Console version If you plan to install the Integrated Solutions Console Advanced Edition version 7.1 on an external WebSphere Application Server, before starting the installation, make sure that all servers are stopped except for the server associated to the profile where you plan to install, which must be active. 2. If you plan to install the Web console on an external WebSphere Application Server where the Integrated Solutions Console Advanced Edition version 7.1 is already installed, make sure that the server associated to the profile where you plan to install is active before starting the installation. You can install Tivoli Dynamic Workload Console version 8.4 on a system where a Tivoli Dynamic Workload Console version 8.3 instance is installed. This is because instances of Tivoli Dynamic Workload Console with different versions have different sets of configuration files. You cannot install more than one instance of Tivoli Dynamic Workload Console version 8.4 on the same system. By default the Tivoli Workload Scheduler installed on its embedded version of WebSphere Application Server using the server name server1. If you plan to install on an external WebSphere Application Server on a system where Tivoli Workload Scheduler is installed, before installing the Web console, create a new profile with a server name different from server1, and use this profile during the installation, as explained in Installing on an existing WebSphere Application Server instance on page 21. This is a sample command to create a new profile referring to a new server name on WebSphere Application Server: installation_directory/appserver/bin/manageprofiles.sh -create -profilename "new_profile" -hostname "hostname" -nodename "node_name" -cellname "cell_name" -servername new_server_name -adminusername administrator Chapter 1. Installing 13

34 Supported installation scenarios -adminpassword administrator_password -enableadminsecurity true -templatepath "installation_directory/appserver/profiletemplates/default" Note: You must restart the Web console immediately after the installation if you plan to connect to Internet Protocol version 6 (IPv6) enabled engines. For more information about installation options refer to Installing on page 15. Available installation methods You can install the Web console using one of the following methods: Graphical wizard You access the graphical user interface of the InstallShield for Multiplatforms (ISMP) wizard by invoking a setup command and entering the configuration settings to install and configure your installation. Using this method you can synchronously monitor the installation processing and results. For more information, see Installing using the graphical wizard on page 17. Silent Installation mode You customize a response file by adding all configuration settings to be used during installation, and then invoke from the command line the setup command using the -silent keyword. Using this method you can run the installation unattended and in the background. For more information, see Installing in silent mode on page 23. Launchpad You run the launchpad which, in turn, invokes the setup command to perform the installation in interactive mode. Using this method, the launchpad guides you through a set of panels where you become familiar with the product documentation and with the information you need to provide during the installation itself. The use of the launchpad adds some prerequisites as described in Additional prerequisites for using the launchpad on page 8. For more information about how to install using the launchpad, see Starting the installation using the launchpad on page 16. media The Web console is packaged into 11 CDs, one for each of the supported platforms. Each CD contains, for that platform, the: v Installable image v Setup file v Sample response files v Launchpad Table 4 lists, for each supported platform, the label of the CD containing the installable image, and the path on the CD to the setup file: Table 4. Labels of the CDs containing the Web console installable images Supported Platform CD Label Setup file path IBM AIX IBM Tivoli Dynamic Workload Console 8.4 for AIX (LCD ) WEBUI/AIX/setup.bin 14 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

35 Installation media Table 4. Labels of the CDs containing the Web console installable images (continued) Supported Platform CD Label Setup file path Microsoft Windows (32-bit operating-system support) Microsoft Windows (64-bit operating-system support) IBM Tivoli Dynamic Workload Console 8.4 for Windows (LCD ) IBM Tivoli Dynamic Workload Console 8.4 for Windows x64 (LCD ) Linux x86 IBM Tivoli Dynamic Workload Console 8.4 for Linux on x86 (LCD ) Linux x86-64 IBM Tivoli Dynamic Workload Console 8.4 for Linux on x86-64 (LCD ) Linux on IBM System z IBM Tivoli Dynamic Workload Console 8.4 for Linux on System z9 and zseries (LCD ) Linux on POWER IBM Tivoli Dynamic Workload Console 8.4 for Linux on POWER (LCD ) Solaris x64 IBM Tivoli Dynamic Workload Console 8.4 for Solaris x64 (LCD ) Solaris SPARC IBM Tivoli Dynamic Workload Console 8.4 Solaris SPARC (LCD ) HP-UX on PA-RISC IBM Tivoli Dynamic Workload Console 8.4 for HP-UX on PA-RISC (LCD ) HP-UX on Intel Itanium Notes: IBM Tivoli Dynamic Workload Console 8.4 for HP-UX on Itanium (LCD ) WEBUI\WINDOWS\ setup.exe WEBUI\WINDOWS_X64\ setup.exe WEBUI/LINUX/setup.bin WEBUI/LINUX_X64/ setup.bin WEBUI/LINUX390/ setup.bin WEBUI/LINUXPPC/ setup.bin WEBUI/SOLARIS_X64/ setup.bin WEBUI/SOLARIS/setup.bin WEBUI/HPUX/setup.bin WEBUI\HPIA64\setup.bin 1. If you copy or mount the CD to a system directory, make sure that the path name to that directory does not contain the following unsupported characters: { } [ ] < > $?! # * + " / % or non US-ASCII characters. 2. If you plan to install on a Windows system from a mapped remote drive, make sure you map the remote folder locally on the system where you want to install, and then run the installation using the local path. 3. If you plan to install on Linux, make sure that the files contained in the mounted image have executable permission, and that the setup.bin file is not located in a path with blanks. Installing This section explains how to install the Web console using the available installation methods. It is divided into the following topics: v Starting the installation using the launchpad on page 16 v Installing using the graphical wizard on page 17 Chapter 1. Installing 15

36 Installation media v Installing in silent mode on page 23 Starting the installation using the launchpad Use the launchpad if you want to be guided through a set of panels that helps you become familiar with the product documentation. From this user interface you can access the following sources of information: v IBM Tivoli Dynamic Workload Console Download Documents v IBM Tivoli Information Center v IBM Publications Center v IBM Tivoli Dynamic Workload Console Installation and Troubleshooting Guide The use of the launchpad adds some installation prerequisites to the normal set. For more information, refer to Additional prerequisites for using the launchpad on page 8. The general procedure for starting the launchpad installation program is as follows: 1. Insert the CD containing the installation image for the required platform into the CD drive. 2. Start the launchpad as follows: For Windows The launchpad starts automatically. If not, from the root directory of the CD, run the launchpad.exe file. For UNIX From the root directory of the CD, run the launchpad.exe file. The launchpad opens: 3. Navigate the documentation and, when ready, click on Install IBM Tivoli Dynamic Workload Console in the left pane. 16 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

37 Installing using the launchpad 4. Click on Install the IBM Tivoli Dynamic Workload Console, to start the installation process. For more information about how to continue the installation, refer to Installing using the graphical wizard. Installing using the graphical wizard Follow these steps to install the Web console using the installation wizard: 1. Move to the directory where the setup file is located, and start the installation by running: setup.bin Refer to Table 4 on page 14 to see the path to the setup file. The installation wizard first checks if there is enough free space available in the Java temporary directory. If not, the installation exits, and you must increase the size of the Java temporary directory, as described in System runtime requirements on page 8, before rerunning the installation wizard. 2. Select the language to use while installing the Web console, and click OK. In the welcome window click Next to continue with the installation. 3. The license agreement window is displayed. Read the license agreement and then select: I accept both the IBM and the non-ibm terms To continue with the installation. I do not accept the terms in the license agreement To exit installation. 4. In the following window: select the WebSphere Application Server instance where you want to install the Web console. v If you choose to install a new instance of embedded version of WebSphere Application Server, follow the instruction in Installing on a new instance of embedded version of WebSphere Application Server on page 18. Chapter 1. Installing 17

38 Installing using the graphical wizard v If you choose to install on top of an existing WebSphere Application Server, follow the instruction in Installing on an existing WebSphere Application Server instance on page 21. For a list of supported WebSphere Application Servers, refer to Supported installation scenarios on page 12. Installing on a new instance of embedded version of WebSphere Application Server Follow these steps if you selected to install the embedded version of WebSphere Application Server and the Web console: 1. Choose the path where you want to install, from now on referred to as tdwc_install_dir, or accept the default path, and click Next to proceed. To prevent the installation from failing, make sure that the installation path is less than 33 characters long and that it does not contain the following special characters: Windows - () / % *!? ( ) # + < > [ ] $ { } UNIX space character and - \ : = ~ *!? ( ) # + < > [ ] $ { } 2. In the following window, select the installation type you prefer. Choose: Default Installation If you want to use the default WebSphere Application Server settings. If so, refer to Default installation. or: Advanced Installation If you want to customize the WebSphere Application Server settings. If so, refer to Advanced installation on page 19. Default installation: Follow these steps to proceed with a Default installation: 1. Specify the User Name and Password of the WebSphere Application Server user that you want to become the Web console administrator, by default the User Name is wasadmin. 18 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

39 Default installation The User Name must be unique, 3 to 60 characters in length, and contain only the characters a-z, A-Z, 0-9, period (.), hyphen (-), underscore (_), and double-byte character set (DBCS) characters. The password must be 5 to 16 characters in length and contain only the characters a-z, A-Z, 0-9, period (.), hyphen (-), and underscore (_). Confirm the password, and click Next to continue. 2. In the next window: select if you want the administrator to access to Tivoli Workload Scheduler Web console, to the Tivoli Dynamic Workload Broker Web console, or to both of them, then click Next. Note: If you select to access one of the two available Web user interfaces, after having installed you can authorize the user to access to the other user interface by assigning him one of the predefined roles created by the installation process. For more information, refer to Managing users and roles on page Check that the values displayed in the installation summary window are correct and click Install to start the installation. While the installation is in progress, you can stop it at any time by clicking Cancel. If you do, the currently processing installation step completes, and you are asked if you want to cancel the current installation. If you choose Yes, the installation is cancelled and a summary window is displayed showing the reason for the cancellation. 4. When the installation completes successfully, a window opens showing the links to access the web user interface on the Integrated Solutions Console portal, for more information refer to Accessing the Web console on page 32. If the installation fails the window contains the list of the items that failed to install and the location of the log file. 5. Click Finish to close the installer. Advanced installation: Follow these steps to proceed with an advanced installation: Chapter 1. Installing 19

40 Advanced installation 1. In the next windows specify the port numbers you want to use for the WebSphere Application Server or accept the default values. Click Next to move to the next screen. These are the port numbers to specify: HTTP Transport Port The number of the port that the WebSphere Application Server uses for HTTP transport. Administrative Console Port The HTTP Administrative Console port on the WebSphere Application Server. HTTPS Transport Port The number of the port that the WebSphere Application Server uses for secure HTTP transport (HTTPS). Administrative Console Secure Port The HTTP Administrative Console secure port on the WebSphere Application Server. Bootstrap Port The port number for the bootstrap function. SOAP Connector Port The port number for the Simple Object Access Protocol (SOAP) connector on the WebSphere Application Server. ORB Listener Port The ORB Listener Port number on the WebSphere Application Server. SAS SSLPort The SAS SSL ServerAuth Listener Port number on the Embedded WebSphere Application Server. CSIV2 Server Authentication Port The CSIV2 SSL ServerAuth Listener Port number on the Embedded WebSphere Application Server. CSIV2 Client Authentication Port The CSIV2 SSL ClientAuth Listener Port number on the Embedded WebSphere Application Server. High Availability Manager Communication Port The High Availability Manager Communication port number for the Embedded WebSphere Application Server. Service Integration Port The Service Integration Port number for the Embedded WebSphere Application Server. Service Integration Secure Port The Service Integration Secure Port number for the Embedded WebSphere Application Server. MQ Transport Port The MQ Transport Port number for the Embedded WebSphere Application Server. MQ Transport Secure Port The MQ Transport Secure Port number for the Embedded WebSphere Application Server. 20 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

41 Advanced installation SIP Container Port The Session Initiation Protocol (SIP) Port number for the Embedded WebSphere Application Server. SIP Container Secure Port The Session Initiation Protocol (SIP) Secure Port number for the Embedded WebSphere Application Server. Click Next to continue. 2. If you are running the installation on a Windows system, select if you want to run the application server as a service, specifying a service ID, by default TDWC, and a name for the service, by default IBM WebSphere Application Server V6.1 - TDWC. 3. Complete the installation running the steps described in Default installation on page 18. Installing on an existing WebSphere Application Server instance Follow these steps if you selected to install the Web console on top of an existing WebSphere Application Server instance: 1. Select the existing WebSphere Application Server instance where you want to install the Web console by specifying the following values: Profile Name The name of the WebSphere Application Server profile defining the Web console runtime environment. Make sure the profile selected has: v The administrative console installed. You can install it also after having created the profile. v The administrative security enabled Server Name The name of the server specified in the profile to be used by the Web console. Note: WebSphere Application Server requires that the host name and server name pair used in a clustered environment must be unique. Because server1 is the hardcoded server name used by Chapter 1. Installing 21

42 Advanced installation Tivoli Workload Scheduler, specify a server name different from that if you install the Web console on the same system where the Tivoli Workload Scheduler connector is installed. Cell Name The name of the group of one or more nodes in a WebSphere Application Server distributed network that the node belongs to. Node Name The unique WebSphere Application Server-specific name that identifies the system where you want to install. 2. Locate the path where the UpdateInstaller wizard is stored. This is a wizard invoked by WebSphere Application Server to install updates. 3. Specify the user ID and password of an existing WebSphere Application Server user that you want to become the Web console administrator, by default the user ID is wasadmin. 4. In the next window: Select if you want the administrator to access the Tivoli Workload Scheduler Web console, to the Tivoli Dynamic Workload Broker Web console, or both then click Next. Note: If you select to access one of the two available web user interfaces, after installing you can authorize the user to access the other user interface by assigning him one of the predefined roles created by the installation process. For more information, refer to Managing users and roles on page Check that the values displayed in the installation summary window are correct and click Install to start the installation. While the installation is in progress, you can stop it at any time by clicking Cancel. If you do, the currently processing installation step completes, and you are asked if you want to cancel the current installation. If you choose Yes, the installation is canceled and a summary window is displayed showing the reason for the cancellation. 6. When the installation completes successfully, a window opens showing the links to access the web user interface on the Integrated Solutions Console 22 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

43 Advanced installation portal. For more information refer to Accessing the Web console on page 32. If the installation fails the window contains a list of the items that failed to install and the location of the log file. 7. Click Finish to close the installer. Installing in silent mode You can run the installation in unattended mode from the command line by adding the -silent parameter when running the setup installation file. For the installation to work, you must specify all the settings that are usually prompted when installing using the installation wizard. The installation settings are provided using a response file. Refer to Sample response file for installation on page 29 for an example of a response file. There is a sample response file named tdwc.rsp on the product installation CD, in the directory:.\webui\operatingsystem\responsefiles To install in silent mode, perform these steps on the machine on which you want to install the Web console: 1. Copy locally in a temporary directory the sample response file for that operating system. 2. Customize the options contained in the response file to suit your requirements and environment. For information on the available options, refer to Table 5 on page 24. For a list of supported Web console installation scenarios, refer to Table 3 on page Run the following command: On On Windows: setup.exe -silent -options response_file_name UNIX:./setup.bin -silent -options response_file_name where response_file_name is the fully qualified path name. 4. Check the result of the silent installation as follows: On On Windows: The installation command is asynchronous, this means that when it is issued it spawns an installation procedure and then ends without returning any value or message. To have a clear statement on whether or not the silent installation ran successfully, refer to the installation result reported in the tdwcinstall.log installation log file stored in the temporary directory. UNIX: The installation command is synchronous and it returns 0 if the installation ran successfully, a nonzero value if the installation failed. Note: In any case, for information about the installation result, refer to the tdwcinstall.log installation log file stored in the temporary directory. Table 5 on page 24 shows a list of the supported variables, together with a short description. Chapter 1. Installing 23

44 Installing in silent mode Table 5. Silent installation configuration variables Variable Description Default value Validation rules Mandatory licenseaccepted Set to false to skip the installation and exit, set to true to accept the license agreement and continue. INSTALL_METHOD The installation could install a new stand-alone WebSphere Application Server, or use an already installed WebSphere Application Server. false Must be true or false. Yes NEW Must be one of these v NEW v Installs a new embedded instance of embedded version of WebSphere Application Server 6.1 ONWAS Installs on an existing installation of WebSphere Application Server V6.1 Yes 24 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

45 Installing in silent mode Table 5. Silent installation configuration variables (continued) Variable Description Default value Validation rules Mandatory IS_DESTINATION ISC_ADMIN_USER ISC_ADMIN_PASSWORD Installation directory of the product WebSphere Application Server admin user. WebSphere Application Serve admin user's password. Windows: C:\Program Files\IBM\TDWC UNIX: /opt/ibm/tdwc 1. Supplied string must have a length of Cannot be read only 3. Must be in the appropriate format for a directory 4. Must not contain any incorrect characters for a directory name. 5. On Linux platforms, make sure that the WebUI.war file of the installation bundle is not located in a path whose name contains blanks. 6. Must not contain space characters on UNIX and Linux platforms. 7. Cannot contain any of the following characters: UNIX - \ : = ~ *!? ( ) # + < > [ ] $ { } Windows / % *!? ( ) # + < > [ ] $ { } wasadmin User name length must be in the range User name can contain the following characters: a-z, A-Z, 0-9, period (.), hyphen (-), underscore ( _ ) and DBCS characters. wasadmin Password length must be in the range Password can contain the following characters: a-z, A-Z, 0-9, period (.), hyphen (-), and underscore (_). For NEW installation type only. Yes Yes Chapter 1. Installing 25

46 Installing in silent mode Table 5. Silent installation configuration variables (continued) Variable Description Default value Validation rules Mandatory ISC_APPSERVER_DIR Fully qualified path for the WebSphere Application Server directory. WAS_PROFILE_NAME WAS_SERVER_NAME WAS_CELL_NAME WAS_NODE_NAME WebSphere Application Server profile name. WebSphere Application Server server name. WebSphere Application Server cell name. WebSphere Application Server node name. UPDATE_INSTALLER_DIR Fully qualified path for the WebSphere Application Server UpdateInstaller. WC_adminhost The port number used to connect using HTTP to Tivoli Workload Scheduler web user interface. The path name of the WebSphere Application Server. The name of the WebSphere Application Server profile defining the runtime environment. The name of the server specified in the profile to be used by Web console. The name of the group of one or more nodes in a WebSphere Application Server distributed network that the Node belongs to. The unique WebSphere Application Server-specific name that identifies the system where you want to install. The path where the UpdateInstaller is located. For ONWAS installation type only For ONWAS installation type only For ONWAS installation type only For ONWAS installation type only For ONWAS installation type only For ONWAS installation type only For NEW installation type only 26 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

47 Installing in silent mode Table 5. Silent installation configuration variables (continued) Variable Description Default value Validation rules Mandatory WC_adminhost_secure The port number used to connect using secure HTTP (HTTPS) to Tivoli Workload Scheduler web user interface. WC_defaulthost The number of the port that the WebSphere Application Server uses for HTTP transport. WC_defaulthost_secure The number of the port that the WebSphere Application Server uses for secure HTTP transport (HTTPS). BOOTSTRAP_ADDRESS The port number for the bootstrap function for the Java Remote Method Invocation (RMI) connector. SOAP_CONNECTOR_ADDRESS The Simple Object Access Protocol (SOAP) connector Port number. SAS_SSL_SERVERAUTH_LISTENER_ADDRESS The SAS SSL ServerAuth Listener Port number. CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS The CSIV2 SSL ServerAuth Listener Port number. CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS The CSIV2 SSL MutualAuth Listener Port number. ORB_LISTENER_ADDRESS The ORB Listener Port number on the Embedded WebSphere Application Server For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only Chapter 1. Installing 27

48 Installing in silent mode Table 5. Silent installation configuration variables (continued) Variable Description Default value Validation rules Mandatory DCS_UNICAST_ADDRESS The High Availability Manager Communication port number for the Embedded WebSphere Application Server. SIB_ENDPOINT_ADDRESS The Service Integration Port number for the Embedded WebSphere Application Server. SIB_ENDPOINT_SECURE_ADDRESS The Service Integration Secure Port number for the Embedded WebSphere Application Server. SIB_MQ_ENDPOINT_ADDRESS The MQ Transport Port number for the Embedded WebSphere Application Server. SIB_MQ_ENDPOINT_SECURE_ADDRESS The MQ Transport Secure Port number for the Embedded WebSphere Application Server. SIP_DEFAULTHOST The Session Initiation Protocol (SIP) Port number for the Embedded WebSphere Application Server. SIP_DEFAULTHOST_SECURE The Session Initiation Protocol (SIP) Secure Port number for the Embedded WebSphere Application Server For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only For NEW installation type only 28 IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

49 Installing in silent mode Table 5. Silent installation configuration variables (continued) Variable Description Default value Validation rules Mandatory ENABLE_TWS Specifies if the Tivoli Workload Scheduler web user interface has to be installed. true Must be true or false. Yes ENABLE_TDWB Specifies if the Tivoli Dynamic Workload Broker Web console has to be installed. true Must be true or false. Yes CREATE_WAS_SERVICE Specifies to start the WebSphere Application Server automatically at system boot. true Must be true or false. On WINDOWS operating systems WAS_SERVICE_NAME The identifier assigned to the Windows service that starts WebSphere Application Server. TDWC Must be a unique string. Can contain the following characters: a-z, A-Z and 0-9. Mandatory if CREATE_WAS _SERVICE is set to true. Sample response file for installation Sample response files for both UNIX and Windows platforms are available on the installation media. This is the content of the response file for UNIX platform: ################################################################################ ## Licensed Materials - Property of IBM ## ## 5698WSH ## ## (C) Copyright IBM Corp All Rights Reserved. ## ## US Government Users Restricted Rights - Use, duplication, ## or disclosure restricted by GSA ADP Schedule Contract with ## IBM Corp. ## ################################################################################ ### Tivoli Dynamic Workload Console License Agreement # The text of the license agreement can be found in the DOCS/license directory # of the cdrom. # Allowable values include: # true To accept the license agreement as devised in the DOCS/license # directory of the cdrom. # false To not accept the license agreement as devised in the DOCS/license # directory of the cdrom. In this case the product will not be # installed. # -V licenseaccepted="false" Chapter 1. Installing 29

50 Sample response file for installation ### Install Method # TDWC 8.4 may be either installed on top of an embedded instance of WebSphere # Application Server - Express V6.1, which is included in the installation # bundle of TDWC 8.4, or on top of an existing installation of WebSphere # Application Server V6.1. # Please check the documentation to know which editions of WebSphere Application # Server V6.1 are supported by TDWC 8.4. # Allowable values include: # NEW Installs TDWC 8.4 and an embedded instance of WebSphere # Application Server - Express V6.1 # ONWAS Installs TDWC 8.4 on top of an existing installation of WebSphere # Application Server V6.1 # -V INSTALL_METHOD="NEW" ### Install Location ("NEW" install type only) # The default install locations are: # C:\Program Files\IBM\TDWC on Windows # /opt/ibm/tdwc on UNIX/Linux # -V IS_DESTINATION="/opt/IBM/TDWC" ### WebSphere Application Server Installation ("ONWAS" install type only) # To use an existing installation of WebSphere Application Server V6.1, provide # the information to identify the profile on top of which TDWC 8.4 should be # installed. # Provide also the install location of the update installer. # Example: # -V ISC_APPSERVER_DIR="/opt/IBM/WebSphere/AppServer" # -V WAS_PROFILE_NAME="AppSrv01" # -V WAS_SERVER_NAME="server1" # -V WAS_CELL_NAME="hostnameNode01Cell" # -V WAS_NODE_NAME="hostnameNode01" # -V UPDATE_INSTALLER_DIR="/opt/IBM/WebSphere/UpdateInstaller" -V ISC_APPSERVER_DIR="" -V WAS_PROFILE_NAME="" -V WAS_SERVER_NAME="" -V WAS_CELL_NAME="" -V WAS_NODE_NAME="" -V UPDATE_INSTALLER_DIR="" ### WebSphere Application Server Administrative Credentials # In case of "NEW" install type, administrative credentials will be used to # create the new embedded instance of WebSphere Application Server - Express # V6.1. # In case of "ONWAS" install type, administrative credentials will be used to # access the existing installation of WebSphere Application Server V6.1. # -V ISC_ADMIN_USER="wasadmin" -V ISC_ADMIN_PASSWORD="wasadmin" ### WebSphere Application Server Ports ("NEW" install type only) # Specify the ports to be used by the embedded WebSphere Application # Server - Express V6.1 # -V WC_adminhost= V WC_adminhost_secure= V WC_defaulthost= V WC_defaulthost_secure= V BOOTSTRAP_ADDRESS= V SOAP_CONNECTOR_ADDRESS= V SAS_SSL_SERVERAUTH_LISTENER_ADDRESS= V CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS= IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

51 Sample response file for installation -V CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS= V ORB_LISTENER_ADDRESS= V DCS_UNICAST_ADDRESS= V SIB_ENDPOINT_ADDRESS= V SIB_ENDPOINT_SECURE_ADDRESS= V SIB_MQ_ENDPOINT_ADDRESS= V SIB_MQ_ENDPOINT_SECURE_ADDRESS= V SIP_DEFAULTHOST= V SIP_DEFAULTHOST_SECURE=25061 ### Web User Interfaces to enable for WAS administrator # TDWC consists of two web user interfaces that allow working with the following # products: # Tivoli Workload Scheduler # Tivoli Dynamic Workload Broker. # Users must be given specific TDWC roles to work with both interfaces. # If you want to automatically give these roles to the WAS administrator, # you have to properly set the variables defined in this section. # Example: # If you want the WAS administrator to be able to use both interfaces, # set the following values: # -V ENABLE_TWS="true" # -V ENABLE_TDWB="true" # -V ENABLE_TWS="true" -V ENABLE_TDWB="true" Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix Pack 3 If you plan to access an environment where Tivoli Workload Scheduler Version 8.3 Fix Pack 3 is installed, you must run an additional configuration task to enable Tivoli Workload Scheduler to work with the Web console. Notes: 1. You do not need to run these steps if you plan to connect to a Tivoli Workload Scheduler Version 8.4 environment. 2. To be able to recover to the initial configuration, make sure you run the backupconfig.sh or backupconfig.cmd script to backup the Tivoli Workload Scheduler configuration. For more information on how to run these scripts, refer to Backing up the WebSphere Application Server configuration files on page 55. This task must be run on the system where the Tivoli Workload Scheduler engine that you want to connect to is installed, and therefore: In a Tivoli Workload Scheduler distributed environment v On the master domain manager. v On a full status fault-tolerant agent (FTA) workstation where the Tivoli Workload Scheduler connector is installed. In a Tivoli Workload Scheduler z/os environment On the distributed system where the Tivoli Workload Scheduler z/os connector is installed. These are the steps you must run on that system: 1. Make sure that the WebSphere Application Server is started on the Tivoli Workload Scheduler workstation and then run the following script: Chapter 1. Installing 31

52 Post-installation steps to connect to Tivoli Workload Scheduler Version 8.3 Fix Pack 3 On Windows: As Administrator, from the directory TWS_home\wastools: On where: Accessing the Web console webui -operation enable -user TWS_user -password TWS_user_pw -port TWS_port [-server TWS_server] UNIX As root, from the directory TWS_home/wastools:./webui.sh -operation enable -user TWS_user -password TWS_user_pw -port TWS_port [-server TWS_server] TWS_user The Tivoli Workload Scheduler administrator user ID. TWS_user_pw The Tivoli Workload Scheduler administrator password. TWS_port The SOAP port of the WebSphere Application Server the Tivoli Workload Scheduler is based on. This is a mandatory setting when using the enable flag. Its default values are for distributed environments, and for z/os environments. TWS_server The name of the server specified in the WebSphere Application Server profile used by Tivoli Workload Scheduler. By default the value assigned to this field is server1. 2. Stop and start the WebSphere Application Server on the Tivoli Workload Scheduler system where you run the script. When you have completed these steps you are ready to create engine connections for the Tivoli Workload Scheduler workstation and to manage your Tivoli Workload Scheduler production environment. For information about how to accomplish these tasks, access the Web console online general help as described in Getting started with the installation on page 2, Step 7. When the installation completes successfully a window, showing a message about the successful installation and the links to access to the Integrated Solutions Console portal, is displayed. If you used the silent installation this information is stored in the tdwcinstall.log installation log file. For more details about where to find the installation logs, see Table 8 on page 53. From a supported browser, access one of the following web links provided by the installation program: where: tdwc_system It is either the hostname or the IP address of the system where you installed the Web console. http_port It is the port number used to access the Web console using an unsecure connection over HTTP. The default value for this port number is IBM Tivoli Workload Scheduler: Dynamic Workload Console Installation and Troubleshooting Guide

53 Accessing the Web console https_port It is the port number used to access the Web console using a secure connection over HTTPS. The default value for this port number is When connecting to the Integrated Solutions Console using an HTTPS connection, a security alert panel might appear. If it does, choose to proceed to continue your Web console working session. Similarly you might see security information panels while navigating through the Integrated Solutions Console; in this case choose to display nonsecure items to proceed. If you are using Internet Explorer you can avoid these panels from appearing by setting Display mixed content to Enable in the Security settings. In the Integrated Solutions Console login portlet, enter the user ID and password you specified during the installation, and click on Log in. On the navigation bar on the left, expand the Tivoli Workload Scheduler entry to access through the Web console to Tivoli Workload Scheduler environments such as Tivoli Workload Scheduler, Tivoli Workload Scheduler for z/os, and Tivoli Workload Scheduler for Applications; expand the Tivoli Dynamic Workload Broker entry to access to Tivoli Dynamic Workload Broker environments. To effectively use the functions of these two products you must define connections to the engines, respectively, the Tivoli Workload Scheduler engines and the Tivoli Dynamic Workload Broker servers. Without defining engine connections you can perform only this limited set of operations: Chapter 1. Installing 33