Updated on 2024-09-24 GMT+08:00

Creating an OM Task

You can create auto OM tasks to let the bastion host automatically execute the task according to task steps, task types, resources, and execution mode you configure. For example, you can create an OM task to upload system disk files or local files to many designation hosts. With the fast operation, a bastion host automatically executes OM tasks based on your configured execution period and time. In addition, it can automatically execute multiple types of tasks concurrently on multiple devices, improving the OM efficiency.

  • Multiple OM tasks can be concurrently performed step by step on multiple resources that use the SSH protocol, including command, script, and file transfer OM tasks.
  • After an operation task is submitted, the system automatically performs operations in sequence and returns the execution result.

Constraints

  • Fast operation is supported by professional editions only.
  • Automated operation tasks can be executed only on Linux host resources that use the SSH protocol.
  • Currently, automated operation tasks cannot be performed on Windows host, database, or application resources.
  • Operation tasks created by you can be managed only by yourself and cannot be managed by other system users.

Prerequisites

  • You have the management permissions for the OM Task module.
  • You have obtained the access permissions for the resources.
  • The network between the managed hosts and the bastion host is connected.

Creating an Automated Operation Task

  1. Log in to your bastion host.
  2. Choose Operation > OM Task > Task.
  3. Click New in the upper right of the OM Task area.
  4. Configure basic information about the task.

    Table 1 Basic task information parameters

    Parameter

    Description

    Task Name

    Name of the task. The value of Task Name must be unique in the system.

    Timing

    Execution mode of the operation task. The options are Manual, Scheduled, and Cycle.

    You need to configure the execution time if Fixed-Time or Cycle is selected.

    • Manual: indicates that you need to manually start the task.
    • Fixed-Time: indicates that the task will start at the specified time. This type of rule is executed only once.
    • Cycle: indicates that the task will start periodically at the specified interval. This type of password change rule is triggered periodically.

    Execute Time

    Date when the task is periodically executed. The default execution time is at 00:00 every day.

    Cycle Frequency

    Task execution frequency.

    • The options are every minute, every hour, every day, every week, and every month.
    • Set the End Time for this type of tasks. Otherwise, the tasks will be executed periodically forever.

    Options

    (Optional) If you have no permissions for the selected accounts, select Sudo to escalate your privilege and execute the task under the sudoers file.

    Remarks

    Brief description of the operation task.

  5. Click Next and start to configure execution accounts or account groups.
  6. Click Next and set task steps.

    1. Click Add Step and select Command, Script, or Transfer File.
    2. Select one or more task types and set task parameters.

      Multiple steps can be added to an operation task.

  7. Click OK. The system returns to the task list page, and you can view the information about the new operation task.

    You can download the execution logs to obtain the task execution results.

Follow-up Operations

On the OM Task page, you can manage all created OM tasks, including managing related execution accounts and deleting, enabling, or disabling OM tasks.

  • To quickly relate an OM task to more accounts, select the task and click Relate in the Operation column.
  • To delete an OM task, select the task and click Delete in the Operation column.
  • To disable a periodic OM task, select the enabled ones and click Disable at the bottom of the list. When the status of those tasks changes to Disabled, they are hibernated.
  • To execute an OM task, click Execute in the Operation column.

    During the task execution, task steps are performed in sequence. When a task step is interrupted or the selected resource is unreachable, the subsequent task steps will be stopped.