The system database holds content available for all databases of a tenant, such as the ARIS method (all model, object, connection, and symbol types), filters, templates, macros, reports, semantic checks, and similar content.
In a new ARIS installation, the system database only contains predefined ARIS content provided by Software AG. ARIS users can customize the system database and add new content, for example, by defining custom method extensions, writing reports, or adding other content to the system database.
Each tenant in your ARIS installation has a different system database. Therefore, each ARIS tenant can have a specific set of ARIS method elements, a special set of reports, or other content that is not shared by the tenants.
As the default content of the system database shipped together with ARIS is updated as part of a new ARIS version, the new version of the system database is applied to an existing installation during an update. It only updates filters, default reports and macros, and templates shipped with the standard product. Default semantic checks will no longer be updated except of the following: Allocation rules, Model attribute rules, Object attribute rules, Relationship attribute rules, Existence rules, and Rules for a BPMN diagram (BPMN 2.0). For these six rule types, the code is updated. The configuration of the rules stays untouched. User-defined modifications made in the configuration will not be overwritten. You can import the latest semantic checks from the ARIS installation package (<ARIS installation package>/ARIS_Installation_and_Documentation-<patch>\Content\Reports\Common_files and../Semantic Checks). Usually, you have your own filters and templates and do not need updates for those that came with the standard product.
If you have an issue with any of the default reports, macros or scripts, or default Mini workflows, or you ran a patch setup, you can update the system database. In this case, it might also make sense to create a test tenant and only execute this command for this tenant. Then you can export individual report scripts or other content and distribute the required content to other tenants.
Run the updatesystemdb ACC command for all operational tenants one after another starting with the default tenant. Do not execute this command for the master tenant. Enter, for example:
invoke updatesystemdb on <abs_instance ID> tenant.name=default \ tenant.user.name=superuser tenant.user.pwd="<superuser password in default>"
invoke updatesystemdb on <abs_instance ID> tenant.name=<tenant1> \ tenant.user.name=superuser tenant.user.pwd="<superuser password in tenant1>"
invoke updatesystemdb on <abs_instance ID> tenant.name=<tenant2> \ tenant.user.name=superuser tenant.user.pwd="<superuser password in tenant2>"
If you use multiple nodes, you must prefix the invoke command with on <node name>. Alternatively, use set current node to switch to those nodes with abs runnables.
If you have more than one abs instance in your installation, you only need to update the system database once per tenant on each instance.
If you do not update the system database for all tenants, the system still works but the latest updates and fixes for SAG default reports, semantic checks, macros, etc. will not be available.