L3 Automation Execute Error deploying gapwalk /Error opnening connection TRANBKP

The errors you're encountering during the L3 Automation Execute step are likely related to compatibility issues with Tomcat 10 and the gapwalk application. Here are some potential causes and solutions:

1. Tomcat version incompatibility: Tomcat 10 uses Jakarta EE instead of Java EE, which can cause deployment issues for applications not updated for this change. The gapwalk and bac applications may not be compatible with Tomcat 10.

2. Application deployment failure: The errors suggest that both the gapwalk-application and bac are failing to deploy properly, which is preventing the TRANBKP script from being accessible.

To resolve these issues, try the following:

1. Downgrade Tomcat: Use Tomcat 9 instead of Tomcat 10. The automation project may be designed to work with an earlier version of Tomcat.

2. Update application code: If you must use Tomcat 10, you'll need to update the gapwalk and bac applications to be compatible with Jakarta EE. This involves changing import statements from javax.servlet to jakarta.servlet and making other necessary adjustments.

3. Check configuration: Ensure that all datasources are correctly configured for jics, bluesam, bac, and primary databases. Verify that the database server is started and running correctly.

4. Review Tomcat logs: Check the Tomcat logs (catalina.out or similar) for more detailed error messages that might provide additional insights into the deployment failures.

5. Verify file paths: Make sure the file paths in your project are correct and that Tomcat has the necessary permissions to access these files.

If these steps don't resolve the issue, you may need to reach out to the Blu Age support team or workshop facilitators for more specific guidance tailored to your environment and workshop version.

Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
L3-Automation-Execute-Online test cases error(tomcat server shutting down after batch test) | AWS re:Post