Open Documentation Menu

Installation and configuration

In this topic you will find information about the installation of dbs | case manager.

Preparation

Warning

Before starting the installation, make sure that the System requirements are met!

If you execute an update of dbs | case manager then the configuration of the previous installation must be finished! A hotfix/update is always deployed as full-setup and can also be used for a reinstallation without installing other versions before.

Creating a new database

Please set up a new database in your respective database management system (DBMS). Create your own user for access to the database. This user must have the rights to create, read, update and remove the database contents and must also be able to carry out all database configuration and maintenance activities.

As the deadlines from dbs | case manager have been outsourced to a separate application, you have the option of creating an additional database in the same way and thus separating the data pools. However, you can also use the same database for both.

If you are using a Microsoft SQL Server, see the Creating a new Microsoft SQL Server database section in the Best Practice Setup and Configuration section for instructions on creating a new database with a user.

Please note the following points for the respective database management systems:

Note

If you are using an Oracle database, make sure that the database user also has the right to create new sequences.

When using an MS SQL database, the "dbo" schema is used as standard. We recommend naming the scheme in the same way.

Please note the following points:

Note

Please create the database for dbs | case manager contract in the same DBMS where the databases of d.3 core components are located.

Under circumstances you have to adjust the configuration for using unicode. The database of d.3 components and that of dbs | case manager should be configured in the same way. A mixed operation is not allowed.

Note

Make sure that the user accessing the database does not have umlauts in the password. Umlauts in the password of the database user are currently not supported.

Setup

You install the software exclusively with d.velop software manager. If an application is required for different products, the corresponding software packages are also installed automatically.

For further information on installing the software, see the d.velop software manager manual.

Note

Please stop the processes of dbs | case manager and d.ecs terms in d.3 process manager in advance. When updating a previous Rising version <=6, new processes may be created for dbs | case manager and d.ecs terms. If changes have been made to the start parameters, these must be adopted.

Starting dbs | case manager

An entry is automatically created in d.3 process manager as part of the installation. You can start and stop dbs | case manager from here.

With Rising 3, the deadlines were outsourced to a separate application, which is delivered as part of the dbs | case manager setup. You must also start this. An entry for this is also automatically created in d.3 process manager during the installation of dbs | case manager.

Setting up the hooks

The Groovy Hooks were placed in the installation directory after the installation was completed. The path in which these hook files are stored must be specified in d.3 admin. Please make sure that Java/Groovy support has been activated. Further information on the hooks supplied can be found in the Hook chapter. Further information on the integration of Groovy Hooks can be found in the d.3 admin documentation.

Note

Note that the file dbsCase_contract_functions.ini is generated in the configuration step Repository configuration, in addition to the Groovy Hook files.

For each update installation, the hook files must be replaced with those in the installation directory. Please note any project-specific adjustments.

If you only use dbs | case manager and not dbs | case manager contract, do not copy the files dbsCaseContractHooks.groovy, dbsCaseContractHooks_prefixGen.groovy and dbsCaseContractHooks.classpath.

Configuring SSL with a self-signed certificate

For the hooks of the dbs | case manager to work via SSL with a self-signed certificate of the gateway app, the certificate of the gateway app must be added to the Windows certificate store. This can be done manually or rolled out automatically per domain. We recommend delivery by domain.

Warning

To ensure that the d.3 server also trusts these certificates, an adjustment must be made in d.3 config in d.3 admin. To do this, switch to edit mode in d.3 admin and open System settings | d.3 config.

Expand the Java/Groovy item from the logical groups and click on the JVM Options area.

Set or add the following entry to the current value (if not already present):

-Djavax.net.ssl.trustStoreType=Windows-ROOT
Update

Warning

If you update dbs | case manager, the configuration of a previous installation must be completed. A hotfix/update is always deployed as full-setup and can also be used for a reinstallation without installing other versions before.

An update is carried out in the same way as the initial Installation.