Connecting Agents

Prerequisites

The network between your host and APM is normal.

You can run the Telnet command to check the network.

Important

Java supports enhanced Agents.

Procedure

  1. Log in to the management console.

  2. Click image1 on the left and choose Application > Application Performance Management.

  3. In the navigation pane, choose Application Monitoring > Applications.

  4. On the displayed page, click Connect Application.

    **Figure 1** Connecting an application

    Figure 1 Connecting an application

  5. Select a region and application.

    **Figure 2** Basic information

    Figure 2 Basic information

  6. Select Java for Backend Language.

    **Figure 3** Access mode

    Figure 3 Access mode

  7. Select Enhanced Agent for Code Source.

  8. Select an access mode based on the application type and access data by following the instructions.

    **Figure 4** Data access

    Figure 4 Data access

    Table 1 Parameter description

    Parameter

    Description

    Mandatory

    APM_AK

    APM_SK

    AK and SK for installing JavaAgent.

    Caution

    CAUTION: When you copy the command to install JavaAgent, delete {} when setting APM_AK and APM_SK.

    Yes

    Probe Installation Path

    Path for installing the Agent.

    Yes

    appName

    Component name, which must start with a letter. A component can contain multiple environments. The names of components under an application must be unique. If there are duplicate names, use instanceName to distinguish them.

    Yes

    env

    Name of an environment where an application is deployed. A program can be deployed in different environments (such as the test or live network environment). Each environment is deployed in one region and has a unique region attribute. If this parameter is blank, the default environment will be used.

    No

    envTag

    Environment tag for filtering environments. Different environments may have the same tag. This parameter can be left blank.

    No

    business

    Name of an application that already exists (a global concept). If this parameter is left blank, the automatically created application will be used.

    No

    subBusiness

    Name of a sub-application (a global concept), which is similar to a folder. If it is left blank, resources will be mounted to the root application. There can be up to three layers of sub-applications. For example, for a/b/c, a, b, and c respectively represents a layer.

    No

    User Application

    Name of a user application.

    Yes