1 of 1 people found this helpful
If your Remedy server is a Microsoft Windows server, and the .bat file resides on the server in a directory that ARServer has permissions to, then you can define an escalation in Remedy Developer Studio that will execute that batch file.
If your server is a Linix/Unix server, then you will need to create a script that performs a similar task to your batch file.
Can you help me with a sample, my server is Windows?
I have an escalation with a Run process and entered a path like this: c:\bmc remedy\arserver\imp.bat. When I execute the .bat file from cmd prompt work fine, but when I test since the escalation, it does not execute the action fine.
The .bat files must be in a particular folder to be processed?
It's possible that it's as easy as putting the path in quotes, like this:
That being said, there are all kinds of other concerns that could be causing issues.
Some things to think about are:
- How many records are matching the criteria of the escalation? If thousands of records match "true" for the run-if condition, it could cause the server to choke on this. I'm guessing that you will only want this to run once per execution. You should probably take measures to ensure that only one record matches the run-if criteria.
- Does the batch file modify files or folders in directories that ARServer does not have permissions to? That could cause issues.
- If you want a positive response that the batch file has run, you could add an output to it, like, 0 for success and 1 for failure or something. Then, instead of doing a Run Process action, you could call the bat file from a set fields action like this: $PROCESS$ "c:\bmc remedy\arserver\imp.bat"
In regards to your other question, it's not that the bat needs to be in a particular folder, it's that the user that the server is running under needs to have permission to whatever folder the batch file is in.