You can just push fields to UDM:Execution
Then the plugin will communicate to the carte server already configured
1 of 1 people found this helpful
addition to above. you can directly call it through filter run process. try below syntax
"<directory of kitchen.bat>\Kitchen.bat" /server:ar server /port:port /user:xxxx /pass:xxx /rep:name or use / which is default /job:spoon job name
"<directory of kitchen.bat>\Kitchen.bat" /server:ar server /port:port /user:xxxx /pass:xxx /rep:name or use / which is default /job:spoon job name /param:Var1="$xx$" /param:Var2="$xxx$"
in second option you also need to define and use variables in spoon job.
I agree that is a solution however there are a few things that you should be aware of:
- The password will be an Administrator one, in plain text and therefore will be in workflow; any filter logs etc. So from an OpSec point of view, that wouldn't pass an audit.
- You lose the audit of this being run (As I write this, you could mitigate this by adding something in the actual job, but that's too long for here)
- As you have said, you would need to set kettle.properties or environment variables for job variables. Rather than the set.
SSO Plugin - Easy to implement and manage Single Sign On (SSO) for BMC