dyn a mi c w o r kl o a d c o n s o l e u s e r’ s g ui d e · cr eating a task to cr eate custom...

330
IBM Workload Automation Dynamic Workload Console User’s Guide Version 9 Release 4 IBM

Upload: duongdieu

Post on 29-Jul-2018

214 views

Category:

Documents


0 download

TRANSCRIPT

  • IBM Workload Automation

    Dynamic Workload Console Users GuideVersion 9 Release 4

    IBM

  • IBM Workload Automation

    Dynamic Workload Console Users GuideVersion 9 Release 4

    IBM

  • NoteBefore using this information and the product it supports, read the information in Notices on page 307.

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

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

  • Contents

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

    About this publication . . . . . . . . ixWhat is new in this release . . . . . . . . . ixWho should read this publication . . . . . . . ixAccessibility . . . . . . . . . . . . . . ixTechnical training . . . . . . . . . . . . ixSupport information . . . . . . . . . . . ix

    Chapter 1. Navigating the DynamicWorkload Console . . . . . . . . . . 1Naming conventions for scheduling objects . . . . 2Convention for specific platform information . . . 3

    Chapter 2. Getting Started . . . . . . . 5Creating and managing engine connections . . . . 6Setting user preferences. . . . . . . . . . . 6Event management configuration . . . . . . . 7

    Chapter 3. Installing and configuring theDynamic Workload Console . . . . . . 9

    Chapter 4. Running IBM WorkloadScheduler from a mobile device . . . . 11

    Chapter 5. Managing users andrepositories . . . . . . . . . . . . 13Managing user settings . . . . . . . . . . 13Changing settings repository . . . . . . . . 14Sharing a settings repository. . . . . . . . . 15Changing the Dynamic Workload Console user ofDB repository . . . . . . . . . . . . . 16

    Chapter 6. Configuring High Availability 19Changing settings repository . . . . . . . . 19

    Chapter 7. Customizing your console 21Customizing the welcome page. . . . . . . . 21Customizing your portfolio . . . . . . . . . 22Customizing your startup page . . . . . . . . 23Customizing your tasks . . . . . . . . . . 24Adding tasks to your favorite bookmarks . . . . 25Accessing hidden portlets . . . . . . . . . 25Using the news notification beacon . . . . . . 26

    Disabling news notification . . . . . . . . 27Customizing the list of notification recipients . . 27Sending internal communications . . . . . . 28

    Customizing your global settings . . . . . . . 30Customize video URLs . . . . . . . . . 31Override graphical view limits . . . . . . . 32Plan View in new window . . . . . . . . 32Plan View auto refresh interval . . . . . . . 33Disable and customize NewsFeed function . . . 33

    Disable and customize the creation of predefinedtasks. . . . . . . . . . . . . . . . 35Add customized URL to job and job streams . . 35User registry . . . . . . . . . . . . . 37z/OS http connections. . . . . . . . . . 38Limit the number of objects retrieved by queries 38Limit task and engine sharing . . . . . . . 40Entries in Workload Designer search windows. . 40Show all dependencies . . . . . . . . . 41Auditing mobile app activity . . . . . . . 41Modifying the number of archived plansdisplayed in the Dynamic Workload Console . . 42Show or hide predecessors from What-if AnalysisGantt view . . . . . . . . . . . . . 42TdwcGlobalSettings.xml sample . . . . . . 43

    Chapter 8. IBM Workload SchedulerConcepts. . . . . . . . . . . . . . 47Scheduling environment . . . . . . . . . . 47

    Workstation . . . . . . . . . . . . . 47Domain. . . . . . . . . . . . . . . 51

    Scheduling objects . . . . . . . . . . . . 54Job . . . . . . . . . . . . . . . . 55Job stream . . . . . . . . . . . . . . 56Workload application . . . . . . . . . . 57Period . . . . . . . . . . . . . . . 57Calendar . . . . . . . . . . . . . . 59Run cycle . . . . . . . . . . . . . . 59Run cycle group . . . . . . . . . . . . 61Operator instructions . . . . . . . . . . 65Parameter . . . . . . . . . . . . . . 66Dependencies. . . . . . . . . . . . . 66User . . . . . . . . . . . . . . . . 80Workstation class . . . . . . . . . . . 80Variable table . . . . . . . . . . . . . 81Workload Broker job definition . . . . . . . 81

    Production process . . . . . . . . . . . . 82Database . . . . . . . . . . . . . . 83Plans . . . . . . . . . . . . . . . 83Preproduction plan . . . . . . . . . . . 85

    Engine connections . . . . . . . . . . . . 87Event management . . . . . . . . . . . . 88Reports . . . . . . . . . . . . . . . . 90Workload service assurance . . . . . . . . . 93

    Processing and monitoring critical jobs . . . . 94Planning critical jobs . . . . . . . . . . 97

    IBM Workload Scheduler for SAP . . . . . . . 98

    Chapter 9. Creating and EditingObjects in the Database . . . . . . . 101Designing your Scheduling Environment . . . . 101

    Creating a workstation . . . . . . . . . 101Editing workstation definitions . . . . . . 104Creating a domain. . . . . . . . . . . 105Creating a pool of agents . . . . . . . . 105

    iii

    |||||||

    ||

    ||

    ||

    ===

    ||

  • Designing your Workload . . . . . . . . . 107Editing objects from the Working List View . . 108Editing objects from the Details View . . . . 109Editing objects from the Graphical View . . . 110Editing object properties . . . . . . . . . 110Creating job stream definitions . . . . . . 110Creating job definitions . . . . . . . . . 111Adding a job to a job stream . . . . . . . 125Quick submit of jobs and job streams . . . . 127Exporting a job stream definition as a workloadapplication template . . . . . . . . . . 128Adding and removing dependencies . . . . 129Creating cross dependencies . . . . . . . 131Creating and managing run cycle groups andtheir run cycles . . . . . . . . . . . . 132Creating Workload Broker objects . . . . . 139Creating an event rule . . . . . . . . . 140Editing event rules . . . . . . . . . . 145Listing object definitions in the database . . . 146

    Creating a workload application template . . . . 149Importing a workload application template . . . 152Import Cron and Windows Task Scheduler . . . 153

    Limitations . . . . . . . . . . . . . 155Managing Workload Security . . . . . . . . 155

    Managing access control list . . . . . . . 156Managing security domains . . . . . . . 158Managing security roles . . . . . . . . . 159Actions on security objects . . . . . . . . 161Attributes for security object types . . . . . 165Specifying object attribute values . . . . . . 166

    Chapter 10. Changing user passwordin the plan. . . . . . . . . . . . . 169

    Chapter 11. Monitoring your Objectsin the Plan . . . . . . . . . . . . 171Monitoring the progress of your plan . . . . . 171Monitor tasks . . . . . . . . . . . . . 173Creating a monitoring task query. . . . . . . 174Monitoring your Scheduling Environment . . . . 176

    Creating a task to Monitor Workstations . . . 177Creating a task to Monitor Domains . . . . . 178

    Monitoring your Workload . . . . . . . . . 179Creating a task to Monitor Jobs . . . . . . 180Creating a task to Monitor Critical Jobs. . . . 182Creating a task to Monitor Jobs on MultipleEngines . . . . . . . . . . . . . . 185Creating a task to Monitor Job Streams . . . . 187Creating a task to Monitor Job Streams onMultiple Engines . . . . . . . . . . . 189Creating a task to Monitor Files . . . . . . 190Creating a task to Monitor Resources . . . . 191Creating a task to Monitor Prompts . . . . . 193Event monitoring tasks . . . . . . . . . 194Creating a task to Monitor Event Rules. . . . 194Creating a task to Monitor Triggered Actions 196Creating a task to Monitor Operator Messages 197

    Creating a dashboard for monitoring . . . . . 198Controlling job and job stream processing . . . . 201

    Using dependencies to control job and jobstream processing . . . . . . . . . . . 201Using time restrictions to control job and jobstream processing . . . . . . . . . . . 202Using job priority and workstation fence tocontrol distributed job processing. . . . . . 203Using limits to control job and job streamprocessing . . . . . . . . . . . . . 204Using job confirmation to control job processing 204Using job recovery actions to control jobprocessing . . . . . . . . . . . . . 205Modifying job instances in the plan to controljob processing . . . . . . . . . . . . 206

    Using advanced statistics to forecast the estimatedduration of a job . . . . . . . . . . . . 206

    Installing the SPSS statistics subset . . . . . 207Selecting the jobs to be measured by theadvanced statistical tool . . . . . . . . . 208Importing and configuring theELAB_JOB_STAT_JS job stream . . . . . . 209Running the ELAB_JOB_STAT_JS job streamand viewing results . . . . . . . . . . 210

    Chapter 12. Working with Plans . . . 211Selecting the working plan . . . . . . . . . 211Generating Trial and Forecast Plans . . . . . . 213Display a graphical plan view . . . . . . . . 213Display a graphical preproduction plan . . . . 215Analyzing the impact of changes on yourenvironment. . . . . . . . . . . . . . 216

    Chapter 13. Submitting Workload onRequest in Production . . . . . . . 219Submitting ad hoc jobs . . . . . . . . . . 219Submitting predefined jobs . . . . . . . . . 220Submitting predefined job streams . . . . . . 220Setting properties for ad hoc jobs and predefinedjobs and job streams . . . . . . . . . . . 220

    Chapter 14. Keeping track of changesto scheduling objects . . . . . . . . 223Auditing justification and reporting . . . . . . 224Checking version information . . . . . . . . 225Auditing justification and reporting- a businessscenario . . . . . . . . . . . . . . . 226Streamline release management - a businessscenario . . . . . . . . . . . . . . . 226Version control - a business scenario. . . . . . 228

    Chapter 15. Reporting. . . . . . . . 229BIRT Reports . . . . . . . . . . . . . 229

    Creating a task to generate a Job Run Statisticsreport . . . . . . . . . . . . . . . 229Creating a task to generate a Job Run Historyreport . . . . . . . . . . . . . . . 231Creating a task to generate a WorkstationWorkload Summary report . . . . . . . . 232Creating a task to generate a WorkstationWorkload Runtimes report . . . . . . . . 233Creating a task to Create Plan Reports . . . . 234

    iv IBM Workload Automation: Dynamic Workload Console Users Guide

    ||

    ||||

    ||

    ===***||||||||||||||

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

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

  • Creating a task to Create Custom SQL Reports 235Tivoli Common Reporting reports . . . . . . 236

    Configuring Tivoli Common Reporting . . . . 237Importing IBM Workload Scheduler reports . . 238

    Chapter 16. Scenarios. . . . . . . . 241Customizing your job stream . . . . . . . . 241Using workload service assurance to monitor z/OScritical jobs . . . . . . . . . . . . . . 243Monitoring jobs running on multiple engines. . . 245

    Chapter 17. Troubleshooting theDynamic Workload Console . . . . . 251Internet Explorer version 10 compatibility mode nolonger required . . . . . . . . . . . . . 251

    Chapter 18. Reference . . . . . . . 253Accessing online product documentation . . . . 253Users and groups . . . . . . . . . . . . 253Type of communication based on SSLcommunication options . . . . . . . . . . 255Status description and mapping for distributed jobs 256Status description and mapping for z/OS jobs . . 259Status description and mapping for distributed jobstreams . . . . . . . . . . . . . . . 261Status description and mapping for z/OS jobstreams . . . . . . . . . . . . . . . 263

    Workstation types . . . . . . . . . . . . 264Graphical views in the plan . . . . . . . . 269Workload Designer . . . . . . . . . . . 275

    Working List . . . . . . . . . . . . 275Details view . . . . . . . . . . . . . 276Graphical View - modelling . . . . . . . 278Run Cycle Preview . . . . . . . . . . 281Message History . . . . . . . . . . . 282Using recovery options in job definitions . . . 283

    Regular expressions and SQL reports . . . . . 285Regular Expressions . . . . . . . . . . 285Samples of report output . . . . . . . . 290SQL report examples . . . . . . . . . . 290

    Event rule . . . . . . . . . . . . . . 292Action properties . . . . . . . . . . . 292Event properties . . . . . . . . . . . 293

    Chapter 19. Glossary . . . . . . . . 295

    Notices . . . . . . . . . . . . . . 307Trademarks . . . . . . . . . . . . . . 309Terms and conditions for product documentation 309

    Index . . . . . . . . . . . . . . . 311

    Contents v

    ||||||||

    ==

  • vi IBM Workload Automation: Dynamic Workload Console Users Guide

  • Figures

    1. Single-domain network . . . . . . . . 522. Multiple-domain network . . . . . . . . 533. Example of a condition dependency definition 764. Example of a condition dependency at run

    time . . . . . . . . . . . . . . . 765. Auto-recovery job stream with step level

    dependency . . . . . . . . . . . . 77

    6. Example of recovery job with conditiondependencies . . . . . . . . . . . . 78

    7. Cross dependencies . . . . . . . . . . 808. Critical path . . . . . . . . . . . . 95

    vii

  • viii IBM Workload Automation: Dynamic Workload Console Users Guide

  • About this publication

    IBM Workload Scheduler simplifies systems management across distributedenvironments by integrating systems management functions. IBM WorkloadScheduler plans, automates, and controls the processing of your enterprise's entireproduction workload. The IBM Dynamic Workload Console User's Guide providesdetailed information about how to configure and use the Dynamic WorkloadConsole to manage your IBM Workload Scheduler environment.

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

    For information about the APARs that this release addresses, the DynamicWorkload Console Release Notes at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048864.

    Who should read this publicationThis publication is intended for the following audience:v IBM Workload Scheduler operatorsv IBM Workload Scheduler administrators

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

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

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

    Technical trainingCloud & Smarter Infrastructure provides technical training.

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

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

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

    problems and workarounds, Technotes, and other information.

    ix

    http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048864http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27048864http://www.ibm.com/software/tivoli/education

  • v Obtaining fixes: You can locate the latest fixes that are already available for yourproduct.

    v Contacting IBM Software Support: If you still cannot solve your problem, andyou need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.

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

    x IBM Workload Automation: Dynamic Workload Console Users Guide

  • Chapter 1. Navigating the Dynamic Workload Console

    An overview to the Dynamic Workload Console.

    For an interactive overview of the product and its features, you can view severaldemo scenarios, available (in English only) on the IBM Workload AutomationYouTube channel.

    To have a quick and rapid overview of the portal and of its use, after logging in,the Welcome page for the Dynamic Workload Console is displayed in theDashboard Application Services Hub console window. This window has anavigation menu across the top, organized in categories. Each category dropsdown to display a number of options that when clicked, display a portlet in thework area on the right. Each portlet displays with a title in its tabbed window inthe work area. Just as the navigation menu items are customized according to therole of the logged in user, the welcome page is also customized for the user. TheQuick start tasks available on the Welcome page allow you to access a relatedhow-to video and launch the related portlet. Only the tasks corresponding to thelogged in user's role are displayed. To get oriented with the navigation bar, takethe tour and explore the available items. The tour brings into focus each of thenavigation bar categories and corresponding descriptive text is displayed.

    There are other helpful links on the page such a link to the embedded online help,the IBM Workload Automation YouTube channel, and a QR code to scan with yourmobile device to launch the mobile applications.

    Several products can be integrated in this portal and their related entries are listedtogether with those belonging to the Dynamic Workload Console in the navigationbar displayed at the top of the page.

    The navigation bar at the top of the page is your entry point to the DynamicWorkload Console.Related tasks:Accessing online product documentation on page 253Accessing the products online publications in IBM Knowledge Center.Adding tasks to your favorite bookmarks on page 25How to save a task to the favorite bookmarks of your browser.Creating a dashboard for monitoring on page 198Customize your console by creating pages with personalized dashboards to use formonitoring.Customizing your startup page on page 23How to customize the startup pageCustomizing the welcome page on page 21How to customize the welcome pageRelated information:Chapter 16, Scenarios, on page 241Scenarios demonstrating practical application of IBM Workload Scheduler in abusiness environment.

    1

    |

    |

    |

    |||

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

    |||

    |||

    ||

    |

    ||

    ||

    |||

    ||

    ||

    |

    |||

    https://www.youtube.com/user/workloadautomation2https://www.youtube.com/user/workloadautomation2https://www.youtube.com/user/workloadautomation2

  • Naming conventions for scheduling objects

    The Dynamic Workload Console allows you to manage and control IBM WorkloadScheduler production for z/OS and distributed environments.

    There are some differences in the processing and behavior between the IBMWorkload Scheduler products for z/OS and distributed environments. When thereare differences, the descriptions and related actions of scheduling objects areexplained for both environments.

    Table 1 lists the objects and object names typical of the IBM Workload Schedulerenvironment where they are defined.

    Table 1. Naming convention for scheduling objects

    Object descriptionObject name in a distributedenvironment

    Object name in a z/OSenvironment

    An ordered list ofactivities in plan for thecurrent productionperiod. The productionplan containsinformation about theprocesses to run, onwhich workstation, andwhat dependencies mustbe satisfied before eachprocess is launched. Theproduction plan isautomatically createdand managed by theproduct and requires nouser intervention. Theproduction plan isgenerated daily at 05:00CDT time.

    Production Plan Current Plan

    A unit of work that ispart of an application ora job stream and that isprocessed at aworkstation.

    Job Operation. An operation cancontain a list of steps to run.

    A list of jobs that run asa unit to accomplish atask (such as calculatingpayroll), together withtimes, priorities, andother dependencies thatdetermine the order inwhich the jobs run.

    Job stream Application

    A run of a job stream oran application scheduledin the plan.

    Instance Occurrence

    2 IBM Workload Automation: Dynamic Workload Console Users Guide

    ||

    ||

    ||||

    ||

    ||

    |||||

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

    ||

    |||||

    |||

    ||||||||

    ||

    |||

    ||

  • Table 1. Naming convention for scheduling objects (continued)

    Object descriptionObject name in a distributedenvironment

    Object name in a z/OSenvironment

    A type of applicationdescription related torun cycle, calendarinformation, or jobdescriptions common toall applications definedas members of thegroup.

    N/A Application Group

    A physical or logicalasset where jobprocessing occurs.

    Workstation. It is qualifiedaccording to its position in thetopology of the schedulingnetwork and on its ability tointeract with the informationcontained in the current plan.

    Workstation. It is qualifiedaccording to the type of jobprocessing it does incomputer workstation,general workstation, printworkstation.

    IBM WorkloadScheduler database

    A customized set of tables in arelational database containingdefinitions for all schedulingobjects, network topology,variables, and job processingstatistics.

    A collection of six sets ofdata, acting as a flatdatabase, that containinformation about calendars,periods, workstationdescriptions, JCL variabletables, applicationdescriptions, and operatorinstructions.

    Related concepts:Workstation on page 47Using workstations for scheduling jobs and job streams.Job on page 55Information about jobs, which are scheduling objects used to define and runactivities in the scheduling environment.Job stream on page 56Production process on page 82Generating the IBM Workload Scheduler production plan.

    Convention for specific platform informationIcons to identify the information related only to specific platforms.

    This publication uses the following icons to identify the information related only tospecific platforms:

    Distributed

    The information applies only to IBM Workload Scheduler running in adistributed environment.

    z/OS

    The information applies only to IBM Workload Scheduler running in az/OS environment.

    All information that is not marked by an icon applies to all the supportedenvironments.

    Chapter 1. Navigating the Dynamic Workload Console 3

    |

    |||||

    ||||||||

    ||

    |||

    ||||||

    ||||||

    ||||||||

    ||||||||||

    |

    ||

    |||

    |

    ||

    ||

    |

    ||

    |||

    |||

    ||

  • 4 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Chapter 2. Getting Started

    Information about the Dynamic Workload Console installation and configuration.

    For more information about this installation, see the IBM Workload Scheduler:Planning and Installation.

    To configure the Dynamic Workload Console, see the section about configuring theDynamic Workload Console in the IBM Workload Scheduler: Administration Guide tofind information about:v Launching in context with the Dynamic Workload Consolev Configuring access to the Dynamic Workload Consolev Configuring Dynamic Workload Console to use Single Sign-Onv Configuring the use of Lightweight Third-Party Authenticationv Configuring Dynamic Workload Console to use SSLv Customizing your global settingsv Configuring Dynamic Workload Console to view reports

    You can access the Dynamic Workload Console from any computer in yourenvironment using a web browser through either the secure HTTPS or HTTPprotocol.

    The first and main actions that you perform when you connect to the DynamicWorkload Console are:

    Creating a connection to a IBM Workload Scheduler engineYou specify the details (such as IP address, user name, and password) toaccess a IBM Workload Scheduler engine, and, optionally, a database tooperate with objects defined in plans or stored in the database.

    From the Dynamic Workload Console, you can access the current plan, atrial plan, a forecast plan, or an archived plan for the distributedenvironment or the current plan for the z/OS environment.

    You might want to access the database to perform actions against objectsstored in it or to generate reports showing historical or statistical data.

    In addition, working both on the database and on plans, you can createand run event rules to define and trigger actions that you want to run inresponse to events occurring on IBM Workload Scheduler nodes.

    Defining a scheduling environment You define your IBM Workload Scheduler network. You create workstationdefinitions in the database to represent the physical machines or computersystems on which your workload is scheduled to run. A IBM WorkloadScheduler network is made up of the workstations where job and jobstream processing occurs. When you design your network, you assign rolesto these workstations to suit your specific business requirements. You candesign your network with multiple domains, to divide control of a largenetwork into smaller manageable groups. A typical IBM WorkloadScheduler network consists of a workstation acting as the master domainmanager and at least one domain.

    5

  • Defining scheduling objects in the databaseYou define your workload, which consists of jobs that are concatenated injob streams. Then, you specify the calendars and run cycles according towhich job streams must run. You can also define dependencies to conditionthe workload processing. All these definitions can be done within theWorkload Designer.

    Creating tasks to manage IBM Workload Scheduler objects in the planYou specify some filtering criteria to query a list of scheduling objectswhose attributes satisfy the criteria you specified. Starting from this list,you can navigate and modify the content of the plan, switch betweenobjects, open more lists, and access other plans or other IBM WorkloadScheduler environments.

    Related concepts:Designing your Scheduling Environment on page 101How to create your Scheduling Environment.Monitoring your Workload on page 179Controlling and managing scheduling activities and objects on plans with tasks.Related tasks:Creating and managing engine connectionsHow you can create, modify, or delete engine connections.Designing your Workload on page 107Create and editing workload definitions in the database.

    Creating and managing engine connectionsHow you can create, modify, or delete engine connections.

    About this task

    To create, modify, or delete an engine connection, perform the following steps.

    Note: You can modify or delete only engine connections that you have created.

    Procedure1. From the navigation toolbar, click System Configuration > Manage Engines.2. From the displayed panel you can create, edit, delete, or share an engine

    connection, and test the connection to the remote server where IBM WorkloadScheduler is installed. You can order the list of engine connections displayed inthis panel by using sorting criteria that you select with the buttons at the topleft corner of the table.

    Related concepts:Scheduling objects on page 54Scheduling objects that you can view and manage using the Dynamic WorkloadConsole.Engine connections on page 87An engine connection is a set of configuration information that identifies a specificworkstation in the IBM Workload Scheduler environment in the network.

    Setting user preferencesYou can set user preferences to use in the output of tasks and reports.

    6 IBM Workload Automation: Dynamic Workload Console Users Guide

  • About this task

    To set the preferences to use in the output of tasks and reports, perform thefollowing steps.

    Note: The preferences that you set in this panel are not used in the output of planreports. Those reports follow the preferences set on the workstation where thequery is run.

    Procedure1. From the navigation toolbar, click System Configuration > Set User

    Preferences. The Set User Preferences panel opens, containing the currentsettings.

    2. To modify the current settings click Edit. In this panel you can specify the:v Number of rows that are displayed in the table of results of all your tasks as

    the default settingv Options to display dates, times, and time zonesv Layout and the refresh rate for the dashboard

    3. Click Save changes to save the changes you made or Discard changes to exitthe page without saving.

    Results

    In the Manage User Preferences panel, you can also enable again the newsnotification. For details, see Disabling news notification on page 27.

    Event management configurationAuthorizations needed to use event management.

    You can use the event management feature both from the IBM Workload Schedulercommand line interface and from the Dynamic Workload Console.

    You need the following authorizations to perform event management operationsfrom the Dynamic Workload Console:

    On Dashboard Application Services HubThe user ID you use to log in to Dynamic Workload Console must bedefined as user on Dashboard Application Services Hub and must bedefined within one of the following groups:

    Table 2. Event Management Authorizations

    Groups Event management operations you can perform

    TWSWEBUIOperator List and manage Event Rule Instances, Log Messages, andTriggered Actions.

    TWSWEBUIDeveloper Create, list, and manage Event Rules.

    Note: Dynamic Workload Console users belonging to theTWSWEBUIAdministrator group can perform all operations available inthe web-based user interface.

    On IBM Workload SchedulerThe IBM Workload Scheduler user credentials defined in the engine

    Chapter 2. Getting Started 7

  • connection must belong to a IBM Workload Scheduler user authorized toperform event management operations in the IBM Workload Schedulersecurity file.

    You need the create permission set for the rule object. You also need the usepermission on the objects (job, job stream, and so on) that you want to useas events.

    For more information about how to define and manage user authorizationsin the security file, see IBM Workload Scheduler: Administration Guide.

    Related concepts:Event management on page 88What the event management feature is and how to use it.

    8 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Chapter 3. Installing and configuring the Dynamic WorkloadConsole

    For more information about this installation, see Planning and Installation orPlanning and Installation

    To configure the Dynamic Workload Console, see the Administration Guide to findinformation about:v Launching in context with the Dynamic Workload Consolev Configuring access to the Dynamic Workload Consolev Configuring Dynamic Workload Console to use Single Sign-Onv Configuring Dynamic Workload Console to use SSLv Customizing your global settingsv Configuring High Availability for Dynamic Workload Consolev Configuring Dynamic Workload Console to view reports

    For more information about z/OS connector instances configuration by usingWebSphere Application Server tools, see IBM Workload Scheduler for z/OS Planningand Installation> IBM Workload Scheduler for z/OS connector > Installing, Upgradingand Uninstalling IBM Workload Scheduler for z/OS connector on distributed systems.

    9

    awspimst_welcome.htm

  • 10 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Chapter 4. Running IBM Workload Scheduler from a mobiledevice

    Use your mobile device to easily and quickly interact with your IBM WorkloadScheduler environment.

    The IT market is moving towards mobile devices, which help you perform a largenumber of tasks, such as manage your sales workforce, read your email, checkyour accounting system, or attend a web conference. Applications designed formobile devices must be intuitive and user-friendly while remaining robust andreliable, and providing instant access to business and client data wherever they are.

    You can interact with IBM Workload Scheduler by using the Self-Service Catalogand Self-Service Dashboards applications.

    To open this home page on your mobile device, access the following URL:https://host_name:port_number/dwc/mobile.jsp

    where host_name and port_number are the host name and port number of theDynamic Workload Console you are connecting to.

    You can open the applications also from the Single Entry Point page.

    For details refer to the section about product user interfaces in IBM WorkloadAutomation: Overview.

    To use an engine connection from a mobile device, ensure the engine credentialsare shared or the Dynamic Workload Console is configured to use Single-Sign On.For more information, see the section about configuring the Dynamic WorkloadConsole to use Single Sign-On in the IBM Workload Scheduler AdministrationGuide.

    Self-Service CatalogDefine services that correspond to IBM Workload Scheduler job streamsand submit them from your mobile, even if you do not have anyexperience with IBM Workload Scheduler. Services are organized intocatalogs.

    11

  • Launch the Self-Service Catalog from your mobile device by connecting tothe following URL:https://host_name:port_number/dwc/sscatalog.jsp

    where host_name and port_number are the host name and port number ofthe Dynamic Workload Console you are connecting to.

    To launch and use this application, you must have one of the followingroles:

    dwcAnalystThis is the minimum role required to access Self-Service Catalog.Users with this role can view catalogs and services to which theyare authorized and submit service requests. They cannot modifyservices or catalogs.

    dwcAdministratorUsers with this role can create, edit, and delete catalogs andservices. They can also associate roles to services and catalogs toauthorize other users to work with them.

    Self-Service DashboardsBy defining filter criteria to be applied to your jobs and workstations, youcan view dashboards and drill down to more detailed information aboutthe jobs and workstations that match the criteria. You can also performrecovery actions on the jobs and workstations.

    Launch the Self-Service Dashboards app from your mobile device byconnecting to the following URL:https://host_name:port_number/dwc/ssmanagement.jsp

    where host_name and port_number are the host name and port number ofthe Dynamic Workload Console you are connecting to.

    To launch and use this application, you must have one of the followingroles:

    dwcAnalystThis is the minimum role required to access Self-ServiceDashboards. Users with this role can view dashboards for whichthey are authorized but they cannot modify dashboards.

    dwcAdministratorUsers with this role can create, edit, and delete dashboards. Theycan also associate roles to dashboards to authorize other users towork with them.

    Related concepts:Monitoring the progress of your plan on page 171Request a graphical view of the progress of the current plan.

    12 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Chapter 5. Managing users and repositories

    How to configure, change, and share your settings repository and change the DB2user. How to manage the user settings.

    The user settings such as user preferences, saved tasks, and engine connections,which by default are stored in a settings repository that is a local XML file, mustbe exported and stored in a settings repository on a DB2 database. Using adatabase as your repository, all your existing user settings relating to currentDynamic Workload Console are saved in the database, and all the operationsinvolving user settings are run using the settings in this repository.

    Managing user settingsHow to export the user settings and import them into a new Dynamic WorkloadConsole

    Before you begin

    To perform this task you need to have the TWSWEBUIAdministrator role.

    About this task

    User settings such as user preferences, saved tasks, and engine connections arestored in the settings repository, which by default is a local file. However, you candecide to have your settings repository on a database for all Dynamic WorkloadConsole operations that involve user settings.

    You can export the content of your settings repository as an XML file, optionallymodify it, and then import it into the same or another instance of DynamicWorkload Console.

    This is particularly useful for migration purposes or if you want to modify thesame settings in multiple Dynamic Workload Console instances.

    To export the settings and import them into a new Dynamic Workload Console,perform the following procedure.

    Note: Import and export operations are performed from and to thecurrently-selected repository.

    Procedure1. From the navigation toolbar, click System Configuration > Manage Settings.2. In the Manage Settings panel, click Export Settings and save the XML file in a

    directory of your choice.3. Optionally, edit the file using an XML editor and save it.4. Log in to the Dynamic Workload Console where you want to import the

    settings and open the Manage Settings panel.5. Click Import Settings and browse to the XML file containing the settings you

    want to import. During the import operation, you choose to update or tooverwrite the existing settings with the new settings.

    13

  • 6. If you are using a local file as repository, restart the Dynamic WorkloadConsole to make the change effective or click Undo before restarting it torestore previous settings. This is not required if you are using a database asyour repository, but in this case you must ensure that during the importoperation there are no other users connected to the Dynamic Workload Consolewhile the repository content is being updated.

    Changing settings repositoryChanging the settings repository.

    Before you beginv To perform this task you need to have the TWSWEBUIAdministrator role.v You need to have access to an installed DB2 where a database has already been

    created. If you need information about how to create a DB2 database, see IBMDB2 Database for Linux, UNIX, and Windows Information Center.

    v You must have Administrator rights on that database.

    About this task

    User settings such as user preferences, saved tasks, and engine connections arestored in the settings repository, which by default is a local file. However, you candecide to have your settings repository on a database for all Dynamic WorkloadConsole operations that involve user settings.

    This can be useful, for example, for scalability purposes or to have multipleDynamic Workload Console instances sharing the same user settings.

    To use a database for your settings repository, you must configure the databasesettings, as described in the following procedure:

    Procedure1. Run the wastool:

    a. Specify the connection details of the DB2 database in theTDWCDatasource.properties file, located in the followingpath:install_dir\wastools, where install_dir is the IBM WorkloadScheduler installation path.

    b. To create the data source, submit the installTDWCDatasource commandfrom the wastools directory (install_dir\wastools), specifying theTDWCDatasource.properties file you modified in the previous step:

    On Windows:installTDWCDatasource.bat TDWCDatasource.properties

    On UNIX and Linux:./installTDWCDatasource.sh TDWCDatasource.properties

    2. Restart the Dynamic Workload Console.3. Export your settings:

    a. From the navigation toolbar, click System Configuration > ManageSettings.

    b. Optionally, in the Manage Settings panel, click Export Settings and save theXML file in a directory of your choice. In this way you save your usersettings in a local file to load them on the database, when it becomes yoursettings repository.

    14 IBM Workload Automation: Dynamic Workload Console Users Guide

    |

    ||||

    |||

    ||

    ||

    |

    http://www.ibm.com/support/knowledgecenter/SSEPGGhttp://www.ibm.com/support/knowledgecenter/SSEPGG

  • 4. Switch repository to DB2.a. In the same panel, click Configure settings repository > Use database as

    settings repository to specify that settings must be saved in the databaseinstead of a local file.

    b. In the Database connection properties section, specify the credentialsrequired to connect to the database.

    Note: For all the details about options and fields displayed in the panels,see the online help by clicking the question mark located at the top-rightcorner of each panel.

    c. Optionally, you can test the connection.d. Save the new configuration.

    5. Import your settings or initialize the database:a. Optionally, click Import settings to import your user settings from the XML

    file to the database repository. During the import operation, keep thedefault choice, which overwrites the existing settings with the new settings.Performing this step, the database is automatically initialized.

    b. If you have not performed previous step, click Configure settingsrepository >Initialize database .

    Results

    As a result, all your existing user settings relating to current Dynamic WorkloadConsole are saved in the database, and all the operations involving user settingsare run using the settings in this repository.

    Sharing a settings repositoryHow to share a settings repository on multiple Dynamic Workload Consoleinstances.

    Before you begin

    To perform this task you need to have the TWSWEBUIAdministrator role.

    About this task

    User settings such as user preferences, saved tasks, and engine connections arestored in the settings repository, which by default is a local file. However, you candecide to have your settings repository on a database for all Dynamic WorkloadConsole operations that involve user settings.

    This can be useful, for example, for scalability purposes or to have multipleDynamic Workload Console instances sharing the same user settings.

    To use a database for your settings repository, you must configure the databasesettings, as described in the following procedure:

    Procedure1. Ensure that all the Dynamic Workload Console instances that will share the

    same settings repository, also use the same user registry.2. Ensure that one Dynamic Workload Console settings repository has been

    switched to database, as described in Switch repository to DB2.

    Chapter 5. Managing users and repositories 15

  • 3. Specify this repository as the default one for all the other Dynamic WorkloadConsole instances that must share it:a. From the IBM Workload Scheduler installation path, open the

    install_dir\wastools directory and run installTDWCDatasource wastool tocreate the data source, specifying the same database settings as in the firstDynamic Workload Console instance.

    b. Restart the Dynamic Workload Console.c. From the navigation toolbar, click System Configuration > Manage

    Settings.d. In the same panel, click Configure settings repository > Use database as

    settings repository to specify that settings must be saved in the databaseinstead of a local file.

    e. In the Database connection properties section, specify the credentialsrequired to connect to the database.

    f. Optionally, you can test the connection.g. Save the new configuration.

    Results

    As a result, all user settings are saved in the database, shared by all the DynamicWorkload Console instances, and all the operations involving user settings are runusing the settings in this repository.

    Changing the Dynamic Workload Console user of DB repositoryHow to change the Dynamic Workload Console user that updates the settingsrepository on DB2.

    Before you begin

    To perform this task you need to have the TWSWEBUIAdministrator role.

    You must have switched the Dynamic Workload Console settings repository from alocal file to a database repository, as described in Changing settings repository.

    About this task

    Only users with database administrator rights are authorized to initialize theDynamic Workload Console related tables on the database.

    If you want the Dynamic Workload Console to access the database repository witha user without database administrator privileges you must follow these steps:

    Procedure1. Create a new DB2 user and grant this user with SELECT, INSERT, UPDATE,

    DELETE rights on all the following tables, belonging to TDWC schema:TDWC_EngineConnectionTDWC_QueryTaskTDWC_ReportTaskTDWC_MEQueryTaskTDWC_CredentialTDWC_ConfigurationPropertyTDWC_Preferenceable

    16 IBM Workload Automation: Dynamic Workload Console Users Guide

    Changing_settings_repository.htm

  • The above are the default permissions. However, if you need to restrict yourpolicy, you can give the following permissions to the new DB2user:revoke connect,bindadd, createtab, implicit_schema on database from public;revoke use of tablespace USERSPACE1 from public;

    grant use of tablespace userspace1 to user twsdb2;grant createtab on database to user twsdb2;grant implicit_schema on database to user twsdb2;

    2. Change Dynamic Workload Console user accessing DB2a. From the navigation toolbar, click System Configuration > Manage

    Settings.b. In the Database Settings section, specify the credentials of the newly

    created user that must to connect to the database.Note: As a result of this user switch, theDynamic Workload Console withoutdatabase administrator privileges will no longer be authorized to the followingactions in the Manage Settings panel:v Initialize databasev Import settings with Cancel and re-create option.

    Chapter 5. Managing users and repositories 17

  • 18 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Chapter 6. Configuring High Availability

    How to configure, change, and share your settings repository.

    Performance can be highly improved by migrating the Dynamic Workload Consoleto High Availability Configuration, so as to have multiple console instancesworking at the same time as one console.

    If you use a Dynamic Workload Console in High Availability configuration, whenyou connect to a Dynamic Workload Console you are not actually connecting to aspecific console but to a load balancer that dispatches and redirects the connectionsamong the nodes in the configuration. Therefore, for example, if a node fails, newuser sessions are directed to other active nodes in the configuration and thischange is completely transparent to users.

    To implement this kind of configuration, you must perform the following steps:1. Change your settings repository as described in Changing settings repository.2. Perform and verify the High Availability configuration for the Dynamic

    Workload Console as described in Administration guide > Configuring theDynamic Workload Console > Configuring High Availability for Dynamic WorkloadConsole

    If you need to upgrade an existing high availability configuration refer to the highavailability configuration topics in the IBM Workload Scheduler: Administration Guide.

    Changing settings repositoryChanging the settings repository.

    Before you beginv To perform this task you need to have the TWSWEBUIAdministrator role.v You need to have access to an installed DB2 where a database has already been

    created. If you need information about how to create a DB2 database, see IBMDB2 Database for Linux, UNIX, and Windows Information Center.

    v You must have Administrator rights on that database.

    About this task

    User settings such as user preferences, saved tasks, and engine connections arestored in the settings repository, which by default is a local file. However, you candecide to have your settings repository on a database for all Dynamic WorkloadConsole operations that involve user settings.

    This can be useful, for example, for scalability purposes or to have multipleDynamic Workload Console instances sharing the same user settings.

    To use a database for your settings repository, you must configure the databasesettings, as described in the following procedure:

    Procedure1. Run the wastool:

    19

    |

    http://www.ibm.com/support/knowledgecenter/SSEPGGhttp://www.ibm.com/support/knowledgecenter/SSEPGG

  • a. Specify the connection details of the DB2 database in theTDWCDatasource.properties file, located in the followingpath:install_dir\wastools, where install_dir is the IBM WorkloadScheduler installation path.

    b. To create the data source, submit the installTDWCDatasource commandfrom the wastools directory (install_dir\wastools), specifying theTDWCDatasource.properties file you modified in the previous step:

    On Windows:installTDWCDatasource.bat TDWCDatasource.properties

    On UNIX and Linux:./installTDWCDatasource.sh TDWCDatasource.properties

    2. Restart the Dynamic Workload Console.3. Export your settings:

    a. From the navigation toolbar, click System Configuration > ManageSettings.

    b. Optionally, in the Manage Settings panel, click Export Settings and save theXML file in a directory of your choice. In this way you save your usersettings in a local file to load them on the database, when it becomes yoursettings repository.

    4. Switch repository to DB2.a. In the same panel, click Configure settings repository > Use database as

    settings repository to specify that settings must be saved in the databaseinstead of a local file.

    b. In the Database connection properties section, specify the credentialsrequired to connect to the database.

    Note: For all the details about options and fields displayed in the panels,see the online help by clicking the question mark located at the top-rightcorner of each panel.

    c. Optionally, you can test the connection.d. Save the new configuration.

    5. Import your settings or initialize the database:a. Optionally, click Import settings to import your user settings from the XML

    file to the database repository. During the import operation, keep thedefault choice, which overwrites the existing settings with the new settings.Performing this step, the database is automatically initialized.

    b. If you have not performed previous step, click Configure settingsrepository >Initialize database .

    Results

    As a result, all your existing user settings relating to current Dynamic WorkloadConsole are saved in the database, and all the operations involving user settingsare run using the settings in this repository.

    20 IBM Workload Automation: Dynamic Workload Console Users Guide

    ||||

    |||

    ||

    ||

    |

  • Chapter 7. Customizing your console

    You can customize your console to have it display just the tasks that you want toaccess.

    When you log in to the Dynamic Workload Console, a welcome page containingquickstart information is displayed with links to additional information such as theonline documentation, a product tour, demos and videos, and more. A horizontalnavigation bar across the top contains categories of tasks for each product installedon the Dashboard Application Services Hub.

    The following sections describe how you can customize the welcome pagecustomize the list of your tasks and the startup page to include only the entriesand the pages that you really need to access. In addition to this, you can see howto customize the tasks that you need to run and how to enable or disable thenotification about product updates.

    For information about customizing user interface labels on the Dynamic WorkloadConsole, see Console identity string.

    For information about customizing user interface labels on the Dynamic WorkloadConsole, see Console identity string in the Administering applications and theirenvironment of the WebSphere Application Server product documentation.

    Customizing the welcome pageHow to customize the welcome page

    About this task

    In the Dashboard Application Services Hub, Administrators can set the consolewelcome page using the Console Properties page available in Console Settings inthe navigation toolbar.

    The content of the default Dynamic Workload Console welcome page iscustomized for the role of the logged in user. The quick start tasks available on thewelcome page allow you to access a related how-to video and launch the relatedportlet. Only the tasks corresponding to the logged in user's role are displayed. Toget oriented with the navigation bar, take the tour the visit the items available. Thetour brings into focus each of the navigation bar categories and correspondingdescriptive text is displayed. There are other helpful links on the page such as linkto the embedded online help, the Workload Automation YouTube channel, and aQR code to scan with your mobile device to launch the mobile applications.

    The administrator can modify the content of the welcome page through the EditPage option when you click the Page Actions icon. You can modify the widgets,add new widgets and remove existing widgets. This page is an arrangement ofwidgets. Compose the welcome page with the widgets needed to complete tasks.Widgets are populated with data from datasets. The Dashboard ApplicationServices Hub provides a set of widgets and the Dynamic Workload Console alsoprovides datasets related to your workload.

    To customize the welcome page, perform the following steps.

    21

    |||

    |

    |

    |

    |||

    |||||||||

    |||||||

    |

    http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fisc%2Fconsole_id.html

  • Procedure1. From the default Dynamic Workload Console welcome page, click the Page

    Actions icon and then Edit Page . If you have startup tasks defined, close thetabs of the startup tasks to return to the welcome page.

    2. Add, remove, or modify the widgets on the page using a combination of theDashboard Application Services Hub widgets and the Dynamic WorkloadConsole widgets.

    3. Click Save and exit to save your changes.

    Results

    The new welcome page is launched every time you log into the console.

    For additional information about the Dashboard Application Services Hub, click ?at the top right hand corner of the console window and launch the DashboardApplication Services Hub information center.

    For more information about customizing dashboards see Creating a dashboard formonitoring on page 198.Related concepts:Monitoring your Workload on page 179Controlling and managing scheduling activities and objects on plans with tasks.Monitoring your Scheduling Environment on page 176Tasks to monitor the workstations and domains of your environment.Chapter 1, Navigating the Dynamic Workload Console, on page 1An overview to the Dynamic Workload Console.

    Customizing your portfolioHow to customize your portfolio.

    About this task

    Several products might be integrated in this portal and their related entries arelisted together with the ones belonging to the Dynamic Workload Console in thenavigation toolbar across the top.

    You can create a list of your favorite pages, including only the tasks you use mostoften.

    The Favorites icon , lets you access your daily tasks. Entries previously displayedin the My Tasks list have been automatically added to Favorites.

    To add a task to Favorites, simply drag it to the Favorites icon. To remove an itemfrom your list of favorites, click and drag the item that you want to remove awayfrom the list.

    Alternatively, to add new tasks or manage existing tasks contained in yourFavorites list, perform the following procedure:

    Procedure1. From the welcome page, click User > Favorites.2. Select only the pages that you want to include among your favorites and click

    Apply.

    22 IBM Workload Automation: Dynamic Workload Console Users Guide

    |

    |||

    |||

    |

    |

    |

    |||

    ||

    |

    ||

    ||

    ||

    ||

  • Results

    Your customized list is displayed in the Favorites list.

    You can also define which pages must be automatically launched when logginginto the Dashboard Application Services Hub by adding them to your startuppages.

    For additional information about the Dashboard Application Services Hub consolecustomization, refer Dashboard Application Services Hub Help sectionCustomizing the console.

    Customizing your startup pageHow to customize the startup page

    About this task

    In the Dashboard Application Services Hub, you can define the list of pages thatare launched every time you log in to the console. Use My Startup Pages to add orremove dashboards from the list of dashboards or pages that are launched everytime you log into the console. Only single task and multiple task dashboards canbe added to the startup list. You can set which dashboard is to be opened as thedefault tab. When you log in, the page or dashboard set as the default startup pageis in focus. All other startup pages are opened in secondary tabs. To open one ofyour startup dashboards, click the link for that page in the Page name column.Close all tabs to return to the welcome page.

    To add a page to your startup pages, perform the following steps.

    Procedure1. Open the page you want to be launched when you log in to the console.2. Click the Page Actions icon at the top right of the panel and select Add to My

    Startup Pages.3. To remove a page, click User > My Startup Pages , select the page in the list

    and click Remove. To specify the page that will be displayed at login time,select Default.

    Results

    The page that you added is launched every time you log in to the console.

    To manage the pages you added, click User > My Startup Pages in the toolbar.From this page you can remove the pages from the list or define the default pageto be displayed when you log in.

    For additional information about the Dashboard Application Services Hub, clickHelp at the top right hand corner of the panel.Related concepts:Monitoring your Workload on page 179Controlling and managing scheduling activities and objects on plans with tasks.Monitoring your Scheduling Environment on page 176Tasks to monitor the workstations and domains of your environment.

    Chapter 7. Customizing your console 23

  • Chapter 1, Navigating the Dynamic Workload Console, on page 1An overview to the Dynamic Workload Console.

    Customizing your tasksHow you edit your task properties.

    Before you begin

    To customize a task, you must be the task owner.

    About this task

    Configured tasks are provided with default values. However, you can customizetheir properties and save the newly-modified tasks. You can modify the properties,such as filters and columns, of all the tasks that you own. Starting from a task, youcan also customize the properties of secondary queries that are launched startingfrom the objects resulting from the task.

    If you have administrator's rights, you can configure a global setting so as to limitthe number of results retrieved by monitor tasks. You can specify the maximumnumber of items that must be retrieved by the queries, and this configuration willapply to all monitor tasks run by current Dynamic Workload Console, except forMonitor Critical jobs. For more information, see Limit the number of objectsretrieved by queries on page 38.

    To customize your tasks, perform the following steps:

    Procedure1. Click System Status and Health > All Configured Tasks.2. In the All Configured Tasks panel, select a task and click Task Properties. The

    task opens displaying some tabs on the left.3. Click the tabs that refer to the properties you want to customize.4. Modify the values as required and click Save to save the modified task.

    Results

    You have personalized your task. Consider that any customization only applies tothe single task you edited. For example, if you change the columns to be displayedin a task named All Jobs in plan, this change does not affect any other task tomonitor jobs.

    What to do next

    Customizing secondary queries

    While editing or creating a task, you can also choose the columns to display insecondary queries. Secondary queries are those that are run from the table of resultsof a task. For example, from the list of jobs resulting from a task named My Jobs,you can run a secondary query to list all job streams and workstations associatedto one of the listed jobs.

    You can also customize these secondary queries from the Columns Definition panelof any task. In the Columns Definition panel of My Jobs task, you can also choosethe columns to display in job stream and workstation tasks. However, this column

    24 IBM Workload Automation: Dynamic Workload Console Users Guide

  • selection only applies to the lists of job streams and workstations obtained bydrilling down from the results of the My Jobs task; it does not apply to any othergeneric monitoring task about job streams or workstations.

    For more information on Customizing your tasks refer to: Creating a monitoringtask query on page 174.

    Adding tasks to your favorite bookmarksHow to save a task to the favorite bookmarks of your browser.

    About this task

    When you run a task, you can save it as one of the favorite bookmarks of yourbrowser so that you can launch it directly from the browser.

    To add a task to your favorite bookmarks, from the panel displaying your task

    results, click the user icon

    and select Favorites.Related concepts:Monitoring your Workload on page 179Controlling and managing scheduling activities and objects on plans with tasks.Monitoring your Scheduling Environment on page 176Tasks to monitor the workstations and domains of your environment.Chapter 1, Navigating the Dynamic Workload Console, on page 1An overview to the Dynamic Workload Console.

    Accessing hidden portletsHow to access hidden portlets

    About this task

    When the Monitor Workload portlet was introduced, several of the monitoringportlets were hidden, not removed. If you prefer to work with one of theseportlets, you can make them visible again in the navigation toolbar.

    Define a task to monitor objects in the plan by specifying a query in a query lineusing the Monitor Workload portlet. The objects for which you can create amonitoring task query are: jobs, critical jobs, job streams, workstations, files,resources, domains, and prompts. In previous versions, there were multiple portletentries in portfolio, one for each object to monitor. These entries have beencondensed into a single entry, the Monitor Workload.

    Procedure1. From the Console Settings page, select Pages.2. Expand the System Status and Health search and click the portlet name you

    want to make visible. In General Properties, under the Navigation visibilityoption, select Visible.

    3. Expand the Roles link, click on the Add button and select the role for exampleTWSWEBUIOperator and Save.

    4. From the Console Settings page, click Widget. A new page is displayedshowing all the widgets. Search for the widget name corresponding to the

    Chapter 7. Customizing your console 25

    |

    |

    |

    |||

    ||||||

    |

    |

    |||

    ||

    ||

  • portlet that you previously modified. If the same name appears more thanonce, perform the following action for each entry. Click on the Widget nameand a new panel is shown. Click Next and you will be directed to the securitytab under the Edit section.

    5. From the Security tab select the roles you previously added in step 3 and clickFinish. To see the changes, log out and log in.

    Results

    For additional information on the Dashboard Application Services Hub consolecustomization, refer to Dashboard Application Services Hub Help sectionCustomizing the console.

    Refer to http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/edit_page.html?cp=SSEKCU_1.1.0.3%2F8-2-1-6&lang=en for more information on editing dashboard content and how to makehide or make visible the navigation bar. To enable the former monitoring portletssuch as the Monitoring Jobs portlet, see the Monitor Workload topic.

    Using the news notification beaconHow to be always up to date with the latest news and information about theproduct and receive internal communications from the environment administrator.

    About this task

    A beacon appears on your screen when an update for the product or an internalcommunication from the administrator is made available. Click the beacon to opena pop-up that describes the update and gives you a direct link to it.

    Update and news notifications relate to different topics, belonging to categories,such as:v APARsv Fixes and utilitiesv Newsv Technotesv Product documentation and publicationsv Internal communications

    By default, the news notification is enabled for all users to all the categories,however, optionally, the TWSWEBUIAdministrator can customize this behaviorspecifying which user roles must receive all the notifications or only some of themor even none. For more information, see: Disable and customize NewsFeedfunction on page 33.

    The news notification is enabled by default, however, to unsubscribe from all thenews, or only form the displayed news category, you can select the relatedcheck-box in the news pop-up.

    In the pop-up window that displays the latest news, you can also navigate throughpast news and notifications and provide your feedback on a piece of news througha feedback form.

    26 IBM Workload Automation: Dynamic Workload Console Users Guide

    ||||

    ||

    |

    |||

    |||||

    http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/edit_page.html?cp=SSEKCU_1.1.0.3%2F8-2-1-6&lang=enhttp://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/edit_page.html?cp=SSEKCU_1.1.0.3%2F8-2-1-6&lang=enhttp://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/edit_page.html?cp=SSEKCU_1.1.0.3%2F8-2-1-6&lang=en

  • If you have TWSWEBUIAdministrator role or writing rights on the system whereDynamic Workload Console, is installed, you can add multiple NewsFeed sectionsin the TdwcGlobalSettings.xml file to transmit different notifications to differentuser roles. For more information, see Sending internal communications on page28.

    Disabling news notificationHow to enable and disable news notification preventing the beacon fromappearing on your screen when an update for the product is made available.

    About this task

    By default, all users receive all the news notifications. However, optionally, you cancustomize this behavior by preventing all or only some specific news from beingnotified to you.

    When the beacon appears on your screen and you click it, the first notificationdisplays in a pop-up. If you do not want to receive any notifications at all, or ifyou want to unsubscribe from some specific categories of notifications, select therelated checkbox in the news pop-up.

    To enable again all the news notifications, perform the following steps:1. From the navigation toolbar, click System Configuration > Set User

    Preferences. The Set User Preferences panel containing the current settings isdisplayed.

    2. Click Restore beacon defaults.Related reference:Disable and customize NewsFeed function on page 33

    Customizing the list of notification recipientsHow to customize the list of recipients of the news notification beacon, byspecifying who must receive what kind of notification or communication.

    Before you begin

    You must have TWSWEBUIAdministrator role or writing rights on the systemwhere Dynamic Workload Console is installed.

    About this task

    By default, the news notification is enabled for all users to all the categories,however, optionally, the TWSWEBUIAdministrator can customize this behaviorspecifying which user roles must receive all the notifications and internalcommunications, or only some of them or even none. You can send multiple feeds,containing different communications, addressed to different recipients bycustomizing the TdwcGlobalSettings.xml file and providing multiple feeds, asexplained in Sending internal communications on page 28.

    For example, often operators do not need to have information about new patchesand fix packs to be installed or about product events. Analysts are only interestedin information and updates about reporting. Whereas, Administrators want toreceive all notifications (and, optionally, force the default settings and send anotification to those who are normally excluded from a category).

    Chapter 7. Customizing your console 27

  • Procedure

    Customize the TdwcGlobalSettings.xml file to specify the news categories thatmust be notified to users, based on their roles.You can find a copy of this file also on the installation media in the directory/utilities/TdwcGlobalSettings.xml.The TdwcGlobalSettings.xml file is organized into several sections that can berepeated multiple times in the same file and applied differently to different userroles. Therefore, to customize a behavior based on the user role, uncomment thesection corresponding to the user role and include the sections that must apply tothis role.The Disable and customize NewsFeed function section contains the configurationdetails regarding the notification beacon. Therefore, for example, to enable thenotifications of specific categories only to a specific user role, you can insert asection like the following:

    Example

    If no customized feed is specified, the default feed is used, which retrieves thelatest product information from official support sites. To disable any notification,comment the entire section. To disable only external notifications about productinformation updates, assign an empty string as value to the FeedURL property ofJSONP feed like:

    Related reference:Disable and customize NewsFeed function on page 33

    Sending internal communicationsHow to use the news feed beacon to transmit internal communications to all orsome Dynamic Workload Console users.

    Before you begin

    You must have TWSWEBUIAdministrator role or writing rights on the systemwhere Dynamic Workload Console, is installed.

    About this task

    You can use the news notification beacon to send specific communications tointernal Dynamic Workload Console users, simply by storing these

    28 IBM Workload Automation: Dynamic Workload Console Users Guide

  • communications on the Dynamic Workload Console server. For example,administrators can use this feature to broadcast maintenance notices or companyrelated announcements.

    Note:

    If no customized feed is specified, the default feed is used, which retrieves thelatest product information from official support sites. To disable any notification,comment the entire section. To disable only external notifications about productinformation updates, assign an empty string as value to the FeedURL property ofJSONP feed like:

    To add customized feeds, specify a list of sections named NewsFeed in theTdwcGlobalSettings.xml file by performing the following procedure:

    Procedure1. Edit the TdwcGlobalSettings.xml file by adding the properties specifying the

    name and format of the file in the NewsFeed section. Example:

    For more details, see the Customizing your global settings on page 30.2. Optionally, specify a polling interval for the feed reading and an image

    associated to the notification. Example:

    Note: To specify multiple feeds, you must specify multiple NewsFeedproperties.

    3. Optionally, specify a list of feeds that must be taken into consideration by thenotification feature. The browser detects new items from all the specified feedsand merge them sorting them by date in a single list.

    4. Write the communication in ATOM 1.0 or RSS 2.0 format and store this file inthe an HTTP server complying with the same origin policy. For browser securityreasons, this policy permits to access information only on server using the sameprotocol, hostname and port number as the one to which you are connected.

    5. Optionally, if you want to store your customized feed on an external server,you must configure an HTTP reverse proxy server mapping the external serveraddress.

    Results

    The notification beacon function reads all the feeds specified in the NewsFeedsection, detects new information and aggregates all in a single file ordering it bydate. Then, it transmits notifications and internal communications to the recipientsbased on the roles specified in the TdwcGlobalSettings.xml file.Related reference:Disable and customize NewsFeed function on page 33

    Chapter 7. Customizing your console 29

  • Customizing your global settingsHow to customize global settings.

    About this task

    To customize the behavior of the Dynamic Workload Console, you can optionallyconfigure some advanced settings. These settings are specified in a customizablefile named TdwcGlobalSettings.xml.template.

    By default, the customizable file is copied into the following path after you installthe Dynamic Workload Console:

    For Windows systems:C:\Program Files\IBM\JazzSM\profile\registry\TdwcGlobalSettings.xml.template

    For UNIX and Linux systems: /opt/IBM/JazzSM/profile/registry/TdwcGlobalSettings.xml.template

    You can find a copy of this file also on the installation media in the directory/utilities/TdwcGlobalSettings.xml.

    If you have Administrator privileges, you can modify the file to replace defaultvalues with customized ones and enable commented sections. To enablecommented sections, remove the tags that enclose the section. Youthen save the file locally with the name TdwcGlobalSettings.xml.

    You can add and modify some customizable information, such as:v The URLs that link to videos in the Dynamic Workload Console. For example,

    you can link to a company intranet server to view help videos rather than to apublic video site.

    v The maximum number of objects to be shown in the graphical views.v The setting to display the plan view in a new window.v The auto refresh interval for the Show Plan View graphical view.v The configuration details to enable the news notification beacon and be

    constantly up-to-date with product information. See Disabling news notification.v The creation of predefined tasks.v The URLs where you can store customized documentation about your jobs or

    job streams to associate customized documentation to them.v The current user registry in use.v The timeout to read and write information on a IBM Workload Scheduler for

    z/OS engine.v The maximum number of objects to be retrieved with a query, the maximum

    number of rows to display in a table, and the maximum number of directqueries to maintain in history.

    v Allowing or preventing users from sharing tasks and engine connections.v The display of all dependencies, both satisfied and unsatisfied.v The use of audit files to track activities in the Self-Service Catalog and

    Self-Service Dashboards mobile applications.v Displaying or hiding all predecessors from the What-if Analysis Gantt view.

    30 IBM Workload Automation: Dynamic Workload Console Users Guide

    |||

    *

    =

    disablingbeacon.htm

  • This file is accessed at each login, and all configurations specified in the file areimmediately applied, except for the precannedTaskCreation property. Thisproperty is read only when a user logs in for the first time and is then usedwhenever this user logs in again.

    You can use any text or XML editor to edit this file, but ensure that you save it isas a valid XML file.

    The file is organized into sections that group similar properties. An explanation ofeach section is available in the file. For more information, seeTdwcGlobalSettings.xml sample on page 43.

    Sections can also be repeated multiple times in the same file and applieddifferently to different user roles. To apply a section only to the users belonging toa role, the section must be included within the tags and , where:

    The user for which the enclosed configuration must be applied. The defaultvalue is all users, unless otherwise specified.

    Only one settings section can be specified for each role. If a user has more thanone role, the settings associated to the higher role are used.

    Example:

    ..

    ..

    To view the complete syntax for the file, see TdwcGlobalSettings.xml sample onpage 43.

    Customize video URLsThis section shows how you should customize your URLs that link video contentin the Dynamic Workload Console so that you can link to a company intranetserver to view help videos rather than a public video site.

    The _baseURL prefix will be added to all your video URLs . If you do not specify alink for your video the default setting will automatically be used.

    ..

    Chapter 7. Customizing your console 31

    |

    |||

    ||

    |||||

  • -

  • .

    .

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.

    Plan View auto refresh intervalUse this section to change the default setting of the auto refresh interval for theShow Plan View graphical view for all users. By default, the auto refresh interval is300 seconds (five minutes).

    PlanViewAutorefreshThe graphical representation of the Plan View is automatically refreshevery 300 seconds by default. To change this setting, edit the valueassigned to the DefaultTime property. The minimum value you can set is30 seconds. Any value specified below this value is reset to 30 seconds.You must restart the Dynamic Workload Console application server aftermodifying this value.

    ..

    ..

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.

    Disable and customize NewsFeed functionThis section contains the configuration details to be constantly up-to-date withproduct information.

    FeedURLContains the URL from which you receive news and updates. Defaultvalue is: https://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/585f5525-a7f5-48ef-9222-50ad582e85f4/page/e599dd3c-8dc3-4ab6-89fd-33f81a994799/attachment/de677e63-5a9d-46db-a010-18ca38f05812/media/tws.jsonp

    FeedTypeA string that identifies the format of update information. Default value isJSONP.

    PollIntervalThe interval in seconds between two checks for updates. Default value is600.

    PollInitialDelayAn initial delay in seconds before the first attempt to read the news feeds.After the initial load, the poll interval is used. Default value is 120.

    Chapter 7. Customizing your console 33

    https://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/585f5525-a7f5-48ef-9222-50ad582e85f4/page/e599dd3c-8dc3-4ab6-89fd-33f81a994799/attachment/de677e63-5a9d-46db-a010-18ca38f05812/media/tws.jsonphttps://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/585f5525-a7f5-48ef-9222-50ad582e85f4/page/e599dd3c-8dc3-4ab6-89fd-33f81a994799/attachment/de677e63-5a9d-46db-a010-18ca38f05812/media/tws.jsonphttps://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/585f5525-a7f5-48ef-9222-50ad582e85f4/page/e599dd3c-8dc3-4ab6-89fd-33f81a994799/attachment/de677e63-5a9d-46db-a010-18ca38f05812/media/tws.jsonphttps://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/585f5525-a7f5-48ef-9222-50ad582e85f4/page/e599dd3c-8dc3-4ab6-89fd-33f81a994799/attachment/de677e63-5a9d-46db-a010-18ca38f05812/media/tws.jsonp

  • NewsFeedProperty used to add further customized news feeds. Specify the formatand address of the file that contains the customized communication.Supported formats are RSS 2.0 and ATOM 1.0. You must write thecommunication in ATOM 1.0 or RSS 2.0 format and store this file in the anHTTP server complying with the same origin policy. For browser securityreasons, this policy permits to access information only on server using thesame protocol, hostname and port number as the one to which you areconnected. Optionally, if you want to store your customized feed on anexternal server, you must configure an HTTP reverse proxy servermapping the external server address.

    Note: To specify multiple feeds, you must specify multiple NewsFeedproperties.

    NewsFeedCategoryThe name of the customized information. It can be used to identifyinformational, warning or alert messages, for example. The path to animage can also be added to better identify the information with an icon.

    To add more category images, specify a list of properties namedNewsFeedCategory, for example:

    If no customized feed is specified, the default feed is used, which retrieves thelatest product information from official support sites. To disable any notification,comment the entire section. To disable only external notifications about productinformation updates, assign an empty string as value to the FeedURL property ofJSONP feed like:

    Example:

    ..

    34 IBM Workload Automation: Dynamic Workload Console Users Guide

  • ..

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.Related tasks:Customizing the list of notification recipients on page 27How to customize the list of recipients of the news notification beacon, byspecifying who must receive what kind of notification or communication.Disabling news notification on page 27How to enable and disable news notification preventing the beacon fromappearing on your screen when an update for the product is made available.Sending internal communications on page 28How to use the news feed beacon to transmit internal communications to all orsome Dynamic Workload Console users.

    Disable and customize the creation of predefined tasksThis section defines the environment for which predefined tasks are created.

    precannedTaskCreationSome predefined tasks are created by default and are available when youlog in to the console. There is a predefined Monitor task for every object,for both z/OS and distributed engines. Default value is all. To change thissetting, use one of the following values:

    all All predefined tasks are created. This is the default.

    distributedOnly predefined tasks for distributed engines are created

    zos Only predefined tasks for z/OS engines are created

    none No predefined task is created.

    ..

    ..

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.

    Add customized URL to job and job streamsThis section contains URLs where you can store customized documentation aboutyour jobs or job streams. By default, this setting is not specified. If you want toassociate customized documentation to a job or job stream, use this setting tospecify the external address where this information is located.

    Chapter 7. Customizing your console 35

  • If you want to specify a URL where customized documentation for a job and jobstream is stored, uncomment the section lines, specify the required URL, andoptionally assign a name to the UI label by specifying a value for thecustomActionLabel property. By default this name is Open Documentation. Thislabel is then displayed in the More Actions menus in Monitor Jobs and MonitorJob Streams tasks, as well as in the graphical views of the plan (in the object'stooltips, context menus and properties). In this example, selecting OpenDocumentation accesses the relevant documentation making it possible to openthe documentation while monitoring your job or job stream in the plan.

    To implement this setting, assign values to the following keywords:

    customActionLabelThe name of the action displayed in menus, object properties, and tooltipsto access customized documentation about your jobs or job streams. Bydefault this name is "Open Documentation" unless you customize the namewith this keyword.

    jobUrlTemplateThe address of your job documentation. No default value available.

    jobstreamUrlTemplateThe address of your job stream documentation. No default value available.

    ..

    ..

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.

    These properties must be valid URLs, containing one or more of the variableslisted in the table below.

    If you use any of the following special characters in the URL, you must write themas follows:

    Table 3. Syntax for special characters

    Special characters Write them as...

    quote (") \"

    apostrophe (') '

    ampersand (&) &

    less than () &gt

    backslash (\) \\

    36 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Multiple variables can be included in a URL and must be specified using thefollowing syntax: ${variable}:

    Table 4. Variables used in the URL definition

    Name Object Description

    job_number_w Job z/OS The number of the job

    job_wkst_w Job The name of the workstationon which the job runs

    job_jsname_w Job The name of the job streamthat contains the job

    job_jswkst_w Job The name of the workstationon which the job stream runs

    job_actualarrival_w Job z/OS The actual start time of thejob (date format:YYYY-MM-DDThh:mm:ss)

    job_actualend_w Job z/OS When the job actuallycompleted (date format:YYYY-MM-DDThh:mm:ss)

    job_starttime_w Job The start time of the job(date format:YYYY-MM-DDThh:mm:ss)

    job_id_w Job The ID of the job

    job_returncode_w Job The return code of the job

    js_name_w Job stream The name of the job streamthat contains the job

    js_wkst_w Job stream The name of the workstationon which the job stream runs

    js_id_w Job stream The job stream ID

    js_latest_start_w Job stream The latest time at which ajob stream can start (dateformat: YYYY-MM-DDThh:mm:ss)

    engine_name_w Engine The name of the engineconnection

    engine_host_w Engine The hostname of the engineconnection

    engine_port_w Engine The port number of theengine connection

    engine_plan_w Engine The ID of selected plan

    engine_serv_w Engine The remote server name ofthe engine connection

    User registryUse this section to configure some properties related to the User Registry in use.

    groupIdMapThe property is related to the groups of User Registry, and can be modifiedto map and display the specified value of each group. The default is thecommon name of the group.

    Examples:

    Chapter 7. Customizing your console 37

  • ..

    ..

    Therefore, if you need to change the default value "cn" to "racfid", you can definethis property as follows:

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.

    z/OS http connectionsUse this section to configure the timeout to read and write information on IBMWorkload Scheduler for z/OS engine. When you connect to the IBM WorkloadScheduler for z/OS engine to retrieve a list of defined objects, you receive an errormessage if the list is not returned within the timeout period. The value isexpressed in milliseconds.

    Example:

    ..

    ..

    See TdwcGlobalSettings.xml sample on page 43 to view the complete syntax forthe file.

    Limit the number of objects retrieved by queriesIf you are connected to engines V9.1 this setting is ignored.

    Use this section to configure: the number of results displayed for Monitor tasks,the maximum number of rows to display on each page, and the number of directqueries to maintain in history.

    If you want to limit the number of results produced by your queries, you canspecify the maximum number of items that must be retrieved using themonitorMaxObjectsPM property. The minimum number of retrieved results is 500.

    The default value is -1; any value lower than 0 means that there is no limit in thenumber of objects retrieved.

    38 IBM Workload Automation: Dynamic Workload Console Users Guide

  • Because data is extracted in blocks of 250 rows, the value you enter is adjusted tocomplete an entire block. For example, if you specify a limit of 500, only 500elements are retrieved, while if you specify a limit of 600, 750 elements areretrieved.