AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
AWS Blu Age Cannot Load DataSet (PS files) in Bluesam administration console
After setting up my tomcat server, launching the Blusam Administration Console and creating datasets from listcat, I'am trying to load dataset(PS Files), but the file informations are not recognized :
"Unreadable bytes"
- Newest
- Most votes
- Most comments
The issue you're experiencing with loading datasets (PS files) in the Bluesam Administration Console is likely related to how the files are being processed or interpreted. Here are a few suggestions to troubleshoot and potentially resolve the issue:
-
File encoding: Ensure that the PS files are properly encoded. The system may be having trouble reading the file due to encoding issues. Try setting the file encoding explicitly to UTF-8 in your workflow configuration.
-
Use server option: Instead of using the local upload option, try using the server option to load the datasets into Bluesam. This approach has resolved similar issues for other users.
-
Clear cache: There might be a caching issue causing incorrect data to be loaded. Try clearing your browser cache or using a different browser to access the Bluesam Administration Console.
-
Verify file format: Double-check that the PS files are in the correct format expected by Bluesam. Ensure they begin with the appropriate headers or structures.
-
Check file permissions: Make sure the application has the necessary access rights to open and read the files you're trying to upload.
-
Synchronize configurations: Run the Publish action on the Tomcat server to synchronize everything between the Eclipse WST working folder and the Tomcat configuration folder.
-
Verify datasource configurations: Ensure all required datasources (jics, bluesam, bac, primary) are correctly configured in your Tomcat configuration files (context.xml and server.xml).
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 "Unreadable bytes" error suggests that the system is having trouble interpreting the file content, which could be due to various factors in the setup or configuration.
Sources
Blu Age L3 Workshop Cannot Upload Datasets in BAC | AWS re:Post
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
Relevant content
asked 2 years ago
asked 2 years ago
asked a year ago
Suggestion 2, using the server with the path to the file, worked for me.