When a project is enabled for remote deployment, you can
deploy parallel jobs that are designed in that project. After you
design the job, you package the job and transfer it to the remote
computer.
Jobs that you plan to deploy remotely cannot use BASIC Transformer
stages, shared containers, or plugin stages.
- Specify the location of the parallel configuration
file to use for jobs that are remotely deployed.
Use
the APT_CONFIG_FILE environment variable to specify the location of
the configuration file in one of the following ways:
- To use the same configuration file for all jobs
on the remote computer, define the APT_CONFIG_FILE environment variable
in the InfoSphere DataStage Administrator
client on the host computer. The value that you specify is included
in all of the remote deployment job packages.
- To use the same configuration file for an individual
job, specify a value for the APT_CONFIG_FILE environment variable
as a job parameter in the job on the host computer. The value that
you specify is included in the remote deployment package for that
particular job.
- To specify the value at run time, set the value
of APT_CONFIG_FILE to $ENV in the InfoSphere DataStage Administrator
client on the host computer. Then, on the remote computer, define
APT_CONFIG_FILE as an environment variable. When you run the job on
the remote computer, the job uses the value that you specify at run
time.
- In the InfoSphere DataStage Designer
client, design your parallel job.
- Compile the parallel job.
- Compress the directory that contains the deployment package
for the job.
The package is in the directory that you specified
when you enabled the project for remote deployment.
- Copy the package to the equivalent directory on the remote
computer, and then extract the package.