Deploying Liberty server packages with Admin Center
You can use the Deploy tool to install Liberty server package (archive) files on hosts within a collective.
Before you begin
- Create a Liberty collective that includes the hosts to which you plan to install the Liberty server. See the Before you begin section of Deploying resources with Admin Center and the Configuring a Liberty collective topic.
- Complete the Before you begin section and steps 1-3 in Deploying Liberty servers using deployment REST APIs.
- If you want to upload the Liberty server package from your browser system to the collective
controller on the Deployment Parameters panel in step 3, add to the controller
server.xml file a remoteFileAccess statement that enables
write access to the location; for
example:
This statement is required even if you have specified host write paths with --hostWritePath in the registerHost or updateHost command on the controller host.<remoteFileAccess writeDir="/home/uploadDir/>
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
.
- From details on hosts in the Explore tool, select
> one_or_more_host_names > Deploy Server Package.
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.
- From the Toolbox, select
- Select to install a Liberty server package.
- For DEFAULT SERVER TYPES, select Liberty.
- Under LIBERTY SERVER, select NEXT.
- For DEFAULT RULES, select the Server Package default rule.
- Under SERVER PACKAGE, select NEXT.
- 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, directory and server package file name values are set automatically. You can also type in
the values.
- Drag or browse option
To upload a file from your browser system to the collective controller, add to the controller server.xml file a statement that enables write access:
<remoteFileAccess writeDir="/home/uploadDir"/>
You then can 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.
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.
- Drag or browse option
- 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.
Each target host must be registered with the collective that is managed by Admin Center. See Registering host computers with a Liberty collective.
- 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.


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-libcore-mp&topic=twlp_ui_deploy_libertypackage
File name: twlp_ui_deploy_libertypackage.html