Execution form


The UDM:Execution vendor form is used to execute transformations and jobs. Creating a new entry for this form leads to the execution of the specified operation on the specified transformation or job listed on the form. If the requesting user does not have permission for the requested transformation or job, an error is returned.

To execute a transformation or job, you must first create an execution instance by creating a row in this form. 

  1. In the Operation drop-down, select Create Execution Instance.
  2. Add a unique name in the Execution Instance Name field.

This execution instance can be started, stopped, paused, or removed by creating another record with the same Execution Instance Name and a new Start, Stop, Pause or Remove operation.

UDM:Execution form

221_Execution.jpg

Use these fields to set up your transformation or job execution:

  • Name (Required)—The name of the transformation or job object to be executed.
  • Type (Required)—The type of the object to be executed, either Transformation or Job.
  • Directory (Optional)—The repository directory location of the object to be executed. This is required for the Create Execution Instance operation, and an object ID is not specified.
  • Object ID (Optional)—The ID of the object to be executed. This is required for the Create Execution Instance operation and a repository directory is not specified.
  • Execution Instance Name (Required)—An unique name used to identify the execution instance.
  • Log Level (Optional)—The level of logging to be used for the execution. This can be set to any of the following:
    • Nothing
    • Error
    • Minimal
    • Basic
    • Detailed
    • Debug
    • Row level—If this is left blank, the Minimal logging option is used.
  • Operation (Required)—This specifies the type of operation to be executed. The available operations are:
    • Create Execution Instance—An execution instance is created with the given instance name. The ARDBC plug-in sends the transformation or job definition to the Atrium Integrator engine. The Atrium Integrator engine then loads the transformation or job definition into memory and creates and execution instance. If the combination of instance name and transformation or job name is not found to be unique an error will be thrown.
    • Start Execution Instance—Start running the execution instance.
    • Stop Execution Instance—Stop an execution instance that is currently running.
    • Pause Execution Instance—Pauses an execution instance that is currently running. This only applies to transformations.
    • Resume Execution Instance—Resumes an execution instance that is currently paused. Note that this also only works for transformations.
    • Remove Execution Instance—Removes an execution instance from the Atrium Integrator engine server's memory.
  • Variable Set Name (Optional)—Optional. Specifies the variable set to be used for this execution instance. The ARDBC plug-in will query all the variables from the UDM:Variable form that contain this variable set name. It will pass all variables to the Atrium Integrator engine server for this execution instance.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Innovation Suite 25.3