Publishing Reports to the Web - Downloads - Oracle

Maintaining High Availability
For servers to be members of the same cluster, they must share a cluster name
(appended to each server's server name) and have the same public and private keys.
If your machines require different job-related configuration settings, you will not
benefit from clustering.
If you must set your servers up for different languages, you’ll want to set up multiple
clusters: one or more for each language.
1.5 Maintaining High Availability
Oracle Application Server provides a number of high availability features to keep its
middle tier running even when particular servers or components fail. To take
advantage of these high availability features, OracleAS Reports Services takes the
following actions when its infrastructure dependencies fail:
■ Retrying the OracleAS Portal database connection. If the connection from the
Reports Server to the OracleAS Portal database schema is dropped for some
reason, then the Reports Server tries to re-establish the connection before
generating an error. First, it retrieves the OracleAS Portal connection string from
the repository. With the OracleAS Portal connection string, the Reports Server can
attempt to reconnect. If reconnection is successful, you need not restart the Reports
Server. OracleAS Reports Services also supports cold failover and RAC on the
infrastructure and disaster recovery on the middle tier.
■ Retrying the Oracle Internet Directory connection. If the Oracle Internet
Directory connection becomes stale for some reason, the Reports Servlet and the
Reports Server try to re-establish the connection before generating errors. If
reconnection is successful, you need not restart the Reports Server.
See Also: For more information about high availability:
■ Oracle Application Server 10g High Availability Guide
Understanding the OracleAS Reports Services Architecture 1-9