Tenant assignment

If you use a multi-node scenario, you can optimize the load balancing of your system. There are two possibilities:

By default, Process Governance follows the tenant-based strategy depicted below. If you have, for example, three nodes you can have three Process Governance runnables installed, one on each server. The number of tenants used can be higher. Let us assume you have five tenants.

When tenants first access Process Governance, they are assigned to the Process Governance instances as follows: Tenant 1 is assigned to Process Governance 1, tenant 2 to Process Governance 2 and so on.

Process Governance scaling - tenant based

To change this to the process-based strategy, proceed as follows.

You can reconfigure the scalability option of Process Governance using ARIS Cloud Controller (ACC). ACC is a command-line tool (see ARIS Cloud Controller (ACC) Command-Line Tool.pdf contained in the downloaded ARIS installation package, ARIS Download Center, or Empower) for administrating and configuring an ARIS installation. It communicates with ARIS Agents on all nodes. For details please refer to ARIS Cloud Controller (ACC) Command-Line Tool.pdf.

Procedure

  1. Start ARIS Cloud Controller (ACC).

  2. Stop the Process Governance runnables in all nodes. To do so, enter

    on all nodes stop <Process Governance instance>, for example, on all nodes stop apg_m.

  3. Enter on all nodes reconfigure<Process Governance instance> "JAVA-Dcom.idsscheer.age.node.assignment.strategy"="PROCESS_INSTANCE_BASED", for example, on all nodes reconfigure apg_m "JAVA-Dcom.idsscheer.age.node.assignment.strategy"="PROCESS_INSTANCE_BASED".

  4. Start the Process Governance runnables in all nodes. To do so, enter

    on all nodes start <Process Governance instance>, for example, on all nodes start apg_m.

You have reconfigured the scalability strategy of Process Governance.

This strategy is depicted below.

Process Governance scaling - instance based

In this scenario, one node can become overloaded, for example, if nodes stop running and the other nodes have to take over.

To switch back to the default behavior, proceed as described above but using the TENANT_BASED parameter.