![]()
BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation
Table of Contents
BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Support files, eBooks, discount offers and more
Why Subscribe?
Free Access for Packt account holders
Instant Updates on New Packt Books
Preface
What this book covers
Who this book is for
Conventions
Reader feedback
Customer support
Errata
Piracy
Questions
1. Get to Know the Concept
Introduce batch processing
The history of batch processing
Batch processing versus interactive processing
Time-based batch- and event-driven batch
Is this the end for batch processing?
Running batch processing tasks
Automating batch processing
Basic elements of a job
What to trigger
When to trigger (Job's scheduling criteria)
Dependencies (Job's predecessors and dependents)
More advanced features of scheduling tools
Ability to generate notifications for specified events
Ability to handle an external event-driven batch
Intelligent scheduling โ decision-making based on predefined conditions
Security features
Additional reporting, auditing, and history tracking features
Centralized enterprise scheduling
Challenges in today's batch processing
Processing time
Batch window length
Batch monitoring and management
Cross-time zone scheduling
Resource utilization
Maintenance and troubleshooting
Reporting
Reacting to changes
The solution
Processing time and resource utilization
Batch monitoring and management
Cross-time zone scheduling
Maintenance and troubleshooting
Reporting
Reacting to changes
From batch scheduling to workload automation
Batch scheduling: Static scheduling
The Workload Automation concept
Dynamic batch processing with virtualization technology and Cloud computing
Integration with real-time system, workload reusability
Summary
2. Exploring Control-M
Control-M overview
Control-M road map
Key features
Supported platforms
The Control-M way
Control-M job
Job conditions
Resources
Submitting jobs
Post processing
From the user's perspective - Control-M/Enterprise Manager
Control-M Enterprise Manager GUI Client
Control-M Desktop
Control-M Configuration Manager
Reporting Facility
Control-M's Optional Features
Control-M Control Modules
Control-M/Forecast and BMC Batch Impact Manager
Control-M/Forecast
BMC Batch Impact Manager
BMC Batch Discovery
Control-M Architecture and Components
Control-M/Enterprise Manager
Control-M/Enterprise Manager Server Components
Naming Service
Control-M Configuration Server
Control-M/Enterprise Manager Configuration Agent
GUI Server
Gateway process (GTW)
Global Alert Server (GAS)
Global Condition Server (GCS)
Control-M Web Server
Control-M/Server
Control-M/Server processes
SU: Supervisor
SL: Job Selector
TR: Job Tracker
NS: Agent Communication Process
CE: New Day and EM Communication Process
CS: Server Process
LG: Logger Process
WD: Watchdog Process
RT: Internal Communication Router
CA: Configuration Agent
Control-M/Agent
AG: Agent Listener, Request Handler
AT: Agent Tracker
AR: Agent Router Process
UT: Utility Process
Agentless Technology
Control-M/Control Modules
How do Organizations Work With Control-M?
Where to Start?
General Product information
Official Education and Certification
Getting a Job in Control-M
Summary
3. Building the Control-M Infrastructure
Three ages to workload automation
Stone age
Iron age
Golden age
Planning the Batch environment
Control-M sizing consideration
Total number of batch jobs run per day
Total number of job execution hosts
Number of datacenters
Amount of concurrent GUI users
Use Control-M/Agent or go Agentless
Production, development, and testing
Control-M high availability requirements
Control-M in a clustered environment
Control-M/Server mirroring and failover
Control-M/Server database mirroring
Control-M/Server failover
Control-M node group
High availability by virtualization technology
Pre-installation technical considerations
Environment compatibility
Choices of database
System configuration requirements
Linux Kernel parameters
Shared memory
Semaphores
User limits
Other requirements
Storage space related considerations for Control-M
Firewall requirements
Between Control-M/Enterprise Manager Clients and Server Components
Between Control-M/Enterprise Manager Server Components and Control-M/Server
Between Control-M/Server and Control-M/Agent
Agentless remote hosts
Database
Last things to make sure of before the installation starts
Installation
Install Control-M/Enterprise manager server components
Download and execute the check_req script
Create a Linux user and allocate space for Control-M/EM
Configuring the system to meet installation requirements
Preparing the installation media
Installation
Post-installation tasks
Install Control-M/Enterprise manager clients
Preparing the installation media
Installation
Post-installation tasks
Installing Control-M/Server
Installation in Linux environment
Pre-installation
Installation
Post-installation tasks
Installation in a Windows environment
Pre-installation tasks
Installation
Post-installation tasks
Installing Control-M/Agent
Installation in Linux environment
Pre-installation tasks
Installation
Post-installation tasks
Installation in a Windows environment
Summary
4. Creating and Managing Batch Flows with Control-M GUI
The Control-M way โ continued
Contents of a job definition
"What" #1: job type
"What" #2: task type
"Who" #1 โ owner of the job
"Who" #2 โ author of the job
"Where" #1 โ job's execution host
"Where" #2 โ storing job definitions
Datacenter/Table/Job
Application/Group/Job
"When" #1 โ job's scheduling date
Defining a job's scheduling date
Calendars
Rule-Based Calendar (RBC)
Retro job
"When" #2 โ time frame for job s...