You can use the job manager to submit jobs to deploy and
manage Liberty profile installations on target hosts.
Before you begin

New feature:
Version 8.5
introduces the Liberty profile, which provides the following features:
- Central administration through job manager jobs
- You can use the job manager to submit jobs that support the full
life cycle of Liberty profile resource
deployment from initial install, to updates, to uninstall.
- A deployment manager is not required, although you can use the
job manager function available on a deployment manager to administer
Liberty profile servers and their resources.
- Quick installation
- Store the Liberty profile resources
in one or more compressed (.zip) files and run
the Install Liberty profile resources job to
transfer and extract the files.
- Installation of Liberty profile resources
requires no formal installation tool such as IBM Installation Manager.
- To simplify deployment and maintenance, you can
share a software development kit (SDK), runtime binary files, server
configuration files, and application binary files among many isolated Liberty profile server instances.
- No agent is required on target hosts, reducing administration
overhead.
- Non-destructive update enables easy installation of new versions
of Liberty profile resources
of any type. You can switch easily between old and new versions of
resources, or run concurrent versions of resources.
newfeat
Your ID at the job manager must be authorized for the
administrator or operator role to submit jobs.
Before submitting
a job, start the job manager. One of the job manager targets must
be an unmanaged host to run Liberty profile jobs. If no target
is an unmanaged host, register a host. See "Registering host computers
with job managers."
When registering a target
host with the job manager on an administrative console New
targets page (), you specify an operating system user name for Administrative
user with installation authority and a password or public-private
key information for user authentication. If you specify a user name
and security credentials during job submission and select more than
one target host, the user name and security credentials is used for
all target hosts. The console user ID and password is not used to
authenticate at the target hosts.
Best practice: When
registering a target host, if you selected
Save security
information on the console or set
saveSecurity to
true in
the
registerHost command, then you do not need
to specify an operating system user name and security credentials
when submitting jobs.
bprac
Best practice: To
easily select the targets on which to run a job, use the administrative
console or wsadmin to define appropriate target groups. Then, when
submitting a job, select the appropriate target group instead of entering
or selecting the individual targets.
bprac
About this task
The topics in this section describe how to install Liberty profile resources and to
administer Liberty profile servers
by running jobs in the job manager console or the deployment manager
console.
The jobs that you can run depend on the jobs supported
by the host targets and your security credentials.
Instead of
using a console, you can run wsadmin commands in the AdministrativeJobs
command group. See the Administrative job types topic.
Procedure
- Before installing Liberty profile resources, create
one or more compressed (.zip) files that contain
the required Liberty profile resources
in a directory structure which satisfies job manager rules.
You
can obtain the Liberty profile in
either of the following ways:
- During installation of WebSphere® Application Server, Network Deployment, select the WebSphere
Application Server Liberty Profile optional feature. If
you did not include this feature during the initial installation,
you can add this feature using the Modify function
in the Installation Manager. Liberty profile server is installed into
the app_server_root/wlp directory.
- Download the .zip file from http://wasdev.net.
Packaging Liberty profile resources describes
how to create properly structured compressed (.zip)
files for several different deployment topologies. For additional
overview information and examples, see the IBM Education Assistant
modules and labs.
A software development kit (SDK) or Java runtime
environment (JRE) is not included with the Liberty profile but is needed to
run the servers and server management jobs. You must use the job manager
to deploy an SDK or JRE to the target hosts or use an SDK or JRE installed
previously on the target hosts.
- Set variables
for Liberty profile installations.
Specify an
absolute path for the WLP_WORKING_DIR WebSphere variable. Depending
your deployment topology, you might need to define the WLP_SHARED_DIR
and WLP_ADDITIONAL_DIRS WebSphere variables. Do not specify relative
paths for any of these variables.
- Optional: If Liberty profile
servers use the serverStatus-1.0 feature, status
from the servers is automatically sent to the STATUS_LISTENER_ADDRESS
port. To change the STATUS_LISTENER_ADDRESS port number, use the Ports page
of a deployment manager console () or job manager console ().
If you change the STATUS_LISTENER_ADDRESS
port number after installing Liberty profile resources, you will no
longer receive automatic status from the previously installed Liberty
profile resources.
- Run the
Install Liberty profile resources job.
- Run
the Inventory job if you need to register preexisting Liberty profile resources with
the job manager. Setting variables for Liberty profile servers explains
how to configure the directories that are searched when the Inventory
job is run.
- Run jobs that administer Liberty profile servers and resources:
What to do next
After you submit a job, go to the Job status page
and click the job ID to view the job status. If the job is not successful,
view any error messages that result from running the job, correct
the error condition, and submit the job again.
If the job is
successful, click to see Liberty resources in the
list of target resources.