Specifying Log On Parameters

webMethods Deployer 10.3 | webMethods Deployer Documentation 10.3 | Using Deployer Commands | Specifying Log On Parameters

Creating a Configuration File for Log On Parameters

All Deployer commands require parameters for logging onto the Integration Server that hosts the Deployer. You can have Deployer commands connect to the Integration Server using HTTP or HTTPS.

If you want the Deployer commands to log on using HTTP, you can use an existing HTTP port on the Integration Server or configure a new one. If you want the Deployer commands to log on using HTTPS, you must do the following:

Use an existing HTTPS port on the Integration Server or configure a new one.

Place the command line interface's client certificate, private key, and signing authority's certificate on the Integration Server host machine.

Map the command line interface's client certificate to an Integration Server user that has Administrator or Developer privileges.

For instructions on these tasks, see webMethods Integration Server Administrator’s Guide.

When you run Deployer commands, the log on parameters you provide depend on whether you want to use HTTP or HTTPS, as follows:

The log on parameters for logging onto an HTTP port are as follows:

Deployer.{sh|bat} --command -host host -port port-user user-pwd password

The logon parameters for logging onto an HTTPS port are as follows:

Deployer.{sh|bat} --command -host host -port port-user user-pwd password
-useSSL -senderCert path_to_cert-privKey path_to_key-caCert path_to_cert

Parameter	Description
-host host -port port	Host machine and port for the Integration Server to log on to.
-user user-pwd password	User name and password to use to log on to the Integration Server. Note: If you do not provide a password, Deployer will prompt you for it.
-useSSL	Tells the Deployer command to log on to an HTTPS port.
	-senderCert path_to_cert	Command line interface's client certificate.
	-privKey path_to_key	Command line interface's private key.
	-caCert path_to_cert	Command line interface's signing authority's certificate. If the certificates and private key do not exactly match the ones in the Integration Server installation for the command line interface, the command will fail.