Help Center> FunctionGraph> User Guide> Application Center
Updated on 2024-05-23 GMT+08:00
View PDF

Application Center

Application Center uses Resource Formation Service (RFS) to deploy peripheral resources (including functions, agencies, and triggers) required by applications so that these resources can cooperate with each other to execute tasks (This feature is supported only in CN North-Beijing4 and CN East-Shanghai1.)

Procedure

  1. Log in to the FunctionGraph console. In the navigation pane, choose Apps.
  2. Click Create in the upper right corner. The Select Template page is displayed.
  3. In the navigation pane on the left, there are two filters: Runtime and Category. You can filter templates based on service requirements. This section describes how to create a DIS data processing template. After the template is determined, click Create Application to go to the application configuration page.

    Figure 1 Selecting a template

  4. On the Application Configuration page, enter the following information:

    • Region: Retain the default setting.
    • Project: Retain the default setting.
    • Application Name: Enter a custom name.
    • Runtime Language: Retain the default setting.
    • Agency: Determine whether to use an agency based on the requirements. For example, in Step 3, the DIS data processing template is created and you need to create an agency to authorize the function to access DIS. For details, see Configuring Agency Permissions.
    • Description: Describe the application.

    Click Create Now after the configuration is complete.

Parameter Description

After the application is created, you can click the application name in the application list to view details. The main parameters are described as follows:

  • Stack Name: You can click this link to go to the task details page after the stack is successfully deployed.
  • ID: Unique ID of the currently deployed application in the system. You can locate faults based on the ID and application name.
  • DIS Data Service (DIS): You can click this link to go to the details page of the created DIS data service.
  • FunctionGraph: You can click this link to go to the details page of a created function.
    Figure 2 Parameters on the Summary page
  • Name in the Repository Info: You can click this link to go to the code repository where the function code is hosted. You can browse and download related code.
    Figure 3 Parameters on the Code page

Common Problems and Troubleshooting Methods

  1. The code repository fails to be created, and the message shown in Figure 4 is displayed.
    Figure 4 Code repository creation failed

    Troubleshooting method: Check whether CodeArts is enabled for your account. For details, see Login Methods to check and enable CodeArts. If the problem persists, contact Huawei Cloud FunctionGraph engineers for further help.

  2. The stack fails to be deployed, and the message shown in Figure 5 is displayed.
    Figure 5 Stack deployment failed
    Troubleshooting method: Click the application name link to go to the Summary page of the application. Click the link of Stack Name to go to the RFS page. Then click View Reason to view the specific problem.
    Figure 6 Summary page
    Figure 7 RFS page
    Figure 8 View failure causes
  3. If the permission is insufficient, the message shown in Figure 9 is displayed.
    Figure 9 Insufficient permissions

    Troubleshooting method: If an error message indicating insufficient permissions is displayed when you create an application for the first time, configure the agency permission for the current account and try again.

  4. If the deletion fails, the message shown in Figure 10 is displayed.
    Figure 10 Deletion failed
    Troubleshooting method: Click the application name link to go to the Summary page of the application. Click the Stack Name link to go to the RFS page. Then click View Reason to view the specific problem. The preceding figure is used as an example. The application fails to be deleted because the API group contains APIs. Go to the Summary page of the application, click Physical Resource Name/ID of the FunctionGraph. On the function details page that is displayed, choose Settings > Triggers to view the API name. Log in to the APIG console, take the API offline, delete the API, and try again.
    Figure 11 Clicking the FunctionGraph link
    Figure 12 Viewing the API name