{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30129,"path":"it-operations-management/discovery-and-service-mapping-patterns/ibm_webseal_discovery_patterns.md","title":"IBM WebSEAL discovery","bundle":null,"doc_type":null,"release":"australia","body":"\n# IBM WebSEAL discovery\n\nThe ® 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.\n\n## Request apps on the Store\n\nVisit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\n## Prerequisites\n\n- **Detailed information on IBM WebSEAL**\n\n For information, see [Detailed information on products discovered by ITOM Visibility](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/itom-visibility/r_SupportedApplications.md)\n\n- **Authentication**\n\n The WebSEAL authentication process includes HTTP header authentication with basic credentials [Basic authentication credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/r_BasicAuthCredentialsForm.md).\n\n If you’re running discovery for the first time, configure Credential affinity for Discovery and Orchestration [Credential affinity for Discovery and Orchestration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/c_CredentialAffinity.md).\n\n **Note:** Credential affinity isn’t available In debug mode.\n\n- **Configured MID Server**\n\n Ensure the MID Server has access and permissions to send HTTPS requests to the WebSEAL application.\n\n- **Configured user permissions to execute API calls**\n\n Ensure that the user has the permission to run the following API:\n\n - /net/general\n\n - /net/dns\n\n - /wga/reverseproxy\n\n - /wga/reverseproxy/<reverse\\_proxy\\_id>/configuration/stanza/junction/entry\\_name/match-vhj-first\n\n - /wga/reverseproxy/<reverse\\_proxy\\_id>/junctions\n - /wga/reverseproxy/\"<reverse\\_proxy\\_id>/junctions?junctions\\_id=<junction\\_id>\n\n - /wga/widgets/health.json\n\n- **HTTP Classification enabled**\n\n 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/create-an-http-classifier.md) and [Run discovery through an HTTP or HTTPS REST call](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/itom-visibility/run-http-discovery.md)\n\n\n## Data collected during horizontal discovery\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nISAM Server \\[cmdb\\_ci\\_isam\\_server\\] \n\n
\n\nname\n\n\n\nThe 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.\n\n
\n\nIP Address \\[ip\\_address\\]\n\n\n\nThe IP address according to the discovery schedule/configuration.\n\n
\n\nfqdn\n\n\n\nThe `search_domain` returned by the`/net/dns` API call.\n\n
\n\nWebSEAL \\[cmdb\\_ci\\_app\\_server\\_webseal\\]\n\n
\n\nname\n\n\n\nThe name of the WebSEAL server as returned by the API.\n\n
\n\nIP Address \\[ip\\_address\\]\n\n\n\nThe IP address according to the discovery schedule/configuration.\n\n
\n\nfqdn\n\n\n\nThe `search_domain` returned by the`/net/dns` API call.\n\n
\n\ninstall\\_status\n\n\n\nThe status is set to **installed** by default.\n\n
\n\noperation\\_status\n\n\n\nThe status is set to **operational** by default.\n\n
\n\ninstall\\_directory\n\n\n\nAccording to the identification requirement, this field is populated with the FQDN of the server.\n\n
\n\nWebSEAL Reverse Proxies \\[cmdb\\_ci\\_webseal\\_reverse\\_proxy\\]\n\n
\n\nname\n\n\n\nThe name of the resource according to the API response.\n\n
\n\nobject\\_id\n\n\n\nThe ID of the resource, of the API response.\n\n
\n\ninstall\\_status\n\n\n\nIndicates if the installation is enabled.\n\n
\n\noperational\\_status\n\n\n\nIndicates if the operation has started.\n\n
\n\nservice\\_type – hard-coded\n\n\n\nThe status is set to `Webseal Reverse Proxy`by default.\n\n
\n\nwebseal\\_health\\_status\n\n\n\nThe WebSEAL reported health status regarding the `/wga/widgets/health.json` API call\n\n
\n\nWebSEAL Junctions \\[cmdb\\_ci\\_webseal\\_junction\\]\n\n
\n\nname\n\n\n\nThe name of the resource according to the API response.\n\n
\n\nobject\\_id\n\n\n\nThe id of the resource, created as a unique hash number corresponding to the case-sensitive name of the resource.\n\n**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.\n\n
\n\ninstall\\_status\n\n\n\nHard-coded to installed status\n\n
\n\noperational\\_status\n\n\n\nHard-coded to operational status\n\n
\n\nstateful\\_junction\n\n\n\nBoolean value indicating whether it’s a stateful Junction\n\n
\n\ntransparent\\_path\\_junction\n\n\n\nBoolean value indicating whether it’s a transparent path Junction\n\n
\n\njunction\\_type\n\n\n\nList for the type of the Junction\n\n
\n\nWebSEAL Backend Servers \\[cmdb\\_ci\\_webseal\\_backend\\_server\\]\n\n
\n\nname\n\n\n\nthe name of the resource, as per API response\n\n
\n\nobject\\_id\n\n\n\nthe id of the resource, as per API response\n\n
\n\ninstall\\_status\n\n\n\nthe status of the resource as per the “enabled” value in the API response\n\n
\n\noperational\\_status\n\n\n\nthe status of the resource as per the “operation state” value\n\n
\n\nserver\\_id\n\n\n\nThe UUID used to identify the junction web server\n\n
\n\nhttp\\_port\n\n\n\nHTTP port of the back-end third-party server. Applicable when the junction type is tcp.\n\n
\n\nservice\\_port\n\n\n\nTCP port of the back-end third-party server. Default is 80 for TCP junctions and 443 for SSL junctions\n\n
\n\nPriority\n\n\n\nThe priority of the server \\(1-9\\). Default is 9.\n\n
\n
\n\nCI\n\n\n\nRelationship Type\n\n\n\nCI\n\n
\n\nWebseal \\[cmdb\\_ci\\_app\\_server\\_webseal\\]\n\n\n\nRuns on::Runs\n\n\n\nISAM Server \\[cmdb\\_ci\\_isam\\_server\\]\n\n
\n\nWebseal Reverse Proxy \\[cmdb\\_ci\\_webseal\\_reverse\\_proxy\\]\n\n\n\nHosted on::Hosts\n\n Reference\\[load\\_balancer\\]\n\n\n\nWebseal \\[cmdb\\_ci\\_app\\_server\\_webseal\\]\n\n
\n\nWebseal Reverse Proxy \\[cmdb\\_ci\\_webseal\\_reverse\\_proxy\\]\n\n\n\nRuns on::Runs\n\n Reference\\[isam\\_server\\]\n\n\n\nISAM Server\n\n \\[cmdb\\_ci\\_isam\\_server\\]\n\n
\n\nWebseal Junction \\[cmdb\\_ci\\_webseal\\_junction\\]\n\n\n\nAllocated to::Allocates\n\n Reference \\[service\\]\n\n\n\nWebseal Reverse Proxy \\[cmdb\\_ci\\_webseal\\_reverse\\_proxy\\]\n\n
\n\nWebseal Junction \\[cmdb\\_ci\\_webseal\\_junction\\]\n\n\n\nOwns::Owned by\n\n Reference \\[pool\\]\n\n\n\nLoad Balancer Pool Member \\[cmdb\\_ci\\_webseal\\_backend\\_server\\]\n\n
\n\nWebseal Junction \\[cmdb\\_ci\\_webseal\\_junction\\]\n\n\n\nReference only \\[load\\_balancer\\]\n\n\n\nWebseal \\[cmdb\\_ci\\_app\\_server\\_webseal\\]\n\n
**Note:** Currently, the relation between the back-end servers and actual server CIs in the CMDB isn’t possible for HD.\n\n**Parent Topic:**[Available on-premise discovery patterns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/available-patterns.md)\n\n"}}