Develop > Command-Line Interfaces > ConfigWsTool Command-Line Interface

ConfigWsTool command-line interface

You can use the ConfigWsTool command-line interface (CLI) to interact with Monitoring Automation using the Monitoring Automation web service API.

The tool enables you to use the web service API without having to set up a REST-based communication channel. It accepts commands and flat input files, and handles the communication details, making it especially useful for development and troubleshooting of external applications using the Monitoring Automation web service.

Location

<OMi_HOME>/opr/bin/ConfigWsTool.[bat|sh]

Synopsis

ConfigWsTool [<CONNECTION_INFO>] {<toolInfo> | <request>} [{‑verbose|‑v}] [{‑output|‑o} <outputFile>]

Note the following with respect to the optional parameters:

  • Specifying ‑verbose results in verbose output.
  • By default, the output is directed to the console. To redirect the output to an output file, specify the ‑output <outputFile> option, where the file name <outputFile> may contain path information. If path information is omitted, the file is stored in the current working directory.
  • All output and input files are formatted as XML.

Options

ClosedSyntax for <CONNECTION_INFO>

-rc_file <file> &| -username <login name> [ -password <password> | -smartcard | -winCrypto | -jks <keystore path> -jksPassword <keystore password> ] [[-port <port>] [-server <gatewayserver>] [-ssl] | [-u <URL>]]

Note If <CONNECTION_INFO> is omitted, the command is executed on the server to which you are logged on.

Option Description
{-rc_file | -rcf }<file> Location of your credential store. Values for your username, password, java keystore location, and java keystore password can be defined here, enabling you to run commands without having to specify the values individually each time. Use the options -list_rc, -set_rc, and -delete_rc to work with the file. The default file is <OMi_HOME>/.opr-cli-rc. If this option is not specified, then commands automatically check the default file location for credentials. You must specify this option if your credential store file is in a non-default location. If this file does not exist or does not contain the correct settings, you must manually specify the credentials using the other command options.
{-list_rc| -lrc} [-rc_file <file>] Display the content of the file from which credentials are read. The file contains fields for java keystore, keystore password, username and password, and is encrypted by a hardcoded key.
{-set_rc | -src} <key>=<value> [-rc_file <file>] Configure one setting in the file from which credentials are read. Specify the setting and the new value by using a key=value pair. For example, -set_rc password=<password string>.
{-delete_rc | -drc} <setting> [-rc_file <file> } Delete setting from file from which credentials are read. Possible settings are username, password, jks, and jksPassword.
{-username|-user} <login name>

Sets the login name of the user required to execute CLI operations on the target gateway server.
{-password|-pw} <password>

Sets the password for the specified user. If using SSH on Cygwin, either enter the password in free text or use other communication methods, for example Java keystore, Windows keystore, or smart card authentication.

Default value: empty string
{-smartcard|-sc}

Use certificate stored on smart card or security token for authentication. When OMi is configured to use CAC authentication, the CLI tools under <OMi_HOME>/opr/bin/ do not directly prompt users to enter the password for the smartcard connected to the system. Instead, users must specify that a smartcard authentication is to be run, using the option -sc or -smartcard. Users attempting to run a tool without the -smartcard option automatically receive an error message.

For more information, see Using command-line tools when client certificate enforcement is used.
{-winCrypto|-wc}

If OMi is configured for TLS mutual authentication, this option specifies to use the Windows certificate store for authentication. The certificate store must hold exactly one client certificate, which OMi will use to authenticate the user. This option is only available on Windows systems.

For details, see Configure Client Certificate or Smart Card Authentication.
{-jks|-j} <keystore path>

If OMi is configured for TLS mutual authentication, this option can be used to specify the Java keystore to be used for authentication. The keystore must hold exactly one client certificate, which OMi will use to authenticate the user.

Note It is not necessary that the client certificate contains the flag "Smart Card Logon (1.3.6.1.4.1.311.20.2.2)" in the "Enhanced Key Usage" field.

For details, see Configure Client Certificate or Smart Card Authentication.
{-jksPassword|-jp} <keystore password>

Password for accessing the Java keystore.
{-port|-p} <port>

Uses port <port> to connect to the target gateway server.

Default:
80 (HTTP)
443 (HTTPS)
-server <GatewayServer>

Sets the target gateway server, using <GatewayServer> as the hostname or IP address to locate it.

Default: FQDN of the OMi gateway server
-ssl

