Command Central syntax:Command Central syntax:Platform Manager syntax:Argument or Option | Description | ||||
node_alias | Command Central only. Required. Specifies the alias name of the installation in which the run-time component is installed. You can view a list of installations and their aliases using sagcc list landscape nodes. | ||||
componentid | Required. Specifies the ID of the run-time component to which the instance you want to update belongs. You can determine the IDs for run-time components using sagcc list inventory components. | ||||
instanceid | Required. Specifies the ID of the instance for which you want to update data. You can determine the IDs for configuration instances using sagcc list configuration instances. | ||||
[sharedsecret=text_string] | Optional. Specify a shared secret password that Platform Manager uses to secure any passwords in the configuration data that you want to update. If you omit this parameter, Platform Manager uses the shared secret defined for the environment or for the whole landscape. For more information, see sagcc add security credentials
sharedsecret. | ||||
{--input | -i} filename{.xml| .json|.properties} | Required. Identifies an input file that contains the updated configuration data. For more information, see input.
When updating instances of common configuration types, XML, json, and properties are all supported types of the input file. However, all of these file types might not be supported when creating instances of a product-specific configuration type.
| ||||
[options] | Optional. Refer to the command syntax for a list of the options the command supports. For a description of the options, see Common Options. |
The data in the input file must match the expected schema for the configuration type.You can use sagcc exec configuration validation
update to validate input data that you want to use to update the configuration instance.You can retrieve schemas for common configuration types. You can use the schemas to validate an XML input data file. The schemas are available from a Platform Manager. For example, you might use the following to retrieve the log4j schema from a Platform Manager with host name “rubicon2” and port “8092”:You can retrieve schemas for common configuration types. The schemas are available from a Platform Manager using the following where hostname is the host name of a Platform Manager server and port is its port number:You can specify the content type for the output data for the command either in the Accept header of the REST client or by adding the --output-format option. For example, if you add --ouput-format text, the command displays data on the console in plain text format. For more information, see output-format.When using an XML input data file to update a configuration instance, use the sagcc get configuration data command with the --output | -o filename.xml option to retrieve a copy of the XML input data file for the configuration instance you require.The data to update a COMMON-PORTS instance is in the c:\inputs\port_data.xml file. To update the configuration instance with ID “COMMON-PORTS-com.softwareag.sshd.pid.properties” for the run-time component with ID “OSGI-SPM”, which is installed in the installation with alias name “sag01” using the authorization of the user with user name “Administrator” and password “manage”:The Software AG_directory /profiles/CCE/configuration/security/user.txt file is updated with a new password that replaces the default Command Central administrator password. To update the modified user.txt file for the instance with ID “ENGINE SIN-INTERNAL-USERS-users.txt” and the run-time component with ID “OSGI-SPM”, which is installed in the installation with alias name “sag01”:To update instance data for the configuration instance with ID “COMMON-PROXY” that belongs to the run-time component with ID “OSGI-SPM” and runs in the installation with alias name “sag01”, using “mysecret123” as the shared secret to secure the proxy configuration password, and save the updated configuration data with the encrypted password in the “configWithEncryptedData.xml” file: