Open Documentation Menu

Notes on the update

Note

Please note that the notes are only extended by new notes with each new version.

For example, if you update from dbs | case manager version 2.0.0 Rising 4 to the latest version, you no longer need to follow the first instructions for the update to Rising 4, but you must follow all other instructions.

If you are updating from an earlier version of dbs | case manager 2.0.0 Rising to version 2.0.0 Rising 4, please note the following points:

  • An additional API key is required for d.ecs terms. However, an existing API key can also be used here if desired.

  • Please run the d.velop Software Manager first and install the infrastructure in version 2.0.

  • During the installation of dbs | case manager, d.ecs terms is installed. Please configure d.ecs terms completely. The database is configured in the same way as dbs | case manager.

    • Note: No additional JDBC driver file may be required for the database configuration. The corresponding area is then automatically missing.

    • Please then configure all configuration pages of d.ecs terms marked with an exclamation mark.

  • After installation, please go to the task type authorization page to give yourself rights to all task types.

  • Then go to the administration page and save it. All deadlines are then loaded into d.ecs terms.

If you are updating from an earlier version of dbs | case manager 2.0.0 Rising to version 2.0.0 Rising 6, please note the following points:

  • The configuration file envConf.yml is replaced by the configuration file application.properties. You find this file as a template in the directory templates\config of the installation directory. If required, create and adjust the file in the working\config directory.

  • Two new configuration areas have been introduced:

    • The extended repository configuration can no longer be accessed via the administration. You can now access these directly via d.ecs config.

    • A new Maintenance section has been introduced for changes that may take a little longer to implement. This area is displayed in d.ecs config after the update to Rising 5. As long as a warning is still displayed there, the tiles are not shown on the d.3one start page.

      • If you have previously installed Rising 1 or 2, all existing deadlines are transferred to the new application d.ecs terms via this page. You must select a language. This language is saved for each deadline and then used to send reminder messages in this language. If a term is saved by a user later during operation, this term is assigned the language of the logged on user. With the release of 3.0.0 / 2.6.0, the persons in charge for contracts/cases are additionally taken over as deadline responsible users in this step for each term without reminder users/groups.

      • If you have previously installed Rising 3 or 4, the existing deadlines in d.ecs terms are updated via this page. Among other things, all terms receive a link to the task that dbs | case manager created on the day of the term reminder. With the release of 3.0.0 / 2.6.0, the persons in charge for contracts/cases are additionally taken over as deadline responsible users in this step for each term without reminder users/groups.

If you are updating from an earlier version of dbs | case manager 2.0.0 Rising to version 2.0.0 Rising 7, please note the following points:

  • With Rising 7 it is possible to save users with a clear name in d3. This requires several manual steps which are described in detail in the Maintenance work section.

  • With Rising 7, dbs | case manager and d.ecs terms are installed via d.velop software manager. Please note:

    • Before you start the installation via d.velop software manager, stop dbs | case manager and d.ecs terms. It is best to check via the Task Manager whether the processes have really been terminated or whether Java processes are still running there via the java.exe from the directory <installation directory of d.velop software manager>\java11\bin\. Terminate them in a hard way if necessary.

    • Remove the existing d.3 process manager entries for dbs | case manager and d.ecs terms. These can be found in the file C:\Windows\dserver.ini. This is necessary as these cannot be removed automatically by the update. This is partly due to the way in which dbs | case manager was previously installed.

      • Search for the appropriate entries in the file. These can look like this or something similar:

        [Process5]
StartupInfo=0
Priority=1
Group=Case Management
Name=dbs | case manager
Command=startCM.bat
WorkDir=C:\d3\dbsCaseManager\working\
Readonly=1
Starttime=00:00:00
Stoptime=00:00:00
Starttime2=00:00:00
Stoptime2=00:00:00
Starttime3=00:00:00
Stoptime3=00:00:00
Failover=0
Delay=0
MinRunTime=0
DayMask=127

      • Change these entries to:

        [Process5]
Name=

      • Alternatively, you can also set the execution of these d.3 process manager entries to STOP.

    • Then start with the installation again.

      • When running d.velop software manager for the first time, you have the possibility to use the option Define as cluster node. This means that not all dependencies need to be installed on the system, such as d.ecs http gateway or d.ecs config.

      • New d.3 process manager entries are created automatically and the processes are started automatically.