Submitting jobs to deploy Liberty profile installations

We can use the job manager to submit jobs to deploy Liberty profile installations on target hosts.

New feature:

v8.5 introduces the Liberty profile, which provides the following features:


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 console New targets page (Jobs > Targets > New Host), specified an operating system user name for Administrative user with installation authority and a password or public-private key information for user authentication. If we 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 we 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 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

If we use an OpenSSH environment, set environment variables for the ssh exec channel:

  1. In the /etc/ssh/sshd_config file, set PermitUserEnvironment to yes.

  2. Change directory to the .ssh directory under the user home. Create a property file called environment and, in the file, set JAVA_HOME=absolute_path_to_the_java_home.

  3. Restart sshd. Run stopsrc -s ssh and then startsrc -s ssh.

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 we can run depend on the jobs supported by the host targets and the security credentials.

Instead of using a console, we can run wsadmin commands in the AdministrativeJobs command group. See the Administrative job types topic.

  1. Before installing Liberty profile resources, create one or more compressed (.zip) files containing the required Liberty profile resources in a directory structure which satisfies job manager rules.

    We can obtain the Liberty profile in either of the following ways:

    • During installation of WAS Network Deployment, select the WAS Liberty Profile optional feature. If we did not include this feature during the initial installation, we 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

  2. 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 SDK or Java runtime environment (JRE) is not included with the Liberty profile but is needed to run the servers and server management jobs. We 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.

  3. Set variables for Liberty profile installations.

    Specify an absolute path for the WLP_WORKING_DIR WebSphere variable. Depending your deployment topology, we might need to define the WLP_SHARED_DIR and WLP_ADDITIONAL_DIRS WebSphere variables. Do not specify relative paths for any of these variables.

  4. 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 (System administration > dmgr > Ports) or job manager console (System administration > Job manager > Ports).

    If we 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.

  5. Run the Install Liberty profile resources job.

  6. Run the Inventory job if we need to register preexisting Liberty profile resources with the job manager. Set variables for Liberty profile servers explains how to configure the directories that are searched when the Inventory job is run.

  7. 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 Jobs > Target resources to see Liberty resources in the list of target resources.


Related concepts

  • Liberty profile resources

    Related tasks

  • Registering host computers with job managers
  • Packaging a Liberty profile server from the command prompt
  • Start and stop the job manager
  • Checking job status

  • New target settings
  • Administrative job types

    Related information:

    IBM Education Assistant, WebSphere Application Server v8.5