Verify Your Setup
After you setup RTViewCentral and one or more RTView DataServers, you can verify your setup.
Open the Monitor and verify that you see data from the RTView DataServer you configured in the Services and Components tabs.
Congrats! You have setup RTView Enterprise.
You can now Configure RTViewCentral features such as the service model, the central database, user and role management, high availability, alert notifications, and modify the Monitor user interface.
You can also continue reading about the Monitor Architecture and components.
For details about using RTView Enterprise displays, see Using the Monitor.
Logging
By default log files are written to a logs directory under the project directory where a process is started, such as projects/rtview-server/logs. The log file name and location relative to the startup directory can be changed in the Configuration Application in the Data Server tab.
By default messages are appended to any existing logs/X.log file (where X is "dataserver", or "historian", etc depending on the name of the server) until it reaches a size of 50MB. Then it is renamed to X.log.N (where N = 1 - 9) and a new empty X.log file is created. So at any time the logs directory may contain X.log (newest, up to 50MB in size), and X.log.N where N = 1 - 9, each approx 50 MB, where 1 is the oldest and 9 is the newest. Once N = 9 is reached, on the next rollover X.log.1 is deleted and each remaining X.log.N is renamed to X.log.N-1.
The logging in RTView© Enterprise utilizes Log4j2, and users familiar with Log4j2 can configure the default logging behavior by editing the logging properties file available at projects/sl.log4j.properties. Refer to the Apache Log4j documentation for more information on configuring Log4j.
Warning! Configuration changes should be restricted to projects/sl.log4j.propertiesThe backup log4j properties file at rtvapm/common/conf/sl.log4j.properties should never be edited.