When this option is specified, the HTTPS protocol is used to connect to the target gateway server. If omitted, the HTTP protocol is used.

Cannot be used in conjunction with the -url option.
{-url|-u} <url>

Sets the target gateway server, using <url> as the URL to locate it.

Default:
https://<OMi gateway FQDN>:80/opr‑config‑server
Closed<toolInfo>

{‑help | ‑version}

Option Description
{‑help|‑h} Displays a summary of the ConfigWSTool command options.
‑version Prints version information for the ConfigWSTool tool.
Closed<request>

{ ‑create_assignment | ‑create_auto_assignment | ‑create_assignment_by_aspect | ‑create_auto_assignment_by_aspect | ‑create_assignment_by_aspect_version | ‑create_auto_assignment_by_aspect_version | ‑create_assignment_by_mgmt_template | ‑create_auto_assignment_by_mgmt_template | ‑create_assignment_by_mgmt_template_version | ‑create_auto_assignment_by_mgmt_template_version | ‑create_assignment_by_template | ‑create_assignment_by_template_version | ‑delete_assignment | ‑delete_auto_assignment | ‑delete_assignment_by_ci | ‑filter_for_not_latest | ‑format | ‑get_draft_assignment | ‑get_draft_auto_assignment | ‑get_draft_assignment_for_aspect | ‑get_draft_auto_assignment_for_aspect | ‑get_draft_assignment_for_aspect_version | ‑get_draft_auto_assignment_for_aspect_version | ‑get_draft_assignment_for_mgmt_template | ‑get_draft_auto_assignment_for_mgmt_template| ‑get_draft_assignment_for_mgmt_template_version | ‑get_draft_auto_assignment_for_mgmt_template_version | ‑get_draft_assignment_for_template | ‑get_draft_assignment_for_template_version | ‑input | ‑list_assignment | ‑list_assignment_by_ci | -list_auto_assignment | ‑list_auto_assignment_by_aspect| ‑list_auto_assignment_by_aspect_version |‑list_assignment_by_mgmt_template | ‑list_auto_assignment_by_mgmt_template | ‑list_assignment_by_mgmt_template_version | ‑list_auto_assignment_by_mgmt_template_version | ‑list_aspect | ‑list_aspect_by_ci | ‑list_aspect_by_view | ‑list_aspect_by_citype| ‑list_aspect_version| ‑list_assignment_by_template | ‑list_assignment_by_template_version | ‑list_deployment_job | ‑list_deployment_job_by_assignment | ‑list_mgmt_template | ‑list_mgmt_template_by_view‑list_mgmt_template_by_ci | ‑list_mgmt_template_by_citype |‑list_mgmt_template_version | ‑list_template | ‑list_template_version | -output | -update_latest_auto_assignment | -use_existing } <arguments>

Option Description
{‑create_assignment|‑ca} {<CIID>{ |,}<mtVersionID>|{‑input|‑i} <inputFile>}

Creates a new assignment of a specific management template version. You can specify the management template version to be assigned and the CI it is to be assigned to in one of the following ways:

  • Provide a literal <mtVersionID><CIID> combination, separated by either a space or a comma. If this method is used, the parameter values used to create the assignment parameters are set to their default values. To override parameter values, use the -input option.

  • Specify the ‑input option, together with an input file name <inputFile>, where the input file is structured as a draft assignment returned by the ‑get_draft_assignment option for the CI and management template version combination.

    The file name <inputFile> may contain path information. If path information is omitted, the file is assumed to be in the current working directory.

Note If the options for both methods are specified, the input file takes precedence.
{‑create_assignment_by_aspect|‑caa} {<CiId>}{<aspectID>} {‑input|‑i} <inputFile>}

Creates a new assignment of the latest version of the aspect to the specified CI.

{‑create_assignment_by_aspect_version|‑caav} {<CiId>}{<aspectVersionID>> }

{‑input|‑i} <inputFile>}

Creates a new assignment of the specified version of the aspect to the specified CI.

{‑create_assignment_by_mgmt_template|‑camt} {<CIID>{ |,}<mtID>|{‑input|‑i} <inputFile>}

Creates a new assignment of the latest version of a management template. You can specify the management template to be assigned and the CI it is to be assigned to in one of the following ways:

  1. Provide a literal <mtID> <CIID> combination, separated by either a space or a comma. If this method is used, the parameter values used to create the assignment parameters are set to their default values. To override parameter values, use the -input option.

  2. Specify the ‑input option, together with a input file name <inputFile>, where the input file is structured as a draft assignment returned by the ‑get_draft_assignment option for the CI and management template combination.

    The file name <inputFile> may contain path information. If path information is omitted, the file is assumed to be in the current working directory.

