Step 6.1. Review Connect to Multiple Projects Technical Notes

Requirements for:

Multiple project tracking support.

Running more than one tracking project on the same node.

Multiple Viewer support.

Moving items across project boundaries

Order Execution Mgt. storage.


Extended attribute storage options.

Multiple project connection architecture.

Multiple project software transactions.

Multiple project tracking support requirements

Each tracking project must run in broadcast mode. Broadcast mode makes PRT data from one project available to other projects running on-node or off-node across a local area network.

Item and Reference ID's must be unique across all projects.

You cannot have two item ID's or reference ID's with the same name, even if they are defined in different projects.

Region names must be unique across all projects.

You cannot have two regions with the same name, even if the regions are in different projects.

Running more than one tracking project on the same node requirements

If you plan on running more than one tracking project on the same node, the name of the PRT services for each project must be unique.

The default service names PRT_DC, PRT_DS and TRK_RP must be modified to be unique on a given node. Before you run more than one project on a node, configure their PRT services uniquely.

It is suggested that you add a prefix to the name of each service that indicates the project it belongs to, e.g. MYPROJECT1PRT_DC.

Whenever you add another project to your multi-project configuration, you must delete the backing files for extended attributes. If you keep the extended attributes in backing files, do the following:

  1. Before deleting these files, use the PRT_Export utility to export PRT data that includes extended attribute data.

Important:  Make a file copy back up of the backing files as an extra precaution. Backing files for extended attributes are located in the ...\Proficy CIMPLICITY\Tracker folder.

  1. Delete the current backing files from project log directory.

  2. Start the project. This will recreate extended attribute backing files.

  3. Import the extended attributes using the PRT_Import utility.

Multiple Viewer support requirements

In order to view multiple projects:

PRT Services must be running for each project.

You must have access privileges to the projects you want to view.

Moving items across project boundaries requirements

If you want to move items across project boundaries, you have to do additional PRT startup configuration.

Order Execution Management central storage requirements

Central storage is:

Required for:

Ranges/criteria sets.

Tracker Attribute database (TADB)

Optional for extended attributes

Extended attribute storage options

Earlier versions stored extended attributes information in backing files. The new default is to store extended attributes in a database.

If you want to store Extended Attributes:


In backing files

Edit the file TrkAttribute.cfg and change the Attribute Storage Bitmask value to 2.

In a database

Accept the default Attribute Storage Bitmask value. If this value has been changed, restore the value of this bitmask to its default value of 4.



Note: See Tracker Extended Attributes Configuration (trkattribute.cfg) for an explanation of the TrkAttribute.cfg format.

More information

Option 10.2. Modify PRT Configuration.

Step 6. Connect to multiple projects.