Skip to main content
Feedback

Scripting engines used by Boomi runtimes

Boomi runtimes use your system’s scripting engine to complete some tasks.

The following scripting engines are supported: shell (.sh), batch (.bat) and Powershell (.ps1).

The scripting engine that is used depends on whether you are running Windows or Linux. If you are running:

  • Linux, shell scripts (.sh) are used in all situations.

  • Windows and you are running a runtime, batch scripts (.bat) are used.

  • Windows and you are running a runtime cluster that does not use UNC paths or forked execution, batch scripts (.bat) are used.

  • Windows and you are running a runtime cluster that uses UNC paths or forked execution, Powershell scripts (.ps1) are used.

  • Windows and you are running a runtime cloud, Powershell scripts (.ps1) are used.

The runtime uses your system’s scripting engine to do the following tasks:

  • Restart — using the restart.sh, restart.bat, or restart.ps1 script file

  • Launch forked executions in runtime clusters and runtime clouds — using the procrunner.sh or procrunner.ps1 script file

  • Launch execution worker in private runtime clouds — using the procworker.sh or procworker.ps1 script file

  • Launch the browsing of connector operations that run in forked executions in runtime clusters and runtime clouds — using the procbrowser.sh or procbrowser.ps1 script file

note

The procrunner.bat, procworker.bat, and procbrowser.bat script files are included in installations, but they are no longer used.