AWS Mainframe Modernization Service (Managed Runtime Environment experience) is no longer open to new customers. For capabilities similar to AWS Mainframe Modernization Service (Managed Runtime Environment experience) explore AWS Mainframe Modernization Service (Self-Managed Experience). Existing customers can continue to use the service as normal. For more information, see AWS Mainframe Modernization availability change.
Upgrade the AWS Blu Age Runtime on Amazon EC2
This guide describes how to upgrade the AWS Blu Age Runtime on Amazon EC2.
Topics
Prerequisites
Before you begin, make sure you meet the following prerequisites.
-
To check if there are specific instructions for your version, see Upgrading instructions for AWS Blu Age.
-
Complete AWS Blu Age Runtime prerequisites and Onboarding AWS Blu Age Runtime .
-
Ensure that you have an Amazon EC2 instance with an existing AWS Blu Age Runtime installation. For more information, see Get started with Amazon EC2 Linux instances.
-
Make sure you can connect to the Amazon EC2 instance successfully, for example, by using SSM.
-
Download the AWS Blu Age Runtime version you want to upgrade to. The framework consists of two archive files :
gapwalk-x.y.z.zipandaws-bluage-webapps-x.y.z.zip. For more information, see AWS Blu Age Runtime artifacts.
Upgrade the AWS Blu Age Runtime in the Amazon EC2 instance
Complete the following steps to upgrade the AWS Blu Age Runtime.
-
Connect to your Amazon EC2 instance and change the user to su by running the following command.
sudo suYou need superuser privilege to run commands in this tutorial.
-
To extract the binaries, use the following commands. Run the commands in each folder.
unzip gapwalk-x.y.z.zip unzip aws-bluage-webapps-x.y.z.zip -
Stop the Apache Tomcat services by using the following commands.
systemctl stop tomcat.service systemctl stop tomcat-webapps.service -
Replace the content of
<your-tomcat-path>/shared/with the content ofgapwalk-x.y.z/shared/. -
Replace
<your-tomcat-path>/webapps/gapwalk-application.warwithgapwalk-x.y.z/webapps/gapwalk-application.war. -
Replace the war files in
<your-tomcat-path>/webapps/, namelybac.warandjac.war, with the same files fromaws-bluage-webapps-x.y.z/velocity/webapps/. -
Start the Apache Tomcat services by running the following commands.
systemctl start tomcat.service systemctl start tomcat-webapps.service -
Check the logs.
To check the status of the deployed application, run the following commands.
curl http://localhost:8080/gapwalk-application/
The following message should appear.
Jics application is runningcurl http://localhost:8181/jac/api/services/rest/jicsservice/
The following message should appear.
Jics application is runningcurl http://localhost:8181/bac/api/services/rest/bluesamserver/serverIsUp
The response should be empty.
The AWS Blu Age runtime is successfully upgraded.
Upgrade the AWS Blu Age Runtime in a container
Complete the following steps to upgrade the AWS Blu Age Runtime.
-
Rebuild your Docker image with the desired AWS Blu Age Runtime version. For instructions, see Set up AWS Blu Age Runtime on Amazon EC2.
-
Push your Docker image to your Amazon ECR repository.
-
Stop and restart your Amazon ECS or Amazon EKS service.
-
Check the logs.
The AWS Blu Age Runtime is successfully upgraded.
