I can’t use a .bat file because I need to perform a cURL command that is not available and cannot be installed on the Commserve for security reasons.
The only alternative I have is to use a Powershell script.
Hello Henke,
I am using the built-in mechanism to send alert to the ticket system but in order to create a ticket, I need to run a cURL command via the Run Command notification because the Email handler is not convenient for the customer.
Oh, sorry I may not have explained properly. Rather than executing the powershell command directly, put the powershell command in a batch script, and allow commvault to execute the batch script first, which will subsequently fire off powershell. I am just wondering if the command is getting tripped up on all the parameters. In the documentation link you sent, you can run the sample batch to output the variables to know how to match up the tokens to the powershell parameters - i.e <CLIENT NAME> may conform to $1 etc.
I can’t use a .bat file because I need to perform a cURL command that is not available and cannot be installed on the Commserve for security reasons.
The only alternative I have is to use a Powershell script.
Hello Henke,
I am using the built-in mechanism to send alert to the ticket system but in order to create a ticket, I need to run a cURL command via the Run Command notification because the Email handler is not convenient for the customer.
I can’t use a .bat file because I need to perform a cURL command that is not available and cannot be installed on the Commserve for security reasons.
The only alternative I have is to use a Powershell script.
Hello Henke,
I am using the built-in mechanism to send alert to the ticket system but in order to create a ticket, I need to run a cURL command via the Run Command notification because the Email handler is not convenient for the customer.
Oh, sorry I may not have explained properly. Rather than executing the powershell command directly, put the powershell command in a batch script, and allow commvault to execute the batch script first, which will subsequently fire off powershell. I am just wondering if the command is getting tripped up on all the parameters. In the documentation link you sent, you can run the sample batch to output the variables to know how to match up the tokens to the powershell parameters - i.e <CLIENT NAME> may conform to $1 etc.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
