Starting with vRealize Suite Lifecycle Manager 8.0, there are only Content Pipelines and Capture pipeline are supported. In the Content Pipelines section, under the Pipelines tab, the status of the last 24 pipeline executions can be seen in the Content_Pipeline card. Each of the content pipeline executions when selected, shows the associated Capture pipelines, if any, in the Capture pipeline card. The execution representations, the colored dot in the pipeline card, can be selected to view a detailed breakdown of the various stages of the selected execution. The Content pipeline execution can contain a maximum of nine stages in the order of execution. However, the actual execution has the stages which are relevant to the execution.
- Post- Capture
The Executions tab lists all the content and capture pipeline executions. The list shows the status, time taken, executed by and time of the request for each of the executions. This list can be filtered by the type of pipeline and execution status.
Each pipeline consists up of various Stages, each stage then can have various Tasks. Tasks can be either parallel or sequential based on your custom business logic. After selecting an action that you want to perform on a content, a content capture can list various types of status related to such an action. Each of the content settings is related to the view displayed on the Content Pipeline page.
Execute Pipeline Conditions:
- EXECUTE_ON_SUCCESS - The stub is executed only if the corresponding stage executes successfully. For example, Post-Capture if configured to EXECUTE_ON_SUCCESS executes only if the Capture stage is executed successfully.
- EXECUTE_ON_FAILURE -The stub is executed only if the corresponding stage execution fails. For example, Post-Capture if configured to EXECUTE_ON_FAILURE executes only if the Capture stage is execution fails.
- EXECUTE_ON_SUCCESS_AND_FAILURE - The stub is executed irrespective of whether the corresponding stage execution passes or fails. For example, Post-Capture if configured to EXECUTE_ON_SUCCESS_AND_FAILURE executes in both cases, whether Capture stage execution passes or fails.