You can submit the Start Liberty profile server job
to start a Liberty profile server
on one or more target hosts.
Before you begin
Start the job manager.
The Liberty profile server that you
want to start must be installed on all job targets. See Installing Liberty profile resources using
the job manager.
Your ID at the job manager must be authorized
for the administrator role or the operator role to submit jobs.
When registering a target host with the job manager,
you can save operating system security information. When you submit
a job to one or more targets for which security information has not
been saved, you must specify an authorized operating system user name
and either password or public-private key information for the user
name. The security credentials must be valid for all job targets.
A
Liberty profile server requires a Java development kit (JDK) or Java
runtime environment (JRE) to run this job. Set the JDK or JRE location
by completing one of the following actions:
- Set the JAVA_HOME property to the JDK or JRE location in the server.env file,
which is located in the server directory. The job reads the JAVA_HOME property
and sets it on the target environment before running the command to
start the server. However, this property is not used by the Liberty
server command if you start the server manually.
If JAVA_HOME is not specified in server.env or
in the user environment, the job manager looks for the JDK or JRE
in the user search path.
About this task
You can use the administrative console of the job manager
or the deployment manager to start Liberty profile servers on one
or more target hosts. From the console, choose the Start
Liberty profile server job, specify the server and job
options, review the summary, and submit the job.
This topic
describes how to run the Start Liberty profile server job
using the job manager console or the deployment manager console. Instead
of using a console, you can run the startLibertyProfileServer job
script in the AdministrativeJobs command group. See the Administrative
job types topic.
Procedure
- Click from the navigation tree of the administrative console.
- Choose a job to start a server.
- Select the Start Liberty profile server job
type from the list.
- Optionally specify a description of the job.
- Click Next.
- Choose the job targets.
- Select a group of targets from the list, or select Target
names.
Only groups of targets that are valid
for the job type that you selected are displayed in the list of target
groups.
- If you selected Target names,
then specify a target name and click Add, or
click Find and specify the chosen targets on
the Find targets page.
- If you did not choose to save security
authentication information when registering the target hosts with
the job manager, specify an operating system user name and password
or public-private key information for access to the target hosts.
The security credentials must be valid for all the job targets.
- Click Next.
- Specify parameters for the start Liberty profile job.
- For Server to be started,
specify the fully-qualified resource ID of the Liberty profile server to start. For example, if you want to start the defaultServer server
in the wlp runtime, specify the following resource
ID:
runtime/wlp/liberty_server/defaultServer
- Click Next.
- Schedule the job.
The times and dates that
you specify are relative to the job manager.
- Optionally specify one or more email addresses where
notifications are sent when the job finishes.
If you
specify multiple email addresses, separate them with commas.
- Select when the job is available for submission.
- Select the job expiration.
- Optionally specify a recurring interval for the job,
a start date and time for the interval, and an end date and time for
the interval.
- Click Next.
- Review the summary, and click Finish to
submit the job.
Results
The targets run the job and attempt to start the server.
What to do next
On the Job status page, click the
ID of the Start Liberty profile server job
and view the job status. Click the status refresh icon
to refresh the displayed 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, the status on the Target resources page
of the server is RUNNING. Click to
see the resource status.