Overview of the Modeler automation interface (automation interface)
An automation interface is a mechanism for sharing information between applications or to control another application.
The Modeler Automation Interface is a comprehensive API that allows you to perform the following operations:
• Read Model item structures, properties and links.
• Write to Model properties.
• Create Model items and links.
You may want to make use of the Automation Interface for the following reasons:
• To define how Publisher extracts items and diagrams from a Model.
• To customize the SDL script used in TDK models.
• To extract information from a Model for inclusion in documents and spreadsheets.
• To create new tab and command buttons, and change on drop and double-click behavior through Stereotypes and Scripts.
• To create applications or utilities that interact with a Model.
 |
If you want a Visual Basic or C# application to work with Modeler on a 64-bit Windows operating system, you must build the application to run as a 32-bit application. To do this, set the Target CPU up as X86 on the Advanced Compilation dialog.
If you want to work with data from a Model, you must have an understanding of the Modeler Meta Model. The Meta Model defines the item types (such as Classes, Attributes and Operations) that exist in the Model, their properties, and how they relate to each other.
|
Notes
• To use the Automation interface you must have a Modeler license and an API Access license.
• The Automation Interface is single-threaded.
• You can run Visual Basic files through the Modeler Tools tab. For more information, see
Running Visual Basic scripts from the Modeler tools menu.
• If you want to use a command line to run VBS script files that work with Modeler on a Windows 64-bit operating system, you must not use the 64-bit version of the VBS interpreter (wscript.exe) to run those script files. To run VBS script files using the 32-bit version of the VBS interpreter (wscript.exe), create and run a batch file that contains the following line:
C:\Windows\SysWOW64\wscript.exe <name of script file>
For example:
C:\Windows\SysWOW64\wscript.exe MyScriptFile.VBS