AWS Mainframe Modernization: Updating Rocket Software Runtime on Amazon EC2

Overview

After deploying the AWS provided Rocket Software marketplace AMIs, you need to maintain both your Operating System (OS) and Rocket Software components up to date:

• Operating System Updates: You have full control to update your host OS packages for security and stability. However, some OS updates may affect the aws-license-daemon dependencies and could disrupt instance operations.

• Rocket Software Patch Updates: Patch updates for Rocket Software components are provided to ensure optimal performance, security, and compatibility. These updates are available through a secure S3 bucket aws-m2-custom-assets.

To prevent disruptions when applying either type of update, we provide:

• Automated patch updates through a secure S3 bucket
• Scripts to maintain license daemon compatibility after OS updates
• Installation tools for Rocket Software component updates

This guide will walk you through the process of applying both OS and Rocket Software updates safely and efficiently.

Updating License Daemon

Choose the appropriate script based on your Rocket Software version:

For Version 7

sudo wget https://d148y999krizvm.cloudfront.net/patch/v7/linux/patch.sh -O /var/microfocuslicensing/bin/patch.sh
sudo chmod +x /var/microfocuslicensing/bin/patch.sh
sudo /var/microfocuslicensing/bin/patch.sh

For Version 8

sudo wget https://d148y999krizvm.cloudfront.net/patch/v8/linux/patch.sh -O /var/microfocuslicensing/bin/patch.sh
sudo chmod +x /var/microfocuslicensing/bin/patch.sh
sudo /var/microfocuslicensing/bin/patch.sh

For Version 8/9 with JDK17 and Amazon Linux 2

sudo curl https://d148y999krizvm.cloudfront.net/patch/v8/linux-jdk17/patch.sh -o /var/microfocuslicensing/bin/patch.sh
sudo chmod +x /var/microfocuslicensing/bin/patch.sh
sudo /var/microfocuslicensing/bin/patch.sh

For Version 9 with JDK17 on Amazon Linux 2023

sudo curl https://d148y999krizvm.cloudfront.net/patch/v9/linux-jdk17-al2023/patch.sh -o /var/microfocuslicensing/bin/patch.sh
sudo chmod +x /var/microfocuslicensing/bin/patch.sh
sudo /var/microfocuslicensing/bin/patch.sh

For Version 10 with JDK17 on Amazon Linux 2

sudo curl https://d148y999krizvm.cloudfront.net/patch/v10/linux-jdk17-al2/patch.sh -o /opt/microfocus/licensing/bin/patch.sh
sudo chmod +x /opt/microfocus/licensing/bin/patch.sh
sudo /opt/microfocus/licensing/bin/patch.sh

For Version 10 with JDK17 on Amazon Linux 2023

sudo curl https://d148y999krizvm.cloudfront.net/patch/v10/linux-jdk17-al2023/patch.sh -o /opt/microfocus/licensing/bin/patch.sh
sudo chmod +x /opt/microfocus/licensing/bin/patch.sh
sudo /opt/microfocus/licensing/bin/patch.sh

After applying any patch, restart the MFCESD service using either of these methods:

Method 1 (Recommended):

sudo systemctl restart mfcesd.service
sudo systemctl status mfcesd.service

Method 2 (Alternative):

sudo /usr/local/bin/mfcesd.sh stop
sudo /usr/local/bin/mfcesd.sh start

To verify the service status and check for any issues:

sudo journalctl -u mfcesd.service

Accessing Product Updates

Access to the aws-m2-custom-assets S3 bucket requires allowlisting. Please contact your AWS representative to get your AWS account allowlisted for access to this bucket. Once your account is allowlisted, you'll need to attach the following IAM policy to your role:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "ListObjects",
            "Effect": "Allow",
            "Action": ["s3:ListBucket"],
            "Resource": ["arn:aws:s3:::aws-m2-custom-assets"]
        },
        {
            "Sid": "GetObjects",
            "Effect": "Allow",
            "Action": ["s3:GetObject"],
            "Resource": ["arn:aws:s3:::aws-m2-custom-assets/*"]
        }
    ]
}

Available Software Components in S3 Bucket

The aws-m2-custom-assets S3 bucket contains the following directory structure for Rocket Enterprise software:

