	Product(s):	APM Implementation and Performance Management
	Version(s):	7
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem Description

In an APM environment with an Assetwise Interoperability integration to SAP, the user noticed a rapid decrease in performance in the processing speed of inbound SAP. There were no overt errors in the APM logs even with increased log on the Job Service Provider and integration related classes.

Solution

The first step in troubleshooting most cases where an APM task is running slowly is to check the error logs for overt errors. The second troubleshooting step is to run the performance monitoring tool, in this particular case the APM Performance Monitoring tool is not useful as the job processing service runs in the background and cannot be easily monitored. However, the Service Monitoring webpage will give an overall indication of slow performance.

In all dataload type actions in APM, integrations included, large datasets are processed frequently. This results in the indexes for the database tables for those objects becoming fragmented and inefficient. As such the APM database requires regular maintenance of the database, this includes actions such as regularly scheduled monitoring of database statistics, planned rebuild of indexes that have become fragmented, scheduled review of size/storage requirements, etc.

The indexes to be analyzed most frequently are those on the classes most frequently written to and vary depending on the user. Some examples include:

Interoperability "Identity" table indexes

Indicator Reading table indexes

Work Order Task tables indexes

Inbound Aweis Messages processing slowly into APM

Problem Description

Solution

See Also