IBM WebSEAL discovery
The ® Discovery application uses the IBM WebSEAL patterns to find WebSEAL applications, web application servers, and junctions on your infrastructure. Discovering some of these resources requires installing the Discovery and Service Mapping Patterns application from the ® Store.
Request apps on the Store
Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Prerequisites
Detailed information on IBM WebSEAL
For information, see Detailed information on products discovered by ITOM Visibility
Authentication
The WebSEAL authentication process includes HTTP header authentication with basic credentials Basic authentication credentials.
If you’re running discovery for the first time, configure Credential affinity for Discovery and Orchestration Credential affinity for Discovery and Orchestration.
Note: Credential affinity isn’t available In debug mode.
Configured MID Server
Ensure the MID Server has access and permissions to send HTTPS requests to the WebSEAL application.
Configured user permissions to execute API calls
Ensure that the user has the permission to run the following API:
/net/general
/net/dns
/wga/reverseproxy
/wga/reverseproxy/<reverse_proxy_id>/configuration/stanza/junction/entry_name/match-vhj-first
/wga/reverseproxy/<reverse_proxy_id>/junctions
/wga/reverseproxy/"<reverse_proxy_id>/junctions?junctions_id=<junction_id>
/wga/widgets/health.json
HTTP Classification enabled
The IBM WebSEAL Pattern is triggered when you run the discovery on the server that the WebSEAL is on. Ensure that the HTTP Classification is present in the instance. For more information, see Create an HTTP classification and Run discovery through an HTTP or HTTPS REST call
Data collected during horizontal discovery
| Field | Description |
|---|---|
| ISAM Server \[cmdb\_ci\_isam\_server\] | |
| name | The name of the server as returned by the `/net/general` API call. If the field is empty, `nslookup` on the IP address would be attempted to populate this field. |
| IP Address \[ip\_address\] | The IP address according to the discovery schedule/configuration. |
| fqdn | The `search_domain` returned by the`/net/dns` API call. |
| WebSEAL \[cmdb\_ci\_app\_server\_webseal\] | |
| name | The name of the WebSEAL server as returned by the API. |
| IP Address \[ip\_address\] | The IP address according to the discovery schedule/configuration. |
| fqdn | The `search_domain` returned by the`/net/dns` API call. |
| install\_status | The status is set to installed by default. |
| operation\_status | The status is set to operational by default. |
| install\_directory | According to the identification requirement, this field is populated with the FQDN of the server. |
| WebSEAL Reverse Proxies \[cmdb\_ci\_webseal\_reverse\_proxy\] | |
| name | The name of the resource according to the API response. |
| object\_id | The ID of the resource, of the API response. |
| install\_status | Indicates if the installation is enabled. |
| operational\_status | Indicates if the operation has started. |
| service\_type – hard-coded | The status is set to `Webseal Reverse Proxy`by default. |
| webseal\_health\_status | The WebSEAL reported health status regarding the `/wga/widgets/health.json` API call |
| WebSEAL Junctions \[cmdb\_ci\_webseal\_junction\] | |
| name | The name of the resource according to the API response. |
| object\_id | The id of the resource, created as a unique hash number corresponding to the case-sensitive name of the resource. Note: The case insensitivity of the queries may create duplicate fields when the name value is identical to the Object ID value. One of the identification attributes must be changed to have a unique value. |
| install\_status | Hard-coded to installed status |
| operational\_status | Hard-coded to operational status |
| stateful\_junction | Boolean value indicating whether it’s a stateful Junction |
| transparent\_path\_junction | Boolean value indicating whether it’s a transparent path Junction |
| junction\_type | List for the type of the Junction |
| WebSEAL Backend Servers \[cmdb\_ci\_webseal\_backend\_server\] | |
| name | the name of the resource, as per API response |
| object\_id | the id of the resource, as per API response |
| install\_status | the status of the resource as per the “enabled” value in the API response |
| operational\_status | the status of the resource as per the “operation state” value |
| server\_id | The UUID used to identify the junction web server |
| http\_port | HTTP port of the back-end third-party server. Applicable when the junction type is tcp. |
| service\_port | TCP port of the back-end third-party server. Default is 80 for TCP junctions and 443 for SSL junctions |
| Priority | The priority of the server \(1-9\). Default is 9. |
| CI | Relationship Type | CI |
|---|---|---|
| Webseal \[cmdb\_ci\_app\_server\_webseal\] | Runs on::Runs | ISAM Server \[cmdb\_ci\_isam\_server\] |
| Webseal Reverse Proxy \[cmdb\_ci\_webseal\_reverse\_proxy\] | Hosted on::Hosts Reference\[load\_balancer\] | Webseal \[cmdb\_ci\_app\_server\_webseal\] |
| Webseal Reverse Proxy \[cmdb\_ci\_webseal\_reverse\_proxy\] | Runs on::Runs Reference\[isam\_server\] | ISAM Server \[cmdb\_ci\_isam\_server\] |
| Webseal Junction \[cmdb\_ci\_webseal\_junction\] | Allocated to::Allocates Reference \[service\] | Webseal Reverse Proxy \[cmdb\_ci\_webseal\_reverse\_proxy\] |
| Webseal Junction \[cmdb\_ci\_webseal\_junction\] | Owns::Owned by Reference \[pool\] | Load Balancer Pool Member \[cmdb\_ci\_webseal\_backend\_server\] |
| Webseal Junction \[cmdb\_ci\_webseal\_junction\] | Reference only \[load\_balancer\] | Webseal \[cmdb\_ci\_app\_server\_webseal\] |
Note: Currently, the relation between the back-end servers and actual server CIs in the CMDB isn’t possible for HD.
Parent Topic:Available on-premise discovery patterns