Migrating to Harmonized Adapter for the AppDynamics for SAP agent

[Dennis.Horvath]

Step-by-Step Guide to Migrating AppDynamics Analytics Data to Harmonized Schemas

Reason to migrate:

This migration pertains exclusively to the analytics data captured and stored on the AppDynamics controller, which has a maximum capacity of 20 schemas. To overcome this limitation, we have reengineered the approach to schema utilization, enabling additional capacity for customers to define their own schemas. Starting with agent version 24.11, this updated approach (called Harmonized) is the sole available option for new installations. However, for customers who are updating to this version, this document will walk them through the process as they should plan to migrate ASAP. Please note that any metrics migrated will begin reporting from the new location, and all historical analytics data associated with those metrics will be lost.

Clean out old data

1. Log into each SAP system (as these schemas are shared)
2. Disable analytics via t-code /DVD/APPD_CUST, then enter Edit Mode
3. Uncheck the analytics events API box
4. Save changes
5. Click the status button or run t-code /DVD/APPD_STATUS
6. Click event service
7. Then click Custom Analytics schema

As stated before, the max number of schemas a controller can have is 20.

Here is a list of the ones that are used going forward related to SAP:

• sap_log_data
• sap_workload_data
• sap_analytics_data_1
• sap_idoc_data
• sap_biq_documents
• sap_hana_data (if a HANA DB is used)
• sap_bw_data (if it is a BW system)
• sap_pi_data (if it is a PI system)
• sap_custom_data_1 (custom)

For the complete list use this Link, which also shows how they will be mapped

Given that standard schemas will be created, it is important to ensure sufficient capacity for their inclusion. This decision will be evaluated on a case-by-case basis, but there are essentially two strategies to consider.

Option 1: 

Start fresh by removing all existing schemas. The necessary schemas will be recreated upon restart. Please note that this approach will result in the loss of all historical data stored on the controller, not just the analytics data that is relocated.

1. In t-code /DVD/APPD_STATUS
2. Click the Debug Mode
   
3. Check both boxes and select the desired time duration
   
4. Delete the ones you want or all of them for a fresh start
5. Once all changes are made click the Debug Mode button again to exit debug mode (or wait for the duration to expire)

Option 2:

Start by just removing the schemas that are marked with the status “Not Used”.

1. Do this by clicking the trash icon on the same row
2. Then confirm the deletion (by clicking 'No' button)
   

Flipping the switch:

1. After deleting all unused schemas and verifying you have enough room go back to the t-code /DVD/APPD_CUST
2. Enter change mode
3. In the Analytics events API settings area, set Version to "Harmonized" and check the box for “Analytics events API is active”

Verify Schemas:

Once all the changes are made and running for a few hours, your end result could look like this.

You can see which systems are using the different schemas by clicking the corresponding Used button

Adjusting Dashboards to new schemas

Any dashboard that has analytical data may have been impacted.

You will need to go into each data field and modify the query like the following

Replace the old (legacy) schema name with the new (harmonized) schema name in the FROM part of the query string.

Add an extra WHERE condition AND sapSchema = <old schema name>.

Example query change:

Legacy query

SELECT * FROM idocs_details WHERE SID = "ED2"

Migrated query

SELECT * FROM sap_idoc_data WHERE SID = "ED2" AND sapSchema = "idocs_details"

Additional Resources

• Troubleshooting