In a flexible management environment, you can submit the Collect
file job to copy a single file or a directory of files
from managed nodes to the job manager. When collecting a directory,
the job recursively zips the directory contents and copies the resulting
compressed format file. You might collect files before submitting
jobs that use the files. For example, you might collect and then distribute
an enterprise application before you install or update the application
on managed application server nodes. Similarly, you might collect
and then distribute a properties file to managed application server
nodes before you apply the file to configure the application servers.
Before you begin
Start the job manager. Ensure that the nodes from which
you want to copy a file are registered with the job manager.
If
a target node is deployment manager, start the deployment manager.
If a target node is a stand-alone application server, 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 node or nodes. When you submit a job
to multiple target nodes, the user name and password or the credentials
for the submitter must apply to all the job targets.
You can
simplify administration of a large number of nodes by submitting jobs
against groups of nodes. Before you can submit a job for a group of
nodes, you must create the group of nodes.
About this task
You can use the administrative console of the job manager
to submit a job that transfers a file or directory of files from target
nodes to the job manager. From the job manager console, choose the Collect
file job, specify the file or directory 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 from the application
server or deployment manager profile directory to the job manager
profile config/temp/JobManager/jobToken/nodeName directory.
This
topic describes how to run the Collect file job
using the job manager console. Instead of using the job manager console,
you can run the collectFile job script in the AdministrativeJobs command
group. See the Administrative job types topic.
Procedure
- Determine the location of the file or directory that you
want to collect relative to the profile_root directory
of the target node.
For example, suppose that you
want to collect the DynaCacheEsi.ear file from
the profile_root/AppSrv01/config/cells/myNode01Cell/applications/DynaCacheEsi.ear directory.
AppSrv01 is the target node profile name. AppSrv01 is a stand-alone
application server. myNode01Cell is the AppSrv01 cell name. The location
of the DynaCacheEsi.ear file relative to the
profile root, AppSrv01, is config/cells/myNode01Cell/applications/DynaCacheEsi.ear
- Click from the navigation tree of the job manager administrative
console.
- Choose the job.
- Select the Collect file job type
from the list.
- Optionally describe the job.
- Click Next.
- Choose the targets from which you want to collect the file
or directory.
- Select a group of nodes from the list, or select Node
names.
Only groups of nodes that are valid
for the job type that you selected are displayed in the list of groups
of nodes.
- If you selected Node names, then
specify a node name and click Add, or click Find and
specify the chosen nodes on the Find nodes page.
Select
the target node from which you want to collect a file or directory.
To continue with the example in step 1, suppose the AppSrv01 profile
is registered with the job manager as nodeA. Select nodeA.
- If user authentication is required, specify your user
name and password.
- Click Next.
- Specify parameters for the collect file job.
- For Source, specify the path
of the file or directory that you want to collect, relative to the profile_root directory
of the target node.
For example, to collect the DynaCacheEsi.ear file
from the profile_root/AppSrv01/config/cells/myNode01Cell/applications/DynaCacheEsi.ear directory,
specify the following path:
config/cells/myNode01Cell/applications/DynaCacheEsi.ear/DynaCacheEsi.ear
To collect a directory such as the logs directory
under the profile_root of
the target node, specify logs in the Source field.
- Optional: For Destination,
specify a destination name for the file or directory that is being
copied to the job manager.
By default, the file or directory
is placed in the job_manager_profile/config/temp/JobManager/jobToken/nodeName directory.
The file or directory retains its name unless you specify a different
name in the Destination field.
For the DynaCacheEsi.ear example, if
you do not specify a value for Destination,
the product copies the DynaCacheEsi.ear file
to a directory such as profile_root/JobMgr01/config/temp/JobManager/124517860634322577/nodeA.
In this example, JobMgr01 is the name of the job
manager profile, 124517860634322577 is the job token
identifier, and nodeA is the target node from which
the file was copied. The DynaCacheEsi.ear file
is placed in the nodeA directory. Suppose that
you want the DynaCacheEsi.ear file to have a
name such as dynacache_esi_sample in the nodeA
directory. If you specify dynacache_esi_sample for Destination,
the DynaCacheEsi.ear file is copied to the profile_root/JobMgr01/config/temp/JobManager/jobToken/nodeA directory,
where it has the name dynacache_esi_sample.
If you specify a Destination value,
remember the value. If you later run a job that references the collected
file or directory, you can use the destination value to identify the
file or directory.
- 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 file or logs directory
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 e-mail addresses where
notifications are sent when the job finishes.
If you
specify multiple e-mail addresses, separate them with commas. The
e-mail addresses are saved in your console preferences. Each e-mail
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 nodes
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 or directory into the job_manager_profile/config/temp/JobManager/jobToken/nodeName directory.
The name of the collection file or directory is the destination. If
you did not specify a destination value, then the file or directory
retains its original name.
For the DynaCacheEsi.ear example,
the file is copied to the job_manager_profile/config/temp/JobManager/jobToken/nodeA directory.
What to do next
On the Job status page, click the ID of the collect 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 or directory from the
targeted nodes to the job manager, you can submit jobs that distribute
collected files.