Note If the options for both methods are specified, the input file takes precedence.
{‑create_assignment_by_mgmt_template_version|‑camtv} {<CiId>}{<mtVersionID>}

Creates a new assignment for the specified CI and the specified version of the management template.

{‑create_auto_assignment|‑cau} {<viewName>{ |,}<mtVersionID>|{‑input|‑i} <inputFile>}[-output]

Creates a new automatic assignment of a specific management template version. Can be used with the ‑output option to specify the path to the output file.

You can specify the management template version to be assigned and the view where it will reside in one of the following ways:

  • Provide a literal <viewName><mtVersionID> combination, separated by either a space or a comma. If this method is used, the parameter values used to create the assignment parameters are set to their default values. To override parameter values, use the -input option.

  • Specify the ‑input option, together with an input file name <inputFile>, where the input file is structured as a draft automatic assignment returned by the ‑get_draft_auto_assignment option for the CI and management template version combination.

    The file name <inputFile> may contain path information. If path information is omitted, the file is assumed to be in the current working directory.

Note If the options for both methods are specified, the input file takes precedence.
{‑create_auto_assignment_by_aspect|‑caua} {<viewName>}{<aspectID>}{‑input|‑i} <inputFile>}[-output]

Creates a new automatic assignment of the latest version of the aspect from a specified view. Can be used with -output option to specify the path to the output file.

{‑create_auto_assignment_by_aspect_version|‑cauav} {<viewName>}{<aspectVersionID>> }{‑input|‑i} <inputFile>}[-output]

Creates a new automatic assignment of the specified version of the aspect from a specified view. Can be used with -output option to specify the path to the output file.

{‑create_auto_assignment_by_mgmt_template|‑caumt} {<viewName>{ |,}<mtID>|{‑input|‑i} <inputFile>}[-output]

Creates a new automatic assignment of the latest version of a management template. Can be used with the ‑output option to specify the path to the output file.

You can specify the management template to be assigned and the view where it will reside in one of the following ways:

  1. Provide a literal <viewName><mtID> combination, separated by either a space or a comma. If this method is used, the parameter values used to create the assignment parameters are set to their default values. To override parameter values, use the -input option.

  2. Specify the ‑input option, together with a input file name <inputFile>, where the input file is structured as a draft automatic assignment returned by the ‑get_draft_auto_assignment option for the view and management template combination.

    The file name <inputFile> may contain path information. If path information is omitted, the file is assumed to be in the current working directory.

Note If the options for both methods are specified, the input file takes precedence.
{‑create_auto_assignment_by_mgmt_template_version|‑caumtv} {<viewName>}{<mtVersionID>}{‑input|‑i} <inputFile>}[-output]

Creates a new automatic assignment for the specified view and the specified version of the management template. Can be used with the ‑output option to specify the path to the output file.

{‑create_assignment_by_template|‑cat} {<CiId><templateID>}

Creates a new assignment for the specified CI and the latest policy template version.
{‑create_assignment_by_template_version|‑catv} {<CiId>}<templateVersionID>>

Creates a new assignment for the specified CI and specified policy template version.
{‑delete_assignment|‑da} [<assignmentID>] Deletes the assignment with the ID <assignmentID>.
{‑delete_auto_assignment|‑dau} [<autoassignmentID>] Deletes the automatic assignment with the ID <autoassignmentID>.
{‑delete_assignment_by_ci|‑daci} [<assignmentID>] Deletes all assignments for the specified CI.
{‑format|‑f} [<XML | JSON | TEXT>] Format of the input or output files associated with a web service request. Valid values are XML, JSON and text.
{‑filter_for_not_latest|-ffnl} Show automatic assignments that are not associated with the latest version of the assigned object.

{-get_draft_assignment|-gda} <CiID><mtVersionID>[-use_existing]

Returns a draft request for assigning the management template version with the version ID <mtVersionID> to the CI with ID <CIID>. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new assignment. Specify the -use_existing option to reuse parameters from an existing assignment.

{‑get_draft_assignment_for_aspect|‑gdaa} <CIID><aspectID> [-use_existing]

Returns a draft request for assigning the latest version of the aspect to the CI with the specified ID. You can modify the response and subsequently use it as an input file for a request to create a new assignment.

