The WorkZone database

Data and files in WorkZone are currently stored in Oracle databases. WorkZone supports for its on-premises and private cloud hosting:

  • Oracle Standard Edition (SE)

  • Oracle Enterprise Edition (EE)

  • Oracle Autonomous Database (ADB)

Oracle platforms

WorkZone can be hosted on different Oracle platforms, such as Oracle SE, Oracle EE, and Oracle ADB. The Oracle platform to select depends on your organization's requirements.

Oracle on-premises

Running Oracle on-premises you have two different options.

  • Oracle SE: Standard Edition is suitable for many workloads, but on-premises it will lack features, such as Oracle Transparent Data Encryption (TDE). The license is based on number of physical CPUs (Max 2 CPUs).
  • Oracle EE: Enterprise Edition scales to higher workloads and includes more enterprise options from Oracle. Add the following options depending on your compliance needs:
    • Oracle TDE: If your compliance needs require encryption at rest, add Oracle Transparent Data Encryption (TDE).
    • Data Guard: If your compliance needs require auditing or disaster recovery in terms of hot or cold standby, add Oracle Data Guard (ODG).

You can use either your own license or an Oracle Applications Specific Full Use license that is delivered as part of the WorkZone license. The license is based on number of cores.

Oracle Cloud Infrastructure (OCI)

If you run Oracle in cloud, you can use Oracle OCI public or regulated clouds, for example, Oracle Sovereign Cloud, that ensures compliance with local compliance requirements, such as EU GDPR. Oracle Cloud offerings are easier to manage and scale, and they include more options than the on-premises editions.

  • Oracle ADB is the managed cloud version of Oracle that allows dynamic scalability.
  • Oracle SE (DB System) is the cloud version of Oracle SE. The major difference is that it includes features, such as Oracle TDE and that it is possible to change the CPU usage.
  • Oracle EE (DB System)is the cloud version of Oracle EE. The major difference is that it includes features, such as Oracle TDE and that it is possible to change the CPU usage. Add the following options depending on your compliance needs:
    • Data Guard: If your compliance needs require auditing or disaster recovery in terms of hot or cold standby, add Oracle Data Guard (ODG).

The licenses in Oracle Cloud are consumption-based, which can be beneficial in many WorkZone workloads.

WorkZone schemas and roles

SJSYSADM

SJSYSADM is the owner of all objects in a WorkZone database, except for the objects that are owned by SJ_ARKIV. SJSYSADM is the schema (database user) that installs and upgrades the database.

SJ_ARKIV

SJ_ARKIV is the owner of all objects that make up the archive. The archive is where the documents that relate to cases are saved.

In addition to the SJSYSADM and SJ_ARKIV users, there are other Oracle users that are used for different purposes, for example SJWEBSIK9USER1 that is used for all connections to the website.

All users except for the SJSYSADM users have their password set by an algorithm. The password will be changed automatically if one or more passwords is about to expire. All passwords for these users are 30 characters long including upper and lower case letters, digits, and special characters.

Character sets in the WorkZone database

Oracle uses UTF8. The overhead using UTF8 is about 20%, because some characters are represented by up to 4 bytes.

Database structure

In the WorkZone database there are two owners. The schema SJSYSADM is the owner of all WorkZone objects and the schema SJ_ARKIV is the owner of the document archive.

SJSYSADM owns approximately:

  • 730 tables

  • 200 views

  • 110 packages

  • 250 triggers

  • 1660 indexes

SJ_ARKIV owns:

  • 3 tables

  • 1 package

  • 3 indexes

When a WorkZone database is installed or upgraded, the following happens:

  1. An exe program loads all sources (object definitions) into a table named wz_source.

  2. All installations and upgrades are performed by packages in the database.

  3. The exe program starts creating the Workzone_dbinitial package that does some initial installation/upgrading including creating/alter all tables.

  4. The exe program creates the Workzone_dbinstall package that does the rest of the installation/upgrading and finally the exe program creates the Workzone_dbfinal package that finishes and checks the installation.