[SEO Subhead]
This Guidance demonstrates how the integration of Stonebranch UAC Scheduler with AWS Mainframe Modernization can help you accelerate your mainframe modernization journey by automating batch scheduling, increasing agility, improving maintenance, and decreasing costs. It shows how to integrate Stonebranch UAC Scheduler with AWS Mainframe Modernization for job scheduling and job submission. When you migrate or modernize your mainframe applications to the AWS Cloud using AWS Mainframe Modernization, this integration enables you to schedule and manage migrated batch jobs effectively for accelerated migration and seamless coordination between different processes.
Please note: [Disclaimer]
Architecture Diagram
[Architecture diagram description]
Step 1
Stonebranch Universal Automation Center (UAC) includes two main components: Universal Controllers and Universal Agents.
Step 2
UAC Universal Controller uses the UAC database. The database can be MySQL, Microsoft SQL Server, or Oracle.
Step 3
AWS Mainframe Modernization runs the modernized mainframe application.
Step 4
UAC invokes the application management APIs of AWS Mainframe Modernization to control application state. It does so by calling the following APIs: StartApplication, StopApplication, GetApplicationStatus, and FetchLogs.
Step 5
UAC invokes the batch management APIs of AWS Mainframe Modernization to orchestrate batch jobs within the application. It does so by calling the following APIs: StartBatchJob, RerunBatchJob, CancelBatchJob, GetBatchJobStatus, and FetchLogs.
Step 6
For high availability, UAC Universal Controller and UAC Universal Agent are installed in an Amazon Elastic Compute Cloud (Amazon EC2) instance of another Availability Zone (AZ).
The UAC database uses an Amazon Aurora replica for availability on the other AZ. When one AZ goes down, Amazon Route 53 makes the UAC components of the other AZ active.
Get Started
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational Excellence
The native integration between AWS Mainframe Modernization and Amazon CloudWatch enables seamless capture and analysis of batch job logs from the Stonebranch Universal Controller. This capability facilitates proactive monitoring of the performance and health of migrated mainframe applications, enabling swift identification and resolution of issues or failures. By configuring alarms for batch job failures, you can take immediate action to address abends.
-
Security
Critical mainframe workloads are protected through the security features of AWS Mainframe Modernization. Stonebranch Universal Controller and its database reside on EC2 instances within private subnets, while AWS Identity and Access Management (IAM) policies manage user access and permissions. The IAM role helps ensure that only authorized services can invoke batch jobs, and the Stonebranch Universal Controller's role-based access controls allow for customized user experiences and limited unauthorized access to the infrastructure.
-
Reliability
The Stonebranch Universal Controller and its Universal Agent are deployed across multiple AZs to achieve high availability. Aurora, with its automatic replication and failover capabilities, helps ensure consistent and accessible batch job data, even in the event of a primary AZ outage. Route 53 routes traffic to the active Stonebranch Universal Controller components, maintaining the reliability of modernized workloads.
-
Performance Efficiency
AWS Mainframe Modernization has built-in autoscaling capabilities that optimize the performance of migrated mainframe batch jobs. CloudWatch monitors and alerts on performance deviations, enabling proactive issue resolution and helping ensure that modernized applications deliver the expected level of performance.
-
Cost Optimization
Migrating mainframe batch workloads to AWS Mainframe Modernization and the Stonebranch Universal Controller reduces the total cost of ownership (TCO). Running the scheduler on EC2 instances significantly lowers costs compared to mainframe scheduling software. AWS Mainframe Modernization optimizes costs by only charging for the resources needed, eliminating the overhead of maintaining a mainframe infrastructure.
-
Sustainability
AWS Mainframe Modernization and the Stonebranch Universal Controller running on EC2 instances contribute to a more sustainable future. Additionally, the elasticity and scalability of AWS Mainframe Modernization minimize environmental impact by optimizing resource utilization and reducing unnecessary provisioning.
Related Content
[Title]
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.