Installing and Configuring Job Scheduling Services (JSS) 1.2 & TWS Distributed Connector 8.1 for use with the Job Scheduling Console, v. 1.2 or 1.3

2 Welcome This presentation is based on the Tivoli Workload Scheduler (TWS) Job Scheduling Console User’s Guide, Version 8.1 The presentation will cover Creating Framework Administrator Collections and assigning necessary rights Backing up the Tivoli Management Region (TMR) Server databases Installing JSS v.1.2* Installing the 8.1 TWS Distributed Connector* Applying patches to the connector* Modifying the Security File for use with the JSC* * information presented in this document can also be used to install the 1.2 JSS and 8.2 TWS Connector with the TWS 8.2 Engine

3 Objectives After completing this presentation, you should be able to do the following:  Perform a backup of your TMR Server  Install Job Scheduling Services 1.2  Install and patch the TWS Connector 8.1  Create Framework Administrator Collections for TWS users  Modify your Security File for TMR Collections  Successfully Start the JSC up and begin using it in your environment

4 Overview  The installation of JSS and connector are relatively new configuration steps for the TWS product and began with TWS 7.0 and are continued in TWS 8.1 & 8.2  The JSC uses Tivoli Management Framework (TMF), the JSS and connector to communicate with the TWS Master Domain Manager (MDM), or other TWS systems the customer wishes to monitor  The JSS is a unified interface in the TMF to different job scheduling engines.  The connector is the JAVA component that allows the JSS to “talk” with a scheduling engine. The Job Scheduling Console communicates with the scheduling engine via the Job Scheduling Services and the connector. A connector can only be installed on a computer where the Tivoli Management Framework and Job Scheduling Services have already been installed.

5 JSC, Connector and JSS Matrix These are the supported configurations for the 1.2 JSC: TWS 8.2 TWS 8.1 JSS 1.2 Connector 8.1 Connector 8.2 It is possible to upgrade the 7.0 Connector and 1.1 JSS when migrating to TWS 8.1

6 Creating User Collections in the TMR  All JSC users must be members of a Framework Administrators Collection  To use the JSC the collection requires a minimum TMR role of “user”. Additional abilities, like stopping connectors, require additional permissions  Multiple users can be included within the same collection  Collection membership should be based on “like roles” within the TWS environment

7 Creating an Administrator Collection  Start the Tivoli desktop, by  Sourcing the environment for Framework “. /etc/Tivoli/setup_env.sh”  Ensure the display is exported and type “tivoli” at the command line  After the desktop starts, double click the “Administrators” Icon

8 Creating an Administrator Collection #2 From here, select “Create” and “Administrator”

9 Creating an Administrator Collection #3 Select a name/label Add a user name to act as an administrator If desired, a group name Add users here Edit roles here

10 Creating an Administrator Collection #4 Add user names to the collection as desired; you must hit “return” to save the Login Name. When finished, select “Change & Close”

11 Creating an Administrator Collection #5 Either select “TMR Roles” from the Create Administrator dialog, or right-click, the collection Icon, and select “Edit TMR Roles” Select “user” from the “Available Roles” and click the arrow to add it to “Current Roles” Then select “Change & Close”

12 Questions about creating an Administrator?

13 Backing up the TMR Server  Now that the Administrator Collection has been created, it is time to backup the TMR Server’s databases before installing the JSS and Connector From the “Desktop” menu, select “Backup”

14 Backing up the TMR Server #2 Highlight the TMR, on the “Available managed nodes” pane, move it to the other side and select “Start Backup”

15 Backing up the TMR Server #3 Once the backup is complete, the JSS and connector can be installed

16 Questions about backing up the TMR?

17 Installing the JSS From the Framework desktop, Select “Desktop”, “Install”, “Install Product” Note: When mounting the 1.2 JSC cd provided with TWS 8.1 on HP-UX systems, use the following syntax: mount -o cdcase /cdrom, or mount -F cdfs -o cdcase /dev/dsk/c#t#d# /mount_cdrom

