Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Applicative credentials

Applicative credentials

Some applications require credentials in addition to the credentials that the host machine requires. Credentials required to access these applications are referred to as applicative credentials.

A typical credential contains a user name and a password for logging into a device or application. While most applications require only one credential for accessing them, sometimes hosts and applications have separate credentials for extra security. For example, ABAP SAP Central Services (ASCS) requires applicative credentials in addition to the SSH or Windows host credentials for the server that hosts ASCS.

Note: In Service Mapping and Discovery, devices and applications are referred to as configuration items (CIs).

Just like with host credentials, you assign applicative credentials to MID Servers.

You create applicative credentials per CI type, for example the CI type for ASCS is SAP ASCS Application [cmdb_ci_appl_sap_ascs]. The preconfigured pattern for discovering CIs belonging to this CI type contains commands that require a MID Server to use the applicative credential for this CI type. If there is more than one credential configured for this CI type, the MID Server tries using these credentials in the order you define until it finds the credential that fits.

Check the discovery requirements information in the ServiceNow documentation to determine if you need to configure applicative credentials for specific application CIs. There is no need to configure applicative credentials, if discovery prerequisites do not mention it.

Table 1. Applicative credentials form fields
Field Description
Name Name of the credential. Use a descriptive name like Oracle DB or London Oracle DB (for an Oracle database).
Active Select this check box to use this credential.
User name Enter the actual user name of the applicative credential.
Password Enter the actual password of the applicative credential.
CI type Select a CI type to which the CI belongs.
Credential alias Enter the table name for the CI type whose applicative credentials the application uses. Applications may use applicative credentials of a CI type different from their own.
For this application Select this table
ABAP SAP Central Services (ASCS) cmdb_ci_appl_sap_ascs
IBM Security Access Manager appliance cmdb_ci_app_server_webseal
SAP Central Instance cmdb_ci_appl_sap_ascs
SAP Central Services (SCS cmdb_ci_appl_sap_ascs
SAP Evaluated Receipt Settlement (ERS) cmdb_ci_appl_sap_ascs
SAP Java Cluster cmdb_ci_appl_sap_ascs
SAP NetWeaver Dialog Instance cmdb_ci_appl_sap_ascs
Microsoft Exchange Mailbox (for Microsoft Exchange) cmdb_ci_exchange_mailbox
Microsoft SQL Database cmdb_ci_db_mssql_instance
MySQL Server cmdb_ci_db_mysql_instance
Oracle Advanced Queue Queue cmdb_ci_db_ora_instance
Oracle Database cmdb_ci_db_ora_instance
Oracle E-Business Suite cmdb_ci_db_ora_instance
Oracle WebLogic Module cmdb_ci_app_server_weblogic
Tibco EMS Queue cmdb_ci_appl_tibco_message
Tibco Enterprise Message Service (EMS) cmdb_ci_appl_tibco_message
Applies to

Select whether to apply these credentials to All MID servers in your network, or to one or more Specific MID servers. Specify the MID Servers that should use these credentials in the MID servers field.

Order

Enter the order (sequence) in which the platform tries this credential as it attempts to log on to devices. The smaller the number, the higher in the list this credential appears. Establish credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number (or none), the instance tries the credentials in a random order.