12 docs tagged with "task"

Deploy keeps all active tasks in the Monitoring section, which is located under the search bar at the top left of the screen.

Deploy records and archives information about all tasks that it executes. This information is available through the statistics, graphs, and task archives on the Reports screen.

As of 9.5, Deploy uses task queuing for workers using the Java Message Service (JMS) 2.0 protocol. Deploy will queue any tasks, regardless of whether a worker is available to execute them. When a worker does become available, it will automatically pick tasks from the queue and execute them.

Deploy can perform multiple deployments at the same time. Each of these deployments is called a task. Users instruct Deploy to start a task, stop a task, or cancel a task. After a task is completed or canceled, it is moved to the task archive. This is where Deploy stores its task history. You can query the task archive for tasks, examine the tasks steps and logs, or export the task archive to an XML file.

If you want to remove tasks that are stuck and cannot be canceled due to failing steps, you can use the force cancel option. It is intended to use force cancel only as a last resort option to clean up tasks.

A task is an activity in Deploy. When starting a deployment, Deploy will create and start a task. The task contains a list of steps that must be executed to successfully complete the task. Deploy will execute each of the steps in turn. When all of the steps are successfully executed, the task itself is successfully executed. If one of the steps fails, the task itself is marked as failed.

In Deploy with the custom microservices deployment technologies, concurrent deployments are causing issues because of middleware limitations that allow only for a single deployment to be performed to the target at a given time.

Using Deploy, you can schedule deployment tasks for execution at a specified moment in time. For more information, see scheduling tasks.

In Deploy you can schedule or reschedule a task for execution at a specified date in time. You can schedule or reschedule tasks that are in a PENDING or SCHEDULED state.

The XLDEPLOYSERVER_HOME/work directory is used to temporarily store data that cannot be kept in memory. Examples of items that are temporarily stored in the work directory are:

In Deploy, you can define control tasks and use them to execute actions from the Deploy GUI or CLI. To create a custom control task, you can use a delegate. Deploy includes a predefined delegate called JythonDelegate that accepts a Jython script that it will execute.

Control tasks are actions that you can perform on middleware or middleware resources. For example, checking the connection to a host is a control task. When you trigger a control task, Deploy starts a task that executes the steps associated with the control task.