Register a host with a collective controller. To register the current host where both the collective controller host and the remote target host
are the same computer, run the
registerHost command on the collective utility
script with no explicit host target. Specify the collective controller's host name, port, and
administrative user name and password. For
example:
wlp/bin/collective registerHost --host=controllerHost --port=controllerHTTPSPort
--user=controllerAdmin --password=controllerAdminPassword
To reduce the number of options needed, use the --controller option instead of--user, --password,
--host, and --port.
wlp/bin/collective registerHost
--controller=controllerAdmin:controllerAdminPassword@controllerHost:controllerHttpsPort
This example command generates a unique SSH key pair for authenticating to the SSH server of a
specified host computer. If you are registering a remote host for which an SSH key pair is already
generated, you can specify the path of the SSH private key file. The following
registerHost command assumes that the SSH private key is stored on the local
controller computer at
/home/user1/.ssh/id_rsa. The other file in the SSH key
pair is the
/home/user1/.ssh/authorized_keys public key file on the remote
target
host.
wlp/bin/collective registerHost remotehost.ibm.com --host=controllerHost
--port=controllerHTTPSPort --user=controllerAdmin --password=controllerAdminPassword
--sshPrivateKey=/home/user1/.ssh/id_rsa
To reduce the number of options needed, use the --controller option instead of--user, --password,
--host, and --port.
wlp/bin/collective registerHost remotehost.ibm.com
--controller=controllerAdmin:controllerAdminPassword@controllerHost:controllerHttpsPort
--sshPrivateKey=/home/user1/.ssh/id_rsa
If the remote target host does not support SSH or you do not want to use SSH keys, you can
specify an operating system login user for
rpcUser and login password for
rpcUserPassword. If you include
rpcUser with
rpcUserPassword, do not include
sshPrivateKey. The command to
specify operating system login user and password
resembles:
wlp/bin/collective registerHost remotehost.ibm.com --host=controllerHost
--port=controllerHTTPSPort --user=controllerAdmin --password=controllerAdminPassword
--rpcUser=osUserForRemoteHost --rpcUserPassword=osUserPasswordForRemoteHost
To reduce the number of options needed, use the --controller option instead of--user, --password,
--host, and --port.
wlp/bin/collective registerHost remotehost.ibm.com
--controller=controllerAdmin:controllerAdminPassword@controllerHost:controllerHttpsPort
--rpcuser=osUserForRemoteHost --rpcUserPassword=osUserPasswordForRemoteHost
To transfer files to and from a host, you must specify host read and write paths. Unless the
registerHost command specifies the paths, you cannot deploy a
Liberty archive to the host. The
hostReadPath specifies the directories that the collective controller can read. The
hostWritePath specifies the directories to which the collective controller can
write. Paths that are specified by
hostWritePath are also readable. For example, to
upload an archive to
/opt/wlp, you must specify
--hostWritePath=/opt. Specify a parameter multiple times for multiple
paths.
wlp/bin/collective registerHost myHost.ibm.com --host=controllerHost
--port=controllerHTTPSPort --user=controllerAdmin --password=controllerAdminPassword
--rpcUser=osUser --rpcUserPassword=osUserPassword
--hostReadPath=/opt --hostWritePath=/dir1 --hostWritePath=/dir2
To reduce the number of options needed, use the --controller option instead of--user, --password,
--host, and --port.
wlp/bin/collective registerHost myHost.ibm.com
--controller=controllerAdmin:controllerAdminPassword@controllerHost:controllerHttpsPort
--rpcuser=osUser --rpcUserPassword=osUserPassword
--hostReadPath=\opt --hostWritePath=/dir1 --hostWritePath=/dir2
To use the Deploy tool of
Admin Center to deploy a
Liberty server package, you must set
hostWritePath to the path to which you want to deploy a server package. To transfer
files to multiple directories, include multiple instances of the
hostWritePath
parameter in the command. For
example:
wlp/bin/collective registerHost myHost.ibm.com --host=controllerHost
--port=controllerHTTPSPort --user=controllerAdmin
--password=controllerAdminPassword --rpcUser=osUser --rpcUserPassword=osUserPassword
--hostWritePath=c:\was\liberty\brokerageAppTest --hostWritePath=c:\wlp_backup
To reduce the number of options needed, use the --controller option instead of --user, --password,
--host, and --port.
wlp/bin/collective registerHost myHost.ibm.com
--controller=controllerAdmin:controllerAdminPassword@controllerHost:controllerHttpsPort
--rpcuser=osUser --rpcUserPassword=osUserPassword
--hostWritePath=c:\was\liberty\brokerageAppTest --hostWritePath=c:\wlp_backup
Optionally, specify the path to the Java home directory of the host with the
-hostJavaHome parameter. For example:
-hostJavaHome=c:\java\jre