Jump to: navigation, search

Stat Server Load Balancing

The relationship between a statistic and the Stat Server pair against which it is requested is maintained. This means that on (re)start or refresh of the adapter, statistics are now re-requested against the same Stat Server(s) as previously. AGA no longer depends on the value set for the Stat Server old-stats-remove-interval option.

If any additional Stat Servers are added after the initial starting of the Adapter, the statistics already requested with previous Stat Servers are not automatically re-distributed with the newly added Stat Server pair. You have two options if a redistribution is needed. Use Option 2 to maintain existing mapping with some of the Stat Servers.

Option 1

1. Run the following SQL statement to truncate the ADAPTER_SS_OBJ_MAPPING platform database table:

DELETE FROM ADAPTER_SS_OBJ_MAPPING WHERE SS_PAIR_ID = <Id of the stat server pair>
where the ID is the ID of the stat server pair from the ADAPTER_SS_CONFIG table.

2. Restart the Stat Servers (this flushes any previous requests).
3. Restart the adapter and Platform server.

Option 2

Run the following SQL statements to selectively update the ADAPTER_SS_OBJ_MAPPING table to point a range of objects to a new Stat Server installation:
SELECT SS_PAIR_ID FROM ADAPTER_SS_CONFIG WHERE NAME = [Name of the new pair's primary Stat Server]

UPDATE ADAPTER_SS_OBJ_MAPPING SET SS_PAIR_ID = [“ID” from above] WHERE OBJECTID IN ( ) AND OBJECTTYPE = ?

Add Stat Servers after Installation

To add Stat Server capacity after the deployment of Advisors Genesys Adapter, use the following procedure. You require access to the Platform configuration database.

1. Insert additional rows into the adapter_ss_config table that describe the additional Stat Servers. Name, Host, and Port are required. One row includes the primary Stat Server and its backup, if applicable.
2. After committing the changes to the database, restart the Platform server and Genesys Adapter.
This page was last edited on May 20, 2014, at 06:03.
Comments or questions about this documentation? Contact us for support!