Mapping application services containing Oracle GlassFish Servers

Service Mapping can discover application services containing Oracle GlassFish Servers.

Discovered components

Name	Platform	Version	Protocol	Discovery type	Pattern (or probe if indicated)
Oracle GlassFish Server	Windows UNIX	3.1, 4.0, 4.1	WMI WinRM SSH	Horizontal and top-down	GlassFish Server
Oracle GlassFish WAR file	Windows UNIX	3.1, 4.0, 4.1	WMI WinRM SSH	Horizontal and top-down	GlassFish WAR

Map application services containing Oracle GlassFish Servers

Map an application service containing an Oracle GlassFish Server correctly.

Before you begin

• (If hosted on a Windows server) On the ServiceNow AI Platform, configure Windows credentials.
• (If hosted on a Linux or UNIX server) (Optional) on the ServiceNow AI Platform, configure SSH credentials.
• (Optional) For discovering using the WinRM protocol, see Configure WinRM trusted hosts on MID Server.

Role required: sm_admin

Procedure

1. Create an application service.
   1. Navigate to All > Service Mapping > Application Services.
   2. Click New.
      The Discoverable by Service Mapping option is selected by default.
   3. In the Name field, enter a descriptive name for the application service.
2. Define the entry point for this application service:
   1. Select the Other Application tile.
      The Discoverable by Service Mapping option is selected by default.
   2. Define the entry point by filling in the fields.

      Field	Description
      Select Entry Point Type	Entry point type: HTTP(S) Endpoint TCP Endpoint Tibco BW Endpoint
      URL	The URL of the process that correlates with the GlassFish Server, for example, http://10.196.xx.xx:28080/hello/. This field appears when HTTP(S) Endpoint is selected in Select Entry Point Type.
      Host	The server that hosts the GlassFish Server. This field appears when Tibco BW Endpoint or TCP Endpoint is selected in Select Entry Point Type.
      Host Name	The host name of the server that hosts the GlassFish Server. This field appears when HTTP(S) Endpoint is selected in Select Entry Point Type.
      Port	The port, which the process correlating with the GlassFish Server uses. This field appears when Tibco BW Endpointo r TCP Endpoint is selected in Select Entry Point Type.
      Process Name	The name of the process that correlates with the GlassFish Server. This field appears when Tibco BW Endpoint is selected in Select Entry Point Type.
      Comments	Free text comment to provide information on the endpoint. This field appears when HTTP(S) Endpoint or TCP Endpoint is selected in Select Entry Point Type.

   3. Click Add.
   4. Click Save.
3. Click Additional Info on the left and clear the Traffic based discovery check box.
4. Click Update.
5. Verify that the mapping result is satisfactory:
   1. Click View Map and wait until the mapping is complete.
      It may take a few minutes.
   2. Review the application service map and make sure that the service layout is as in the following example.

      
      
      

   In addition, verify that the GlassFish Server CIs are inclusions, each of which contains a WAR file.

If the mapping result is not as you expected, perform basic troubleshooting.

Symptom	Cause	Solution
Service Mapping fails to discover the GlassFish Server CI. The discovery log displays the following message: Process is not running or port is not correctFailed to identify CI due to the host 10.196.xx.xx lacking an application running on port 28080. Make sure that the application is running and run quick discovery on the host.	There is no process running on the port that is part of the entry point.	Make sure that the entry point is correct. If the entry point is correct, check that here is a process running on the port by running a quick discovery on the host.