AWS BluAge L3 Workshop. Go Live->Testing->Test Online. Getting blank screen when testing online Transactions for CC00

When encountering a blank screen while testing online transactions for CC00 in the AWS BluAge L3 Workshop, there are a few troubleshooting steps you can try:

1. Refresh your browser: Sometimes, simply refreshing the page can resolve the issue of a blank screen.

2. Check browser network requests: Use your browser's developer tools to trace the REST requests made to the back-end. This will help you understand the structure and parameters of the requests.

3. Reproduce the query outside the browser: Use a tool like curl to reproduce the same query outside of the browser environment. This can help isolate whether the issue is browser-specific or related to the back-end.

4. Update Tomcat version: Try using Tomcat 10 instead of Tomcat 9 for the carddemo-automation project. You can find Tomcat 10 in the c:\work\program directory.

5. Verify application deployment: Ensure that the application has been successfully deployed and started. You can check the BluageConsoleLog for confirmation.

6. Review security group settings: If you're accessing the application from a different VPC or region, you may need to adjust security group rules to allow traffic from your current location.

7. Check for dependency issues: Based on the error logs you've provided, there might be issues with dependency injection and bean creation, particularly related to Redis cache and database configuration. Review your application configuration files, especially application-main.yml, for any misconfigurations.

If the issue persists after trying these steps, you may want to reach out to the AWS BluAge L3 workshop support team for further assistance.

Sources
BluAge L3 Workshop (Go Live --> Testing --> Test Online) Blank Screen when testing Online Transactions CC00 | AWS re:Post
AWS BluAge L3 workshop. Go-Live->Deploy->Start application. Application fails to start. | AWS re:Post

The blank screen issue appears to be related to application configuration and bean creation errors rather than a network or infrastructure problem, since it works in the local environment but fails in the test environment. This seems to be a Spring bean creation issue related to AWS Blu Age modernised code. The error occurs because the application is unable to create the 'fileFactory' bean, which is part of the gapwalk.datasimplifier-io package.

Based on the logs showing bean creation and file configuration errors, here are a few troubleshooting steps to help resolve the blank screen issue:

1. Ensure that the fileConfigurations bean is properly defined in the parent application's configuration and necessary configuration files are correctly loaded.
2. Verify that the gapwalk.datasimplifier-io-4.2.0.jar file is present and not corrupted. Also, check if there are any version conflicts between the jar file and other dependencies.
3. Try using browser developer tools to trace the REST requests made to the backend to understand the request structure and parameters .
4. You can use curl or your preferred tool to reproduce the same query outside the browser to identify if the issue is browser-specific .
5. The error logs indicate there are issues with file configurations bean and FileFactory creation, which suggests there may be problems with the application's configuration setup .