Skip to main content
vbabu-41-Visitor
1-Visitor
Sep 13, 2016 2:47 PM UTC
Solved

How to run .bat file in trigger scripting of Integrity

How to run a batch file in trigger script of Integrity?

java.lang.Runtime.getRuntime().exec('cmd /c start E:\\oval\\CPProject.bat');

is above command is right to execute batch using JAVA API in Integrity server.

I am able to write and read batch file using JAVA API script but above command does not execute the batch file after writing. Kindly help me to execute the batch file in Integrity server. 

Thanks in advance

    bbauer-2Answer
    1-Visitor
    Sep 15, 2016 1:58 PM UTC

    When doing something similar I think I had to specify the complete path to "cmd". Here is a code snippet I used:

    var exec = "C:\\Windows\\System32\\cmd.exe /C C:\\Progra~1\\Integrity\\IntegrityServer10\\data\\triggers\\scripts\\batchFile.bat";

    var r = java.lang.Runtime.getRuntime();

    var p1 = r.exec(exec);

    var returnCode = p1.waitFor();

    View in thread

    3 replies

    bbauer-21-VisitorAnswer
    1-Visitor
    Sep 15, 2016 1:58 PM UTC

    When doing something similar I think I had to specify the complete path to "cmd". Here is a code snippet I used:

    var exec = "C:\\Windows\\System32\\cmd.exe /C C:\\Progra~1\\Integrity\\IntegrityServer10\\data\\triggers\\scripts\\batchFile.bat";

    var r = java.lang.Runtime.getRuntime();

    var p1 = r.exec(exec);

    var returnCode = p1.waitFor();

    Translate
    vbabu-41-VisitorAuthor
    1-Visitor
    Sep 16, 2016 12:46 PM UTC

    Thanks a lot it works for me 🙂

    Translate
    mrump16-Pearl
    16-Pearl
    Sep 16, 2016 3:04 PM UTC

    Please keep in mind, that any process you start inside a trigger context is/might be "blocking" the trigger and therefore your entire server for all other users.

    If you do not detach the severtrigger and yout batch operations it can lead to serious performance issues.

    detach a long running process from the trigger context that started it

    Translate
    Terms & ConditionsAccessibility statement