AWS Blu Age L3 Workshop -> Execution -> Test -> Batch - No such File exception for AWS.M2.CARDDEMO.TRANSACT.BKUP.json

The issue you're experiencing with the AWS Blu Age L3 Workshop during the Execution -> Test -> Batch step is related to the GDG (Generation Data Group) file handling. The error suggests that the system is unable to locate the GDG state file, which is expected to be named "AWS.M2.CARDDEMO.TRANSACT.BKUP.json" in the current directory.

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

1. Verify that the file "AWS.M2.CARDDEMO.TRANSACT.BKUP.json" exists in the correct directory. The error message indicates it's looking for the file in the current working directory (denoted by ".").

2. Check the file permissions to ensure that the process has read access to the file.

3. Make sure that the GDG support is properly configured in your Groovy script. You may need to add or modify the GDG support configuration in your TRANBKP job. For example, ensure you have something similar to this in your Groovy script:

   .gdgSupport("FILEOUT") .name("AWS.M2.CARDDEMO.TRANSACT.BKUP").ownerPath(".").relativeGeneration(1) .storageProvider("filesystem") .recordSize(350) .disposition("NEW") .normalTermination("CATLG") .abnormalTermination("DELETE")

4. If the issue persists, you might need to check the Bluesam configuration in your application definition. Ensure that the Bluesam database configuration is correct, particularly the secret manager ARN for the database connection.

5. In some cases, clearing any cached data or temporary files and rerunning the classification step in your code base project might help resolve metadata inconsistencies.

If these steps don't resolve the issue, you may need to reach out to the AWS Blu Age support team or the workshop facilitators for more specific guidance tailored to your environment and workshop version.
Sources
AWS BluAge L3 Workshop - Execution - Test - Batch - COMBTRAN - Issue | AWS re:Post
BluAGE L3 workshop issue with Go-Live Test batches and Online | AWS re:Post

Hi,

In step 4 you have set Tomcat working directory here:

https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/execution/backend

Then it will have a reference to how to set it up.

https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/tools/eclipse/tomcat/working-directory