7. 人見人愛的Control-M作業請求流程
7
Control-M
Managed File Transfer
Build, schedule, and manage file
transfers within in a single system via
an ecosystem-wide dashboard view
Automation API
Build workflows in JSON, and manage
them together with other applications
in a source code environment
On the Cloud
Provision, install, configure, and scale
up / down automation environments to
meet changing business needs
Self-Service
Submit and monitor jobs through an
easily-understandable interface (incl.
mobile) without interfacing with IT.
For Hadoop
Develop, schedule, manage, monitor,
and integrate Hadoop workflows
within a single, centralized system.
Workload Change Manager
Build workflows that automatically
adhere to enterprise-wide standards
Application Integrator
Extend workflow automation
solutions to any application via a
simple, web-based design tool.
Batch Impact Manager
Automatically detect delays and errors
in workflows, and extrapolate those
errors to see a system-wide impact
根據 Site Standards 定義批次排程
提供線上使用手冊
WCM is an intuitive user interface which does not require a steep learning curve.
This is one of many forward thinking innovations from BMC which is designed to include those areas which need batch scheduling so that the time to value is decreased.
Time to deployment is key to value.
The next several slides are in lieu of a demo. This presentation is intended for a technical audience and a live demo is always preferred to slides. If however, you do not have an environment or are not comfortable doing a live demo, these slides provide an alternative.
This slide builds so watch it in Slideshow mode:
The first image is of Notepad++, a very popular text editor showing jobs in json format. This is the visual of Jobs-as-Code.
Items to highlight are:
You code only what you need
The folder has a “defaults” section that applies to all the jobs, to reduce the effort even further
Flow definitions implicitly define “conditions”. If desired, they can be defined explicitly.
JSON is a de-facto standard for RESTful Web Services
The Command prompt shows the “ctm env sh” command and output. The “environment” in Automation API is a combination of a logical name, the RESTful Endpoint providing services, username and password.
You can see multiple environments in the list , with one being the default. When submitting requests, they are sent to the default environment unless another one is specified explicitly.
The next operation we perform is a build. This lets us verify the syntax of the json. The verification is performed with the “standards” of that environment.
So this is the next click where we see the Workload Change Manager site standards. Whatever that target Control-M has defined as its syntax, that’s the validation that is applied,
Next is testing. Use the “run” service to actually run jobs in a Control-M environment. The service returns a “run id”.
As we saw previously, you can define multiple environments and then run the jobs in any of those environments by adding the “-e <environment name> to the run request.
If you’re a developer or DevOps engineer, you may be working on building a CI/CD process or developing an automated test that will be included in the pipeline. You may want to submit the run request to a persistent test environment.
In any case, the run id that is returned , is used to query the status of the submission using “ctm run status <runid>.
The stats of each job is provided along with a “job id” which can then be used to get a job’s output, log, rerun the job, kill it if it’s still running, etc. Functions to demonstrate if doing a demo:
ctm run job:output::get <runid>
ctm run job:log::get <runid>
ctm run job::hold <runid>
不需額外安裝作業環境
由開發人員定義排程
提供良好的溝通介面
AAPI
可 Run SQL script,也支援 docker 、Hadoop…等應用