Jump to: navigation, search

Applications, Advisors Servers, and Cluster Nodes


For background information see:

Two Advisors Servers on One Cluster Node

The following figure illustrates that two Advisors servers can be installed on the same cluster node.


There is one cluster node with one ID.

CCAdv XMLGen is installed on the node. It is controlled by Solution Control Server (SCS) through an application created in the Management Layer.

WA Server is also installed on the node. It runs in Geronimo, which is controlled by SCS through a different application.

Primary/Backup Pair of Advisors Servers on Two Cluster Nodes

The following figure shows how a primary and backup pair of Advisors servers is deployed.


The example uses CCAdv XMLGen as the Advisors server.

One XMLGen is deployed on one cluster node and controlled by an application using SCS.

The second XMLGen is similarly deployed on a different cluster node.

In this scenario, there are two cluster nodes with two different node IDs.

The two applications are linked as primary and backup applications in the Management Framework.

One Advisors Server with Two Modules on One Cluster Node

Controlled by Solution Control Server

The following figure shows two Advisors modules running in one Advisors server on one cluster node.


These modules are natively integrated with SCS. Both modules run in the same Geronimo server and the server is controlled by an application in SCS.

Controlled by Service on Operating System

The following figure shows two Advisors modules running in one Advisors server on one cluster node.


Because these modules are not natively integrated with SCS, the Advisors server is managed by a Windows or Linux service.

Instead of creating an OS service, you could configure a "third party" application in SCS for the Advisors server, and start and stop it from SCS that way.

This page was last modified on July 5, 2018, at 19:53.


Comment on this article:

blog comments powered by Disqus