========================================================== Systems Requirements for: RTView(R) Enterprise APM.5.1.1.0_20190814_002.31522 ========================================================== 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 64-bit Oracle Java 9 64-bit ---- Operating System Support ------------------------------- Microsoft Windows 7, 8.x, 10 (x86, x86-64) Microsoft Windows Server 2008 (R2), 2012 (R2), 2016 (x86-64) Red Hat Linux 6.x, 7.x (x86, x86-64) Solaris 10, 11 (x86-64, SPARC) IBM AIX 6.1 (64 bit POWER RISC) NOTE: Other platforms running a standard Oracle 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 ---- 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 11 (ojdbc6.jar) MySQL 5.5, 5.6, 5.7 (mysql-connector-java-8.0.*.jar) Requires: ANSI_QUOTES sql_mode NO_BACKSLASH_ESCAPES sql_mode latin1 charset MS SQL Server 2008 R2, 2014, 2016 (sqljdbc41.jar, sqljdbc42.jar) Sybase ASE 16.0 (jconn4.jar) Requires pagesize of 8k 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 == acwmon ============================================== AWS SDK for Java 1.9.x, 1.10.x, 1.11.x == amxmon ============================================== TIBCO ActiveMatrix BusinessWorks(TM) 5.7.2+, 5.9.x, 5.10.x, 5.11.x 5.7.0 and 5.7.1 contain a defect that prevent the monitor from correctly displaying data TIBCO ActiveMatrix(R) Service Grid 3.x 2.x is unable to provide JVM memory metrics TIBCO Hawk(R) 4.8.x, 4.9.x, 5.1.x 5.1.x is supported with the limitations: Java 1.7 RVD and EMS transports only (AS DataGrid transport not supported) TIBCO Rendezvous(R) 8.x == bw6mon ============================================== TIBCO BusinessWorks(TM) 6.3.x, 6.4.x TIBCO BusinessWorks(TM) Container Edition 2.2.x, 2.3.x, 2.4.x TIBCO Hawk(R) 5.1.x, 5.2.x RVD and EMS transports only (AS DataGrid transport not supported) TIBCO Rendezvous(R) 8.4.2+ == bwmon ============================================== TIBCO BusinessWorks(TM) 5.7.2+, 5.9.x, 5.10.x, 5.11.x 5.7.0 and 5.7.1 contain a defect that prevent the monitor from correctly displaying data TIBCO ActiveMatrix(R) Service Grid 3.x 2.x is unable to provide JVM memory metrics TIBCO Hawk(R) 4.8.x, 4.9.x, 5.1.x, 5.2.x RVD and EMS transports only (AS DataGrid transport not supported) TIBCO Rendezvous(R) 8.x == db2mon ============================================== IBM(R) DB2(R) 10.5.x == dockermon ============================================== Docker 1.8, 1.9, 1.10, 1.11, 18 == emsmon ============================================== TIBCO Enterprise Message Service(TM) 6.x, 7.x, 8.x == hawkmon ============================================== TIBCO Hawk(R) 4.8.x, 4.9.x, 5.1.x, 5.2.x RVD and EMS transports only (AS DataGrid transport not supported) TIBCO Rendezvous(R) 8.x == jbossmon ============================================== JBoss EAP 6.1, 6.2, 6.3 WildFly 9, 10 NOTE: JBoss AS 7.1.1 does not provide session nor servlet jmx mbeans. Monitoring functionality is reduced in this version. See https://developer.jboss.org/thread/219739?tstart=0 == kafkamon ============================================== Apache Kafka 2.11-1.0.0 == mongomon ============================================== MongoDB 3.0, 3.2.1 == mqmon ============================================== IBM(R) MQ 7.0.1.3, 7.5, 8.0 == mssqlmon ============================================== Microsoft SQL Server 2008 R2, 2014, 2016 == mysqlmon ============================================== MySQL 5.6, 5.7* *NOTE: MySQL 5.7.11 and later are only supported with the database property 'show_compatibility_56=ON'. == nodemon ============================================== Node.js 4.4.0 == ocmon ============================================== Oracle(R) Coherence 3.5.3, 3.7.1, 12.1.2, 12.1.3, 12.2.1 == oemcon ============================================== Oracle(R) Enterprise Manager 12.1.0.3 == oramon ============================================== Oracle(R) Database 11g == solmon ============================================== Solace Appliances/VMRs 8.2, 8.4, 8.8, 8.9, 8.12, 9.1 Solace Cloud Edition == tadmon ============================================== Adapters developed with TIBCO Adapter(TM) SDK 5.8+ == tasmon ============================================== TIBCO ActiveSpaces(R) 2.1.6, 2.2.1 == tbemon ============================================== TIBCO BusinessEvents(R) 4.0.x, 5.0.x, 5.1.x See notes below regarding 4.0.x limitations LIMITATIONS 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 == tdgmon ============================================== TIBCO ActiveSpaces(R) Version 4.1.x TIBCO FTL(R) 6.1.x == tftlmon ============================================== TIBCO FTL 6.x == vmwmon ============================================== VMWare vSphere 5.x, 6.0 Standalone ESXi servers are also supported. == wlm ============================================== Oracle(R) WebLogic 10.3.3.0, 12.1.3.0 == wsm ============================================== IBM(R) WebSphere(R) Application Server 8.5 LIMITATIONS Secure connections are not supported. The Data Server classpath requires the following library from IBM WebSphere 7.0: com.ibm.ws.admin.client_7.0.0.jar