========================================================== 
 
Systems Requirements for: 
 TIBCO(R) RTView(R) for TIBCO BusinessEvents(R) 
 
APM.6.3.0.0_20221223_002.3d86c
BWM.7.1.1.0_20221223_002.3d86c
EMM.7.1.1.0_20221223_002.3d86c
TBE.7.1.1.0_20221223_002.3d86c
 
========================================================== 
 
 


 THIN CLIENT


---- Browser ------------------------------------------------

 Google Chrome (latest)
 Microsoft Edge
 Mozilla Firefox (latest)

 Other browsers with Java Script enabled should also 
 work, but are not guaranteed.

 TABLET LIMITATIONS
 Not all functionality is available in a tablet client.
 See the User's Guide "Deployment -> Web Application" page 
 for more details about these limitations
 
 

 SERVERS AND BUILDER


 
---- JVM Support --------------------------------------------

 Oracle Java 8,9,11,17 64-bit
 Oracle OpenJDK 8,11,17 64-bit
 AdoptOpenJDK 8,11 64-bit

 NOTE: Other OpenJDK implementations may work, but are not
 officially supported.


 
---- Operating System Support -------------------------------

 Microsoft Windows (x86-64)
	7, 10, 11
 Microsoft Windows Server (x86-64)
	2008 (R2), 2012 (R2), 2016, 2019, 2022
 Red Hat Linux (x86-64)
	7.x, 8.x
 Solaris
	11 (x86-64, SPARC)
 
 NOTE: Other platforms running a standard supported JVM 
 (see JVM Support) should work, but are not guaranteed.


 
 
 
---- Recommended Hardware -----------------------------------------------

 2.8 GHz Core 2 Duo equivalent or faster
 200 MB disk space for installation
 2 GB of RAM or higher*
 
 *The optimal minimum and maximum heap size for a given server 
 process are context-dependent, but the default values (listed below) 
 are a good starting point. 
 
 Some practical guidelines to consider are that Data Server 
 memory will be dependent on the volume of data and Display Server 
 memory usage is dependent on the number of simultaneous users. 
 Historian memory is dependent on configured persistence and 
 compaction workloads.
 
 Keep in mind as well that the maximum java heap size possible
 will be JVM dependent.
 
 Java Heap Defaults
	Display Server 256 MB - 1 GB
	Data Server 256 MB - 1 GB*
	Historian 128 MB - 384 MB
	Thick Client Viewer 128 MB - 256 MB

*The default maximum for the RTViewDataServerSolace is 4 GB.
 
---- Servlet Container --------------------------------------

 An application server is required to run a thin client 
 deployment (for example, Tomcat 6.0 or greater).
 
 NOTE: Any production quality application server may be used.
 
---- Database JDBC Support ----------------------------------
 
 Evaluation environments can use the bundled HSQLDB database.
 
 Production environments should use one of the following 
 supported databases:

 Oracle 19 (ojdbc8.jar)
 MS SQL Server 2016, 2019 (sqljdbc41.jar, sqljdbc42.jar)
	Requires:
		View Server State permission
 MySQL 5.7, 8.0 (mysql-connector-java-8.0.*.jar)
	Requires:
		ANSI_QUOTES sql_mode
		NO_BACKSLASH_ESCAPES sql_mode
 IBM DB2 10.5 (db2jcc4.jar)
	Requires pagesize of 8k

 A pre-configured version of MySQL 5.7 is available on 
 Docker Hub as slcorp/mysql-rtview.  For more information 
 refer to rtvapm/containers/docker/myql-rtv/README.txt 
 
 
 
 
 THIRD-PARTY APPLICATION SUPPORT 
 
 
 
== tbemon ============================================== 
 

 TIBCO BusinessEvents(R) 4.0.x, 5.0.x, 5.1.x, 6.0.x, 6.1.x, 6.2.x

 LIMITATIONS

 TIBCO BusinessEvents(R) 6.x

  The Storage Node Summary display is not expected to populate 
  for 6.x, but remains in the product for continued support for 5.x.

 TIBCO BusinessEvents(R) 4.0.x

  Applications using JMX to monitor applications on 
  a server with the server's firewall enabled might 
  experience connection problems. The JMX protocol allows 
  initial contact on a known port, but subsequent 
  communications might occur over a second randomly chosen 
  port. Version 5 of Tibco BusinessEvents has a fix that 
  allows the follow-on communications to occur over the 
  same port. However, BE version 4.0 does not have this 
  fix. BE 4.0 installations should use a local agent to 
  push the necessary MBean data to the central RTView 
  Data Server, or use a "premain agent" as described here:

  https://blogs.oracle.com/jmxetc/entry/connecting_through_firewall_using_jmx

  Even better, try using the generic JMX connector (JMXMP)
  which is part of the JSR 160 Reference Implementation.
  When using the generic JMX adapter, your connection 
  properties will look like the following:

  sl.rtview.jmx.jmxconn=demoBENode - - URL:service:jmx:jmxmp://192.168.1.1:5555 - - false