Blu Age L3 Workshop Cannot Upload Datasets in BAC

The issue you're experiencing with uploading datasets in the Blu Age L3 Workshop is likely related to how the JSON files are being processed or interpreted by the Blusam Administration Console.

Here are a few suggestions to troubleshoot and potentially resolve the issue:

1. Double-check file format: Even though you've verified the JSON files, ensure they are properly formatted and begin with a curly brace '{'. The error suggests the system is expecting an object but receiving a string.

2. Use server option: Try using the server option instead of the local option when loading datasets to Bluesam. This has resolved similar issues for other workshop participants.

3. Clear cache: There might be a caching issue causing incorrect data to be loaded. Try clearing your browser cache or using a different browser.

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

5. Synchronize configurations: Run the Publish action on the Tomcat server to synchronize everything between the Eclipse WST working folder and the Tomcat configuration folder.

6. Check file permissions: Ensure the application has the necessary access rights to open and read the files you're trying to upload.

If these steps don't resolve the issue, you may need to review the workshop documentation for any specific instructions related to dataset uploading, or reach out to the workshop support for further assistance. The error you're seeing is not common, and it may require more in-depth investigation of your specific setup.
Sources
AWS BluAge L3 Workshop : bac.war causing issues in loading KSDS files to postgres | AWS re:Post
BluAge - L3 Workshop - org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL | AWS re:Post