Configuring PACs and SORs

You can configure a number of enterprise server instances to act as a Performance and Availability Cluster (PAC). See Scale-Out Performance and Availability Clusters for more information. The PAC acts as a single logical entity that supports scale-out growth.

Configuring a PSOR for use with a PAC

Firstly you need to specify a PSOR which will store the system and configuration data that will be shared between all the enterprise server instances that are part of the PAC:

  1. In the menu bar, click NATIVE.
  2. In the navigation pane, click Groups > PACs > SORs.
  3. Click +ADD.

    This opens the SCALE-OUT REPOSITORY CONFIGURATION dialog box.

  4. In the Name field, type the name of your PSOR. For example, type MyPSOR.
  5. In the Type field, select Redis.
  6. Optionally, in the Description field, type a description for your PSOR.
  7. In the Connection Path(s) field, type the host name and port number to connect to, in the form host:port. For example, if you are running Redis locally on the default port, type localhost:6379.
    Note: If you are using Redis Sentinel, you can specify the connection details for multiple Sentinels. Each connection must be delimited by a comma. For example:
    host1:5000,host1:5001,host2:5000
  8. Click SAVE.
Important: Only one PSOR can be associated with a given PAC. A PSOR can be specified with multiple Redis Sentinel connections. This configuration can help support high availability. You can specify multiple connections in the Connection Path(s) field, each delimited by a comma.

Configuring a PAC

You now need to specify a PAC:

  1. In the menu bar, click NATIVE.
  2. In the navigation pane, click Groups > PACs.
  3. Click *NEW.
  4. In the Name field, type the name of your PAC. For example, type MyPAC.
  5. Optionally, in the Description field, type a description for your PAC.
  6. The PAC SOR field lists all the available SORs that could be used. Click MyPSOR, which you configured in the steps above.
  7. Click SAVE.

You have now specified a PAC and its PSOR and you can now add regions to the PAC.

Sending TSQs and TDQs to a SOR

You can optionally send TSQs and TDQs to a PSOR that has already been specified or you can create a new SOR to store this information:

  1. In the menu bar, click NATIVE.
  2. In the navigation pane, click Groups > PACs.
  3. Click Edit in the row containing the PAC you want to edit.
  4. Click *NEW next to the SOR MODELS heading.

    This opens the SCALE-OUT REPOSITORY CONFIGURATION dialog box.

  5. In the Resource field, select the resource type you want to store in the SOR.
  6. In the Prefix field, type a prefix that will match the instances that you want to be stored in the SOR. You can use the following wildcard characters:
    • * Matches any string of characters.
    • + Matches any one character.
    Note: This field will have the remaining characters padded with the + wildcard. For example, if you type T for a TD Queue resource, then the remaining characters will be padded with the +.
  7. In the SOR field, select the name of the SOR you want to associate the model with.
  8. Click SAVE to save the model in the SOR MODELS list.

Adding an enterprise server instance to a PAC

To add an enterprise server instance to your PAC:

  1. In the menu bar, click NATIVE.
  2. In the navigation pane, click Groups > PACs.
  3. Click on the name of the PAC you want to add enterprise server instances to.
  4. Click INSTALL.

    This opens the Install PAC Definition to Regions dialog box.

  5. In the left pane, click the directory server that hosts the enterprise server instance you want to add.
  6. In the right pane, click the enterprise server instances you want to add to your PAC.
  7. Click ADD.

    This adds the enterprise server instances to the PAC field in the General Properties for the region.

Once you have added an enterprise server instance to a PAC you will be able to see its scale-out configuration information under its region's GENERAL PROPERTIES.

Note: If the configuration of a PAC changes, including the configuration of any of its SORs or SOR Models, then you will need to reinstall the PAC to ensure that all enterprise server instances within that PAC are synchronized.