========================================================== Systems Requirements for: RTView Enterprise Monitor(R) for TIBCO(R) APM.4.2.0.0_20180911_002.28868 ========================================================== THIN CLIENT ---- Browser ------------------------------------------------ Google Chrome 47.x+ Microsoft Internet Explorer 11.x, Edge Mozilla Firefox 43.x + Mac Safari 8.x+ iPad iOS Safari 4+ 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 1.7 32-bit, 64-bit Oracle Java 1.8 32-bit, 64-bit NOTE: Data Servers may have more restrictive JVM requirements due to compatibility requirements of the third-party technologies being monitored. These restrictions are mentioned in the third-party application support notes. ---- Operating System Support ------------------------------------------- Microsoft Windows 7, 8.x, 10 (x86, x86-64) Microsoft Windows Server 2003, 2008 (R2), 2012 (R2) (x86-64) Red Hat Linux 6.x, 7.x (x86, x86-64) Solaris 10, 11 (x86-64, SPARC) 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). 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 (mysql-connector-java-5.1.6-bin.jar) Requires modes: ANSI_QUOTES NO_BACKSLASH_ESCAPES MS SQL Server 2008 (jtds12.jar) Sybase ASE 16.0 (jconn4.jar) Requires pagesize of 8k IBM DB2 Express 9.7 (db2jcc4.jar v4.14.137) Requires pagesize of 8k THIRD-PARTY APPLICATION SUPPORT == bwmon ============================================== 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.2.x RVD and EMS transports only (AS DataGrid transport not supported) TIBCO Rendezvous(R) 8.x == emsmon ============================================== TIBCO Enterprise Message Service(TM) 6.x, 7.x, 8.x == 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 == 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 == 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 == vmwmon ============================================== VMWare vSphere 5.x, 6.0 Standalone ESXi servers are also supported. == tadmon ============================================== Adapters developed with TIBCO Adapter(TM) SDK 5.8+ == tftlmon ============================================== Tibco FTL 5.2 64-bit Java version 8