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
PAC Scale-Out Repository (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:
- In the menu bar, click
NATIVE.
- In the navigation pane, click
.
- Click
+ADD.
This opens the
SCALE-OUT REPOSITORY CONFIGURATION dialog box.
- In the
Name field, type the name of your
PSOR. For example, type
MyPSOR.
- In the
Type field, select
Redis.
- Optionally, in the
Description field, type a description for your PSOR.
- 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 or Cluster, you can specify the connection details for multiple nodes. Click
+ to add an additional node name and port number.
- Click
SAVE.
Important: Only one PSOR can be associated with a given PAC. A PSOR can be specified with multiple Redis Sentinel or Cluster connections.
This configuration can help support high availability. You can specify multiple connections in the
Connection Path(s) field.
Configuring a PAC
You now need to specify a PAC:
- In the menu bar, click
NATIVE.
- In the navigation pane, click
.
- Click
*NEW.
- In the
Name field, type the name of your PAC. For example, type
MyPAC.
Note: The PAC Name is limited to no more than 8 characters long.
- Optionally, in the
Description field, type a description for your PAC.
- The
PAC SOR field lists all the available SORs that could be used. Click
MyPSOR, which you configured in the steps above.
- 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:
- In the menu bar, click
NATIVE.
- In the navigation pane, click
.
- Click
Edit in the row containing the PAC you want to edit.
- Click
*NEW next to the
SOR MODELS heading.
This opens the
SCALE-OUT REPOSITORY CONFIGURATION dialog box.
- In the
Resource field, select the resource type you want to store in the SOR.
- 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 +.
- In the
SOR field, select the name of the SOR you want to associate the model with.
- 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:
- In the menu bar, click
NATIVE.
- In the navigation pane, click
.
- In the navigation pane, click on the name of the PAC you want to add enterprise server instances to.
- Click
INSTALL.
This opens the
Install PAC Definition to Regions dialog box.
- In the left pane, click the directory server that hosts the enterprise server instance you want to add.
Note: Micro Focus recommends a minimum of three regions to a PAC and that each region should be located on Directory Servers hosted on separate
hardware. This will help reduce single points of failure.
- In the right pane, check the enterprise server instances you want to add to your PAC.
- 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.