In addition: is there a specific set of privileges that the user a client uses to connect to the JBPM database is running as must have?
I can see that I can have hibernate create the objects in the schema automatically - fine. I can then reverse engineer the database structure into DDL. Fine.
The database user you would need to run as in order for hibernate to create the table structure would require the access to create tables and other objects in the specified schema... ie: probably the schema owner. Most security minded folk wouldn't be comfortable running a client application to be connecting to the database as that user, however. Presumably the runtime user could simply have read and write access to the tables instead? Any advice?