RESTful API: Activating a configuration: Difference between revisions
Nicole Tan (talk | contribs) (NT: added credential to the command line and explanation) |
Lucas Joyal (talk | contribs) (Corrected the tbconfig command, removed the -r) |
||
| Line 1: | Line 1: | ||
== Activating a configuration == | == Activating a configuration == | ||
tbconfig /systems/gw_12358/target_configuration="config_new" | tbconfig /systems/gw_12358/target_configuration="config_new" -u <username> -p <password> | ||
or | or | ||
tbstatus /system::target_configuration=config_new -r -u <username> -p <password> | tbstatus /system::target_configuration=config_new -r -u <username> -p <password> | ||
where username and password is one of your valid user and password to log in the webportal | where username and password is one of your valid user and password to log in the webportal | ||
Revision as of 13:56, 11 October 2016
Activating a configuration
tbconfig /systems/gw_12358/target_configuration="config_new" -u <username> -p <password>
or
tbstatus /system::target_configuration=config_new -r -u <username> -p <password>
where username and password is one of your valid user and password to log in the webportal