General rules

• To switch to a group, for example to http, type cd http or http/. Using only / takes you to the system group.
• To execute a command of a group different from the current one, use the syntax <group>.<command> where <group> stands for the name of desired group and <command> is the name of the command.
• To separate the parameters of a command, use spaces and if a single parameter contains spaces enclose the whole string of this parameter in a pair of quotation marks.
• In the fw command group, you may pass URLs as input parameters besides bundle IDs.
• To pass a list of bundle IDs as parameter to a command, use <start_ID>-<end_ID>. For example: fw.manifest 1-10
• If installing a bundle from bundles directory and the ../../bundles value of the mbs.bundles.base system property is preserved, then you may specify only the bundle JAR filename. For example, instead of specifying the full path of the Preferences bundle:

  fw.install D:/<Bosch IoT Gateway Software_server>/bundles/com.prosyst.mbs.osgi.preferences.jar

  you may type:

  fw.install com.prosyst.mbs.osgi.preferences.jar

You may set mbs.bundles.base to the directory hosting most of the bundles that you are to use and then only type bundles' JAR names.

• To avoid waiting until time-taking command A completes its job in order to issue then command B, you can attach "&" at the end of command A. For example: fw.manifest 1-10&
• Options are applied to the command entry that comes after. For example, the command:

  install com.prosyst.mbs.osgi.scr.jar -s com.prosyst.mbs.osgi.connector.socket.jar

  will install com.prosyst.mbs.osgi.scr.jar and will install and start com.prosyst.mbs.osgi.connector.socket.jar