Metadata Manager Command Reference

Back Next

updateResource Options

The command uses the following options:

[<-dn | --domainName>]: Required if the domain uses Kerberos authentication and you do not specify the --gateway option. Name of the Informatica domain.

This option uses the gateway connectivity information in the domains.infa file. If the domains.infa file is missing or contains connectivity information that is out of date, you must use the --gateway option instead.

[<-hp | --gateway>]: Required if the domain uses Kerberos authentication and you do not specify the --domainName option. Also required if the domain uses Kerberos authentication and the domains.infa file is missing or contains connectivity information that is out of date. Host names and port numbers of the gateway nodes in the domain.

If there are multiple gateway nodes, separate the gateways with a space. For example:

-hp host1:6001 host2:6002

If you run the command from a machine where the Informatica client or the Informatica utilities are installed, the host name must be fully qualified.

[<-mm | --mmServiceName>]: Required if the domain uses Kerberos authentication. Name of the Metadata Manager Service.

<<-url>>: Host name and port number of the Metadata Manager Service that runs the Metadata Manager application. Use the following format:
http(s)://<host>:<port>
.

If a secure connection is configured for the Metadata Manager web application, the host name must match the common name (CN) used to generate the keystore that you use for the HTTPS connection to the Metadata Manager Service.

[-ep | --encryptedPassword]: Required if you specify an encrypted password. Encrypted password flag. Use with the password option to indicate that the password for the Metadata Manager user is encrypted. For example:

-ep -pw WP+qtfYwB2KYLXID9jgC+6WHbMOg/94AO8R1nOC1vd0=

[<-pw | --password>]: Required if the domain does not use Kerberos authentication. Also required if the domain uses Kerberos authentication and you do not specify the --keyTab option. Password for the Metadata Manager user. For example:

-pw Administrator

To specify an encrypted password, you must specify the --encryptedPassword option in addition to this option.

[<-n | --namespace>]: Required if the domain uses LDAP authentication or Kerberos authentication. Optional if the domain uses native authentication. Name of the security domain to which the Metadata Manager user belongs. The security domain name is case sensitive.

[<-kt | --keyTab>]: Required if the domain uses Kerberos authentication and you do not specify a password. Path and file name of the keytab file for the Metadata Manager user.

<<-r | --resource>>: Name of the Metadata Manager resource that you want to update. If the resource name contains spaces, enclose the resource name in quotes.

<<-rcf | --resourceConfigurationFile>>: File name and path for the resource configuration file that contains the modified resource properties. You can import a resource configuration file (.rcf file). Alternatively, you can import a resource configuration file that also contains all the rule sets and rule set parameter definitions associated with the resource (.rcz file). If you do not include a path, mmcmd looks for the file in the mmcmd directory.

The source files of the resource must be in the directory specified in the resource configuration file or in the directory specified using the -pdir option. If you do not specify a path, mmcmd looks for the source files in the mmcmd directory.

[<-pdir>]: Directory where the source files of the Metadata Manager resources are stored.

[<-rpw | --resourcePassword>]: Required if the resource uses a password and the resource configuration file does not contain the resource password. Resource password in plain text.

[<-sjp | --secureJDBCParameters>]: Secure JDBC parameters that you want to append to the JDBC connection URL. Use this option with database management resources to specify secure connection parameters such as passwords. Metadata Manager does not display secure parameters or parameter values in the resource configuration properties. Enter the parameters as name=value pairs separated by the delimiter character that the database driver requires.

If secure communication is enabled for the metadata source database, enter the secure JDBC parameters in this option.