Configuring PACs and SORs

Configuring a PSOR for use with a PAC

Firstly, you need to specify a Scale-out Repository (SOR) which will store the system and configuration data that will be shared between all the enterprise server region that are part of the PAC:

1. In the menu bar, click Native.
2. In the navigation pane, click 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 list, select the SOR type. Redis and Oracle Coherence are supported as SORs. See Scale-Out Performance and Availability Clusters for more information.

   The default is Redis.

6. Optionally, in the Description field, type a description for your PSOR.
7. Depending on the type of SOR selected:
   • If Redis is selected, 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.
   • If Coherence is selected, in the Connection String field, type the connection string which takes the form [userid@][configfile][,property=[value]]…

     See PAC and SOR Environment Variables for more information.

8. Click Save.

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.
   Note: The PAC Name is limited to no more than 8 characters long.
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 SOR Model 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. Check Shared if you require the SOR model to be shared between PACs.
9. 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. In the navigation pane, 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.
   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.
6. In the right pane, check 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.