Creating a Project-Based Job
Project-based jobs allow you to schedule ePublisher AutoMap to generate the output defined by an existing ePublisher project. You first create the ePublisher project as needed, or you can use an existing project. Then, you create a project-based job so ePublisher AutoMap can use the project to generate the output defined by the project.
To create a project-based job
Start ePublisher AutoMap.
On the File menu, click New Job.
Click ePublisher project on the New Job window.
Type the path or click the Browse Folder icon to select the ePublisher project you want to schedule, and then click OK.
In the Job Name field, type the desired job name.
The Choose ePublisher project field displays the previously selected ePublisher project. You can change the selected project.
If you want to run a pre- or post-build script before or after the job runs, complete the following steps:
Click the Edit Script button for the Pre-build or Post-build script field.
Type or paste your script into the editor, and then click OK. For more information about scripts, see “Using Scripts for Additional Custom Processing” on page 309.
ePublisher displays the Target Selection window. This window lets you select which targets to generate as part of this ePublisher AutoMap job. Depending on your project, there may be multiple targets listed in the Target Selection window.
Select the check box in the Build column next to each target you want to generate, and then click Finish.
Schedule the job as needed, and then click OK. You can also schedule the job at a later time. For more information, see “Scheduling Jobs with Windows Scheduler” on page 306.
Project-based jobs deploy output only if a deployment target is set in the project itself. This deployment information is specified in the target settings in ePublisher. ePublisher AutoMap reads only the deployment target name from the project. Therefore, you must make sure an output destination with the same name and is defined in ePublisher AutoMap or you may receive a deployment error. For more information, see “Defining Output Destinations” on page 300.