Process mapping for IDL (IDL code)
For each Process, ACS generates an Instance element and localityConstraint element in the Component Deployment Plan (CDP) file that is generated for the Deployment Plan that owns the Process.
ACS generates code similar to this:
<instance xmi:id="_aaeb79f9-3aa0-41c4-9578-53dc3dc33229">
<name>Process 1 [IDL Profile::DnC Elements::CCM_DDS::LocalityManager - Package1::Deployment Plan2]</name>
<node></node>
<source/>
<implementation xmi:idref="360772cf-433e-455c-9926-251051348650"/>
<configProperty>
<name>edu.vanderbilt.dre.DAnCE.LocalityManager.ProcessName</name>
<value>
<type>
<kind>tk_string</kind>
</type>
<value>
<string>Process_1</string>
</value>
</value>
</configProperty>
</instance>
<localityConstraint>
<constraint>SameProcess</constraint>
<!--Process 1 [IDL Profile::DnC Elements::CCM_DDS::LocalityManager - Package1::Deployment Plan2]-->
<constrainedInstance xmi:idref="_aaeb79f9-3aa0-41c4-9578-53dc3dc33229"/>
</localityConstraint>
When a Process is deployed to a Node, the Node is referenced by the Node element within in the Instance element that is generated for the Process.
When a value is set for the cpuAffinity attribute of a Process, ACS generates a configProperty element for the Instance element that is generated for the Process. The configProperty element specifies the value of edu.vanderbilt.dre.DAnCE.LocalityManager.CPUAffinity.
When a value is set for the localityArguments attribute of a Process, ACS generates a configProperty element for the Instance element that is generated for the Process. The configProperty element specifies the value of edu.vanderbilt.dre.DAnCE.LocalityManager.LocalityArguments.
When a value is set for the processPriority attribute of a Process, ACS generates a configProperty element for the Instance element that is generated for the Process. The configProperty element specifies the value of edu.vanderbilt.dre.DAnCE.LocalityManager.ProcessPriority.
Was this helpful?