Migrating tenant data holding large databases

To achieve a predictable migration time and smaller tenant backup files, exclude all ARIS databases from the tenant backupthe tenant backup. Thus, you can start the database migration separately.

Prerequisites

Warning

Do not store backup files in ARIS document storage.

Tenant data is fully backed up only if the user executing the commands has sufficient privileges for all components in every tenant and if all components were selected for the backup.

User administration audit events are not part of the tenant backup.

Extensions, for example, TLS/SSL certificates, SAP® Java Connector, and JDBC drivers, added using the enhance ACC command are not backed up.

To avoid data inconsistencies and possible data loss, you must not perform any of the following activities in parallel, neither manually nor scheduled:

- Deleting any Process Governance process instance, process version, or process

- Archiving Process Governance process instances

- Backup/restore tenant (containing Process Governance or ARIS document storage data)

Procedure

  1. In each of your ARIS 9 tenants, check the system user's functional privileges. If not revoked by an administrator, the system user has all required privileges by default:

    • Analysis administrator

    • Collaboration administrator

    • Document administrator

    • Database administrator

    • License administrator

    • Process Governance administrator

    • Server administrator

    • Technical configuration administrator

      Only use the system user account to start the tenant backup with.

  2. Rename the ARIS 9 United Motor Group example database to avoid name conflicts witch the ARIS 10 example database.

  3. Start ARIS Cloud Controller (ACC) on the ARIS 9 system.

    To start ACC under a Windows operating system click Start > All Programs > ARIS > Administration > Start ARIS Cloud Controller. If you have changed agent user credentials you must enter the password.

    To start ACC under a Linux operating system, execute the acc.sh shell script instead. ACC is available if you have copied and installed the aris-acc-<number> deb or rpm file depending on the Linux operating system.

  4. Enter help or help <command> to get information about the usage of the commands.

  5. Exclude the ABS runnable from being backed up. If you back-up data from ARIS, enter:

    set acc config backup.restore.tenant.app.types = UMC, ADS, ECP, OCT, APG

    or:

    set acc config backup.restore.tenant.app.types = UMC, ADS,OCT, APG

    These commands exclude all databases from the backup. All data from the listed runnables will be saved.

  6. Reconfigure load balancer ports (recommended step). This will prevent users to log on. User access is rejected due to changed ports.

  7. Make sure that no Process Governance processes are running when starting the backup.

  8. Back-up all tenants after another, except the master tenant. Enter these ACC commands:

    list tenants

    All tenants to be backed-up are listed.

    backup tenant <tenant name> to <pathToBackUpFile> username=<user name of a user holding the required privileges> password=<this user's password>

    such as:

    backup tenant default to “D:\\backupARIS9\\default.zip" username=system password=manager

    backup tenant custom1 to “D:\\backupARIS9\\custom1.zip" username=system password=manager

    Notice the double backslashes. Alternatively, use a single forward slash (/).

    The backup is started. Each backup is written to one single archive file.

  9. Check the archive files when completed. You can open the archive, for example, with WinZip® or 7zip. Make sure that there are subfolders for each runnable, containing all relevant data. Depending on your ARIS server license, there must be 5 subfolders or only 4 subfolders.

  10. Migrate the tenant data by starting ACC on the ARIS 10 system. Enter:

    restore tenant <tenant name> from <pathToBackUpFile> username=<user name of a user holding the required privileges> password=<this user's password>

    such as:

    restore tenant default from “D:\\backupARIS10\\default.zip" username=system password=manager

    All additional tenants must be created before you can restore them. If you use an external database management system, make sure to have created schemes and have assigned them to those tenants (see Technical Help:ARIS server Installation - Windows or ARIS server Installation Linux). You can open or download documents and the Technical Help from the Documentation Web site. Documentation is also contained in the ARIS installation package that is available in the ARIS Download Center..

    create tenant custom1

    This command is mandatory for all additional tenants. Tenants can only be restored if they exist already. The master tenant and the default tenant are installed by default.

    restore tenant custom1 from “D:\\backupARIS10\\custom1.zip" username=system password=manager.

  11. If ARIS was customized or ARIS Publisher still is in use, after migration you must perform some additional steps. Make sure to add required extensions again.

  12. Restore the United Motor Group database from the ARIS installation package (..\Content\Databases). This will make new content available mandatory for dashboards (ARIS Aware).

  13. Restart all runnables (enter stopall and startall) and check the status (Enter List tenants).

  14. Migrate the excluded databases.

All data of the ARIS 9.8.7 backup files are now restored on the ARIS 10 Server. The default user accounts are automatically reset to their default values. The system databases are updated automatically.

If ARIS document storage is in use, timestamps must be adjusted and all migrated databases must be processed by a report.

The default user accounts are automatically reset to their default values. To prevent unauthorized access to the ARIS system, after installation or data migration, always change the default passwords of all users that are automatically created (arisservice user, guest user, system user, superuser user) on all operational tenants, as well as on the infrastructure tenant (master).

Warning

To prevent unauthorized access to the ARIS system, after installation or data migration, always change the default passwords of all users that are automatically created (arisservice user, guest user, system user, superuser user) on all operational tenants, as well as on the infrastructure tenant (master).

'system' user

The system user is created automatically. By default, the system user has all function privileges. This user can log in to Process administration Process administration, ARIS Administration, User Management, and ARIS Process Board. In ARIS Designer and ARIS Designer, this user has all access privileges for all database groups of all databases. This user only uses up a license if a license privilege is activated for this user. The default password is manager. You should change the default password to prevent unauthorized access. You can change all user data except for the user name.

Having more than one system user can avoid problems, if, for example, your single system user has forgotten his password. You can create additional system users or copy the existing system user. If your only system user was deleted accidentally, create a new one by using the superuser. The user can only be deleted individually. Enable the Generate, if not available option (Application launcher Application launcher > Administration Administration > Configuration > User management > Users >) so that the user is automatically generated again at startup with the last saved password.

'superuser'

The user superuser is created automatically. By default, this user is assigned the User management, License management, and Configuration administrator function privileges. This user can also enable this function privilege for other users. Users of the superuser type do not use up a license. They manage the system administration, but cannot use ARIS products due to license restrictions. The default password is superuser. You should change the default password to prevent unauthorized access. The password of the superuser is very important, as it is the only user who cannot be deleted. You can change all user data except for the user name. The superuser can recreate the other default users (system, arisservice, guest) if they were deleted.

'arisservice' user

The user arisservice is created automatically. By default, this user is assigned the Database administrator and Process Governance administrator function privileges. This user only uses up a license if a license privilege is activated for this user. The default password is arisservice. You should change the default password to prevent unauthorized access. You can change all user data except for the user name. The user can only be deleted individually. Enable the Generate, if not available option (Application launcher Application launcher > Administration Administration > Configuration > User management > Users >) so that the user is automatically generated again at startup with the last saved password.

'guest' user

The user guest is created automatically. By default, no function or license privileges are assigned to this user. This user serves technical purposes only. It is not for use by end users. Logging in to ARIS or other Software AG products with this user is not allowed. Further information is available in the Software AG license terms (http://softwareag.com/licenses). The user can only be deleted individually. Enable the Generate, if not available option (Application launcher Application launcher > Administration Administration > Configuration > User management > Users >) so that the user is automatically generated again at startup with the last saved password.

If you are going to use ARIS Tenant Management Tool, in ARIS 10 make sure to configure the component and create schedules again (see ARIS Tenant Management.pdf or online help).