Java Supported Environment
Java agent support environment
Before installing the agent, make sure that the JVM application server meets the following specifications.
It can be applied not only to Web Application Server (WAS) but also to all applications running on JVM, such as daemons and batch applications. For the versions earlier than Java 1.6, contact support@whatap.io or see the following.
Supported Versions
| Category / JDK Version | Java 6 ~ 21 | Java 22 ~ 26 |
|---|---|---|
| Support | ✅ | ✅ |
| Support Level | Limited Support | Fully support |
Java 25 and 26 are supported by Java agent 2.2.67 or later. For more information, see the Java Agent v2.2.67 release notes.
Operating System
| OS Family | Supported Version | Architecture |
|---|---|---|
| Unix | HP-UX 11.x | 32bit, 64bit |
| Oracle Solaris 2.8, 2.9, 10, 11 | 32bit, 64bit | |
| Linux | Red Hat | Itanium 64bit |
| x86 Intel Linux | 32bit | |
| Windows | Windows Server | 2000 or later |
| Windows | XP or later | |
| Others | Itanium | 64bit |
Supports all operating systems that can install JDK 6.
Application Server
| Vendor | Product | Supported Version |
|---|---|---|
| Apache | Jakarta Tomcat | 6.x ~ 10.x |
| Red Hat | JBoss Application Server | 6.x, 7.x |
| TmaxSoft | JEUS | 6.x, 7.x |
| Oracle | WebLogic Server | 9.x ~ 12.x |
| GlassFish | 3.x ~ 5.x | |
| SUN Application Server | 8.x, 9.x | |
| IBM | WebSphere, WebSphere Liberty | - |
| BlueMix | - | |
| Caucho | Resin | 3.x, 4.x |
| Eclipse | Jetty | - |
| Fujitsu | Interstage | 5.x ~ 7.x |
| Hitachi | Cosminexus | 7.x ~ 9.x |
| AWS | Elastic Beanstalk | - |
| Docker | Container Environment | - |
Supports all application servers that comply with Java EE Spec. See this link for details.
Framework / Library
| Category | Framework | Supported Version |
|---|---|---|
| Web Framework | Spring Boot | 1.5.x ~ 3.x |
| Async Framework | Netty | - |
| Akka HTTP | - | |
| Play Framework | - | |
| Microservices | Quarkus | - |
| Quarkus Reactive | 1.x ~ 2.x | |
| Integration Framework | Mule Framework | 3.9.5, 4.5 |
Supports all libraries that operate on Application Servers complying with Java EE Spec.
Database Driver
| Category | Database | Driver | Supported Version |
|---|---|---|---|
| RDBMS | Generic | JDBC | any compliant driver |
| MySQL | JDBC | 5.x ~ 8.x | |
| AWS MySQL | JDBC | 1.x | |
| MariaDB | JDBC | 1.x ~ 3.x | |
| PostgreSQL | JDBC | - | |
| Oracle | ojdbc | 5, 6, 7, 8, 14 | |
| Microsoft SQL Server | JDBC | - | |
| DB2 | JDBC | - | |
| Derby | JDBC | - | |
| H2 | JDBC | - | |
| jTDS | JDBC | - | |
| Tibero | - | - | |
| NoSQL | Redis | Jedis | - |
| Redis | Lettuce | 5.x ~ 6.x |
Compatibility and data sources for each application server
Tomcat
Compatibility
| WAS Ver. | Java SE 6 (jdk1.6.0) | Java SE 7 (jdk1.7.0_80) | Java SE 8 (jdk1.8.0_91) |
|---|---|---|---|
| Tomcat 6 | ✅ | ✅ | ✅ |
| Tomcat 7 | ✅ | ✅ | ✅ |
| Tomcat 8 | ❌ | ✅ | ✅ |
| Tomcat 9 | ❌ | ❌ | ✅ |
| WAS Ver. | OpenJDK 6 (1.6.0_45) | OpenJDK 7 (1.7.0_80) | OpenJDK 8 (1.8.0_91) |
|---|---|---|---|
| Tomcat 6 | ✅ | ✅ | ✅ |
| Tomcat 7 | ✅ | ✅ | ✅ |
| Tomcat 8 | ❌ | ✅ | ✅ |
| Tomcat 9 | ❌ | ❌ | ✅ |
| WAS Ver. | ibm-java-x86_64-60 | ibm-java-x86_64-71 | ibm-java-x86_64-80 |
|---|---|---|---|
| Tomcat 6 | ✅ | ✅ | ✅ |
| Tomcat 7 | ✅ | ✅ | ✅ |
| Tomcat 8 | ❌ | ✅ | ✅ |
| Tomcat 9 | ❌ | ❌ | ✅ |
DataSource
| DB | JDBC Driver file name | JDBC Ver. | JDK Ver. | Compatibility |
|---|---|---|---|---|
| MySQL | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| MariaDB | mariadb-java-client-1.4.6.jar | 1.4.6 | JDK 1.7.0_80 | ✅ |
| PostgreSQL | postgresql-9.4.1209.jre7.jar | 9.4.1209 | JDK 1.7.0_80 | ✅ |
| Amazon Aurora | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| Oracle | ojdbc6-11.2.0.2.0.jar | 11.2.0.2.0 | JDK 1.7.0_80 | ✅ |
| DB2 | db2jcc.jar, db2jcc_license_cu.jar | 1.4.2 | JDK 1.7.0_80 | ✅ |
JBoss
Compatibility
| WAS Ver. | Java SE 6 (jdk1.6.0) | Java SE 7 (jdk1.7.0_80) | Java SE 8 (jdk1.8.0_91) |
|---|---|---|---|
| JBOSS EAP 7.0 (standalone) | ❌ | ❌ | ✅ |
| JBOSS EAP 6.1.1 (standalone) | ❌ | ✅ | ❌ |
| JBOSS EAP 6.2 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 6.3 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 6.4 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 7.0 (domain) | ❌ | ❌ | ✅ |
| JBOSS AS 5.1.0 (default) | ✅ | ✅ | ✅ |
| WAS Ver. | OpenJDK 6 (1.6.0_45) | OpenJDK 7 (1.7.0_80) | OpenJDK 8 (1.8.0_91) |
|---|---|---|---|
| JBOSS EAP 7.0 (standalone) | ❌ | ❌ | ✅ |
| JBOSS EAP 6.1.1 (standalone) | ❌ | ✅ | ❌ |
| JBOSS EAP 6.2 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 6.3 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 6.4 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 7.0 (domain) | ❌ | ❌ | ✅ |
| JBOSS AS 5.1.0 (default) | ✅ | ✅ | ✅ |
| WAS Ver. | ibm-java-x86_64-60 | ibm-java-x86_64-71 | ibm-java-x86_64-80 |
|---|---|---|---|
| JBOSS EAP 7.0 (standalone) | ❌ | ❌ | ✅ |
| JBOSS EAP 6.1.1 (standalone) | ❌ | ✅ | ❌ |
| JBOSS EAP 6.2 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 6.3 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 6.4 (standalone) | ❌ | ✅ | ✅ |
| JBOSS EAP 7.0 (domain) | - | - | - |
| JBOSS AS 5.1.0 (default) | ✅ | ✅ | ✅ |
DataSource
| DB | JDBC Driver file name | JDBC Ver. | JDK Ver. | Compatibility |
|---|---|---|---|---|
| MySQL | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| MariaDB | mariadb-java-client-1.4.6.jar | 1.4.6 | JDK 1.7.0_80 | ✅ |
| PostgreSQL | postgresql-9.4.1209.jre7.jar | 9.4.1209 | JDK 1.7.0_80 | ✅ |
| Amazon Aurora | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| Oracle | ojdbc6-11.2.0.2.0.jar | 11.2.0.2.0 | JDK 1.7.0_80 | ✅ |
| DB2 | db2jcc.jar, db2jcc_license_cu.jar | 1.4.2 | JDK 1.7.0_80 | ✅ |
JEUS
Compatibility
| WAS Ver. | Java SE 6 (jdk1.6.0) | Java SE 7 (jdk1.7.0_80) | Java SE 8 (jdk1.8.0_91) |
|---|---|---|---|
| JEUS 7 | ✅ | ✅ | ✅ |
| JEUS 6 | ✅ | ✅ | ✅ |
| WAS Ver. | OpenJDK 6 (1.6.0_45) | OpenJDK 7 (1.7.0_80) | OpenJDK 8 (1.8.0_91) |
|---|---|---|---|
| JEUS 7 | ✅ | ✅ | ✅ |
| JEUS 6 | ✅ | ✅ | ✅ |
| WAS Ver. | ibm-java-x86_64-60 | ibm-java-x86_64-71 | ibm-java-x86_64-80 |
|---|---|---|---|
| JEUS 7 | ✅ | ✅ | ✅ |
| JEUS 6 | ✅ | ✅ | ❌ |
DataSource
| DB | JDBC Driver file name | JDBC Ver. | JDK Ver. | Compatibility |
|---|---|---|---|---|
| MySQL | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| MariaDB | mariadb-java-client-1.4.6.jar | 1.4.6 | JDK 1.7.0_80 | ✅ |
| PostgreSQL | postgresql-9.4.1209.jre7.jar | 9.4.1209 | JDK 1.7.0_80 | ✅ |
| Amazon Aurora | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| Oracle | ojdbc6-11.2.0.2.0.jar | 11.2.0.2.0 | JDK 1.7.0_80 | ✅ |
| DB2 | db2jcc.jar, db2jcc_license_cu.jar | 1.4.2 | JDK 1.7.0_80 | ✅ |
WebSphere
Compatibility
| WAS Ver. | ibm-java-x86_64-60 |
|---|---|
| 8.5.5.10 | ✅ |
DataSource
| DB | JDBC Driver file name | JDBC Ver. | JDK Ver. | Compatibility |
|---|---|---|---|---|
| Mysql | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| Oracle | ojdbc6-11.2.0.2.0.jar | 11.2.0.2.0 | JDK 1.7.0_80 | ✅ |
JETTY
Compatibility
| WAS Ver. | Java SE 6 (jdk1.6.0) | Java SE 7 (jdk1.7.0_80) | Java SE 8 (jdk1.8.0_91) |
|---|---|---|---|
| Jetty 8.1.21 | ❌ | ✅ | ✅ |
| Jetty 9.2.18 | ❌ | ✅ | ✅ |
| Jetty 9.3.12 | ❌ | ❌ | ✅ |
| WAS Ver. | ibm-java-x86_64-60 | ibm-java-x86_64-71 | ibm-java-x86_64-80 |
|---|---|---|---|
| Jetty 8.1.21 | ❌ | ✅ | ✅ |
| Jetty 9.2.18 | ❌ | ✅ | ✅ |
| Jetty 9.3.12 | ❌ | ❌ | ✅ |
DataSource
| DB | JDBC Driver file name | JDBC Ver. | JDK Ver. | Compatibility |
|---|---|---|---|---|
| MySQL | mysql-connector-java-5.1.39-bin.jar | 5.1.39 | JDK 1.7.0_80 | ✅ |
| Oracle | ojdbc6-11.2.0.2.0.jar | 11.2.0.2.0 | JDK 1.7.0_80 | ✅ |
Common supported environment
Service deployment models
You can use WhaTap Monitoring as a SaaS or on-premises (self-hosted) service. Whichever you choose, you use the same agents and the same monitoring features.
| Deployment | Support | Description |
|---|---|---|
| SaaS | ✅ | Connects to collection servers operated by WhaTap. See the firewall section for regional addresses |
| On-premises (self-hosted) | ✅ | Collection servers you build and operate yourself (air-gapped environments supported). Contact your sales representative for the scope |
You can also deploy WhaTap on-premises in air-gapped environments without internet connectivity.
Feature differences by deployment model
Whichever you choose, the monitoring features are the same. The mobile app is the only exception and is available on the service.whatap.io SaaS service only.
To use certain features on-premises, a separate agreement is required.
Supporting the browser
WhaTap Monitoring is available in web browsers and mobile Apps.
| Browser | Recommended | Supported version |
|---|---|---|
| Google Chrome | ✅ | 111 or later |
| Mozilla FireFox | ❌ | Latest version |
| Edge | ❌ | Latest version |
| Safari | ❌ | Latest version |
Support guidance
- For browser compatibility and performance reasons, the latest version of Chrome is recommended.
- The user interface (UI) is implemented using HTML5 standard technologies, so Internet Explorer is not supported.
Limitations
WhaTap’s web interface does not support mobile browsers. To access WhaTap on a mobile device, install the WhaTap app for Android or iOS. The WhaTap mobile app is optimized for mobile environments. For more information about the WhaTap mobile app, see this document.
Firewall
The WhaTap agent must be able to access the collection server through TCP port 6600. Allow access to the collection server address that is closest to the monitored target.
Source: WhaTap agent
| Cloud | Destination | Destination IP | Port |
|---|---|---|---|
| AWS | WhaTap collection server (Seoul) | 13.124.11.223 / 13.209.172.35 | TCP 6600 |
| WhaTap collection server (Tokyo) | 52.68.36.166 / 52.193.60.176 | TCP 6600 | |
| WhaTap collection server (Singapore) | 18.138.0.93 / 18.139.67.236 | TCP 6600 | |
| WhaTap collection server (Jakarta) | 108.136.91.69 / 108.137.158.44 | TCP 6600 | |
| WhaTap collection server (Thailand) | 43.209.109.219 / 43.209.48.86 | TCP 6600 | |
| WhaTap collection server (Mumbai) | 13.127.125.69 / 13.235.15.118 | TCP 6600 | |
| WhaTap collection server (California) | 52.8.223.130 / 52.8.239.99 | TCP 6600 | |
| WhaTap collection server (Virginia) | 107.23.220.101 / 54.236.221.105 | TCP 6600 | |
| WhaTap collection server (Frankfurt) | 3.125.142.162 / 3.127.76.140 | TCP 6600 | |
| Azure | WhaTap collection server (Seoul) | 52.231.66.38 / 20.194.5.115 | TCP 6600 |
| WhaTap collection server (Tokyo) | 52.246.169.54 / 20.210.27.232 | TCP 6600 | |
| Kakao | WhaTap collection server (Seoul) | 61.109.237.237 / 61.109.238.166 | TCP 6600 |
If the agent cannot directly access the collection server, use the provided proxy module to access it.
Mobile app
The WhaTap mobile app supports both Android and iOS environments. You can install the WhaTap app by following the link or scanning the QR code. For detailed information about the mobile app, see the following.
| iOS | Android |
|---|---|
 iOS 12 or later |  Android 5.0 or later |