AWS Blu Age Tomcat server start : FATAL: role "bluesam" does not exist

The error you're encountering indicates that the "bluesam" role is missing in your PostgreSQL database, which is required for the AWS Blu Age Tomcat server to start properly. This issue typically occurs when the database roles haven't been set up correctly during the workshop setup process. To resolve this, you need to:

1. Check your database configuration: Ensure that the connection details in your application configuration files (such as application-main.yml) are correct.

2. Create the missing "bluesam" role: You need to create this role in your PostgreSQL database. This can be done using SQL commands or a database management tool.

3. Grant appropriate permissions: After creating the role, make sure it has the necessary permissions to access and modify the required database objects.

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

5. Run the Publish action on the Tomcat server: This will ensure that everything is synchronized between the Eclipse WST working folder and the Tomcat configuration folder.

If you've recently made changes to the Tomcat configuration, especially adding data sources, make sure you've saved all changes in the server.xml file in Eclipse. It's easy to overlook saving these changes, particularly if an AppStream session times out before saving.

If the problem persists after trying these steps, you may need to review the workshop documentation for any specific instructions related to database setup, or reach out to the workshop facilitators for more tailored assistance.
Sources
Tomcat start up problem in L3 workshop | AWS re:Post
BluAge - L3 Workshop - org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL | AWS re:Post
Tomcat isn't starting in AWS Blu Age L3 Workshop | AWS re:Post

Is bluesam role supposed to be configured in PostgreSQL? I noticed that only carddemo & postgres roles are suggested during roles setup.

I manually created bluesam role but now it errors out as bluesam database is missing.

First exception during start is:

java.io.FileNotFoundException: C:\Work\AWS-BluAge\Runtime-Timebomb\webapps\bac.war (The system cannot find the file specified):

It has only 1 WAR file. No bac.war

Figured out that the WARs are now spread across different folders instead of webapps folder as per demo solution settings.