AWS Mainframe Modernization self-managed experience is no longer open to new customers. For capabilities similar to AWS Mainframe Modernization self-managed experience, explore capabilities from vendor-direct offerings and from AWS Transform. Existing customers can continue to use the service as normal. For more information, see AWS Mainframe Modernization availability change.
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.
Set up licensed dependencies in AWS Transform for mainframe Runtime on Amazon EC2
This guide describes how to set up additional licensed dependencies that you can use with AWS Transform for mainframe Runtime on Amazon EC2.
Prerequisites
Before you begin, make sure you complete the following prerequisites.
-
Complete AWS Transform for mainframe Runtime prerequisites and Onboarding AWS Transform for mainframe Runtime.
-
Make sure that you have an Amazon EC2 instance with AWS Transform for mainframe Runtime (on Amazon EC2) installed. 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.
-
Get the following dependencies from their sources.
Oracle database
Supply an Oracle database
driver
IBM MQ connection
Supply an IBM MQ
client
With this dependency version, also supply the following transitive dependencies:
-
bcprov-jdk15to18-1.76.jar
-
bcpkix-jdk15to18-1.76.jar
-
bcutil-jdk15to18-1.76.jar
RabbitMQ connection
Supply a RabbitMQ Java
clientcom.rabbitmq:amqp-client). We tested the AWS Transform for mainframe Runtime (on Amazon EC2)
functionality with version amqp-client-5.35.0.jar, but a more
recent version might be compatible.
Starting with this release, the RabbitMQ Java client is no longer included in the AWS Transform for mainframe Runtime
distribution and must be supplied as an extra dependency. This applies only to applications that
use a RabbitMQ broker (for example, queues.broker: rabbitmq or
dataqueue.queues: rabbitmq for JICS, JHDB, or data queue messaging, or the hybrid MQ
bridge). Applications that do not use RabbitMQ are unaffected. If the client is missing at
runtime, RabbitMQ features fail to initialize and the runtime logs a message instructing you to
add the JAR. For more information, see
Upgrading instructions for AWS Transform for mainframe.
DDS Printer files
Supply the Jasper reports library (https://community.jaspersoft.com/download-jaspersoft/community-edition). We tested the AWS Transform for mainframe Runtime (on Amazon EC2) functionality with jasperreports-6.16.0.jar, but a more recent version might be compatible.
With this dependency version, also supply the following transitive dependencies:
-
castor-core-1.4.1.jar
-
castor-xml-1.4.1.jar
-
commons-digester-2.1.jar
-
ecj-3.21.0.jar
-
itext-2.1.7.js8.jar
-
javax.inject-1.jar
-
jcommon-1.0.23.jar
-
jfreechart-1.0.19.jar
-
commons-beanutils-1.9.4.jar
-
commons-collections-3.2.2.jar
Installation steps
To install the dependencies, complete the following steps.
-
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.
-
Navigate to the
<your-tomcat-path>/extra/folder.cd <your-tomcat-path>/extra/ -
Copy any of the above dependencies as required at this folder.
Note
For JAC and BAC webapps with Oracle-hosted databases, ensure you include the Oracle database driver (ojdbc) in this folder.
-
Stop and start the tomcat.service by running the following commands.
systemctl stop tomcat.servicesystemctl start tomcat.service -
Check the status of the service to make sure it is running.
systemctl status tomcat.service -
Verify the logs.
