The EAC allows scripts to be provisioned and invoked via Web service calls. A script is provisioned by specifying a working directory, a log directory into which output from the script is recorded, and a command to execute the script.

The AppConfig.xml document allows defined scripts to be provisioned by specifying the command used to invoke the script from the command line. When the provisioning configuration information is included, the script is provisioned and becomes available for invocation via Web service calls or from the EAC Admin console in Oracle Commerce Workbench. When excluded, the script is not provisioned.

  <script id="BaselineUpdate">
    <log-dir>./logs/provisioned_scripts</log-dir>
    <provisioned-script-command>
        ./control/baseline_update.bat
    </provisioned-script-command>
    <bean-shell-script>
      <![CDATA[ 
...
      ]]>
    </bean-shell-script>
  </script>

The command line used to invoke scripts can always be specified in this form, relative to the default Deployment Template working directory:

./control/runcommand.[sh|bat] [script id]