Liberty profile resources can be packaged into one or more compressed (.zip) files for deployment by the WebSphere® Application Server, Network Deployment Version 8.5 job manager. The grouping of the resources within the compressed files affects the scope and sharing of the resources. For resources in the compressed files to deploy correctly, the path names of the resources must satisfy job manager rules.
"Packaging a Liberty profile server from the command prompt" describes how to run the package command to create a compressed file that contains a Liberty profile runtime, files in the shared resources directory, one embedded server, and any applications embedded in the server. If you want to deploy a Liberty profile installation of this type and you do not need to place the installation in a project directory, consider using the package command to create the compressed file. For other types of Liberty profile installations, you must manually create one or more compressed files.
Supported Liberty profile resource types include project, runtime, Liberty server, application binary, and software development kit (SDK). For more information, read "Liberty profile resources."
The job manager distinguishes between the different types of Liberty profile resources in a compressed file using the following rules:
Determine the type of Liberty profile installation that you need, and then create one or more compressed (.zip) files that contain Liberty profile resources.
[-] liberty
[-] working
[-] samples
[-] wlp-08.05.00.00
[+] bin
[ ] clients
[+] dev
[ ] lafiles
[+] lib
[+] templates
[-] usr
[-] servers
[-] SecuritySample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o SecuritySample-01.00.war
[-] ServletSample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o ServletSample-01.00.war
[-] samples
[-] wlp-08.05.00.00
[+] bin
[ ] clients
[+] dev
[ ] lafiles
[+] lib
[+] templates
[-] usr
[-] servers
[-] SecuritySample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o SecuritySample-01.00.war
[-] ServletSample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o ServletSample-01.00.war
JAVA_HOME=/opt/jre-06.00.31
[-] samples
[-] wlp-08.05.00.00
[-] usr
[-] servers
[-] SecuritySample-01.01-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o SecuritySample-01.01.war
For information about sharing server configuration settings at the host and network levels, see "Using includes in the configuration."
[-] liberty
[-] shared
[-] jre-06.00.31
[+] bin
[+] lib
[-] wlp-08.05.00.00
[+] bin
[ ] clients
[+] dev
[ ] lafiles
[+] lib
[+] templates
[-] working
[-] samples
[-] servers
[-] SecuritySample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o SecuritySample-01.00.war
[-] ServletSample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o ServletSample-01.00.war
JAVA_HOME=${WLP_SHARED_DIR}/jre-06.00.31
WLP_RUNTIME_DIR=${WLP_SHARED_DIR}/wlp-08.05.00.00
The paths
include the WLP_SHARED_DIR WebSphere variable instead of a hardcoded
path. When the isolated servers are deployed to the server hosts,
the job manager replaces ${WLP_SHARED_DIR} with the
actual shared directory path, in this case /liberty/shared.[-] jre-06.00.31
[+] bin
[+] lib
[-] wlp-08.05.00.00
[+] bin
[ ] clients
[+] dev
[ ] lafiles
[+] lib
[+] templates
The following directories and files are included in the compressed (.zip) file for initial deployment of the Liberty profile servers and their applications to the working resources directory that is defined by the WLP_WORKING_DIR WebSphere variable. The project directory, samples, is located at the root of the compressed file.
[-] samples
[-] servers
[-] SecuritySample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o SecuritySample-01.00.war
[-] ServletSample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o ServletSample-01.00.war
[-] samples
[-] servers
[-] SecuritySample-01.01-01
o bootstrap.properties
o server.env
o server.xml
[ ] apps
o SecuritySample-01.01.war
This example first illustrates how to package the Liberty profile resources for an environment where the SDK (JRE), the Liberty profile runtime, and several applications are stored on shared disk, and two isolated (working) servers are stored on each server host. It then illustrates how to package a new version of a server and the application that it supports. Use of the job manager is mandatory for environments that include isolated Liberty profile servers. You cannot use the Liberty server script to manage the servers. For information about sharing server configuration settings at the host and network levels, see "Using includes in the configuration."
Shared disk
[-] liberty
[-] shared
[-] jre-06.00.31
[+] bin
[+] lib
[-] wlp-08.05.00.00
[+] bin
[ ] clients
[+] dev
[ ] lafiles
[+] lib
[+] templates
[-] samples
[ ] apps
o SecuritySample-01.00.war
o ServletSample-01.00-01.war
Server hosts
[-] liberty
[-] working
[-] samples
[-] servers
[-] SecuritySample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[-] ServletSample-01.00-01
o bootstrap.properties
o server.env
o server.xml
JAVA_HOME=${WLP_SHARED_DIR}/jre-06.00.31
WLP_RUNTIME_DIR=${WLP_SHARED_DIR}/wlp-08.05.00.00
The paths
include the WLP_SHARED_DIR WebSphere variable instead of a hardcoded
path. When the isolated servers are deployed to the server hosts,
the job manager replaces ${WLP_SHARED_DIR} with the
actual shared directory path, in this case /liberty/shared.
On each server host, the remote shared resources directory is mounted
at /liberty/shared.<application id="SecuritySample"
location="/liberty/shared/apps/SecuritySample-01.00.war"
name="SecuritySample" type="war"/>
apps.dir=${WLP_SHARED_DIR}/${CURRENT_PROJECT}/apps
security.sample.version=1.00
<application id="SecuritySample"
location="${apps.dir}/SecuritySample-${security.sample.version}.war"
name="SecuritySample" type="war"/>
[-] jre-06.00.31
[+] bin
[+] lib
[-] wlp-08.05.00.00
[+] bin
[ ] clients
[+] dev
[ ] lafiles
[+] lib
[+] templates
[-] samples
[ ] apps
o SecuritySample-01.00.war
o ServletSample-01.00.war
The following directories and files are included in a compressed (.zip) file for initial deployment of the Liberty profile servers to the working resources directory that is defined by the WLP_WORKING_DIR WebSphere variable:
[-] samples
[-] servers
[-] SecuritySample-01.01-01
o bootstrap.properties
o server.env
o server.xml
[ ] ServletSample-01.00-01
o bootstrap.properties
o server.env
o server.xml
[-] samples
[ ] apps
o SecuritySample-01.01.war
The following directories and files are included in a compressed (.zip) file for later deployment of a new version of a server to the working resources directory that is defined by the WLP_WORKING_DIR WebSphere variable. The project directory, samples, is located at the root of the compressed file.
[-] samples
[-] servers
[-] SecuritySample-01.01-01
o bootstrap.properties
o server.env
o server.xml
You must change the application element in the server.xml file to include Version 1.01 of the WAR file; for example:
<application id="SecuritySample"
location="/liberty/shared/apps/SecuritySample-01.01.war"
name="SecuritySample" type="war"/>
Alternatively, if the bootstrap.properties file contains the application version information, you must change the file accordingly; for example:
security.sample.version=1.01
You then use the updated version information in the application element in the server.xml file; for example:
<application id="SecuritySample"
location="${apps.dir}/SecuritySample-${security.sample.version}.war"
name="SecuritySample" type="war"/>
Set variables that enable the job manager to install and search for Liberty profile resources.