{‑get_draft_auto_assignment_for_aspect|‑gdaua} <viewName><aspectID> [-use_existing][-output]

Returns a draft request for automatically assigning the latest version of the aspect in a specified view. You can modify the response and subsequently use it as an input file for a request to create a new automatic assignment. Can be used with the ‑output option to specify the path to the output file.

{‑get_draft_assignment_for_aspect_version|‑gdaav} <CIID><aspectVersionID> [-use_existing]

Returns a draft request for assigning the specified version of the aspect to the CI with the specified ID. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new assignment. Specify the -use_existing option to reuse parameters from an existing assignment.

{‑get_draft_auto_assignment_for_aspect_version|‑gdauav} <viewName><aspectVersionID> [-use_existing][-output]

Returns a draft request for assigning the specified version of the aspect for the specified view. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new automatic assignment. Specify the -use_existing option to reuse parameters from an existing automatic assignment.

{‑get_draft_assignment_for_mgmt_template|‑gdamt} <CIID><mtID>[-use_existing]

Returns a draft request for assigning the latest version of the management template with the ID <mtID> to the CI with ID <CIID>. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new assignment. Specify the -use_existing option to reuse parameters from an existing assignment.

{‑get_draft_auto_assignment_for_mgmt_template|‑gdaumt} <viewName><mtID>[-use_existing][-output]

Returns a draft request for assigning the latest version of the management template with the ID <mtID> to the specified view. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new automatic assignment. Specify the -use_existing option to reuse parameters from an existing automatic assignment.

{‑get_draft_assignment_for_mgmt_template_version|‑gdamtv} <CIID><mtVersionID>[-use_existing]

Returns a draft request for assigning the specified version of the management template with the ID <mtID> to the CI with ID <CIID>. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new assignment. Specify the -use_existing option to reuse parameters from an existing assignment.

{‑get_draft_auto_assignment_for_mgmt_template_version|‑gdaumtv} <viewName><mtVersionID>[-use_existing][-output]

Returns a draft request for assigning the specified version of the management template with the ID <mtID> for the specified view. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new automatic assignment. Specify the -use_existing option to reuse parameters from an existing automatic assignment.

{‑get_draft_assignment_for_template|‑gdat} <CIID><templateID> [-use_existing]

Returns a draft request for assigning the latest version of the specified policy template to the CI with ID <CIID>. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new assignment. Specify the -use_existing option to reuse parameters from an existing assignment.

{‑get_draft_assignment_for_template_version|‑gdatv} <CIID><templateVersionID> [-use_existing]

Returns a draft request for assigning the specified version of the specified policy template to the CI with ID <CIID>. The response is stored as file <outputFile>. You can modify the response and subsequently use it as an input file for a request to create a new assignment. Specify the -use_existing option to reuse parameters from an existing assignment.

{‑input|‑i} [<path to input file>] Input file for creating an assignment with the same structure as a draft assignment returned by one of the -get_draft_assignment options.

{‑list_assignment|‑la} [<assignmentID>]

Lists all assignments in the database. To return a single assignment, provide the parameter <assignmentID>. Can be used with -output option to specify the path to the output file.
{‑list_assignment_by_aspect|‑laa} [<aspectID>] Lists all assignments of all versions of the specified aspect. Can be used with -output option to specify the path to the output file.
{‑list_auto_assignment|‑lau} [<autoassignmentID>] [-output][-filter_for_not_latest]

Lists all automatic assignment rules in the database. To return a single automatic assignment rule, provide the parameter <autoassignmentID>. Can be used with the -output and -filter_for_not_latest options.
{‑list_auto_assignment_by_aspect|‑laua} [<aspectID>][-output][-filter_for_not_latest]

Lists all automatic assignments of all versions of the specified aspect. Can be used with the -output and -filter_for_not_latest options.
{‑list_assignment_by_aspect_version|‑laav} [<aspectVersionID>] Lists all assignments of the specified version of the specified aspect. Can be used with -output option to specify the path to the output file.
{‑list_auto_assignment_by_aspect_version|‑lauav} [<aspectVersionID>][-output][-filter_for_not_latest] Lists all automatic assignments of the specified version of the specified aspect. Can be used with the -output and -filter_for_not_latest options.

{‑list_assignment_by_ci|‑laci} <CIID>

