Page tree
Skip to end of metadata
Go to start of metadata

Note

GlassFish Extended Discovery pattern is available only for ADDM 8.3 and later

Overview

This pattern extends the GlassFish discovery with additional data from the GlassFish configuration files and builds a J2EE inferred model of its applications and resources.

The pattern triggers off a GlassFish Server Software Instance (one of Oracle GlassFish Server, Oracle GlassFish Server Domain Administration Server, Sun GlassFish Enterprise Server, Sun GlassFish Enterprise Server Domain Administration Server, Sun Java System Application Server or Sun Java System Application Server Domain Administration Server) with the domain, instance and install_root attributes populated.

Configuration Options

There are several configuration options available for this Extended Discovery:

  • use_config_file := false; - allows to use configuration file-based discovery method
  • use_active_command := false; - allows to use active command-based discovery method

Domain Root

The pattern obtained domain root from the triggering SI's domain_root attribute or derived from the install_root and domain attributes:

  • <install_root>/domains/<domain>

J2EE Applications

If the configuration file-based discovery method is enabled in the Configuration Section, the pattern will attempt to read the following file:

  • <domain_root>/config/domain.xml

and extract application names from its contents via the following xpaths:

  • //applications/application/@name
  • //applications/j2ee-application/@name
  • //applications/web-module/@name

A SoftwareComponent, contained within the triggering SI, will be created for each application name.

JDBC Resources

For the triggering SI instance, the pattern will attempt to get its JNDI names from the contents of domain.xml using the following xpath:

  • //servers/server[@name='<instance>']/resource-ref/@ref

The pattern then attempts to get pool names for each JNDI name via the following xpath:

  • //resources/jdbc-resource[@jndi-name='<jndi_name>']/@pool-name

The pattern then attempts to get the JDBC URLs for each poolname using the following xpath:

  • //resources/jdbc-connection-pool[@name='<poolname>']/property[@name='URL']/@value

For each successfully parsed JDBC URL, the pattern creates a detail node linked to the triggering SI.

Mail Resources

The same domain.xml file is read and processed in order to get needed modeling information. The JNDI name of the Mail Resource is obtained from read file by using the following XPath queries:

  • jndi_name: //resources/mail-resource/@jndi-name

  • description: //resources/mail-resource/@description

  • mailserver_name: //resources/mail-resource/@host

after which a detail node is created and linked to the triggering SI.