Configuring an ObjectServer failover pair to support load balancing

Learn how to configure an ObjectServer failover pair to support Web GUI load balancing.

Web GUI load balancing can be supported by an ObjectServer failover pair. We suggest that a typical AGG layer is deployed. An existing AGG pair can be adopted, or a brand-new dedicated pair can also be deployed.

Note: In the command line examples, user root with password secret are shown as an example. For your system, substitute these values with a valid user name and password for your own system. To have all the necessary permissions for the ObjectServer, the user should be a member of either the WebHA or System built-in groups.

For more information about deploying an AGG layer failover pair, see Failover configuration.

The configuration items for the ObjectServer failover pair and their gateway can be found at:
  • UNIX: $NCHOME/omnibus/extensions/webha
  • WINDOWS: %NCHOME%\omnibus\extensions\webha

Extending the primary ObjectServer

Load the dashdb failover database schema into a primary (AGG_P) server that is up and running:
  • UNIX:
    $NCHOME/omnibus/bin/nco_sql -server AGG_P -user root –password secret <
$NCHOME/omnibus/extensions/webha/objectserver/webha.sql
  • WINDOWS:
    "%NCHOME%\omnibus\bin\isql" -S AGG_P -U root -P secret -i "%NCHOME%
\omnibus\extensions\webha\objectserver\webha.sql"

Extending the backup ObjectServer

Load the dashdb failover database schema into a backup (AGG_B) server that is up and running:
  • UNIX:
    $NCHOME/omnibus/bin/nco_sql -server AGG_B -user root –password password <
$NCHOME/omnibus/extensions/webha/objectserver/webha.sql
  • WINDOWS:
    "%NCHOME%\omnibus\bin\isql" -S AGG_B -U root -P password -i "%NCHOME%
\omnibus\extensions\webha\objectserver\webha.sql"

Extending the bidirectional aggregation ObjectServer Gateway

Append the table mappings and replication definitions for the dashdb database to the AGG_GATE configuration.

  • UNIX:
    cat $NCHOME/omnibus/extensions/webha/gateway/AGG_GATE.map.parts >>
$NCHOME/omnibus/etc/AGG_GATE.map
cat $NCHOME/omnibus/extensions/webha/gateway/AGG_GATE.tblrep.def.parts >>
$NCHOME/omnibus/etc/AGG_GATE.tblrep.def
  • WINDOWS:
    type %NCHOME%\omnibus\extensions\webha\gateway\AGG_GATE.map.parts >>
$NCHOME\omnibus\etc\AGG_GATE.map
type %NCHOME%\omnibus\extensions\webha\gateway\AGG_GATE.tblrep.def.parts >>
%NCHOME%\omnibus\etc\AGG_GATE.tblrep.def

The gateway must be stopped/restarted for the updates to its table mappings and replication definitions to become effective.

Removing the WebHA failover data from an ObjectServer failover pair

If you need to drop the WebHA configuration and data from a failover ObjectServer pair, use the following commands, depending on your operating system:

Run the following command for the primary server:
  • UNIX:
    $NCHOME/omnibus/bin/nco_sql -server AGG_P -user root –password secret <
$NCHOME/omnibus/extensions/webha/objectserver/webha_rollback.sql
  • WINDOWS:
    "%NCHOME%\omnibus\bin\isql" -S AGG_P -U root -P secret -i "%NCHOME%
\omnibus\extensions\webha\objectserver\webha_rollback.sql"

Run the following command for the backup server:

  • UNIX:
    $NCHOME/omnibus/bin/nco_sql -server AGG_B -user root –password secret <
$NCHOME/omnibus/extensions/webha/objectserver/webha_rollback.sql
  • WINDOWS:
    "%NCHOME%\omnibus\bin\isql" -S AGG_B -U root -P secret -i "%NCHOME%
\omnibus\extensions\webha\objectserver\webha_rollback.sql"

For more information, see Configuring a load balancing environment.

Updating the WebHA database schema in the ObjectServer

Prerequisites
  • DASH 3.1.3.15 or later
  • Omnibus 8.1.0.30 or later
A system with WebHA already deployed can be upgraded by applying the artifacts that are found in:
$NCHOME/omnibus/extensions/webha/update/update81fp26to81fp30
Complete the following steps:
  • Update the schema in the backup ObjectServer.
  • Update the data mapping specification in the bi-directional gateway that synchronizes the primary and backup ObjectServers.
  • Restart the bi-directional gateway.
There is no need to upgrade a primary ObjectServer. The primary ObjectServer is automatically updated when the WebGUI client connects.

Procedure

  1. Apply $NCHOME/omnibus/extensions/webha/update/update81fp26to81fp30/update81fp26to81fp30_webha.sql to an existing backup ObjectServer by running the following command against the server:

    Unix

    $NCHOME/omnibus/bin/nco_sql -server AGG_B -user root -password secret < update81fp26to81fp30_webha.sql

    Windows

    "%NCHOME%\omnibus\bin\isql" -S AGG_B -U root -P password -i update81fp26to81fp30_webha.sql
  2. Update the bi-directional AGG_GATE gateway configuration:
    1. Update the AGG_GATE table replication definition by editing the current definition. This definition is usually found at: $NCHOME/omnibus/etc/AGG_GATE.tblrep.def Append the following lines to the existing file:
      REPLICATE ALL FROM TABLE 'dashdb.TRANSFORMATIONS'
USING map 'dashhatransformationsmap';

REPLICATE ALL FROM TABLE 'dashdb.WIRES'
USING map 'dashhawiresmap';
      Refer: $NCHOME/omnibus/extensions/webha/update/update81fp26to81fp30/AGG_GATE.tblrep.def.parts
    2. Update the AGG_GATE table mapping definition by editing the current definition:
      cat $NCHOME/extensions/webha/update/update81fp26to81fp30/AGG_GATE.map.parts >> $NCHOME/omnibus/etc/AGG_GATE.map
  3. Restart the AGG_GATE gateway for the changes to take effect.
  4. Verify that the AGG_B ObjectServer schema now contains the following tables as well as the same data (if any) found in the primary server:
    dashdb.TRANSFORMATIONS
dashdb.WIRES