Considerations for Clustered Architecture Models

In this section:

Outlined below are considerations for single-tier or multi-tier clustered architecture models.

We begin with two options for installing WebFOCUS for use with a clustered architecture model:

Top of page

Separate WebFOCUS Installation

This is the recommended installation option and encompasses the following guidelines.

WebFOCUS Client


There are several options for installing the ReportCaster Distribution Server.

WebFOCUS Reporting Server

Stand-Alone WebFOCUS Hyperstage

WebFOCUS Workload Distribution Facility (CLM)

Considerations of a Separate Installation

Top of page

Shared WebFOCUS Installation

Similar to the separate installation option, there are advantages and disadvantages to a shared installation.



Top of page

Shared Files

In a clustered architecture model, members must have the same view of configuration and application content at all times.

The most common way to do this is to place the files on a shared device. The other way is to keep the files on the local file system of each cluster member, but synchronize them through some external process.

Let us take a look at:

Files that can be shared between cluster members

Files that can be shared between cluster members are of the following two types:

Reporting Server/Application Content

Reporting Server/Configuration

WebFOCUS Client/Application Content

ReportCaster Configuration

Sharing Mechanisms for Shared Files

There are two mechanisms for providing cluster members with the same view of application content and configuration files.

Top of page

WebFOCUS 8 Repositories

WebFOCUS 8 requires two database repositories:

WebFOCUS 8 Client

Resource Analyzer

Note: Some customers will need to keep both WebFOCUS 8 Repositories in a common database schema to conform to company policy. This does not create any conflict between the two repositories because they are logically separated and have different table names.

Information Builders