BMC’s Control-M product is leveraged to provide transparent management of workflows across UTD applications and compute resources. The creation of batch job scheduling and monitoring across IT environments makes it easy to build and monitory workflows end-to-end. Control-M integrates with many enterprise applications and can use exposed APIs (e.g. Peoplesoft, Hadoop, Amazon) to ensure no gaps of visibility for each workflow. Control-M provides extensive file transfer feature including SFTP, FTPS, encryption, decryption, S3, and PGP along with dropping and retrieving files with external vendors.

The Control-M application that delivers the Workflow Automation Service is monitored 24×7 throughout the year. Support staff responds to any issues or job failures. The job owner/requestor identifies the type of notification per job desired along with directives to the OIT Production Support staff.

Some examples of Control-M jobs currently being managed include PeopleSoft Queries, PeopleSoft Jobs, PeopleSoft Processes, PeopleSoft SQRs, internal file transfers (any combination of Linux, Windows and file system sources, Linux, Windows and file system targets), external file transfers (file system targets/sources, encryption, decryption, secure tunnels, firewall allows, PGP, S3, SFTP), Operating System jobs (Windows and Linux), custom scripts as needed to provide specialized functionality.

Control-M provides a very flexible platform for job scheduling. Jobs can be triggered on regular schedules such as once a day, every hour, once a week, quarterly, skipped for UTD holidays, when a file exists and just about any other schedule as needed.

A sample workflow example to be managed by Control-M is:

  • External vendor provides a file to be picked up
  • This file is sent to PeopleSoft for processing
  • A PeopleSoft process is run to import the vendor data
  • A PeopleSoft Query is executed that includes the processed vendor data
  • The file created by the Query is then transferred to a UTD department for validation
  • The validated file is then transferred back to the vendor

Throughout this workflow, all interested parties can be notified of the status. If one of the steps in Control-M fails, automated resolution is evaluated and if manual intervention required, key individuals are automatically alerted to correct the issue. Documentation guides the impacted areas for criticality, resolution steps and contact information.

Request Workflows – New or Updates

To request a new workflow or modification to an existing workflow managed through Control-M, create an OIT Prod Support JIRA ticket in the OITPRDSUPP project.

Information to include in the request:

  • Due date of the workflow delivery
  • Purpose of the workflow
  • Applications and systems that will be part of the workflow
  • Contact for the request

Forms for the type of jobs to be included in the workflow will be provided after the request is reviewed by the OIT Production Support team.

OIT Prod Support JIRA

For more information about Workflow Automation, contact [email protected].