Skip to content

Configuring GE Proficy iFIX jobs

  1. Create a job with the Network (UNC) upload type.
  2. In the Username and Password fields under Network (UNC) settings, enter the credentials of the user who is accessing the network resources. The user must have the necessary access rights.
  3. In the Resource field, enter the computer name or IP address of the computer that you want to access via the network.
  4. To ensure that the the login to the computer is possible with the specified credentials, select the Check button. If the check is not successful, the job will also fail.

  5. If the data is stored in a subdirectory of the network resource, enter the path of the subdirectory in the Subdirectory field. Access to the subdirectory must be possible with the specified credentials.

  6. Under Advanced, you can reduce the network load caused by the job by increasing the value of the Sleep interval between data packets field and reducing the value for Maximum size of data packets.

    Higher values for the waiting time and lower values for the maximum packet size mean that the job execution takes more time.

  7. Select the Upload only when timestamp is different (reduces network load) checkbox to ensure that the timestamp instead of the content of the files is checked during the upload. This means that only new and edited files are uploaded for a backup. Files without changes are transferred from the previous backup, which further limits the network load.

  8. The Make offline project available to scripting interface checkbox enables upload scripts started by the job to access the latest checked-in version.

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 .SCU project file. 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.

    Example:

    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.

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

    Example:

    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

    Only the project file is found because its actual relative location does not match the path within the file.

    The project data is always versioned in all cases.

Related topics