Why WCC 11.3.6 can't implement HA mode like WCC 11.3.5?
11.3.6 runs in HA mode with the use of an external database.
Yes, It is possible to configure WCC r11.3.6 in HA mode.
You are able to configure WCC 11.3.6 with a core / spectator WCC server (core being the "primary" and spectator being the "shadow" or "failover").
WCC 11.3.6 HA mode is the same as for WCC 11.3.5.
Since WCC 11.3.5, the HA concept is different from previous version.
In previous version of WCC (up to 11.3) the "HA" mode was more a configuration replication with notion of core/spectator/standalone.
Since 11.3.5 (11.3.6 and 11.4 included), the HA concept is defined by HA nodes (WCC servers) using the same external (e.g. not Derby) databases (for both WCC DB - monitoring configuration- and Reporting DB). All nodes are equal (no slave/master notion). When a modification is done on one node (new server, new view, ...) it is immediately reflected in all the HA nodes. The installer will recognize when selecting the WCC database if it is already used by another node. The Reporting database already configured for the first node will be used even if another one has been selected by the user. A clear message is displayed so user is aware of the situation. The EEM server(s) cannot be modified, password is required for confirmation. Ports are server specific and can be different on each HA node.
When using HA mode only one server in the cluster retrieve data form autosys server at a time this distribute the load on the WCC servers.
This HA mode can be used with a load balancer (like the Apache httpd) to enable costumer to present a single URL, hide the URLs of the HA nodes and distribute the load on the different nodes. See Implementation Guide for more details.
Retrieving data ...