The database plugin has the facility to execute SSIS packages. It sounds like you want to build some logic into your project and use Control-M to orchestrate the execution of these SSIS packages as in building dependencies etc? You could just build a job flow with the conditions and if a parameter is 0, the job would end and satisfy a condition, otherwise it would not and the dependent job would then execute or not based on that control.
Please check this post to see if it may help:
Good morning Haw Kor,
I understand the basic concept of running an SSIS package. I do not know how set up to conditional operations that decide if the process runs or not. Would this be done somewhere in the 'In Condition'?
When you are referring to parameters, are you speaking about the exit code of the SSIS package? if that is the case then you can detect it from a database job type. You can then modify the "On Do" actions depending on OS completion status and either add a condition or remove a condition which would trigger or prevent triggering a job downstream.
Thank you for the response Haw Kor
When I mention parameters I am referring to a variable I can pass the project when I order it.
This variable would be evaluated before the step runs.
If the RunStep3 variable is set to False when I order the project, then step three will be skipped after step two runs.
I hope this makes sense.
1 of 1 people found this helpful
I believe this can be accomplished by defining a job at the top that will trigger your SSIS packages. This job can be an embedded script which will check the variable values that you set either at the job level or at the folder level ( you would need to make the folder smart if you want folder level variables).
The jobs can be defined like this where step1 is the step where the variable values are evaluated and the decision to proceed to step2 or step3 is decided:
The following is defined in the On Do Actions to remove the conditions that are not satisfied:
The first job can then do something similar to this:
if "%TestVar%" == "3" (
In order to have the Control-M variables defined as OS variables you will need this option turned on at the agent level. The following link describes how to make use of this feature.
Chris - All of these answers will work fine, but are a bit overkill... based on your screenshot, it looks like your using an older version of App Integrator? Your requested capability is built into App Int, in the modern versions. Note my screenshot. I'd recommend double checking to make sure that you've got newest possible [for your environment] version along with the appropriate EM_FILES installed