In Development - All

Re-Architect Control-M

Control-M has been ASU’s production Workload Management tool for many years. It was originally architected when the mainframe was ASU’s primary production platform with Unix starting to take on more significance in the production environment. With the evolution of ASU’s PeopleSoft environment to the point where it is now the primary production platform, and the Windows environment hosting more applications, the growth in the number of processes managed by Control-M has increased significantly. As a result of this growth and the addition of new platforms to manage, we need to re-architect to meet future growth and satisfy Auditor requirements outlined in the current Audit project.

This project will occur in 4 phases, each addressing a specific area as outlined below:

·         Clean up our old Control-M environment

·         Upgrade Control-M to Version 6.4

·         Implement Control-M Disaster Recovery

·         Build a Control-M test environment     

Restructure old Control-M environment  Business requirement

Several Control-M components and related scripts are running on very old servers that the Systems team would like to discard. One of the servers has already failed once, causing a 12 hour production batch processing outage. 

 Goal:

We need to move all processes off ECSX and PROD1X onto more stable severs prior to building the new Control-M environment.  We will also Purge old records  from the database.

 Control-M upgrade to V6.4  Business requirement:

The number of processes managed by Control-M continues to increase. As this workload grows, the business impact of any Control-M failure or outage also grows. Control-M V6.4 gives us greater auditing capabilities, better security, and additional capabilities to help us better manage the production batch environment.

Goal:

·         Better auditing of activities within the Control-M environment

·         Enhanced management capabilities such as mass changes to all fields within Control-M schedule definitions

·         Enhanced support for Agent-less workload management

Disaster Recovery for Control-M Business requirement:

Control-M is ASU’s Enterprise Workload Scheduler. It is responsible for the timely execution, monitoring, and management of our Production batch processing and file transfers. We currently process 1,700+ processes through Control-M per day and that workload level continues to increase. Over the years, a significant knowledge base has built into the system regarding process timings, dependencies, resource requirements, and failure recovery procedures.

Should Control-M fail, and be unavailable for anytime period of time, the Scheduling team would need to manually initiate all processes, satisfy all process dependencies, manage all resources, and manually inspect all processes to determine its success or failure status once completed. Control-M is a mission critical application that must be available at all times.

 Goal:

Our objective is to re-architect the Control-M environment to eliminate any single point of failure of critical Control-M components and provide for automated failover to backup servers.  Control-M must also be able to manage processing in both the PeopleSoft and Advantage Disaster Recovery sites to ensure business continuity should either need to be brought online.

Test environment for Control-M Business requirement:

We currently have no isolated way to test development process flows prior to production migrations. Control-M upgrades are also more cumbersome than necessary since we don’t have an isolated environment to fully test patches and upgrades.

Goal:

Our objectives for this test environment are to:

·         Provide an environment where Control-M upgrades and patches can be fully tested before we apply them to the production Control-M environment.

·         Provide an environment, isolated from the production Control-M environment, which can be used by developers to run new process flows prior to their migration to production.

The Super Report provides access to financial data related to awards and grants. The purpose of this project is to provide quicker access to the report for individuals designated as 'principal investigators'.