Example commands for asynchronously starting an instance of a control flow

In this example, you need to execute control flow Y of application X immediately and monitor the execution of the control flow. The control flow references three variables named ${file_ref/rejected_records}, ${file_ref/duplicate_records} and ${numbers/threshold}.

Solution 1

Assume that a profile P with the appropriate values was created for control flow X. Run the following commands to create and monitor a named control flow instance:

# Start an instance and provide a name
startControlFlowInstance -app X -controlFlow Y -instance run_Y -profile P

# Retrieve the status (you must invoke the command multiple 
# times to monitor the progress of the control flow)
getControlFlowInstanceStatus -app X -controlFlow Y -instance run_Y

To be useful in batch processing, this solution requires some custom scripting. A unique instance name must be created for each iteration. Instance names cannot be reused until the previous instance with an identical name is deleted.

Solution 2

Assume that a profile P with the appropriate values was created for control flow X. Run the following commands to create and monitor a generically named control flow instance:

# Start an instance and have a name automatically assigned
startControlFlowInstance -app X -controlFlow Y -profile P

# Display control flow instances for the specified control flow
listControlFlowInstances -app X -controlFlow Y

# Manually identify the instance name based on the output
# or use a custom script to identify the control flow instance
# name (example assumes that Y1165356017323 was assigned
# as an instance name)

# Retrieve the instance status (has to be invoked multiple times to
# monitor the progress)
getControlFlowInstanceStatus -app X -controlFlow Y -instance Y1165356017323

startControlFlowInstance does not return the automatically generated name.

Feedback | Information roadmap