

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](https://docs.aws.amazon.com/m2/latest/userguide/mainframe-modernization-availability-change.html).

# Set up licensed dependencies in AWS Transform for mainframe Runtime on Amazon EC2
<a name="ba-runtime-dependencies-ec2"></a>

This guide describes how to set up additional licensed dependencies that you can use with AWS Transform for mainframe Runtime on Amazon EC2.

**Topics**
+ [Prerequisites](#ba-runtime-dependencies-prereq)
+ [Installation steps](#ba-runtime-dependencies-overview)

## Prerequisites
<a name="ba-runtime-dependencies-prereq"></a>

Before you begin, make sure you complete the following prerequisites.
+ Complete [AWS Transform for mainframe Runtime prerequisites](ba-runtime-setup-prereq.md) and [Onboarding AWS Transform for mainframe Runtime](ba-runtime-setup-onboard.md).
+ 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](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html).
+ 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
<a name="ba-runtime-dependencies-prereq-oracle"></a>

Supply an [Oracle database driver](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html). We tested the AWS Transform for mainframe Runtime (on Amazon EC2) functionality with version **ojdbc11-23.3.0.23.09.jar**, but a more recent version might be compatible.

### IBM MQ connection
<a name="ba-runtime-dependencies-prereq-mq"></a>

Supply an [IBM MQ client](https://www.ibm.com/support/pages/mqc91-ibm-mq-clients). We tested the AWS Transform for mainframe Runtime (on Amazon EC2) functionality with version **com.ibm.mq.jakarta.client-9.3.4.1.jar**, but a more recent version might be compatible.

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

### DDS Printer files
<a name="ba-runtime-dependencies-prereq-dds"></a>

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
<a name="ba-runtime-dependencies-overview"></a>

To install the dependencies, complete the following steps.

1. Connect to your Amazon EC2 instance and change the user to **su** by running the following command.

   ```
   sudo su
   ```

   You need Superuser privilege to run commands in this tutorial.

1. Navigate to the `<your-tomcat-path>/extra/` folder.

   ```
   cd <your-tomcat-path>/extra/
   ```

1. 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.

1. Stop and start the tomcat.service by running the following commands.

   ```
   systemctl stop tomcat.service
   ```

   ```
   systemctl start tomcat.service
   ```

1. Check the status of the service to make sure it is running.

   ```
   systemctl status tomcat.service
   ```

1. Verify the logs.