Anonymous_User Absent Member.
Absent Member.

scalability of NOC's system

Hi guys,

Is it possible to create a master/slave scheme of NOC systems? The first
system collects data and does the portal, but the second one uses only
for reporting.
So we should have a small and fast database for the first system and the
same base with the same elements, but with other purging settings.

The main question in this situation: Is it possible to force NOC working
with a config database and a data warehouse database in readonly mode?

Strakhov's Profile:
View this thread:

Labels (1)
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: scalability of NOC's system

In the Customizer, under the configStore settings, there is an option
for Clustering. This allows you to have two or more instances of NOC
working together. There are ways that you can use different instance
for different roles.

By default, when you have multiple instances of NOC running in a
cluster, all are readers of the repository, but only one is a writer for
Service Levels, Profiles, etc.

Some other things you can do are having one (or more) instances run the
Service Configuration Manager jobs. Some have even had that instance
run extra adapters required to build views and have the other instances
only run the core adapters.

The dashboard is separate, you can run one or more of those against the
NOC Cluster.

You can use load balancers or content switches to direct users to
specific instances of NOC and/or Dashboard server.

tisenberg's Profile:
View this thread:

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.