The workflow management system JobRouter saves all application data in the underlying database. Depending on the use case, this can be Microsoft SQL Server, MySQL respectively MariaDB, Oracle DB or IBM DB2.
The stored data can be basically divided into three essential areas:
•First, all organization data, e.g. users, Job Functions or process owners are stored in the database.
•In addition, all defined process models are also stored in the database.
•Finally, all instance related data, e.g. process data or the start and completion time of the individual process steps are also stored in the database.
JobRouter offers the JobRouter Web Service as first choice for working with organization data. With it, you are able to read, write and delete users, Job Functions, etc. In addition, you have direct access to the respective tables. The chapter Storing of organization data describes briefly the essential tables and their links.
The database structure of the stored process models is not mentioned in this manual, as this structure is constantly changing and a reading and writing of process model data would be pointless and might lead to errors.
Reading out instance data for the purpose of evaluation is a main topic of this manual. You can find a description of tables containing instance data and how they are logically linked in the chapter Instance data.
Please note that the structure of JobRouter tables might change at any time when updating to a new service pack or release. Always make sure that your queries are still working and returning correct values.
Please note: VARCHAR columns are created as NVARCHAR when installing JobRouter on a Microsoft SQL Server with Unicode support. For this reason you will find (N)VARCHAR as column value in the documentation.
Columns of the VARCHAR(MAX) type are created as CLOB on an Oracle DB and as CLOB(1G) on an IBM DB2.
All numeric column types are created as NUMBER on an Oracle DB and as INT on MySQL respectively MariaDB. This document uses INTEGER for them.
