Filter
Top Products
Features Benefits
High availability
(Failover)
Oracle RAC supports high availability by eliminating the dependence
on a single server, where the chances of database downtime are more
due to hardware failure.
v Initial connection time failover
In initial connection time failover, the database node availability is
determined while establishing the connection. The connection is
established with the available database node. However, if a database
node goes down while a transaction is in progress, the transaction
will fail and throw a SQLException error, and a new connection will
be established with the available node.
Initial connection time failover can be configured on the JDBC
multi-instance URL on the client side by setting this parameter:
FAILOVER=ON
Sterling B2B Integrator supports two-node Oracle RAC setup.
To establish initial time connection failover in Sterling B2B Integrator,
perform the following tasks:
1. Configure the following properties in ASI node and in
customer_overrides.properties.in file in containers. You can set
values for these properties (in milliseconds) that are suitable for
your operating environment.
Setting a value too low would result in genuine SQL queries
getting terminated before they have a chance to be processed and
return the dataset. A value too high means that the application
threads are holding connections which are waiting on a query
timeout for that duration and are not available for other tasks.
This could result in lower throughput. An optimum setting
depends on the customer's environment.
jdbcService.oraclePool.prop_oracle.jdbc.
ReadTimeout=<milliseconds>
jdbcService.oraclePool_local.prop_oracle.jdbc.
ReadTimeout=<milliseconds>
jdbcService.oraclePool_NoTrans.prop_oracle.jdbc.
ReadTimeout=<milliseconds>
jdbcService.oracleUIPool.prop_oracle.jdbc.
ReadTimeout=<milliseconds>
jdbcService.oracleArchivePool.prop_oracle.jdbc.
ReadTimeout=<milliseconds>
2. From the install_dir/install/bin (install_dir\install\bin for
Windows) directory, run (UNIX or Linux) setupfiles.sh or
(Windows) setupfiles.cmd.
3. Restart the ASI and container JVMs to apply the changes.
34 Sterling B2B Integrator: Performance Management