Jobs
A job is a unit of replication. It has source locations that specify where to replicate from and a destination location that specifies where to replicate to. Jobs have list of subjobs. Each subjob represents a database table that should be replicated or a stored procedure that is executed to replicate data. To perform replication through a job, the job must be run. Jobs can be run manually or scheduled to run at a specific time or at specific time intervals.
To view a list of all the jobs in the system go to General setup > Replication > View jobs. The Jobs view appears.
If you have inserted the default replication data (see section Insert Default Replication Data) that ships with the Site Manager, you will see a list similar to the one in the image above.
To create a new job, click the add 
button.
Enter a description for the new job. Click OK and the Job view appears.
4.3.1 The Subjobs Tab
The subjobs tab shows all subjobs used by this job. For a new job, this list will be empty. Below the subjob list are buttons to work with the subjobs:
|
|
Edit the selected subjob |
|
|
Add a new subjob |
|
|
Remove all selected subjobs |
|
|
Move a subjob up in the list* |
|
|
Move a subjob down in the list* |
* In most cases, the order of the subjobs in the list does not matter. However, if the subjobs are working with database tables that have foreign key constraints, the correct order of the subjobs in the list is critical for the successful run of the job.
When you click the add button to add a new subjob the Add Subjob dialog box appears:
The list of available subjobs is partially dependent upon which source location you have set for your job because normal and action type subjobs are always bound to a specific database version. In the Add Subjob dialog box you can set the source location explicitly and once you have, the list of available subjobs will be refreshed.
You can select as many subjobs as you need. Click OK to have the selected subjobs added to your job. You can also click the add 
button to create a new subjob from scratch.
By default, a job has its own list of subjobs. In some cases, however, you might want to use the subjob list of another job. The Use subjobs from job field can be set to use a subjob list from another job. By default, this field is set to Current job. If you change this to some other job, the subjob list of the selected job will be used instead.
Note, however, that you can only use the Add, Remove, Move up and Move down buttons when the Current job is selected.
For more information on how to set up a subjob see section Subjobs.
The subjobs listed in the subjob tab have a checkbox in front of their names.
Uncheck a subjob in the subjob list to disable that subjob from being used when the job is run.
The Triggers Tab
Under the Triggers tab you specify when the job will be run.
Three triggering options are available:
Run manually - The job will only be run if a user explicitly runs it from the Jobs list view or the Job edit view.
Run once - The job will be run only once at a specific date and time.
Run multiple times - The job will be run repeatedly at the interval specified in the Recurrence pattern box. The Range box allows you to specify the earliest start time of the job through the Start fields, and optionally when the job should no longer be run through the End by fields.
The Log tab
Under the Log tab you are able to view the log for all jobs
| Last updated: | 29th November 2016 |
| Version: | LS One 2016.1 |
