You can use the Deploy tool to install Liberty server package (archive) files on hosts
within a collective.
About this task
After you define the Liberty collective,
create the server package, and register one or more target hosts, use the Deploy tool to install the
server package on hosts within the collective.
Procedure
-
Go to the Deploy tool.
- From the Toolbox, select Deploy .
- From details on hosts in the Explore tool, select .
To directly launch the Deploy tool in the future, you can use the URL that is shown in the
browser when viewing the Deploy tool.
-
Select to install a Liberty server
package.
-
For DEFAULT SERVER TYPES, select Liberty.
-
For DEFAULT RULES, select the Server Package
default rule.
-
Under SERVER PACKAGE, select CONFIRM.
-
For Deployment Parameters, specify the Liberty server package file to
deploy and the target installation directory. If you drag a package to the Deploy tool or browse for
a package, the server package file name value is set automatically. You can also type in
values.
- Drag or browse option
To upload a file from your browser system to the collective
controller, drag a package to the Deploy tool or browse for a package.
- Use a file located on the collective controller option
To use a
file in the controller, the server package must be available to the controller. If you have not done
so already, complete step 2c in Deploying Liberty servers using deployment REST APIs. You
then can use the Use a file located on the collective controller
option.
After you upload or drop a file, select
Use a file located on the collective controller again to edit the
Package directory field.
For server package ZIP or JAR formats, specify the installation directory. For example, specify
/home/user1/liberty
for the product to upload the server package to
/home/user1/liberty, create a server directory in the
liberty directory, and then unzip the server package.
The installation directory must be the same as the --hostWritePath value
specified when you registered the target host with the controller.
The RPC user of each target host must have read and write access to the parent of the
installation directory.
-
For Selected Hosts, select the host computers on which to install the
server package. If you do not see the wanted target host in the list of available hosts, you can
search for a host.
-
For Security Details, specify a password to protect newly generated
keystore files that contain server authentication credentials.
The product generates keystore files in the resources directory of each
deployed server.
-
Select Deploy.
Results
The Deploy action runs. The Deploy tool displays messages about deployment status and
results.