Import a Process Model

Depending on the size of your model, the import may take some time. A progress box shows all changes being made to the Galaxy (or a preview of all changes if preview mode is selected).

You can cancel the import while it is running, but it may take some time for it to get to a good cancelation point.

The import utility retains several of the key settings between imports. The settings it retains are typically not changed from one run to the next. If you are importing in preview mode, the settings are not retained.

Important: The settings are only saved for the current IDE node. If you run the import on a different IDE, make sure the settings are identically configured.

After you perform the import, check the ArchestrA Logger for warnings. If name conflicts occur, you will need to manually correct them and retry the import.

To import a process model

1. In the ArchestrA IDE, on the InBatch menu, click Import AVEVA Batch Management Model. The Import AVEVA Batch Management Model dialog box appears.

   

2. In the Batch Server area, type the node name for the AVEVA Batch Management Server you want to connect to and then click Connect.

   After the utility connects to the server, the remainder of the dialog box becomes available.

   If you can't connect to the AVEVA Batch Management Server, check the ArchestrA Logger for more details.

3. In the Base Templates area, type the four base template names for the AVEVA Batch Management ApplicationObjects. These default to the imported template names, but should be changed to a new derived template name.

4. In the Options area, configure the optional import options.

   • Select the Preview only mode check box for the utility to perform the import actions without actually making any changes to the Galaxy or TagLinker database. This allows you to see (and possibly verify) what changes will be made by a normal import.

   • (rarely used) Select the Do not update AVEVA Batch Management Tag Linker Database check box for the utility to perform the import normally, but not make any changes to the TagLinker database (CfgLinkDB). This option is only used if you want to create the AVEVA Batch Management Process Model in the Galaxy, but not have any run-time communications through the objects (that is, no IBMX).

     Important: If you use this feature once, you should always use this feature. Otherwise, your TagLinker database will most likely end up in an inconsistent state.

   • Click Prefix or Suffix for the utility to perform the import normally, but add a prefix or suffix to every Process, Transfer, Unit, Connection, and Segment object. This allows you to avoid possible naming conflicts with existing objects in a Galaxy.

     Important: Because Unit and Connection names are concatenated with Phase names in the Galaxy to create a unique "tagname" for each phase, you must be sure that the length of this "tagname" with the prefix/suffix added does not exceed 32 characters.

5. In the AVEVA Batch Management Security Credentials area, configure the user name and password for a user who has application access to both ModelEdit and TagLinker.

   If a domain is required, you can specify it in front of the user name (for example, domain\userid).

6. Click Import.