Maintaining Tivoli Workload Scheduler Agents With IBM Endpoint Manager

1y ago
5 Views
1 Downloads
548.36 KB
11 Pages
Last View : 28d ago
Last Download : 3m ago
Upload by : Melina Bettis
Transcription

Maintaining Tivoli Workload Scheduler Agents with IBM Endpoint Manager Mark Delaney mark.delaney@systemsmanaged.com

Typical Scenarios Many different versions of TWS agents and patch levels in your estate New TWS agents are being added all of the time End of support for a TWS version requires you to audit and upgrade to meet compliance Maintenance slots are difficult to predict as an agent could be running work at any time TWS versions go out of support every 12 months root/administrator access required for patch or upgrade of TWS agents is often difficult to obtain Transfer of TWS software to agents can be problematic

Why Upgrade Your TWS Agents? Reduce Incident Tickets Stay in support Get access to new features Protect Your TWS Network

The Goals A proven, default TWS agent version and patch level deployed across all servers in the estate New TWS agents being added must adhere to the default level Upgrades of TWS agents must not affect running workloads Reduce the manual effort required to upgrade TWS agents as much as possible Remove any manual tasks and administrative overhead (pulling root password etc.) Utilise network bandwidth effectively observing company firewall restrictions

How IBM Endpoint Manager Can Help One-click, on-demand upgrades or patches of TWS agents Scheduled upgrade or patch of agents based on maintenance window, hostname, subnet, group membership, etc. Easily configure static or dynamic groups of agents as targets Upgrade, patch or rollback to FTAs, DAs, or z/OS Agents Perform multiple actions in one click using a baseline (e.g. upgrade TWS 8.3 - TWS 8.6 - TWS 9.1 - TWS 9.1 FP1) New TWS agents can be upgraded to meet the baseline automatically Intelligently upgrades around an agent’s workload (e.g. “You’re busy running jobs, I’ll come back later”) IEM agent takes care of the upgrade. No manual logging into agent is required

TWS Agent Upgrade Paths Upgrade to TWS 8.6 8.3 FP7 8.4 Upgrade to TWS 9.1 8.5 8.5.1 8.6 Upgrade to 8.6 Upgrade to 9.1 IBM Endpoint Manager upgrades Designated agents 8.3 and 8.4 agents to are upgraded to 9.1 8.6 GA GA by IBM Endpoint Manager Apply 9.1 FP1 The latest fix-pack can be applied automatically

How The Upgrade Process Works Run An Action Apply Baseline Deploy the IBM Endpoint Manager agent to the TWS servers using remote deploy or a manual installation IBM Endpoint Manager analyses run continually on IEM agents to evaluate TWS version and patch levels on all known servers Run an action to manually upgrade or patch agents to a required version or level Alternatively, schedule the upgrades based on date/time, maintenance window, location, hostname, subnet, group membership, and so on Or, designate a baseline that a subset of agents must be at using a powerful set of criteria and IBM Endpoint Manager will take care of the rest

Using IBM Endpoint Manager Relays

IBM Endpoint Manager Solution Key Points Reduce the overhead of upgrading an agent to minutes rather than hours Utilise IBM Endpoint Manager relays to reduce the amount of traffic and throttle bandwidth when transferring files Schedule unattended upgrades around the business Web-based reporting to show what was upgraded and when Covers all versions of TWS from v 8.3 and above Handles Fault Tolerant Agents, Dynamic Agents and z/OS agents for upgrades, patching or rollbacks IBM Endpoint Manager incorporates IBM Licence Metric Tool – required for Sub-Capacity Licencing

For further information, or to discuss a demonstration, contact Mark Delaney. Email: mark.delaney@systemsmanaged.com Website: http://www.systemsmanaged.com Follow me on Twitter: @SYSMANAGED

TWS Agent Upgrade Paths Upgrade to 8.6 IBM Endpoint Manager upgrades 8.3 and 8.4 agents to 8.6 GA Upgrade to 9.1 Designated agents are upgraded to 9.1 GA by IBM Endpoint Manager Apply 9.1 FP1 The latest fix-pack can be applied automatically

Related Documents:

monitoring tasks for inexperienced users of IBM Tivoli Workload Scheduler for z/OS. Your workload can run on various platforms, but you control it from a central z/OS system that runs IBM Tivoli Workload Scheduler for z/OS controller. Readers should know how t

Tivoli Security Operations Manager Products include: Tivoli Composite Application Manager Tivoli Config Mgr Tivoli Decision Support for z/OS 9Tivoli Monitoring 9IBM Director Tivoli Ent Console Tivoli NetView Tivoli OMEGAMON 9Tivoli Provisioning Manager Tivoli Remote Cnt

viii Implementing IBM Tivoli Workload Scheduler V 8.2 Extended Agent for IBM Tivoli Storage Manager defense industry as a software developer on military weapon systems design projects. Carl Buehler is an IBM Certified IT Specialist working in IBM Software Services for Tivoli (ISST). He joined IBM in 1987 and has been a software developer,

Decision Support for z/OS IBM Tivoli System Automation & IBM Tivoli Workload Automation IBM Tivoli Netview for z/OS, OMEGAMON, IBM Tivoli Composite Application Manager, DFSMS IBM Tivoli Identify Manager, IBM Tivoli Access Manage

To this end, Tivoli went to work on redesigning the GUI and unveiled the new interface product with the release of Version 7 of what was now the Tivoli Workload Scheduler (TWS). The product of their development effort is the java-based Job Scheduling Console (JSC). An unanticipated issue arose immediately: Customer

CA Workload Automation Agent for Windows (CA WA Agent for Windows) CA Workload Automation Agent for z/OS (CA WA Agent for z/OS) CA Workload Automation CA 7 Edition (formerly named CA Workload Automation SE) CA Workload Automation ESP Edition (formerly named CA Workload Automation EE) CA Workload Control Center (CA WCC) Contact CA Technologies

Tivoli Workload Scheduler network is made up of the workstations where job and job stream processing occurs. When you design your network, you assign roles to these workstations to suit your specific business requirements. You can design your network with multiple domains, to divide control of a large network into smaller manageable groups. A .

editing jobs created on Windows .119 Chapter 8. Troubleshooting dynamic workload scheduling .121 How to tune the rate of job processing .121 Troubleshooting common problems .123 Dynamic workload broker cannot run after the Tivoli Workload Scheduler database is stopped . 123 Getting an OutofMemory exception when