Lists all assignments for the CI with ID <CIID>. Can be used with -output option to specify the path to the output file.
{‑list_assignment_by_mgmt_template|‑lamt} <mtID> Lists all assignments of the management template with ID <mtID>. Can be used with -output option to specify the path to the output file.
{‑list_auto_assignment_by_mgmt_template|‑laumt} <mtID>[-output][-filter_for_not_latest] Lists all automatic assignments of the management template with ID <mtID>. Can be used with the -output and -filter_for_not_latest options.
{‑list_assignment_by_mgmt_template_version|‑lamtv} <mtVersionID> Lists all assignments of the management template version with ID <mtVersionID>. Can be used with -output option to specify the path to the output file.
{‑list_auto_assignment_by_mgmt_template_version|‑laumtv} <mtVersionID>[-output][-filter_for_not_latest] Lists all automatic assignments of the management template version with ID <mtVersionID>. Can be used with the -output and -filter_for_not_latest options.

{‑list_auto_assignment_by_view|‑lauvi} <viewName>[-output][-filter_for_not_latest]

Lists all automatic assignments for the specified view. Can be used with -output option to specify the path to the output file.
{‑list_aspect|‑lasp} [<aspectID>] Lists all aspects in the database. To return a single aspect, provide the parameter <aspectID>. Can be used with -output option to specify the path to the output file.
{‑list_aspect_by_ci|‑laspci} [<CiID>] Lists all aspects that can be assigned to the specified CI. Can be used with -output option to specify the path to the output file.
{‑list_aspect_by_view|‑laspvi} [<viewName>] Lists all aspects that can be assigned for the specified view. Can be used with -output option to specify the path to the output file.
{‑list_aspect_by_citype|‑laspcit} [<Ci type name>] Lists all aspects that can be assigned to CIs of the specified CI type. Can be used with -output option to specify the path to the output file.
{‑list_aspect_version|‑laspv} [<aspectVersionID>] Lists all versions of all aspects in the database. To return a single aspect version, provide the parameter <aspectVersionID>. Can be used with -output option to specify the path to the output file.
{‑list_assignment_by_template|‑lat} [<templateID>] Lists all assignments of all versions of the specified policy template. Can be used with -output option to specify the path to the output file.
{‑list_assignment_by_template_version|‑latv} [<templateVersionID>] List all assignments of the specified version of the specified policy template. Can be used with -output option to specify the path to the output file.
{‑list_deployment_job|‑ldj} [<deploymentJobID>] Lists all deployment jobs for all current assignments. To return a single deployment job, provide the parameter <deploymentJobID>.Can be used with -output option to specify the path to the output file, and -format text to display the output in text format.
{‑list_deployment_job_by_assignment|‑ldja} <assignmentID> Lists all deployment jobs for the assignment with ID <assignmentID>. Can be used with -output option to specify the path to the output file, and -format text to display the output in text format.
{‑list_mgmt_template|‑lmt} [<mtID>] Lists all management templates in the database. To return a single management template, provide the parameter <mtID>. Can be used with -output option to specify the path to the output file.
{‑list_mgmt_template_by_ci|‑lmtci} <CiID> Lists all management templates that can be assigned to the specified CI. Can be used with -output option to specify the path to the output file.
{‑list_mgmt_template_by_view|‑lmtvi} <viewName> Lists all management templates that can be assigned for the specified view. Can be used with -output option to specify the path to the output file.
{‑list_mgmt_template_by_citype|‑lmtcit} <CIType> Lists all management templates that can be assigned to CIs of the CI type <CIType>.
{‑list_mgmt_template_version|‑lmtv} [<mtVersionID>] Lists all versions of all management templates in the database. To return a single management template version, provide the parameter <mtVersionID>. Can be used with -output option to specify the path to the output file.
{‑list_template|‑lt} [<templateID>] Lists all templates in the database. To return a single template, provide the parameter <templateID>. Can be used with -output option to specify the path to the output file.
{‑list_template_version|‑ltv} [<templateVersionID>] Lists all versions of all templates in the database. To return a single template version, provide the parameter <templateVersionID>. Can be used with -output option to specify the path to the output file.
{‑output|‑o} [<path to output file>] When specified, the response returned by a web service request is saved to a file.
{‑update_latest_auto_assignment|‑ulau} Updates all existing automatic assignment rules to the newest version of a management template or aspect. Specify the -use_existing option to reuse parameters from existing automatic assignments.
{‑use_existing|‑ue} Reuses parameter values (if compatible) from an already existing assignment for the new assignment. The existing and the new assignment must refer to the same CI and policy template/aspect/management template, but must refer to a different version of the policy template/aspect/management template.

