Job configuration

Based on the procedure for upload type SIMATIC S7, you will be shown an example of a job configuration. For each upload types, there are specific variations in the job configuration.

Section: Job configuration

Example:

1. Start the AdminClient and open the Jobs module.
2. In the Project tree, select the component for which you want to create the job.
3. In the menu tab, click on Create or drag-and-drop the components into the Jobs section.
4. Check in the Job configuration (right side) if the preselected Upload type is the one that you want to use.
5. When selecting Execute, you need to decide if the job is to be executed according to Scheduled, Not scheduled, Using BackupClient or Triggered by URL*.

*You have the option to trigger a job using an OPC variable. This functionality is an add-on and therefore requires additional licensing.

Section: General

1. Job name: Give your job a descriptive name (limited to 64 characters).
2. Components: Under Components, select the path to your component in the Project tree.
3. Warning when the Backup is older than: Select an age for the backup from the dropdown if required. The default selection is Never warn.
   If a time period has been selected here, jobs, for which the backup is older than the selected time period, are marked with a warning icon. This is located in the column Timestamp backup.




4. Schedule: This field will only be displayed if you have selected the value According to schedule located under the drop-down menu Execute. Once you have selected this field, the dialog Schedule will then open. Here, you can enter the start time and the frequency that you require.
   
   Image: Dialog Schedule
   
   
5. On error: This field will only be displayed if you have selected the value According to schedule located under the drop-down menu Execute. Once you have clicked on this field, the dialog On error will then open. Here, you can enter if you want a job execution to be repeated when errors occur. You have also the option here to determine the maximum number of attempts as well as the length of pauses between different attempts.
   
   Image: Dialog On error
   
   
6. Execution by: This displays the name of the machine from which to run the job. By default, this is determined automatically. For parallel server systems you can select a computer.
   In case of server synchronization, if the job is to be executed only on one of the synchronized servers, the corresponding server must be selected here. When the value Automatic is used, the job will be executed by both servers after synchronization.
   After importing a license with a new serial number, it may happen that the (old) serial number is displayed here instead of the computer name. If this should occur, you can do the following steps:
   

• Restart the MasterService, if you have not already done so.

• For parallel servers, check in the System Dashboard module whether all to-dos have been processed.

• If the display is still wrong, you have to select a new computer name. Otherwise, the job cannot be executed according to the schedule.

Section: Notification

The Notification section is displayed only if you have specified in the Upload Type-Specific Configuration dialog that job-specific or daily emails are to be sent for job execution.

1. When you click on the field Who to notify.
2. The dialog Who to notify will open.
3. Select the users and user groups to be notified and check the appropriate checkboxes.
4. E-mail recipients who are not users can be entered in the field Additional email addresses. Enter multiple users separately with commas.

Section: Upload and Compare

1. Save policy: The following options are available to you:
• Always save backup (overwriting previous backup if equal):
  Use this option if you want to create a maximum of one backup. It contains the current values and all other files that are ignored during the comparison.
• Save backup only if different to previous backup:
  Use this option if you only want to add a new backup, when a change is detected (which depends on what values are included in the compare process)
  
• Always save backup (keeping previous backup even if equal):
  Use this option if you want to add a new backup every time a job is executed. If your traceability rules require you to keep backups for at least a year, you will need to make sure that the number of remaining backups (Rollover) is set based on your backup frequency. Bear in mind that use of this save policy with a high roll-over number could result in a lot of disk space being used up.
  
2. Number of remaining Backups (Rollover): Entered the desired value. After reaching this value, the new Backup will overwrite the oldest. The default is: 5
3. Upload Agent: If you want to use an upload agent for this job, select it under Upload agent. Click on Check connection: To ensure that the computer on which the agent is installed can be accessed. If no success, the job will fail as well.
   Remember that when you use an agent, all user ID information and paths relate to the computer on which the agent is installed and not the server. If you later specify a username or a network path, you need to make sure that this user exists on the computer on which the agent is installed or that the network path is accessible from the computer in question.
   
4. Comparison strategy: Select a Compare policy from the dropdown list.
   This contains the following options:
   • Server version <-> Backup, Previous backup <-> backup
     The backup of the (online) version on the device is first compared with the last checked-in version of the project, this backup is then compared to the last backup.
     This option can give you more information than any other. It is however important to think carefully when interpreting the results.
     Examples:
     • If the backup is different from the previous backup, but the same as the last checked-in version of the project, this indicates that a version was developed in the project, checked-in, and then deployed to the device. This is the recommended workflow.
     • If the backup is different from the last checked-in version of the project, but the same as the previous backup, this indicates that a new version of the project has been created and checked-in, but not yet deployed to the device.
     • If the backup is different to both the last checked-in version of the project and the previous backup, this indicates that a new version of the project has been developed and deployed to the device, but not yet versioned and checked-in.
   • Server version <-> Backup
     The program running on the device is compared with the latest checked-in version of the project. Job results are not compared. We recommend using this option if the system Always detects differences between backup and previous backup (regardless of the compare configuration). In this case, there is no point running the comparison between backup and previous backup.
   • Previous backup <-> backup
     The program running on the device is compared with the previous backup. It is not compared with the newest version.
     Detecting a difference here could mean one of the following things:
     • A new version of the project has been developed and deployed to the device.
     • Actual or forced values were not ignored during the comparison (through which the backup always differs from the previous backup).
     • The program on the device was changed. You can find out what was changed by using the compare functionality.
5. Compare Agent: If you want to use a compare agent for this job, select it under Compare agent. Click on Check connection to ascertain whether it is possible to access the computer on which the agent has been installed. If the connection fails, the job will fail as well.
6. To configure the comparison, check the Enable configuration of job-specific compare checkbox, and then select Comparison configuration.

Section: automatically creating versions after job execution

This section is only displayed if in the dialog Upload specific configuration:

• the option Enable automatic creation of a version in the General tab has been activated, and
• if in the tab of the corresponding upload type, the option Enable automatic creation of a version has been checked.

Create version when: In the dropdown list, you can specify when a new version of the component should be created automatically:

• Never: No versions will be automatically created.
• Differences found (Server version <-> Backup): A new version is produced automatically if differences between the server version and backup are detected.
• No base version exists: If no base version exists, a base version will be created independent of the job status.
• Always: If the job has been successfully executed, a new version will be automatically created. If an error occurs during execution, a new version will not be created.

Section: Job information

In this section, you will be find the Job ID and the component ID. These are for example relevant for Scripting.

Section: SIMATIC S7 Settings

Configure the settings for your chosen upload type.

Section: Configure the section Access path details

Select the Access path you want to use for communication with the controller.

Section: Backup

Reduce network load and exclude defined blocks from comparison.

Section: Advanced

Change the TCP/IP port, specify a CPU password, configure retries on failed uploads, and specify waiting times between data packets.

  	[Common]

        4900=1

	[FTP]

        4900=1

	[Common]

	4930=2

	[FTP]

	4930=2