AWS BluAge Runtime: Backend Modernization step missing SCRIPTS

Based on the information you've provided, it seems that you're encountering an issue with the AWS Blu Age Runtime where the scripts are not being displayed as expected. This could indeed be related to missing dependencies or configuration issues. Here are a few things to consider:

1. Configuration files: The AWS Blu Age Runtime uses YAML configuration files. Make sure that your application-main.yml and application-profile.yml files are properly set up and contain the necessary configurations for scripts.

2. Additional web applications: Check if you have the required web application WAR files in the correct location. The AWS Blu Age Runtime has additional web applications in its webapps-extra folder. If you need specific functionality, you may need to move the relevant WAR file from webapps-extra to the webapps folder.

3. Groovy scripts: Ensure that any necessary Groovy scripts are placed in the correct location and follow the proper naming conventions.

4. Java version: Verify that you're using a compatible Java version. The latest versions of AWS Blu Age Runtime are tested with Java 17.

5. Spring Boot and other dependencies: Confirm that you're using compatible versions of Spring Boot and other dependencies. The latest versions use Spring Boot 3.2.4 and Spring Core 6.1.5.

6. Logging: Check your application logs for any error messages or warnings that might indicate why the scripts are not being loaded or displayed.

7. Deployment method: If you're using Amazon ECS with Fargate for deployment, ensure that your task definition and container configuration are correct.

If you've verified these points and are still experiencing issues, you may want to consult the AWS Blu Age documentation or reach out to AWS support for further assistance. They can provide more specific guidance based on your exact setup and configuration.
Sources
Set up configuration for AWS Blu Age Runtime - AWS Mainframe Modernization
AWS Blu Age runtime is now available packaged for easier ECS on Fargate deployment
AWS Blu Age release notes - AWS Mainframe Modernization

Hello, Could you check that groovy files are present in your project carddemo-service in

/carddemo-service/src/main/resources/scripts

Could you share the log of your tomcat when started?

Hello, thank you for taking the time to respond.

I confirmed the scripts are at /carddemo-service/src/main/resources/scripts

It appears the carddemo service is detaching due to missing aws.bluage.l3.workshop.servlet.ValidationFilter

2024-11-02T19:46:54.565Z ERROR 5664 --- [           main] o.apache.catalina.core.StandardContext   : One or more Filters failed to start. Full details will be found in the appropriate container log file

2024-11-02T19:46:54.566Z ERROR 5664 --- [           main] o.apache.catalina.core.StandardContext   : Context [/carddemo-service] startup failed due to previous errors
About to detach context named carddemo
Selector is null, cannot detach context. Skipping.``