{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":49098,"path":"servicenow-platform/service-graph-connectors/configure-appdynamics-integration.md","title":"Configure Service Graph Connector for Observability - AppDynamics using the guided setup","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure Service Graph Connector for Observability - AppDynamics using the guided setup\n\nSet up scheduled import jobs to pull in data from AppDynamics into your Configuration Management Database \\(CMDB\\).\n\n## Before you begin\n\n**Important:** Unless there are configuration issues, use SGC Central to configure the connection. The guided setup method for configuration is being deprecated.\n\nTo use this Service Graph Connector, you need a subscription to a Subscription Unit that is based in the IT Operations Management \\(ITOM\\) Visibility application or in the ITOM Discovery application. As defined in the section titled \"Managed IT Resource Types\" in [ServiceNow Subscription Unit Overview](https://www.servicenow.com/products/entitlements-packages.html) for your subscription, for managed IT resources that are created or modified in the CMDB by this Service Graph Connector, but that aren’t yet managed by [ITOM Visibility or ITOM Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/itom-license-module.md), these resources will increase Subscription Unit consumption from that application. Review your current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.\n\nDependencies and requirements:\n\n-   The [Integration Commons for CMDB](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/cmdb-integration-commons/integration-commons-for-cmdb.md) store app, which is automatically installed.\n-   The CMDB CI class models store app, which is automatically installed. See [CMDB CI Class Models app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/cmdb-ci-class-models/cmdb-ci-class-models.md).\n-   The ITOM Discovery License plugin \\(com.snc.itom.discovery.license\\). You must activate this plugin.\n-   ITOM Licensing plugin \\(com.snc.itom.license\\). For more information, see [Request Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/t_ActivateTheDiscoveryPlugin.md).\n-   The Datastream Action plugin \\(com.glide.hub.action\\_type.datastream\\), which is automatically installed.\n-   Observability Commons for CMDB \\(sn\\_observability\\), which is only required for event ingestion. This must be installed prior to installing the connector for Event Management to work. For more information, see [Observability Commons for CMDB](https://store.servicenow.com/sn_appstore_store.do#!/store/application/97e04562072020107add6a77c4a9351a) on the ServiceNow Store.\n\nWhen using client credentials for authentication, obtain the OAuth credentials from your AppDynamics administrator. Make a note of the following details:\n\n-   Application \\(client\\) ID\n-   Client Secret\n\n**Note:** If you have an earlier version of the Service Graph Connector for Observability - AppDynamics, then do not migrate data from the old connector. You must uninstall the previous version and run the new integration.\n\nRole required: SGC-Admin \\(sn\\_cmdb\\_int\\_util.sgc\\_admin\\) or admin\n\n**Note:** The admin user role is required to run background scripts and to provide access to global tables to the SGC-Admin user. For information about the user roles for Service Graph Connectors, see [Service Graph Connector user roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/cmdb-sgc-intro.md).\n\n## Procedure\n\n1.  Ensure that the application scope is set to the Service Graph Connector for Observability - AppDynamics application by using the application picker.\n\n    For more information, see [Application picker](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/c_ApplicationPicker.md).\n\n2.  Navigate to **All** &gt; **Service Graph Connectors** &gt; **AppDynamics** &gt; **Setup**.\n\n3.  On the Getting started page, select **Get Started**.\n\n4.  Configure the authentication credentials and establish an HTTP connection to send requests to the AppDynamics API.\n\n    1.  In the Configure API authentication section of the Service Graph Connector for Observability - AppDynamics page, select **Get Started**.\n\n    2.  Configure the connection for AppDynamics by editing the default connection.\n\n        You can configure either a Basic Auth connection or an OAuth connection.\n\n        **Note:** As the connector supports only single instance, edit the **AppDynamicsConnectionAlias** connection, available by default.\n\n        -   Configure a Basic Auth connection.\n            1.  For the Configure Basic Auth Connection task, select **Configure**.\n            2.  Select **Edit** for AppDynamicsConnectionAlias.\n\n                **Note:** If not redirected to the connection setup, search for **AppDynamicsConnectionAlias** on the Integrations page, and then select **View Details** to edit the default connection.\n\n            3.  In the Connection Information section of the Edit Connection window, fill in the fields.\n\n<table id=\"table_umb_r4t_zfc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nConnection name\n\n</td><td>\n\nName to identify the AppDynamics connection record.`AppDynamicsConnectionAlias` is the default credential alias name and is read-only.\n\n</td></tr><tr><td>\n\nHost name\n\n</td><td>\n\nHost name of your AppDynamics controller.\n\n</td></tr></tbody>\n</table>            4.  \\(Optional\\) If a MID Server is required for the AppDynamics server connection, select the **Use MID server** check box. Then, select the MID Server-related fields accordingly.\n            5.  In the Credential Information section of the Edit Connection window, fill in the fields.\n\n<table id=\"table_vmb_r4t_zfc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nUsername\n\n</td><td>\n\nAppDynamics account user name that is used to authenticate the connection request.**Note:** Verify that Server Visibility is active for the AppDynamics account and the AppDynamics user has the Applications and Dashboards Viewer \\(Default\\) and Server Monitoring User \\(Default\\) roles.\n\n</td></tr><tr><td>\n\nPassword\n\n</td><td>\n\nPassword that is used to authenticate the connection request.\n\n</td></tr></tbody>\n</table>            6.  Select **Edit Connection**.\n            7.  Return to the guided setup page.\n            8.  Set the Configure Basic Auth Connection task to complete by selecting **Mark as Complete**.\n        -   Configure an OAuth connection.\n            1.  For the Configure OAuth Authentication: Client Credentials task, select **Configure**.\n            2.  Select **Edit** for AppDynamicsConnectionAlias.\n\n                **Note:** If not redirected to the connection setup, search for **AppDynamicsConnectionAlias** on the Integrations page, and then select **View Details** to edit the default connection.\n\n            3.  In the Connection Information section of the Edit Connection window, fill in the fields.\n\n<table id=\"table_rsj_ppt_zfc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nConnection name\n\n</td><td>\n\nName to identify the AppDynamics connection record.`AppDynamicsConnectionAlias` is the default credential alias name and is read-only.\n\n</td></tr><tr><td>\n\nConnection URL\n\n</td><td>\n\nBase URL of your AppDynamics controller.\n\n</td></tr></tbody>\n</table>            4.  \\(Optional\\) If a MID Server is required for the AppDynamics server connection, select the **Use MID server** check box. Then, select the MID Server-related fields accordingly.\n            5.  In the Credential Information section of the Edit Connection window, fill in the fields.\n\n<table id=\"table_ssj_ppt_zfc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nOAuth Client ID\n\n</td><td>\n\nApplication \\(client\\) ID of your AppDynamics client application as noted in the [Before you begin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-graph-connectors/configure-appdynamics-integration.md) section.**Note:** Verify that the API client has a role with the required privileges and sufficient Token Expiration Time.\n\n</td></tr><tr><td>\n\nOAuth Client Secret\n\n</td><td>\n\nClient secret of your AppDynamics client application as noted in the [Before you begin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-graph-connectors/configure-appdynamics-integration.md) section.\n\n</td></tr></tbody>\n</table>            6.  Select **Edit Connection**.\n            7.  Return to the guided setup page.\n            8.  Set the Configure OAuth Authentication: Client Credentials task to complete by selecting **Mark as Complete**.\n    3.  Test the connection.\n\n        1.  For the Test connection task, select **Configure**.\n        2.  Select the **Test Connection** related link to start the testing process.\n        3.  When the **Status** field is set to **Success**, return to the guided setup page.\n\n            **Note:** If any of the tests have errors, follow the suggestions for remediation.\n\n        4.  Set the Test the connection task to complete by selecting **Mark as Complete**.\n    4.  Enable AppDynamics event integration with your ServiceNow instance by pushing a default HTTP Request Template to AppDynamics.\n\n        **Note:** To push HTTP requests, verify that the Observability Commons for CMDB application \\(sn\\_observability\\) is installed for events ingestion on your ServiceNow instance. Also, on your AppDynamics instance, as the ServiceNow user, you must have the account-level Configure HTTP Request Templates permission to create or modify HTTP Request Templates.\n\n        1.  For the Push HTTP Request Template task, select **Configure**.\n        2.  Select the **Push HTTP Request Template** related link.\n        3.  Return to the guided setup page.\n        4.  Set the Push HTTP Request Template task to complete by selecting **Mark as Complete**.\n        After you push the HTTP request template, multiple API calls are executed to start the event ingestion service in AppDynamics. For more information, see the [Service Graph Connector for Observability AppDynamics](https://www.servicenow.com/community/cmdb-blog/service-graph-connector-for-observability-appdynamics/ba-p/2275530) article on the ServiceNow Community site.\n\n5.  Configure duplicate detection rules.\n\n    1.  For the Configure duplicate detection rules task in the Duplicate detection rules section, select **Configure**.\n\n    2.  In the CMDB Duplicate Row Rules list, set the **Active** column value for a rule to **true** to activate the rule.\n\n        **Note:** To remove fields from being evaluated, add the field names in the **Ignore Fields** column for a rule. To ignore multiple fields, separate the fields with commas.\n\n    3.  Return to the guided setup page.\n\n    4.  Set the Configure duplicate detection rules task to complete by selecting **Mark as Complete**.\n\n6.  Configure advanced settings.\n\n    1.  For the Advanced Settings task in the Advanced section, select **Configure**.\n\n    2.  Review and modify the advanced properties.\n\n        |Property|Description|\n        |--------|-----------|\n        |Toggle to populate relationships between tiers|Option to enable the import of relationships between AppDynamics tiers in the CI Relationship \\[cmdb\\_rel\\_ci\\] table.|\n        |The number of minutes of metrics to fetch in order to generate tier to tier relationships|Number of minutes of metrics to fetch for generating tier-to-tier relationships. For example, `60` retrieves the last hour's relationships.|\n        |Toggle to import business transactions from AppDynamics|Option to enable the import of business transactions into the Calculated Application Service \\[cmdb\\_ci\\_service\\_calculated\\] table.|\n        |Toggle to populate tags for imported servers|Option to enable the import of server tags into the Key Value \\[cmdb\\_key\\_value\\] table.|\n        |Toggle to import node data from AppDynamics and map to the cmdb\\_ci\\_appl hierarchy|Option to enable the import of nodes into the Application \\[cmdb\\_ci\\_appl\\] table hierarchy.|\n\n    3.  Select **Save**.\n\n    4.  Set the Advanced Settings task to complete by selecting **Mark as Complete**.\n\n7.  Set up the SG-AppDynamics Servers and Applications scheduled job available by default.\n\n    1.  For the Configure scheduled job task in the Set up scheduled import jobs section, select **Configure**.\n\n    2.  On the Scheduled Data Import form, verify the field values for the SG-AppDynamics Servers and Applications scheduled job and select the **Active** check box.\n\n        For more information, see [Schedule a data import](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/t_ScheduleADataImport.md#table_r53_5hm_xp).\n\n    3.  Select **Update**.\n\n    4.  Set the Configure scheduled job task to complete by selecting **Mark as Complete**.\n\n\n"}}