EM 5.0

New Deployment Architecture

Enterprise Monitor has been enhanced to support a new deployment architecture. Instead of a single RTViewEnterpriseMonitor deliverable containing both the RTViewCentral servers and the RTView Data Servers, there is now an RTViewCentral deliverable and several RTViewDataServer deliverables. The project in the RTViewCentral deliverable is similar to the central servers in the emsample project that was included in previous releases and is described in this document. The RTViewDataServer deliverables are similar to the solution package-specific servers in the emsample project that was included in previous releases. To make it easy to connect one or more RTViewDataServers with RTViewCentral, an Integrate with EM tab has been added to the RTView Configuration Application. See Installation and Setup for information on how to install and set up RTViewCentral and one or more RTViewDataServers to work together.

Upgrading Existing Projects

Existing emsample projects created with previous releases of RTView can be run with no changes against the new RTViewCentral deliverable. To do this, extract the RTViewCentral deliverable and do the following:

In your old deliverable, rename the RTViewEnterpriseMonitor/rtvapm directory to rtvapm_old.

Copy RTViewCentral/rtvapm to RTViewEnterpriseMonitor

Open a command prompt or terminal window, navigate to RTViewEnterpriseMonitor/rtvapm, and run rtvapm_init.

In your command prompt or terminal window, navigate to RTViewEnterpriseMonitor/emsample/servers.

In each directory you are using under RTViewEnterpriseMonitor/emsample/servers, run update_wars.sh/.bat and copy the generated war files to RTViewEnterpriseMonitor/apache-tomcat-8.5.24-sl.

Run RTViewEnterpiseMonitor as you did previously (for example, run bin/start_servers.sh/.bat).

The emsample application will run as before, but there are a few limitations when using the RTView Configuration Application with your old emsample project.

RTViewCentral Servers Section Changes and Limitations

The General->COMMON tab has been removed as the new RTViewCentral project does not support common properties files. When running the RTView Configuration Application in an emsample project from a previous release, properties from conf\project-common.properties are merged into the properties for the server being edited and are saved to that servers' properties files.

The General->About tab has a new field named Central Server URL. This field is for reference purposes only to store the URL that RTView DataServers should use to connect to the Central Server and defaults to localhost:10018. When running the RTView Configuration Application in an emsample project from a previous release the Config Server URL from conf\project-common.properties is copied into this field.

A new Databases entry has been added to the navigation bar, which contains all of the Database connection fields: The Alert Threshold and Historian database fields were moved here from the General->COMMON tab. The Diagram Generator, Metric Explorer, and CMDB databases were moved here from the Central Config Server-> CONFIGURATION, and CMDB tabs. The Access the Alert Threshold Database via the Central Config Server Instead of Connecting Directly field has been removed as the new deployment architecture has merged the Central Config Server and Central Alert Server into a single server. When running the RTView Configuration Application in an emsample project from a previous release, the Alert Threshold and Historian databases properties from conf\project-common.properties are copied to this tab and saved locally. If the Access the Alert Threshold Database via the Central Config Server Instead of Connecting Directly setting is enabled, it will be maintained but the RTView Configuration Application does not provide a way to disable it.

The Central Config Server section has been removed. The new RTViewCentral deliverable has merged the Central Config and Central Alert Servers into a single Central Server that serves both functions. The database fields on the Central Config Server->CONFIGURATION SERVER and CMDB tabs have moved to the Databases section. The other fields on the CMDB tab have moved to the new Service Model navigation bar entry. When running the RTView Configuration Application in an emsample project from a previous release where the Memory and/or Log settings for the Central Config Server were overridden, those values are copied to the General->CUSTOM PROPERTIES tab.

The Central Alert Server section has been removed. The new RTViewCentral deliverable has merged the Central Config and Central Alert Servers into a single Central Server that serves both functions. The ALERTS and DATA STORAGE tabs have moved to the new Alerts navigation bar entry. When running the RTView Configuration Application in an emsample project from a previous release where the Memory and/or Log settings for the Central Alert Server were overridden, those values are copied to the General->CUSTOM PROPERTIES tab.

The Data Servers navigation bar entry has been removed and the Data Servers->CONNECTIONS tab has been moved to the new Central Server section. The Select Mode for Including Solution Packages on the COMPONENTS tab field has been removed. The COMPONENTS tab in the new RTViewCentral project has been enhanced to only include displays for the solution packages in all enabled connections. When running in an emsample project from a previous release where the tree was customized, this filter will be applied in addition to any customization.

The new Central Server entry in the navigation bar lets you set memory and log file options for the Central Server. These settings will not apply to an emsample project from a previous release.

RTView Data Server Configuration Section Changes and Limitations

The General->ALERTS tab has moved to the Alerts navigation bar entry. The Alert Threshold Database Connection entry has moved to the new Databases navigation bar entry. When running the RTView Configuration Application in an emsample project from a previous release, the Alert Threshold database property from conf\project-common.properties (previously set on the COMMON tab under RTViewCentral Servers) is copied to this tab unless it was previously overwritten locally. If the Access the Alert Threshold Database via the Central Config Server Instead of Connecting Directly setting was enabled, it will be maintained but the RTView Configuration Application does not provide a way to disable it. The Configure notifications for this server in addition to central notifications option has been removed but will be maintained when running in an emsample project created with a previous release. To disable local notifications, turn off Enabled Notifications.

The Historian->HISTORIAN Historian Database Connection entry has moved to the new Databases navigation bar entry. When running the RTView Configuration Application in an emsample project from a previous release, the Historian database property from conf\project-common.properties (previously set on the COMMON tab under RTViewCentral Servers) is copied to this tab and saved locally unless it was previously overwritten locally.

A new EM Integration navigation bar entry allows you to integrate the RTViewDataServer with the RTViewCentral. This feature is not compatible with emsample projects created with a previous version.

High Availability

The method for configuring and enabling High Availability has been enhanced and simplified. Projects created with a previous version of Enterprise Monitor that were configured for HA will continue to work with no changes.