18 Installing the JSS #2 Mount the JSC 1.2 CD and path to it and select the “contents.lst file” The 1.2 JSS and 8.1 TWS Connector are located in the 1.2 JSC CD in the connector/TWS/TWS_CONN directory The 1.2 JSS and 8.2 TWS Connector are located in the IBM Tivoli Workload Scheduler Disk 1 of 2 TWS_CONN directory

19 Installing the JSS #3 Highlight the JSS entry and and select the system to install on Then select Install & Close Always monitor the messages generated by the install process and look for error messages.

20 Questions about installing the JSS?

21 Installing the Connector Installing the Connector is very similar to installing JSS with one difference… Creating an instance Always monitor the messages generated by the install process and look for error messages.

22 Installing the Connector #2  What is an instance?  An instance is a pointer into the Framework database which provides the connector with three important pieces of information – Host name – A “label” to identify the instance. This can be any name you select – Path to the …/ directory to allow the JSC to find the Symphony file and TWS databases*  An instance is necessary to connect the JSC to a TWS system  The instance label will be displayed in the JSC to identify each TWS system that has an instance created  * For TMR Servers running on Windows platforms, the syntax of this is c:/win32app/maestro (use the “/” for POSIX)

23 Questions about installing the connector?

24 Installing Connector Patches  The process for installing connector patches is very similar to installing the base JSS or Connector  The distributed connector patches are co-located with the TWS engine patches in the CONNECTOR subdirectory on the IBM patch website located at: ftp://ftp.software.ibm.com/software/tivoli_support/patches/  TWS 8.1 engine patches are located in patches_8.1  TWS 8.2 engine patches are located in patches_8.2  JSC 1.2 patches are located in patches_1.2  JSC 1.3 patches are located in patches_1.3  The connector patches located in the patches_1.2 and 1.3 directories are for TWS for z/OS use only!

25 Installing Connector Patches #2  The current 8.1 TWS Connector patch directory ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_ 8.1/8.1-TWS-FP08/CONNECTOR/ ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_ 8.1/8.1-TWS-FP08/CONNECTOR/  contains one file:  The connector patch – U1_TWS.image.TAR  Download and untar/unzip the patch so you can path to it  Issue a stop command on the connector to make sure all JSC processes are down before applying the patch. You must be sourced for Framework to run the command: “wmaeutil ALL –stop”

26 Installing Connector Patches #3 From the Framework desktop, Select “Desktop”, “Install”, “Install Patch”

27 Installing Connector Patches #4 Path to the un-tarred connector patch

28 Installing Connector Patches #5 And install the connector patch by selecting the client, verifying the label of the patch, and selecting “Install & Close” Always monitor the messages generated by the install process and look for error messages.

29 Questions about connector patches?

30 Modifying the Security File  Following installation of the connector patch, the next step is to modify the TWS Security file by using “dumpsec” and “makesec” to add the Framework Administrator Collections created earlier.  The collection names are handled exactly like a userid within TWS  By enabling TWS auditing, it is possible to determine which member of a collection made a specific change within the plan or database  The connector must be stopped anytime changes are made to the TWS Security file for those changes to be recognized  The $Framework variable is used to require an id to login via the JSC and only useful with a user and collection of the same name

31 Modifying the Security File #2 This is a sample Security file which includes Framework collection entries

32 Questions about the Security File?

33 Additional Commands These are some additional commands that can be used to gather information and perform service on the connector and TMF wtwsconn.sh -create -h (node) -n (instance name) -t (TWS Directory) - This will create an instance wtwsconn.sh -view -n (instance name) - This will show the path to the maestro home directory wtwsconn.sh -remove -n (instance name) - This will remove an existing instance wtwsconn.sh -set -n (instance name) -t (TWS Directory) wmaeutil (connector instance name) -stop "*" - This will stop a specific connector instance wmaeutil ALL -stop (this will stop all connector instances) wlsinst -ah - This will list the products and patches installed on the TMR. wlookup -ar MaestroEngine - This will display the connector instance name and oid

34 Conclusion Today, we have discussed: Creating Framework Administrator Collections and assigning necessary rights Backing up the Tivoli Management Region (TMR) Server databases Installing JSS v.1.2 Installing the 8.1 and 8.2 TWS Connector Applying patches to the connector Modifying the Security File for use with the JSC