Cisco Cisco Workload Automation 6.3 ユーザーガイド
25
Configuring the CWA Transporter
Configuring Transporter Options
Configuring Transporter Options
You use the Configuration Options dialog to configure the Transporter to work according to your personal preference.
Keep these things in mind when configuring the Transporter:
Keep these things in mind when configuring the Transporter:
Performance Properties
The following configurations are available in order to provide improved performance for unfiltered job reads. Multiple options
have been provided for flexibility and the option to be configured may require some tuning based on specific user
environments. For tuning purpose, it is best to run Transporter in debug mode with an open console so that you can view how
the reads are performing.
have been provided for flexibility and the option to be configured may require some tuning based on specific user
environments. For tuning purpose, it is best to run Transporter in debug mode with an open console so that you can view how
the reads are performing.
Note: Only one parameter, READJOBS_PAGINATED, READJOBS_BATCHES, or READJOBS_ALL should be set to “true” at a
time. Parameter READ_BATCHES applies to READJOBS_PAGINATED or READJOBS_BATCHES. If none of these parameters
is set, the default configuration is READ_BATCHES=500, READJOBS_BATCHES=true.
time. Parameter READ_BATCHES applies to READJOBS_PAGINATED or READJOBS_BATCHES. If none of these parameters
is set, the default configuration is READ_BATCHES=500, READJOBS_BATCHES=true.
READJOBS_PAGINATED
Configures Client Manager to return job data in pages of READ_BATCHES batches.
For example:
READ_BATCHES=1000 and READJOBS_PAGINATED=true
tells Client Manager to return job data in batches of 1000. This approach reduces
the overhead on Client Manager as data is sent in smaller batches, as opposed to
the entire job data in one request. Increasing the READ_BATCHES will reduce the
number of requests sent to Client Manager, since the jobs are returned in larger
batches.
the overhead on Client Manager as data is sent in smaller batches, as opposed to
the entire job data in one request. Increasing the READ_BATCHES will reduce the
number of requests sent to Client Manager, since the jobs are returned in larger
batches.
Note: This approach may have less benefit given many jobs (i.e. 50K or more). The
batching is done at the Client Manager level.
batching is done at the Client Manager level.
None
READJOBS_BATCHES
Reads jobs given a range of job id’s, where the range is specified via
READ_BATCHES.
READ_BATCHES.
For example, if you have 50K job records with job IDs starting at 1 and ending at
50,000, and you have set
50,000, and you have set
READ_BATCHES=1000 and READJOBS_BATCHES=true
,
requests will be sent to Client Manager to query job records, in ranges as follows,
until no more records are returned.
until no more records are returned.
1. jobid >=1 and jobid <=1001
2. jobid >=1002 and jobid <= 2002
3. jobid >=2003 and jobid <= 3003
4. …
Note: This approach appears to be more beneficial when there are many job
records, for example, 50,000 or more).
records, for example, 50,000 or more).
None
READJOBS_ALL
This reads all jobs given the first and last job id. The result is that all jobs will be
read in a single request. This approach is different from the job.getList call in that
while both return all jobs, this request adds a query condition to the request, which
seems to produce better performance. However, because all records are returned
in a single request, Client Manager will need to process all the records for return to
Transporter. If there are many job records, the overhead on Client Manager may be
to high.
read in a single request. This approach is different from the job.getList call in that
while both return all jobs, this request adds a query condition to the request, which
seems to produce better performance. However, because all records are returned
in a single request, Client Manager will need to process all the records for return to
Transporter. If there are many job records, the overhead on Client Manager may be
to high.
None
XPORTER_DEBUG
Specify YES to run the Transporter in debug mode. Run the Transporter using the
transporter.cmd script located in bin.
transporter.cmd script located in bin.
None
Transporter Properties
Description
Default