aws-m2-custom-assets/
└── mf/
    ├── scripts/
    ├── v8/
    │   ├── enterprise-analyzer/
    │   │   ├── release-notes/
    │   │   └── windows/
    │   ├── enterprise-build-tools/
    │   │   ├── linux/
    │   │   └── windows/
    │   ├── enterprise-developer-eclipse/
    │   │   ├── release-notes/
    │   │   └── windows/
    │   ├── enterprise-developer-visual-studio/
    │   │   ├── 2017/
    │   │   ├── 2019/
    │   │   └── 2022/
    │   └── enterprise-server/
    │       ├── linux/
    │       ├── release-notes/
    │       └── windows/
    ├── v9/
    └── v10/

This structure provides access to multiple versions (v8, v9, v10 etc.) of Rocket Software Enterprise components with platform-specific installers for both Linux and Windows environments. Each version contains:

• Enterprise Analyzer: Analysis tools for mainframe applications
• Enterprise Developer: Development environments (Eclipse and Visual Studio variants)
• Enterprise Server: Runtime server components
• Release Notes: Documentation and patch information
• Installation Scripts: Automated installation utilities in the scripts directory

You can browse the available components using the AWS CLI:

# List all available versions
aws s3 ls s3://aws-m2-custom-assets/mf/

# List components for a specific version
aws s3 ls s3://aws-m2-custom-assets/mf/v9/

# List platform-specific installers
aws s3 ls s3://aws-m2-custom-assets/mf/v9/enterprise-server/linux/

Example: Downloading Updates

For example, to update Enterprise Server V9 on Linux:

List available updates in the directory:

aws s3 ls s3://aws-m2-custom-assets/mf/v9/enterprise-server/linux/

Download the required update:

aws s3 cp s3://aws-m2-custom-assets/mf/v9/enterprise-server/linux/setup_ent_server_9.0_patchupdate12_366515_amazon_x64 .

Installation Guidelines

Windows Environments

• Only one version can be installed at a time
• Consider creating a test environment before updating production
• Updates are self-installing executables
• Back up your environment before updating

Linux Environments

• Multiple versions can be installed in parallel
• Default installation paths:
  • Enterprise Server: /opt/microfocus/EnterpriseServer
  • Build Tools: /opt/microfocus/EnterpriseBuildTools
  • Enterprise Developer: /opt/microfocus/EnterpriseDeveloper

AWS Provided Installation Script

AWS provides an automated installation script that identifies the update being applied and selects the correct default installation location. The script is available at:

s3://aws-m2-custom-assets/mf/scripts/Linux_Installer

Script Usage

The basic command syntax is:

sudo ./Linux_Installer update=[update file] user=[ES userid] loc=[Custom Install location]

Parameters

Mandatory Parameter:

• update=[update file]: Specifies the name of the installation file to execute

Optional Parameters:

• user=[ES userid]: Specifies the Linux user ID for ES processes (defaults to "ec2-user" if not specified)
• loc=[Custom Install Location]: Specifies custom installation path (if not specified, uses default folder for the product)

Example Usage for Different Products

Enterprise Server:

sudo ./Linux_Installer update=setup_ent_server_n_n_patchupdatenn_nnnnn_amazon_x64

Enterprise BuildTools:

sudo ./Linux_Installer update=setup_entdev_server_n_n_patchupdatenn_nnnnn_amazon_x64

Enterprise Developer for Eclipse:

sudo ./Linux_Installer update=setup_entdev_eclipse_n_n_patchupdatenn_nnnnn_amazon_x64

Manual Installation Alternative

If you prefer not to use the Linux_Installer script, you can install updates manually using these commands:

Enterprise Server:

sudo ./setup_ent_server_n_n_patchupdatenn_nnnnn_amazon_x64 -ESadminID="ec2-user" -installlocation="/opt/microfocus/EnterpriseServer"

Enterprise BuildTools:

sudo ./setup_entdev_server_n_n_patchupdatenn_nnnnn_amazon_x64 -ESadminID="ec2-user" -installlocation="/opt/microfocus/EnterpriseBuildTools"

Enterprise Developer for Eclipse:

sudo ./setup_entdev_eclipse_n_n_patchupdatenn_nnnnn_amazon_x64 -ESadminID="ec2-user" -installlocation="/opt/microfocus/EnterpriseDeveloper"

Best Practices

1. Export MFDS repository before updating
2. Back up any custom configurations
3. Apply the update using provided scripts
4. Restore customizations and MFDS repository
5. Verify functionality after update

Important Notes

• The installation script automatically detects the product update type and chooses the appropriate installation folder
• Always verify the installation location is correct for your environment
• Back up your configuration before performing any updates
• After installation, restore any customizations and the MFDS repository if necessary

For assistance with installation or configuration issues, please contact AWS Support.