+ All Categories
Home > Documents > Reducing CONTROL-M TCO with Version 6.3

Reducing CONTROL-M TCO with Version 6.3

Date post: 03-Feb-2022
Category:
Upload: others
View: 2 times
Download: 0 times
Share this document with a friend
22
9/2/2006 Reducing CONTROL-M TCO with Version 6.3.01 August 2006
Transcript
Page 1: Reducing CONTROL-M TCO with Version 6.3

9/2/2006

Reducing CONTROL-M TCO with Version 6.3.01

August 2006

Page 2: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software2

Agenda

› Agentless Job Scheduling

› CONTROL-M Configuration Manager

Page 3: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software3

CONTROL-M Maintenance Costs

› Initial install

› On-going software updates

› Maintenance and administration

› TCO examples:

– Large Insurance Company (15,000 agents), Computers Manufactures, Large Banks…

› The need: reduce CONTROL-M TCO

Page 4: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software4

Addressing the Challenge

› Dramatically reduce the CONTROL-M TCO by significantly decreasing footprint over the IT enterprise while maintaining:

– No footprint on the application host

– Scalable solution

– Out of the box approach

• Straightforward usage

• Transparent to existing CONTROL-M end-users

• No need to change existing job definitions

• Simplify CONTROL-M topology and architecture

• First day support for new platforms

Page 5: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software5

Use Case Example

› A customer is running jobs on 2500 agents, out of which 1500 aresimple backup jobs

› Once in about 6 months the CONTROL-M administrator is required to Install a new fix pack on all agents to upgrade the environment.

› Using Agentless technology, performing such maintenance activities is not necessary

› There is no need to upgrade, uninstall or maintain the servers on which the backup jobs are executed in any way

Page 6: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software6

Solution Overview

› CONTROL-M 6.3.01 can submit jobs to Remote Hosts– Modern O/S platforms provides the technologies to run O/S jobs without installing

software on the target machine or leaving footprints

– SSH (Secure Remote Shell)

– WMI (Windows Management Instrumentation)

› The job submission method (using regular agent or agentless technology) is operated by CONTROL-M/Server

› CONTROL-M/Agent 6.3.01 execute the job on the remote host

› Requires CONTROL-M/EM 6.3.01.100 (Fix-Pack 1)

Page 7: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software7

Installation Simplicity

› “Agent-less” implementation requires no CONTROL-M/Agent installations on the remote hosts

– A single CONTROL-M/Agent is required to access remote hosts

– CONTROL-M/Server installation bundles CONTROL-M/Agent installation

– Elapsed time until first job execution drastically reduced

– Simplify the solution for small/medium workload

› CONTROL-M/Agent installation is still available on a separate CD

– Can be implemented as a regular standard agent

– Can be used to balance the remote execution workload

Page 8: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software8

Agentless Architecture

CONTROL-M/EM CONTROL-M/Server

WINUNIXLinux

CM for Remote ExecCONTROL-M/Agent

UNIX

CONTROL-M/AgentRemote Execution Interface

Page 9: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software9

Submitting Jobs To Remote Hosts

› Job submission to remote hosts is transparent to end-users

› The remote host name is set in the NODEID field on the job definition

› CONTROL-M/Server maps the remote hosts and monitors their availability (as done for CONTROL-M/Agent)

› Remote host administration is set on the Configuration Manager GUI

Page 10: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software10

Agentless Architecture Benefits

Significantly reduces CONTROL-M TCO

› Decreasing the amount of CONTROL-M/Agents

– Remote execution technology allows zero footprint

› Substantial improvement in CONTROL-M deployment

– Day one support for new platforms

› Dramatically reduce on-going maintenance effort

– Fix Packs, Patches, etc..

› Simplified administration

– Centralized management using Configuration Manager

Page 11: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software11

Central Management - The Need

› Different management tools for different components

– CONTROL-M/EM: Using the Administration Facility

– CONTROL-M/Server (DS and z/OS), Agent & CM’s: Local abilities only

› Full picture of the enterprise is not available

› Example: Setting the CONTROL-M/EM port in CONTROL-M/Server

– Login to server Enter “ctm_menu” Select the “Parameter Customization” option Select the “Basic Communication and Operational Parameters” option

Page 12: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software12

Addressing The Challenge

› CONTROL-M Configuration Manager

– Central management capabilities to the CONTROL-M administrator

– Enhanced management tools allow controlling the entire CONTROL-M environment from a single focal point

• CONTROL-M/EM

• Batch Impact Manager & Forecast Server

• CONTROL-M/Server, CONTROL-M/Agents and remote hosts

• CONTROL-M/CM’s

– Reduced TCO through faster implementation & deployment of CONTROL-M

– Improved problem detection and analysis

Page 13: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software13

Automatic Components Definition

› When starting the CONTROL-M Configuration Manager at the first time, it realizes there no CONTROL-M/EM server components defined and suggest to automatically define them

› Gateways are automatically defined with CONTROL-M/Servers

Page 14: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software14

Components View

› By Component / By Computer

Page 15: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software15

CONTROL-M/Server Definition

› A singleCONTROL-M/Server definition serves all CONTROL-M/EM components

– No need for multiple CONTROL-M/Server definitions

– CONTROL-M details are retrieved fromCONTROL-M/Server

Page 16: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software16

CONTROL-M for z/OS

› One Configuration Agent is installed for the entire SYSPLEX

› Monitor and manage the following components:

– IOAGATE

– CONTROL-M Application Server

– CONTROL-M Global Monitor

– CONTROL-M Local Monitor

– CMEM Monitor CONTROL-O Monitor

› All CCM management activates can be blocked from the MF side

Page 17: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software17

CONTROL-M/Server Security

› CTM/Server security graphical management interface(Graphical “ctmsec”)

Page 18: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software18

CONTROL-M/Server Debug

› Set a debug level for each of the CONTROL-M/Server processes

Page 19: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software19

CONTROL-M/Agent Properties

› CCM users can modify the communication properties ofCONTROL-M/Agents or add new CONTROL-M/Agents to the topology

Ping Agent

Page 20: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software20

Configuration Manager Benefits

› Enhanced management tools allow controlling the CONTROL-M environment from a focal point

› Reduced TCO through faster implementation & deployment of CONTROL-M

› Provide faster problem detection and analysis

Page 21: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software21

Reducing TCO with CONTROL-M 6.3.01

› Agentless Technology

– Decreasing the amount of CONTROL-M/Agents

– Dramatically reduce on-going maintenance effort

– Simplified administration

› CONTROL-M Configuration Manager

– Enhanced management tools allow controlling the CONTROL-M environment from a focal point

– Provide faster problem detection and analysis

Page 22: Reducing CONTROL-M TCO with Version 6.3

9/2/2006 ©2006 BMC Software22

Questions?


Recommended