Dynamic routing command

--host=name

Required for single-collective dynamic routing. The hostname of the target collective controller.

Do not specify --host with the --collectives option.

--password[=pwd]

Required for single-collective dynamic routing. The password for the Administrator user for the target collective controller. If no value is defined, you are prompted.

Do not specify --password with the --collectives option.

--port=num

Required for single-collective dynamic routing. The HTTPS port number of the target collective controller.

Do not specify --port with the --collectives option.

--user=name

Required for single-collective dynamic routing. An Administrator user for the target collective controller.

Do not specify --user with the --collectives option.

--pluginInstallRoot=path

Required. The fully qualified path of the WebSphere plug-in root directory on the web server host.

--targetPath=directory|(full_file_path)

Optional. By default, the plug-in configuration file is generated in the current directory. When webServerNames option has only one name, the file name is plugin-cfg.xml. Otherwise, the file name is plugin-cfg-webServerName.xml for each of the webServerNames options. You might either specify the directory name where the file must be placed, or specify a fully qualified file name. The new file replaces an existing file. The path must exist with one exception. The final path component can be the ${webServerName} variable.

// Existing "config" folder and default names for plug-in configuration files.
--targetPath='config/' 

// The existing "config" folder. Each plug-in configuration file is created. The file name must end with ".xml".
--targetPath='config/${webServerName}.xml' 

// Folders are created for each webServerName and default names for the plug-in configuration files.
--targetPath='config/${webServerName}/' 

// Folders are created for each webServerName and plug-in configuration files named plugin-cfg.xml.
--targetPath='config/${webServerName}/plugin-cfg.xml' 

--logFileName=file_path

Optional. A fully qualified path of the WebSphere plug-in log file on the web server host. By default, pluginInstallRoot/logs/webserverName/http_plugin.log. For Apache-based web servers, a path that begins with a pipe character is interpreted as an external piped logger.

--webServerNames=webServerName[,webServerName1]

Required. Comma-separated names of the web servers for which WebSphere plug-in configuration files need to be generated.

With the --collectives option, specify only one web server name. Run the command multiple times if you need more than one plugin-cfg.xml file. Copy the generated plugin-cfg.xml file to the web server directory before you run the command again.

--collectives=user1[:password1]@host1:port1,user2[:password2]@host2:port2,…

Required to generate artifacts for more than one collective. A list of collective controllers to connect to for dynamic routing information. Select one controller from each collective. All controllers must be started. Specify collectives in the format collective_user:user_password@collective_host:port with a comma that separates each collective. If a password is not specified, you are prompted.

--autoAcceptCertificates

Optional. Automatically trust SSL certificates during this command. Alternatively, SSL certificates are automatically trusted by setting the JVM property com.ibm.websphere.collective.utility.autoAcceptCertificates to true.

--host=name

Required for single-collective dynamic routing. The hostname of the target collective controller.

Do not specify --host with the --collectives option.

--password[=pwd]

Required for single-collective dynamic routing. The password for the Administrator user for the target collective controller. If no value is defined, you are prompted.

Do not specify --password with the --collectives option.

--port=num

Required for single-collective dynamic routing. The HTTPS port number of the target collective controller.

Do not specify --port with the --collectives option.

--user=name

Required for single-collective dynamic routing. An Administrator user for the target collective controller.

Do not specify --user with the --collectives option.

--keystorePassword[=pwd]

Required. The password for the generated keystore. If specified and no value is defined, you are prompted.

--keystoreType=type

Optional. The type of the generated keystore. Default type is PKCS12. Valid values are PKCS12 and JKS.

--certificateSubject=DN

--certificateSubject=DN is no longer used and is ignored. For more information, see Dynamic Routing SSL Certificates.

--collectives=user1[:password1]@host1:port1,user2[:password2]@host2:port2,…

Required to generate artifacts for more than one collective. A list of collective controllers to connect to for dynamic routing information. Select one controller from each collective. All controllers must be started. Specify collectives in the format collective_user:user_password@collective_host:port with a comma that separates each collective. If a password is not specified, you are prompted.

--autoAcceptCertificates

Optional. Automatically trust SSL certificates during this command. Alternatively, SSL certificates are automatically trusted by setting the JVM property com.ibm.websphere.collective.utility.autoAcceptCertificates to true.

Generating keystore...

Successfully completed MBean request to the controller.
Successfully generated keystore plugin-key-default.p12.
Generating keystore...

Successfully completed MBean request to the controller.
Successfully generated keystore plugin-key-collective2.p12.

Generated keystore file plugin-key-default.p12, plugin-key-collective2.p12, plugin-key.p12 that enables secure communication between the Dynamic Routing service and clients.
If you are using Intelligent Management in the WebSphere plug-in, copy keystore file plugin-key-default.p12, plugin-key-collective2.p12, plugin-key.p12 to a directory on the web server host, 
and run "gskcmd" to convert the keystore to CMS format and to set personal certificate as the default.
For example:

gskcmd -keydb -convert -pw <password> -db /tmp/plugin-key-default.p12, plugin-key-collective2.p12, plugin-key.p12 -old_format pkcs12 -target /tmp/plugin-key.kdb -new_format cms -stash
gskcmd -cert -setdefault -pw <password> -db /tmp/plugin-key.kdb -label default

Copy resulting /tmp/plugin-key.kdb, .sth, .rdb files to the keyring directory specified in the WebSphere plug-in configuration file.