Skip to content

Creating jobs

  1. Start the AdminClient and open the Jobs module.
  2. Select your GE Proficy iFIX component in the Project tree.
  3. Select the Create button in the menu bar or drag and drop the component into the Jobs area.
  4. Check that the upload type GE Proficy Machine Edition is displayed in the Job configuration area.
  5. Configure the general sections General, Notification, Upload and compare and Create a version automatically after job run. The sections Notification and Create a version automatically after job run are only displayed if the settings required for this have been made.
  6. Enter your access data for domain/user or computer name/user and your password in Network (UNC) settings under User name and Password.
  7. Enter the shared directory where the project data is stored in Resource and Subdirectory. If the network connection is successful, you can select the correct directory from the dropdown menu.
  8. Test access to the resource with the Check button.
  9. In Advanced you can adjust the data transfer on your network if necessary.
  10. In File specifications and compare settings you can adjust the comparison for the job. Activate the Enable specific configuration for this job checkbox and then click on Edit.
  11. Enter the desired files in the Configuration of backup files dialog.
  12. Save the job and test it with Execute selected jobs once.

Info

You can implement further settings for jobs of this upload type in the AdminClient in the Global settings dialog.

Notes on the recognized differences after successfully creating the Backup

Differences without details

For the differences for which no textual representation is offered, the project data is available in not interpretable form.

Searching for project data

The directories in which project data resides are stored in the project file SCU. Two scenarios are possible here:

  1. Parts of the project data are located outside the processing directory. A warning is issued that the parts of the project cannot be compared. This project data is then not part of a Version.

  2. Parts of the project data are inside the processing directory, but they are incorrect in relation to the project file SCU. A warning is issued that the parts of the project cannot be compared.

Example for Scenario 1:

Processing directory: ..\vdClientArchive\Prj\{working directory}

Project file: ..\Local\example.scu (relative to the working directory)

Local: ..\vdClientArchive\Prj\{working directory}\Local (path in project file)

Main recipes on drive C:\dynamics\RCM (path in project file)

Info

The files present in C:\dynamics\RCM are neither compared nor versioned.

Example for Scenario 2:

Processing directory: ..\vdClientArchive\Prj\{working directory}

Project file: ..\Local\example.scu (relative to working directory)

Local: ..\vdClientArchive\Prj\Working directory\Local (path specification in project file)

Info

Nothing except the project file is found, as the actual relative location of the project file does not match the location in the project file.

The project data is always versioned in any case.