All Products
Document Center

Application profiling

Last Updated: Nov 22, 2021

Advanced Database & Application Migration (ADAM) allows you to use application profiling to analyze the data collected from a single application by using intelligent analysis algorithms.

1. Procedure

1.1 After you collect data from an application, click Next: Create Application Profile.

1.2 Create an application profile

Click Create to go to the Create Profile page, as shown in the following figure.

Enter the profile name, select Chinese or English as the report language, and upload a static or dynamic data file.

Static Data File: a WAR package or a collection package of static data.

Dynamic Data File: a ZIP package of collected data. A ZIP package can contain data collected for the same application from different IP addresses. You cannot package or add data of multiple applications to the same application profile.

Database Profile: required. Select profiles of Oracle databases accessed by the application.

After setting all parameters, click Create. It takes 1 to 10 minutes for application profiling to analyze data.

1.3 Application profile details

An application profile consists of overview, system Information, object overview, and object details.


Download Report: You can download the report of the application profile.

The basic information section includes a radar chart for application analysis and the basic information of the application profile.

ADAM uses a radar chart to show the overall performance of an application with respect to six dimensions.

Complexity is calculated based on conditions such as application scenarios and database features. This dimension indicates the application usage. A higher score indicates a more complex application that requires more transformations.

Session indicates the connection status of the application. A higher score indicates a larger number of connections to the application. This dimension is significant for configuring the connection pool when you transform the application.

Risk indicates the potential performance bottlenecks and stability risks of the application, especially the performance risks of SQL operations.

Hotspot indicates whether the database contains frequently accessed objects. A higher score indicates that the database to access contains objects that are frequently accessed.

Scale indicates the number of deployment units or instances of the application.

Load indicates the running performance of the application.

System Information

The System Information tab shows the system parameters that are collected by the ADAM application collector to help you evaluate the application running status.

Object Overview

The Object Overview tab shows information about the SQL statements and database objects that the application collects and analyzes.

Object Details

The Object Details tab shows the relationship between database objects, SQL statements, and application code that are analyzed by ADAM. The section on the left side of the tab lists the database objects accessed by the application in the form of a tree diagram that uses schema and object type as dimensions. The section on the right side of the tab lists database objects and the corresponding SQL statements used to access the objects.

You can configure a blacklist when you configure a call stack to obtain required information about the call stack.