Liberty profile resources

Liberty profile resources can be packaged into one or more compressed (.zip)
files. We can use the job manager in the WAS Network Deployment v8.5
product to deploy the resources to remote hosts. The grouping of the resources within a compressed file affects the scope and sharing of the resources. For more information, see Packaging Liberty profile resources.

Descriptions of Liberty profile resource types follow:

project

An optional container for resources. We can group related resources under the same project for ease of management and to avoid name conflicts
with resources from other projects.

runtime

The Liberty profile runtime, which includes the bin, clients, dev, lafiles, lib, and templates directories.

A customized instance of the runtime can include the etc directory with optional environment configuration files server.env and jvm.options.

liberty_server

A directory containing a server configuration file, server.xml, and the optional environment configuration files bootstrap.properties, server.env, and jvm.options. This directory is also the default location for the server working directory and log directory.

A server can be embedded in a runtime or isolated (separated)
from the runtime. We must configure isolated servers to use a specific instance of the runtime. We can administer isolated servers only using the job manager. (Command-line administration is not possible.)
For more information, see Packaging Liberty profile resources.

application_binary

An archive or a directory containing an application. The application binary is optionally deployed to a Liberty profile server. An application can be embedded in a server, embedded in a runtime, or isolated (separated)
from the runtime.

sdk

The Java software development kit that supports the Liberty profile servers and related tools. The SDK resource contains the directory path JRE_name/jre/bin/java or JRE_name/bin/java, where JRE_name is the name of the Java runtime environment.

Example Liberty profile resources

Each
of the following example Liberty profile resources includes a resource name, a resource ID, and a location on disk. The runtime, Liberty server, application binary, and SDK resources are included in a project resource named project1; however, project membership is optional for all resource types. Each resource is assumed to be installed in base directory /liberty.

Resource sharing and packaging

We can deploy self-contained Liberty profile installations that include the runtime, one or more embedded servers, and one or more embedded applications. To simplify initial deployment and ongoing
administration of large multiple-server environments, we can also deploy Liberty profile installations
where the runtime, application binary, and SDK resources are shared by multiple servers that reside on one host, or even many hosts.

Packaging Liberty profile resources illustrates several different deployment schemes and provides detailed information about configuring and packaging the resources for deployment to target hosts.