Prerequisites
Some Functional Item Management bundles are required for the work of Scripting module. They are included in the installation script and listed in the Manual Installation, described below.
Installation
Automated Installation
The installation of the Scripting module can be performed through execution of a Kit Manager installation script located in bin/pscripts:
To install the Scripting module, type the following command in the console:
kitman.install "Scripting"
The kitman command group is exported by the Kit Manager Bundle. The required bundles for the Scripting module are listed in the Manual Installation section below.
There is Scripting With LuaJ Support provided too, which installs Util Lua Scripting Bundle (com.prosyst.mbs.util.lua.jar) along with the required module bundles described further below. The command in that case would be:
kitman.install "Scripting With LuaJ Support"
As a result the Util Lua Scripting Bundle installs the Lua script engine.
Manual Installation
In order to install the Scripting module manually, the following bundles from the <mbs_home>/runtime/osgi/bundles directory have to be installed and started with the install command options as follows:
For installing Lua script engine, the Util Lua Scripting Bundle – com.prosyst.mbs.util.lua.jar, should be installed and started in addition to the list above: fw.i -f -s -l com.prosyst.mbs.util.lua.jar. For details and examples refer to Using Lua Scripts.
System Properties
There are no system properties defined for this module.
Configuration Properties
Scripting Core Bundle Configuration
The Scripting Core Bundle – com.prosyst.mbs.scripting.core, provides the following configuration – Scripting Module Config:
Name |
PID |
Property |
Type |
Default Value |
Description |
|---|---|---|---|---|---|
Scripting Module Config |
mbs.scripting.core.pid |
scriptsFolder |
String |
../../../scripts |
Default folder where scripts will be searched and which contents the 'list' command shows. |
Troubleshooting
No troubleshooting information is available for this module.