This topic describes how to create an application (job group), check the workers that run an application, and authorize one or more Resource Access Management (RAM) users to access an application on the Application Management page of the SchedulerX console.
Create an application
Before you create a job, you must create an application.
- Log on to Distributed Task scheduling platform.
- In the top navigation bar, select a region.
- In the left-side navigation pane, click Application Management.
- On the Application Management page, select the namespace in which you want to create the application and click Create application.
- In the Basic configuration step, specify Application Name and Application ID, select the application type, configure advanced settings based on your business requirements, and then click Next Step.
Parameter Description Default value Application Name Enter the name of the application. None Application ID The Application ID parameter specifies the group ID that is used to connect the application to SchedulerX. The application ID must be unique in the namespace. Otherwise, the system fails to create the application. You can also use the value of Application Name as the application ID. None Description Enter the description of the application. None app type - general app: Select this option if you do not want to deploy the application in a Kubernetes cluster or do not require Kubernetes jobs.
- k8s App: Select this option if you want to deploy the application in a Kubernetes cluster and require Kubernetes jobs.
general app Release Select a version as required. Professional edition Remote Log Server If you enable this feature, you must configure Log4j or Logback. Then, you can view the scheduling log of every job (including distributed jobs) in the console for troubleshooting. Disabled load5 The value cannot be greater than the number of CPU cores available on the worker where the agent is deployed. 0 Memory usage If the average memory usage within the previous 5 minutes exceeds the threshold that is specified by this parameter, the worker is considered busy. 90% Disk Usage If the disk usage exceeds the threshold that is specified by this parameter, the worker is considered busy. 95% Whether to trigger a busy machine Select whether to trigger jobs on busy workers. Enabled Advanced Configuration Maximum number of tasks Set the maximum number of jobs that are supported by the application. 1000 Automatic expansion Select whether to enable automatic expansion. If you enable this feature, you must configure the Number of global tasks parameter. Disabled Flow Control Select whether to enable traffic throttling. If you enable this feature, you must configure the Number of concurrent task instances parameter. Disabled Number of concurrent task instances Set the maximum number of job instances that can run the application at the same time. Job instances that exceed the limit are not discarded but are waiting in a queue for execution. 0 - In the Notification configuration step, specify the Notification channel and Contact: parameters. You can set Contact: to Contact group or user-defined.
- Contact group
All contacts in the contact group can receive notifications. For information about how to create a contact group, see Create a notification contact and a notification contact group.
- user-defined
Add a contact who can receive notifications. To add multiple contacts, repeat the following steps: click Add contact and specify the contact information.
Parameter Description Notification channel Valid values: SMS, Mail, webhook, and Telephone. Nickname Enter the nickname of the contact. Mail Enter the email address of the contact. Webhook - Enter the webhook URL that you want to use. WeCom, Lark, and DingTalk are supported. You can configure multiple webhook URLs by separating the URLs with commas (,).
- If you use the DingTalk chatbot, you must add the keyword SchedulerX (case-sensitive). Otherwise, the alert information cannot be received.
Mobile phone number Enter the mobile phone number of the contact. After you create the application, the application list is automatically refreshed.Important- Application ID: This configuration item must be specified for agent initialization. It is the unique identifier of an application.
- Application key: This configuration item must be specified for SDK requests. It is used for request verification. Do not disclose it to others.
- Contact group
View workers
After you connect an application to SchedulerX, you can view the workers that are scheduled to the application. To view workers, perform the following steps:
- On the Application Management page, view the number of workers of an application in the Total number of instances column of the application. Note If the Total number of instances column displays 0, the application fails to connect to workers.
- In the Operation column of the application, click View instances.
- In the Connect to an instance panel, view the workers that are scheduled to the application and the status of the workers.
- The IP address of a worker is followed by a number that is enclosed in a pair of parentheses. The number indicates the number of SchedulerX agents that run on the worker. In most cases, only one agent runs on a worker. However, a worker can host one or more SchedulerX agents.
- Workers can be in the Health or Busy state. By default, SchedulerX does not deliver jobs to busy workers. If all workers are busy, SchedulerX does not deliver jobs. If you want to force SchedulerX to deliver jobs to busy workers, turn on Whether to trigger a busy machine in the Machine Instance busy configuration section.
Authorize RAM users to access an application
You can authorize RAM users to access a specific application by using an Alibaba Cloud account or a RAM user.

{
"Version": "1",
"Statement": [
{
"Action": "ram:ListUsers",
"Resource": "*",
"Effect": "Allow"
}
]
}
Delete an application
If you no longer want to create jobs for an application, you can delete the application. After you delete an application, the jobs that belong to the application cannot be triggered.
- On the Application Management page, find the application that you want to delete and click Delete in the Operation column.
- In the Delete application dialog box, confirm the information, enter the application name, and then click OK.
- After you delete an application, the jobs that are associated with the application cannot be triggered, and the Application Management page does not display the application.
- To restore a deleted application, Join the DingTalk group (ID: 23103656) to contact SchedulerX technical support.