Running Via Command Line

The new WMS SDK comes with a command line tool that makes it possible to run simulations from the command line without using the GUI.

This can be beneficial for CI pipelines, test setups etc. It still requires Windows. The GUI uses the command line tool behind-the-scenes.

You can find the command line software in the WMSSDKApplication folder.

You can invoke it from the command line by doing one of the following:

rm -r "C:\ProgramData\AutoStore\WMS SDK\backup\*"
& "C:\Program Files\AutoStore\AutoStore WMS SDK\WMSSDKApplication\cubecontrol-supervisor.exe" "C:\Program Files\AutoStore\AutoStore WMS SDK\WMSSDKApplication\wmssdk-stable_1.0.0.json" --workspace=".." --package-arguments="backup:--primary-location='C:\ProgramData\AutoStore\WMS SDK\backup' --backup-aslog='C:\Program Files\AutoStore\AutoStore WMS SDK\examples\basic.aslog'"

del "C:\\ProgramData\\AutoStore\\WMS SDK\\backup\*" /q & rmdir "C:\\ProgramData\\AutoStore\\WMS SDK\\backup\\ASLogs" /q /s &  
.\\cubecontrol-supervisor.exe "C:\\Program Files\\AutoStore\\AutoStore WMS SDK\\WMSSDKApplication\\wmssdk-stable_1.0.0.json" --  
workspace="../" --package-arguments="backup:--primary-location=""C:\\ProgramData\\AutoStore\\WMS SDK\\backup"" --backup-aslog=""C:\\Program Files\\AutoStore\\AutoStore WMS SDK\\examples\\basic.aslog"""

The initial rm command (powershell) or rm and rmdir (cmd) clears out the dedicated backup folder of the WMS SDK. This is required to be able to initialize a simulation from a .aslog file.

The subsequent unnamed argument indicates which software package to use for simulation. The example above shows wmssdkstable_1.0.0.json being used, which will provide the latest stable software package using AutoStore Planner. To use a different software package, simply change the JSON file (the last part of the path) to the one matching the desired package. The following files are available:

The --workspace argument needs to point to the parent folder as in the example invocation above. “--workspace=../”. Providing an absolute path to the WMS SDK root folder (C:\Program Files\AutoStore\AutoStore WMS SDK) will also work.

The --package-arguments=backup: indicates the beginning of the arguments sent to the AutoStore Backup.

The --primary-location argument defines the working folder for the AutoStore Backup which handles the database initialization and refresh. The value of this parameter should not be changed, as this points to the dedicated Backup working directory for the WMS SDK GUI application.

The --backup-aslog argument is the .aslog file the simulation should initialize the system with. It has to be a path, e.g. to the examples included in the WMS SDK like in the command above.

You can also copy the command from the GUI as described earlier.

ℹ️

To re-run a previous simulation, simply ommit the deletion commands (rm / del, rmdir). AutoStore Backup will use already existing

backup data even if an aslog is specified through the backup-aslog argument if it can find a complete backup in its working directory
(denoted by --primary-location)

🚧

Take great care when using the CLI to NOT remove the --primary-location argument from the Backup. Doing so will lead AutoStore

Backup to use the default Backup Program Data folder for storing simulations, which could cause conflicts with existing files.

🚧

Beware that the WMS SDK GUI application shares its working folder with the CLI, so using both could lead to conflict. It is

recommended to consequently use one or the other, or work in such a way that previously stored states can be discarded.