Controlling Automation Service with Command-line Parameters
Read this section to learn how to use command prompt to:
Start or stop Automation services.
Control which configurations are loaded.
Control which triggers are active.
Note
Make sure you are running Command Prompt in elevated mode (with administrative permissions). Right-click cmd.exe and select Run as Administrator.
Starting and Stopping the Services
To start both services, use the following commands:
net start LoftwareProxyService
net start LoftwareAutomationService
If you want to open configuration file when the Service is started, use:
net start LoftwareAutomationService [Configuration]
For example:
net start LoftwareAutomationService "c:\Project\configuration.MISX"
To stop services, use the following commands:
net stop LoftwareProxyService
net stop LoftwareAutomationService
Managing the Configurations and Triggers
Loftware Automation service can be controlled using Automation Manager command-line parameters. Use the following general syntax:
LoftwareAutomationManager.exe COMMAND Configuration [TriggerName] [/SHOWUI]
Note
Include full path to the configuration name. Do not use the file name alone.
To ADD configuration
The provided configuration gets loaded into service. No trigger is started. If you include the /SHOWUI parameter, Automation Manager UI is started.
LoftwareAutomationManager.exe ADD c:\Project\configuration.MISX /SHOWUI
To RELOAD configuration
The provided configuration gets reloaded into service. The running status of all triggers is preserved. Reloading the configuration forces the refresh of all files cached for this configuration. For more information, see section Caching Files. If you include the /SHOWUI parameter, Automation Manager UI is started.
LoftwareAutomationManager.exe RELOAD c:\Project\configuration.MISX /SHOWUI
To REMOVE configuration
The provided configuration and all of its triggers are unloaded from service.
LoftwareAutomationManager.exe REMOVE c:\Project\configuration.MISX
To START a trigger
The referenced trigger is started in the already loaded configuration.
LoftwareAutomationManager.exe START c:\Project\configuration.MISX CSVTrigger
To STOP a trigger
The referenced trigger is stopped in the already loaded configuration.
LoftwareAutomationManager.exe STOP c:\Project\configuration.MISX CSVTrigger
Status Codes
Status codes provide feedback about the command-line execution. To enable the status codes return, use the following command-line syntax:
start /wait LoftwareAutomationManager.exe COMMAND Configuration [TriggerName] [/SHOWUI]
The status codes are captured in the errorlevel system variable. To see the status code, execute the following command:
echo %errorlevel%
List of status codes:
Status Code | Description |
0 | No error occurred |
100 | Configuration file name not found |
101 | Configuration cannot be loaded |
200 | Trigger not found |
201 | Trigger cannot start |
Providing User Credentials for Application Authentication
If you have configured the LMS Enterprise or LMS Pro system to use Application Authentication (not Windows Authentication), you have to provide user credentials with sufficient permissions to manage the configurations and triggers.
There are two command-line parameters you can use:
-USER:[username]. Where [username] is a placeholder for the actual user name.
-PASSWORD:[password]. Where [password] is a placeholder for the actual password.
more