In a flexible management environment, you can submit the Distribute
file job to copy files to managed targets of the job manager.
You must distribute files before you can submit jobs that use the
files. For example, you must distribute an enterprise application
before you can install or update the application on managed application
server targets. Similarly, you must distribute a properties file to
managed application server targets before you can apply the file to
configure the application servers.
Before you begin
Start the job manager. Ensure that the targets to which
you want to copy a file are registered with the job manager.
- To register a stand-alone application server with the job manager,
first use the administrative agent registerNode command to register
the stand-alone application server with the administrative agent.
Then, use the administrative agent console or registerWithJobManager
command to register the stand-alone application server target with
the job manager.
- To register a deployment manager with the job manager, use the
deployment manager console or the registerWithJobManager command.
If you are collecting a file on a host, you must first register
the host with the job manager.
Start the targets. If a target
is a stand-alone application server, also start the administrative
agent.
Your ID at the job manager must be authorized for the
administrator role or the operator role to submit jobs. When you submit
a job, you can specify a user name and password for authentication
and authorization at the target or targets. When you submit a job
to multiple targets, the user name and password or the credentials
for the submitter must apply all the job targets.
You can simplify
administration of multiple targets by submitting jobs against groups
of targets. Before you can submit a job for a target group, you must
create the target group.
About this task
You can use the administrative console of the job manager
or the deployment manager to submit a job that moves a file to targets.
From the console, choose the Distribute file job,
specify the file to transfer, specify job options, schedule the job,
review the summary, and submit the job. When the job runs, the job
manager copies the file into the downloadedContent directory
of the administrative agent profile or deployment manager profile.
You
must distribute a file before running the following jobs:
- Install application
- Update application
- Configure properties
- Run wsadmin script
This topic describes how to run the Distribute
file job using a job manager console or the deployment
manager console. Instead of using a console, you can run the distributeFile
job script in the AdministrativeJobs command group to distribute the
file to targets. See the Administrative job types topic.
newfeat Avoid trouble: The distribute
file job can transfer files to the QShell only. Files are transferred
in binary mode, therefore there is no conversion of character sets
or encoding during the transfer.
gotcha
newfeat Avoid trouble: The distribute file job can transfer
files that are accessible from the z/OS UNIX shell only. Files are
transferred in binary mode, therefore there is no conversion of character
sets or encoding during the transfer.
gotcha
Procedure
- Copy the file that you want to distribute to the /config/temp/JobManager directory
of the job manager profile.
If the JobManager directory
does not exist, create the JobManager directory
in the job manager profile /config/temp directory.
To create and access the directory, you must have the appropriate
authority.
For example, copy the DynaCacheEsi.ear file
from the app_server_root/installableApps directory
to the /config/temp/JobManager directory of the
job manager profile.
- Click from the navigation tree of the administrative console.
- Choose a job to distribute a file.
- Select the Distribute file job
type from the list.
- Optionally describe the job.
- Click Next.
- Choose the targets to which you want to distribute the
file.
- 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.
The target
can be a host.
If the targets are stand-alone application servers
that are administered by an administrative agent, you can select one
stand-alone target instead of all the stand-alone targets. All the
targets can use the file that is distributed to the downloadedContent directory
of the administrative agent.
- If user authentication is required, specify a user name,
password, or any other authentication values as needed.
- Click Next.
- Specify parameters for the distribute file job.
- For Source, specify the uniform
resource locator (URL) for the file that you want to distribute.
For the default distribution provider, the location is a
file URL relative to the job manager profile config/temp/JobManager directory.
For the DynaCacheEsi.ear file, specify
the following:
- Node:
file://DynaCacheEsi.ear
![[Updated in April 2013]](../../deltaend.gif)
apr2013
- Host:
DynaCacheEsi.ear
newfeatYou can specify files on hosts using
wildcards. Supported wildcard characters are (*) and (?).
- Asterisk (*) – for multiple unknown or variable characters in
the term.
- Question mark (?) – for a single unknown or variable character
in the term.
- For Destination, specify the
location on the target where the job manager stores the file. The
destination parameter is relative to the downloadedContent directory
of the administrative agent or deployment manager profile.
Remember
the value that you specify for the file. If you later run a job that
references this file, you use the destination value to identify the
file.
For the DynaCacheEsi.ear file,
specify a value that identifies the file. For example:dynacache_esi_sample
For hosts, there are
no restrictions. Specify an absolute path. The path must be a directory.
For example:
/home/userA
- For Distribution provider, if
you use a distribution provider other than the default distribution
provider, specify the name of the distribution provider. For
the DynaCacheEsi.ear example, do not specify
a value and use the default distribution provider.
- 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. The email
addresses are saved in your console preferences. Each email address
is validated for format errors.
- Select when the job is available for submission.
You can submit the job to be available now, or specify a
time and date that the job is retrieved from the job manager.
- Select the job expiration.
The job expiration
is the time at which the job will no longer be available for targets
to run. You can use the default expiration, specify a time and date
for the job expiration, or specify an amount of time in which the
job expires. The default expiration is defined on the Job manager
configuration panel.
- 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 job manager copies the file into the downloadedContent directory
of the administrative agent or deployment manager profile. The name
of the file is the destination.
For the DynaCacheEsi.ear example,
a file named dynacache_esi_sample is copied to
the downloadedContent directory.
What to do next
On the Job status page, click the ID of the distribute
file 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 manager successfully copies the file to the targets, submit
jobs that use the distributed file:
- Install application
- Update application
- Configure properties
- Run wsadmin script
- Remove file
For the DynaCacheEsi.ear example, you
can install the application.