Initial Author's note: There are a lot of tidbits scattered around the documentation, but I'm finding it difficult to find all the places to configure things so that manifold will run on my development desktop (where the DB get's used for lots of things, and it can't have the whole thing, and I want it to play in the user/schema I define). I'm going to collect some of the scattered bits I have found and hope that someone else who actually knows where the all the handles are can edit this and make it authoritative. Until then, UAYOR/YMMV.
Database Connection Properties
Properties are set in the xml properties file that configures manifold.
The following properties are used to create a database instance in the Quick-Start and Multiprocess examples, and thus must have database super-user abilities:
These properties are not used anywhere else; if you are using commands to initialize the database you would supply similar credentials to the DBCreate command.
Actual access to an already-created instance uses the following properties:
When the database instance is created through whatever means described above, the values in the second set of properties are what are used to initialize the user meant to access the instance.
To use PostgreSQL you will need to set the following property
If you create the database and user ahead of time and set the user as the database owner, then you can use the same user for dbsuperusername with no additional privileges.
The recommended way to create the database is to run start.jar. There is no separate script. Since start.jar requires jetty, several other properties are required:
These are not required for your final deployment if you are not running on jetty, so in that case you probably want to create a separate copy of your properties file and add them to that replacing the properties.xml in the examples directory.
Other DB Related Notes
Not sure if I've missed something in setting things up, or this is a side effect of not having created the db properly yet, but possibly there's a connection closing issue (based on this log trace). If I find that a missing/outdated jar is to blame, I'll put it here. If it's still around when I get everything else working I'll log an issue (if it doesn't already exist).