Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > IDL Code > Modeling IDL code in Modeler > Overview of modeling IDL3+ and DDS code in Modeler (IDL code) > Overview of modeling IDL3+ and DDS code in Modeler (IDL code)
  
Overview of modeling IDL3+ and DDS code in Modeler (IDL code)
This topic provides an overview of modeling IDL3+ and DDS code in a model, from which you can generate the following files:
IDL3+ files for items such as Components, Bound Modules and Messages.
Component Domain Descriptor (CDD) files for Domains
Component Deployment Plan (CDP) files for Deployment Plans.
The generated deployment files (CDD and CDP files) are suitable for input to the Dance tool.
The Help provides reference, mapping and creation information for each IDL item type:
For information about adding the IDL Profile package to a Model, see Adding the IDL profile package to a model (IDL code).
For procedural information about creating IDL diagrams and items, see Creating a bound module (IDL code), Creating a client (IDL code), Creating a component (IDL code).
For reference information about an IDL diagram or item type, see Attribute item (IDL code), Bound module item (IDL code), Client item (IDL code).
For information about how the Modeler and IDL items map to IDL code, see Attribute mapping for IDL (IDL code), Basic Type mapping for IDL (IDL code), Bound module mapping for IDL (IDL code).
When you reverse engineer IDL files to a model that does not contain the IDL profile, the Reverser creates an IDL Profile in the Model; however, the IDL profile may contain only the Stereotypes and Tag Definitions required for the code you reverse engineered:
If you want to add the complete IDL profile to a Model that does not contain the IDL Profile package, see Adding the IDL profile package to a model.
If the Reverser has created an IDL profile in your Model and you want to update it so that it is complete, see Updating the IDL profile package in a model.
Modeling template modules
The IDL Profile includes the CCM_DDS::Typed template module that is specified in Annex A of the DDS for Lightweight CCM specification.
Most users will typically use the CCM_DDS::Typed template module and will not have to create any new Template Modules in the model.
For information about creating a Template Module, see Creating a template module.
Modeling assemblies
Create a top-level assembly (Component) from a Package.
After creating the top-level Component, you can create an Internal Component Diagram for that Component, and on the diagram you can define its Component Parts.
When you create a Component Part on the diagram, you select or create a Component to use as a type. You can create Attributes as necessary on a Component that is used as a type.
On each Component Part, create the required Clients, Services, Extended Port (Publishers), Extended Port (Consumers) and Connector Instances:
Create Clients and Services to communicate control instructions that do not require DDS. When you create a Client or Service, you select or create an Interface to use as a type. On the Interface, create the Operations that are required for the communication.
Create Extended Port (Consumers) and Extended Port (Publishers) to communicate data transfer that requires DDS. When you create an Extended Port (Consumer) or Extended Port (Publisher), you must select a Port Type to use as a type through either a selected or new Bound Module.
Create Connector Instances required to link Extended Port (Consumers) to Extended Port (Publishers).
Create Connections to link the Clients and Services that communicate with each other, and to link the Extended Port (Consumers), Extended Port (Publishers) and Connector Instances that communication with each other.
Use Package and Component owned Sequence Diagrams to help you model high-level communication between Component Parts and low-level communication between ports and Connector Instances.
Modeling domains
Create a Domain from a Package.
After creating a Domain, you can create an Internal Domain Diagram for that Domain, and on the diagram you can define its Nodes. For each Node, specify its host name and port number.
Modeling deployment plans
Create a Deployment Plan from a Package.
Through the Deployment Plan Editor, define Processes, Locality Constrains and attribute values:
Create Locality Constraints and apply those Locality Constraints to Component Parts.
Create Processes and allocate those Processes to Nodes.
Deploy Components Parts to Processes.
Modeling IDL file code
Create the other IDL profile items as necessary to model the IDL file code you want to generate.
Support for the BaseIDL Profile
The IDL Profile includes Stereotypes to support the BaseIDL Profile, as defined and described in the OMG UML Profile for CORBA and CORBA Components Specification Version 1.0. To open the UML Profile for CORBA and CORBA Components Specification and find out more about the BaseIDL Profile Stereotypes, click the following link: http://www.omg.org/spec/CCCMP/1.0/PDF/
The BaseIDL Profile Stereotypes reside in the IDL Profile::BaseIDL package.