AWS Blu Age - Can´t get http://localhost:8080/gapwalk-application/script/TRANBKP to D:\PhotonUser\Workshop\workspace\carddemo-automation\TRANBKP.log

The issue you're experiencing with the AWS Blu Age L3 Workshop automation step is likely related to compatibility problems between the Tomcat version and the application.

The error suggests that the automation project is using an older version of Tomcat (9.0.x), which is not compatible with the current application. This is because newer versions of Tomcat (10.0.x and above) use different Java packages (jakarta.servlet instead of javax.servlet).

To resolve this issue, you should try the following steps:

1. Locate the Tomcat installation in the c:\work\programs\tomcat directory.
2. Replace the Tomcat version in the automation project with the one from c:\work\programs\tomcat.
3. After making this change, try running the execute.xml script again.

This should allow the gapwalk-application to start correctly. If you're unable to downgrade Tomcat to version 9, you may need to update the application code to be compatible with Tomcat 10.x, which would involve changing the servlet imports from javax to jakarta.

If the problem persists, you should also verify that:

1. All required datasources (jics, bluesam, bac, primary) are correctly configured.
2. The database server is started and running properly.

If you continue to face issues, you may need to reach out to AWS support or consult the Blu Age documentation for more specific troubleshooting steps related to your environment setup.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
AWS BluAge L3 Workshop - IMPORT to Eclipse - Archive for required library not resolved | AWS re:Post

Hello,

Based on the error the issue you're experiencing is likely related to compatibility problems between the Tomcat version and the application.

✑ The error suggests that the automation project is using an older version of Tomcat (9.0.x), which is not compatible with the current application. This is because newer versions of Tomcat (10.0.x and above) use different Java packages (jakarta.servlet instead of javax.servlet).

To resolve this issue, you should try the following steps:

• Locate the Tomcat installation in the c:\work\programs\tomcat directory.
• Replace the Tomcat version in the automation project with the one from c:\work\programs\tomcat.
• After making this change, try running the execute.xml script again.

✑ This should allow the gapwalk-application to start correctly. If you're unable to downgrade Tomcat to version 9, you may need to update the application code to be compatible with Tomcat 10.x, which would involve changing the servlet imports from javax to jakarta.

✏︎ If the problem persists, you should also verify that:

1. All required datasources (jics, bluesam, bac, primary) are correctly configured.
2. The database server is started and running properly.

If you continue experiencing issues, feel free to open a case with AWS Premium Support.