EM 4.0
Solution Package for TIBCO ActiveMatrix and the Solution Package for TIBCO BusinessWorks version 6
The ports used by the sample projects for the Solution Package for TIBCO ActiveMaxtrix and the Solution Package for TIBCO BusinessWorks version 6 have changed. Projects created in previous releases will continue to use the old ports. Users of these solution packages should just be aware the ports have been changed in the new sample projects as follows:
| • | For BusinessWorks Monitor the new port prefix is 45. This results in the following default port assignments: |
dataserver data port 4578
dataserver JMX port 4568
dataserver SC port 4570
dataserver rtvhttp port 4575
dataserver rtvagent port 4572
dataserver sender data port 4576
dataserver sender JMX port 4566
displayserver data port 4579
displayserver JMX port 4569
historian JMX port 4567
database (hsqldb) JMX port 4561
| • | For ActiveMatrix Monitor the new port prefix is 44. This results in the following default port assignments: |
dataserver data port 4478
dataserver JMX port 4468
dataserver SC port 4470
dataserver rtvhttp port 4475
dataserver rtvagent port 4472
dataserver sender data port 4476
dataserver sender JMX port 4466
displayserver data port 4479
displayserver JMX port 4469
historian JMX port 4467
database (hsqldb) JMX port 4461
Custom Solution Package
The custom solution package example has been removed from EM. Contact SL technical support for information on creating custom solution packages.
Existing custom solution packages will continue to work as they did before. It is recommended, but not required that existing custom solution packages make the following changes. These changes are needed in order to be compatible with the new Configuration Application. Custom solution packages will continue to work as before without these changes, but data servers containing custom solution packages without these changes should not be configured via the Configuration Application:
1. Move the following server level properties from conf\rtvapm.sp.properties to conf\rtvapm.sp.compat.properties:
- all ports
- all proctag properties
- sender.sl.rtview.sub=$rtvAgentName
- sl.rtview.alert.persistAlertEngineName
- sl.rtview.sub=$domainName
2. Put the custom solution package directory under RTVAPM_HOME or RTVAPM_USER_HOME. If under RTVAPM_HOME, the solution package name must end in mon for the “RTView Configuration Application” to detect it.
This will add the custom solution package to the list of available solution packages in the Configuration Application.
3. Add rtvadmin\sp.meta.json under lib with the following - the “RTView Configuration Application” will use this as the display name for your solution package:
{
"displayname": "The Display Name for your SP"
}
4. Copy src\rtfiles\rtvconfig.sp.xml to lib\rtvadmin so the “RTView Configuration Application” can read its CI Types.
Property File Handling and Configuration Application
Property file handling has been modified in order to support the Configuration Application. Existing applications will continue to work as before with no changes. However, customers should be aware of the following if they want to merge their old properties into the new version of emsample.
In previous releases, each solution package defined its own ports, sender target and server identification properties. These properties have been removed from the solution package properties and should be defined in the project properties instead. The emsample project been updated to include these properties which have been set to the same values that they inherited from the solution package properties in previous releases (except for TIBCO ActiveMatrix and TIBCO BusinessWorks version - see note above). Upward compatibility support is included for projects created previous to EM 4.0. In EM 4.0, the rtview.properties files in all sample projects were replaced with project.properties files. Any project with an rtview.properties file is recognized as a project created with a previous release. In that case, RTView will automatically read in the old ports, sender target and server identification properties for all solution packages in the rtview.properties file. Therefore, projects created with previous of EM will continue to run with no modifications. However, projects containing an rtview.properties file cannot be configured using the new “RTView Configuration Application”. The emsample\conf\emcommon.properties file has been replaced by emsample\conf\project-common.properties which is read just before project.properties at the end of the property file list. The emcommon.properties file will still be read, but the properties in it will be overridden by the properties in project-common.
Merging properties from an old version of emsample to the new release has 2 parts. First there are the central and common settings. Second there are the solution package server setting.
There are two options for merging old central server and common properties from a previous release into the new version of emsample.
The first option for applying central server settings from a previous version is to use the “RTView Configuration Application” to reapply the settings. This is more work, but has the benefit of allowing you to use the Configuration Application moving forward. If you haven't done much to customize emsample Central Server, this won't be a big effort. To do this, run the new version of emsample, bring up the Configuration Application and apply all configurations that were part of your previous emsample project. See {xref}“Configure RTViewCentral ” for more information on how to configure your Central Server using the “RTView Configuration Application”.
The second option for applying central server settings from a previous version is to use your old properties files. This has the downside that you will not be able to use the Configuration Application to configure your common properties or Central Server. To use this option, do the following:
1. Start with the new emsample.
2. Copy the old conf\emcommon.properties into the new emsample\conf directory.
3. In the new emsample, delete conf\project.properties and conf\project.properties.json.
4. Copy the old servers\central\central.properties and the old servers\central\rtview.properties into the new emsample\servers\central directory.
5. In the new emsample, delete servers\central\project.properties and servers\central\project.properties.json.
There are three options for merging old solution package server properties from a previous release into the new version of emsample.
The first option for applying solution package server settings from a previous version is to use the “RTView Configuration Application” to reapply the settings. If you have a lot of connections, this isn't really practical, but if you only have a few, it could be worthwhile since you'll be able to use the Configuration Application for everything moving forward. To do this, run the new version of emsample, bring up the Configuration Application and apply all configurations that were part of your previous emsample project. See {xref}“Configure RTViewCentral ” for more information on how to configure your solution package servers using the “RTView Configuration Application”.
The second option for applying solution package server settings from a previous version is to use your old properties files instead of the Configuration Application. This has the downside that you cannot use the Configuration Application moving forward. To do this, do the following in each solution package project directory under emsample\servers:
1. Start with the new emsample
2. Copy the properties files from the old solution package server directory into the new solution package server directory including the old rtview.properties.
3. Remove the project.properties and project.properties.json from the new solution package project directory.
4. Add your properties files to the appropriate lines in servers\rtvservers.dat.
The third option for applying solution package server settings from a previous version is a combination of the above. This has the benefit of allowing you to use the “RTView Configuration Application” without having to re-enter all of your connections.
1. Start with the new emsample.
2. Copy the properties files from the old solution package server directory into the new solution package project directory. Do NOT copy the old rtview.properties into the new solution package project directory.
3. Edit the properties file you just copied over to comment out or remove all non-connection properties.
4. Run emsample and use the Configuration Application to apply all settings from your previous project except connections. See {xref}“Configure RTViewCentral ” for more information on how to configure your solution package servers using the Configuration Application.
5. Add your properties files from step 2 to the appropriate lines in servers\rtvservers.dat.
6. Moving forward, new connections can be added via the Configuration Application or by hand editing the properties file from step 2, whichever is more convenient. However, only connections added via the Configuration Application will be editable in the Configuration Application.
NOTE: The following files are read and written by the Configuration Application and should never be manually edited: project.properties, project.properties.json, conf\project-common.properties and conf\project-common.properties.json.
Return to Download, Install, Register and Upgrade RTViewCentral.