Step 6.1. Review Connect to Multiple Projects Technical Notes
About this task
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. | |
and | |
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: