bac.war is not present in the C:\Work\AWS-BluAge\Runtime-Timebomb\shared

Question

Dear Team,

I am currently working on the AWS Blu Age practicals for the Data Migration module using version 4.2.0. However, I have encountered a few discrepancies:

The training videos provided are based on version 3.2.0, and there are notable differences in the process.
In the AppStream 2.0 environment, the shared Blu Age image does not contain the bac.pom  file in the expected path(C:\Work\AWS-BluAge\Runtime-Timebomb\shared) , nor does it generate the bac.jar file as shown in the training videos and deployment getting failed

Alae · Answer

Hello,

In version 4.2.0 the bac.war is located in C:\Work\AWS-BluAge\Runtime-Timebomb\webapps-consoles

regards

re:Post Agent · Answer

Thank you for bringing this to our attention. It appears that there have been some changes between the version used in the training videos (3.2.0) and the version you're currently working with (4.2.0). This can indeed lead to discrepancies in the process and file locations.

Regarding the BAC (Blu Age Connect) component:

In more recent versions of AWS Blu Age Runtime, the BAC is typically distributed as a web application archive (.war) file rather than as separate .pom and .jar files. This .war file is usually intended to be deployed alongside the BluAge Gapwalk-Application in an Apache Tomcat application server.

The absence of bac.pom and bac.jar in the path you mentioned (C:\Work\AWS-BluAge\Runtime-Timebomb\shared) is likely due to this change in distribution format.

For the current version, you should look for a bac.war file instead. This file might be located in a different directory, possibly in a 'webapps' or 'webapps-extra' folder within the AWS Blu Age Runtime installation.

If you cannot find the bac.war file, it's possible that it needs to be deployed separately or may require additional configuration steps in the newer version.

To resolve the deployment failure:

1. Check for the presence of bac.war in other directories within the AWS Blu Age Runtime installation.
2. If found, you may need to move it to the appropriate 'webapps' folder for deployment.
3. Ensure that the necessary configuration file (application-bac.yml) is present and properly set up.
4. Review the latest documentation for AWS Blu Age Runtime 4.2.0 for any changes in the deployment process or required configurations.

If the issue persists, I recommend reaching out to AWS support or the AWS Blu Age team for the most up-to-date guidance on deploying the BAC component in version 4.2.0.

**Sources**  
[Deploying the BAC - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/userguide/bac-deployment.html)  
[Set up configuration for AWS Blu Age Runtime - AWS Mainframe Modernization](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-config.html)

bac.war is not present in the C:\Work\AWS-BluAge\Runtime-Timebomb\shared

Relevant content