Database Cluster Configuration

Access to the Database Layer

Support for cluster level solutions like Oracle RAC or MSSQL Cluster requires configuration in configuration objects that access the database layer. Most of these configuration objects (except the regular one) provide an extension called Custom JDBC URL that must be used in cluster solutions like Oracle RAC or MSSQL Cluster. Objects and their configurations are listed below:

• The DAP in IWD Runtime Node that accesses the iWD Data Mart database (Custom JDBC URL can be set up using:
  GAX -> Configuration/iWD Plugin -> Datamart -> chosen solution -> Database field "Custom URL (for Datamart)")
• The DAP in IWD Runtime Node that accesses the Configuration Server database (Custom JDBC URL can be configured manually by adding a jdbc section to the DAP options, with key url and a suitable value)
• The DAP in Interaction Server that accesses the Interaction Server database (Custom JDBC URL can be configured manually by adding a jdbc section to the DAP options, with key url and a suitable value)
• The DAP in Interaction Server that accesses the EventLog database (Custom JDBC URL can be set up using:
  GAX -> Configuration/iWD Plugin -> Business Structure -> chosen solution two times -> Interaction Server Settings -> EventLog JDBC URL)
• The JDBC URL in Runtime Node that uploads to Stat Server Java Extensions via one of the Data Mart jobs (Custom JDBC URL can be set up using:
  GAX -> Configuration/iWD Plugin -> Datamart -> <chosen solution> -> Database filed "Custom URL (for iWD SSJE)")
• The JDBC URL in the iwd.properties file in iWD Manager that accesses the iWD Manager database—click here.

Configuration for Oracle Support

Oracle 12c and Oracle 12c RAC are both supported in release 8.5.103. Configurations with and without Single Client Access Name (SCAN) are supported.

Custom JDBC URLs

There are different Oracle JDBC URLs depending on whether your configuration has SCAN enabled or disabled.

SCAN enabled

The Oracle JDBC URL for the Data Mart DAP is:

jdbc:evo:oracle:@//rac-scan:1521/orcl.abc.xyz.domain.com

The Oracle JDBC URL for the Stat Server Java Extensions is:

jdbc:evo:oracle:@//rac-scan:1521/orcl.abc.xyz.domain.com

SCAN disabled

The Oracle JDBC URL for the Data Mart DAP is:

jdbc:evo:oracle:@(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=RACNode1)
(PORT=RACNodePort1))(ADDRESS=(PROTOCOL=TCP)(HOST=RACNode2)(PORT=RACNodePort1))
(CONNECT_DATA=(SERVICE_NAME=RACServiceName)))

The Oracle JDBC URL for Stat Server Java Extensions is:

jdbc:evo:oracle:@(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=RACNode1)
(PORT=RACNodePort1))(ADDRESS=(PROTOCOL=TCP)(HOST=RACNode2)(PORT=RACNodePort1))
(CONNECT_DATA=(SERVICE_NAME=RACServiceName)))

Limitations

• If RAC failover is forced when iWD Data Mart jobs are running, iWD Data Mart jobs will finish with an error. The next execution of iWD Data Mart jobs finish correctly without errors.
• Database initialization processes (dbup) for the iWD Manager and iWD Data Mart databases do not support failover. Initial configuration should be carried out made in a stable environment. If an error occurs during initialization the database must be dropped and created again from scratch.
• In this initial release of Oracle support, only one SCAN is supported, though there might be up to three in a given environment.