Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > IDL Code > IDL items (reference information) > Locality constraint item (IDL code)
  
Locality constraint item (IDL code)
Create a Locality Constraint through the Deployment Plan Editor: Right-click the Deployment Plan, and then click Edit Plan. From the Deployment Plan Editor, click the Locality Constraints tab, right-click in free space, point to Add Locality Constraint, and then click the command for the appropriate locality kind. The available Locality Kinds are as follows:
Same Node Any Process
Same Node Same Process
Same Node Different Process
Different Node
Different Process
No Constraint
After creating a Locality Constraint, you can apply the Locality Constraint to a Component Part through the Deployment Plan Editor.
A Locality Constraint can be applied to many Component Parts, and a Component Part can have many Locality Constraints applied.
After applying Locality Constraints to Component Parts, the Deployment Plan Editor enforces those constraints when attempting to deploy Component Parts to Processes. ACS does not generate any code for Locality Constraints created in the model.
* 
When a Locality Constraint is applied to a Component Part, the IDL Profile creates a Constrains link between the two items. A Constrains link is a UML Dependency that is stereotyped by the «Constrains» stereotype.
To change the Locality Kind of a Locality Constraint: on the Locality Constraint's property pages, click the Locality Constraint tab, and then set the value of the Locality Kind tag definition as required.
You can create a Locality Constraint Report for a Deployment Plan. The report shows the Component Parts to which each Locality Constraint is applied.
In Modeler, the Relationships pane shows which Locality Constraints are applied to Component Parts:
Expand a Locality Constraint, and then expand the Depends on folder to show the Component Parts to which the Locality Constraint is applied.
Alternatively, you can open the Locality Constraint's Property Pages, click the Items tab, and in the Show Associated list select Dependees.
Expand a Component Part, and then expand the Dependents folder to show the Locality Constraints that are applied to the Component Part.
A Locality Constraint is a UML Constraint that is stereotyped by the «Locality Constraint» stereotype.
The following sections provide information about how a Locality Constraint is used in the model.
Owned By
Deployment Plan
Owns
None.
Shown on these diagrams
None.
IDL Profile properties
Locality Kind - specifies the kind of the Locality Kind, that is, Same Node Any Process, Same Node Same Process, Same Node Different Process, Different Node, Different Process or No Constraint.