Exit status

Exit Status

Description

Output
0

Successful completion of the requested operation

 No output.
1

Failure of the requested operation

 An error message stating why the operation failed, followed by the tool's help text.
300‑399

HTTP Redirection (300-399)

An error message stating the HTTP error number and description.

For more information about HTTP error status values, see publicly available HTTP documentation.
400‑499

HTTP Client Error (400-499)
500‑599

HTTP Internal Server Error (500-599)

Note On Linux, ConfigWs Tool returns system error codes instead of HTTP status codes.

Restrictions

All operations require authorization. To operate the -list_assignment commands, the user must be an OMi user with permission to view assignments of the management template he wants to work with. To operate the -list_deployment_job command, the user needs full control for the Deployment Jobs interface. To operate the -list_management_template commands, the user needs viewing rights on the configuration folder containing the corresponding management templates. To operate the -create_assignment commands, the user needs full control permission for assignments of the management template, aspect, or template the user wants to assign. For more information about permissions, see Users, Groups, and Roles.

If <CONNECTION_INFO> is omitted when requesting an operation requiring authentication, ConfigWSTool does not execute the requested operation, and exits with the following error:

Username may not be null. Operation requires authentication. Please enter the login name and password.

The error can be fixed by inserting a valid <CONNECTION_INFO>.

Non-admin users also need the following file permissions to operate this command-line tool:

File Windows Permissions Linux Permissions
<OMi_HOME>/conf/TopazInfra.ini read r
<OMi_HOME>/log/opr-clis.log full control rw

<OMi_HOME>/log/opr-pgctl.log

Note: This file is not available on gateway server systems.
full control rw
<OMi_HOME>/conf/encryption.properties read r
<OMi_HOME>/conf/seed.properties read r

Examples

This section shows examples you can use as a starting point for developing your own ConfigWsTool commands.

All examples use basic authentication with the credentials myU/myPwd, and are executed on the local host.

  • List all management templates that can be assigned to a specific CI type

    Issue the following command to list all CI Types that can be assigned to a CI of the type myCIType:

    ‑lmtcit myCIType

    The management template IDs to be used for subsequent lists or assignments can be parsed from the response.

  • List all management template versions currently assigned to a specific CI

    Issue the following commands to list all management template versions that are currently assigned to a CI with the ID 5e2cef17df64ec4b35a0459e7ba33c8c:

    1. ‑laci 5e2cef17df64ec4b35a0459e7ba33c8c

    2. The response lists all current assignments for the CI. Parse the response, and for each assignment ID in the list, denoted as assgIdK, issue the following command:

      ‑la assgIdK

      The management template version IDs to be used for subsequent lists or assignments can be parsed from the response.

  • Create an assignment by using an explicitly specified combination of CI and management template

    Issue the following command to assign the management template version with version ID 430738c-796e-cfbd-9653-ee9fab02388a to the CI with the ID 5e2cef17df64ec4b35a0459e7ba33c8c:

    configwstool -user myU -pw myPwd -ca 5e2cef17df64ec4b35a0459e7ba33c8c c430738c-796e-cfbd-9653-ee9fab02388a

  • Create an assignment by using an input file

    Issue the following command to create an assignment using the XML input file \tmp\myAssg.xml:

    configwstool -user myU -pw myPwd -ca -i \tmp\myAssg.xml

  • Create an assignment from a draft assignment

    Issue the following command to retrieve a draft assignment of the management template version with version ID 430738c-796e-cfbd-9653-ee9fab02388a to the CI with the ID 5e2cef17df64ec4b35a0459e7ba33c8c:

    configwstool -user myU -pw myPwd -gda 5e2cef17df64ec4b35a0459e7ba33c8c c430738c-796e-cfbd-9653-ee9fab02388a -o \tmp\myDraft.xml

    The draft is stored as \tmp\myDraft.xml. Modify the file as required and save it, for example as file \tmp\myModifiedDraft.xml. Then, create a new assignment using the modified file as input file by issuing the following command:

    configwstool -user myU -pw myPwd -ca -i \tmp\myModifiedDraft.xml

  • Update all automatic assignments

    Issue the following command to retrieve all automatic assignment and update them to the latest version of a management template or aspect:

    configwstool -user myU -pw myPwd -ulau

    To use parameter values from existing automatic assignments, run the following command instead:

    configwstool -user myU -pw myPwd -ulau –ue

Send Help Center feedback