Automatically archive tasks according to a user-defined policy
This topic explains how to manage active tasks using the Monitoring section.
This topic explains how to manage active tasks using the Monitoring section.
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.
This topic covers how Deploy uses task queuing with JMS 2.0 to manage task execution in version 9.5 and later. 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.
This topic covers how Deploy manages multiple deployments simultaneously, each referred to as a task. Users can instruct Deploy to start, stop, or cancel a task. Once a task is completed or canceled, it is moved to the task archive, 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.
This topic describes how to use the force cancel option to remove tasks that are stuck and cannot be canceled due to failing steps. The force cancel option should only be used as a last resort to clean up tasks.
This topic covers tasks in Deploy, which are activities with steps for deploying, updating, or managing applications that can be scheduled, recovered, and manually archived post-execution.
This topic describes the issues caused by concurrent deployments in Deploy when using custom microservices deployment technologies. Middleware limitations may restrict the target environment to performing only one deployment at a time, leading to potential conflicts.
Using Deploy, you can schedule deployment tasks for execution at a specified moment in time.
This topic describes how to schedule or reschedule tasks in Deploy for execution at a specified date and time. You can schedule or reschedule tasks that are in a PENDING or SCHEDULED state.
This topic provides information about the XLDEPLOYSERVER_HOME/work directory, which is used to temporarily store data that cannot be kept in memory.
In Deploy, you can define control tasks and use them to execute actions from the Deploy GUI or CLI.
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.