Child pages
  • Database Configuration
Skip to end of metadata
Go to start of metadata

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.

Generic Properties

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.

PostgreSQL Config

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.

Derby Config

Database Creation

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).

  • No labels

5 Comments

  1. What I wish I could find in the docs is the location of an SQL script to run to create the database, and a property to set the name of the database, so I can install it into the database of my choice (with a name of my choosing). I'd really rather not let code I can't see loose on my db with super-user privileges. (smile)

    1. You can set the database name also via a parameter. If you create your own user with privs for table creation in the database you want it to use, then running the Initialize, Register, and RegisterConnector/RegisterAuthority/RegisterOutput commands will do the appropriate database and index creation for you.

      We in general discourage the idea that you can set up a schema through a SQL script, because individual connectors (which can be registered or deregistered) also own database tables, which they need to create and destroy accordingly.

      1. Thx for the quick reply (smile) found the property for db name, and added it above. Seems that in the future folks will likely want control over tablespaces, which partition various tables are on and things like that (I'm not a db guru, but it's due to hearing things like that from the DBA's I've come to expect/produce scripts). I'll give it a whirl with the user I defined and see what privs I need to give it (if any) and note that above.

  2. The exception you included is harmless; it's a bit amusing too because it results from the fact that Tomcat is unloading a class before it has invoked the shutdown hook for the web application (which shuts down the thread that's still running when the webapp is unloaded).

    If you create a ticket for the problem please include what version of Tomcat this is.

    1. Ah, yet another tomcat shutdown quirk... FWIW this was tomcat 7.0.23