J2EE Applications - Discovery & Transform without X-Ray
Discovery is the OmniDeq process to acquire the information about the process, which is running on the server, from the perspective of transforming it (the process), to be able to run in the container. This involves gathering information about all the files/folders relevant to the process. Once the information about the process is acquired, a subprocess called X-Ray is needed to gather the additional information about the incoming and outgoing connections by the process.
In case of the process that run Java Application servers, OmniDeq also provides the transformation of the individual Applications and its configurations into the Base J2EE containers, rather than the entire process itself. In case of J2EE applications, the X-Ray is not performed as the outgoing connections can be determined from the J2EE server configurations (configurations like DataSource, JMS, etc.). On Discovery, these applications are ready for transform without need for X-Ray.
The difference between X-Ray and Non-X-Ray is explained as X-ray Vs Non-Xray.
Once the phase 1 discovery is complete you can see the "process name-web application name" combination under the process-name column in Processes tab as below. Here the process name detected is "java" and one of the web-application running under it as "jenkins.war".
Please note the X-Ray is skipped. This means that without X-Ray you can immediately start transforming this web application.
Java Applications Server support matrix
App Server | Discover | Transform |
---|---|---|
Oracle WebLogic | 12.1.3, 12.2.1.4 | 12.1.3, 12.2.1.4 containers respectively |
IBM WebSphere | 8.x, 9.x | WebSphere Liberty |
Apache Tomcat | 7,8,9,10 | Tomcat 7/8/9/10 base containers respectively |
JBoss | EAP 6.1 | WilfFly 8.2.1.Final |