AWS Blu Age L3 Workshop

The issue you're experiencing with the "Create dataset from LISTCAT" option not working in the BAC (Blusam Administration Console) after restarting AppStream is a known problem in the AWS Blu Age L3 Workshop environment. This could be related to several factors:

1. Session persistence: When AppStream sessions end, some configurations may not persist, which can lead to issues with previously working features.

2. Cache problems: There might be caching issues causing incorrect data to be loaded or preventing the proper functioning of certain features.

3. Configuration synchronization: The Tomcat server configuration might not be properly synchronized after the AppStream restart.

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

1. Clear your browser cache or try using a different browser to access the BAC console.

2. Verify that all required datasources (jics, bluesam, bac, primary) are correctly configured in your Tomcat configuration files (context.xml and server.xml).

3. Run the Publish action on the Tomcat server to synchronize everything between the Eclipse WST working folder and the Tomcat configuration folder.

4. If the problem persists, try restarting the Tomcat server or even the entire AppStream fleet.

5. Double-check that you're using the correct User ID when accessing AppStream. For the Blu Age L3 Workshop, it's typically "BluAge-L3-Workshop-User".

If these steps don't resolve the issue, you may need to review the workshop documentation for any specific instructions related to dataset creation and management after AppStream restarts. If the problem continues, it would be advisable to reach out to the workshop support team for further assistance, as they can provide more specific guidance based on the workshop's setup and requirements.
Sources
AWS Blu Age L3 Workshop | AWS re:Post
AWS Blu Age Cannot Load DataSet (PS files) in Bluesam administration console | AWS re:Post