About data model

You can find here DODS generated documentation of various data models used in default shark configuration:

Instance persistence data model - (html, pdf)

Event audit data model - (html, pdf)

Repository persistence data model - (html, pdf)

Participant map persistence data model - (html, pdf)

UserGroup persistence data model - (html, pdf)

Application map persistence data model - (html, pdf)

Id Counter data model - (html,pdf)

Database support

What Needs to be Configured in Order to Use Database Other Then HypersonicSQL

The scripts for creating tables for various databases (by using Octopus) are distributed with Shark. If you want to use different database then the one originally configured to work with Shark (HypersonicSQL database), you should do the following:

  • first you'll need to stop any Shark instance that may be running.

  • Edit the configure.properties file and set values for:

    db_loader_job

    name of the directory containing Octopus loader job, options are: db2, hsql, informix, msql, mysql, oracle, postgresql, sybase

    db_user

    username for database authentication

    db_passwd

    password for database authentication

    db_ext_dirs

    directory containing jar file(s) with JDBC driver, if you need more then one directory specified here - use ${path.separator} to concatenate them

    ${db_loader_job}_JdbcDriver

    classname of the JDBC driver you want to use

    These entries are already filled with default values.

    ${db_loader_job}_Connection_Url

    full database URL

    These entries are already filled with default values, too.

  • run the configure.[bat|sh]

Note

When loading newly created database, Octopus will complain about not being able to drop indices and tables, but theses warnings should be ignored.

At this time, sharkdb.properties file(that is placed in lib/client folder) and Shark.conf are adjusted to use selected database.