Displaying items by tag: vbscript
Use C#, Java, for your VB Scripting
Use C#, Java from your EA Context Menu:
This works for all EA Versions, even without Administration rights to install an Add-In or so.
EA Version 13 supports an IDE to develope in C# and Java with full EA API support and debugging. They name it Hybrid Scripting. You may use the EA 13 Hybrid Script environment or other IDEs. Going the first steps is easier with EA 13.
This article shows you with a little example how to use C# for your Scripting. After you have understood C#, it should be easy to use Java in a similar way. The main idea is to use a small wrapper you call within your VB Script. Of course, after you have understood it's also easy to write this little wrapper for JavaScipt/JScript.
SPARX delivers two DLLs to use the EA API efficiently. With these DLLs, you can use the EA Hybrid development environment as well as any other IDE you like most. In other words: You can use the power of state of the art languages to perform your scripting. Integrating Scripting in EA is as easy as you know it from the well-known Scripting Languages VB Script, JavaScript, JScript. This without installing anything or needing Admin rights.
Just insert the line:
- 'RunCommand("myLogic.exe, "", " ")'
in your VB Script and you are done with VBScript to call your C#. Java would be similar.
Let's make a quick example with EA Version 13 and C#:
Make an EA C# ConsoleApplication
- Create a new EA Project
- Create a Package ('Select and Apply Model Pattern')
- C#, RepositoryInterface 4.0
- c:\temp\hybrid
- Build the Application
- Have a look in the generated Application
- c:\temp\hybrid\RepositoryInterface 4.0\
Import VBScript wrapper to call C#
- Configure, Transfer, Import Reference Data
- Make EA Scripting visible
- Code, Scripting (you may have to refresh Scripts)
- You see the new VB Scripts inside the ScriptGroup HybridScripting:
- RunCommand
- RunCommandTest
Run C# ConsoleApplication.exe
- Adapt VBScript RunCommandTest
- Adapt path to 'ConsoleApplication.exe'
- See
- Line:28/29 Needed references
- Line:35 Path to *.exe which executes your logic
- Line:36 The call of the wrapper, result contains the StandardOutput of the Script
- Run VBScript RunCommandTest
- Right Click on RunCommandTest
- Run Script
How do you use it
There are two approaches: Generates you VB Script by inserting the the wrapper Call in the EA templates at the appropriate location. The other way is to remove the template and just call the wrapper like
'result = RunCommand("myLogic.exe, "", " ")'
instead of the using the template scuffold.
Under the hood
EA delivers the two dlls:
- Interop.EA.dll
- SparxSystems.Repository.dll
They expect the Process ID, first parameter, to know which EA Instance the *.exe wants to use. So, RunCommands makes:
- Estiminate the own Process ID
- Call 'RunCommand...'
- Reads the Standard output from your *.exe
- Returns to Standard output to the caller
Inside the *.exe you have full access to the EA API.
JavaScript, JScript, Java?
With this example it's easy to migrate 'RunCommand' to JavaScript or JScript. Remember, you can use every Language supported by EA and every IDE you like most.
References
- SPARX Webinar Hybrid Scripting
- SPARX Tutorial Hybrid Scripting
- hoTools Hybrid Scripting
- RunCommand.vbs (The wrapper to call your C#, Java,..)
- https://github.com/Helmut-Ortmann/EnterpriseArchitect_hoTools/blob/master/HybridScripting/vb/RunCommand.vbs
- RunCommandTest.vbs (An Example with EA example C# Hybrid Script ConsoleApplication.exe, see Tutorial )
- https://github.com/Helmut-Ortmann/EnterpriseArchitect_hoTools/blob/master/HybridScripting/vb/RunCommandTest.vbs
The challenge with Script Debugging, Microsoft Process Debug Engine within Enterprise Architect.
"VBScript and JScript require the Microsoft Process Debug Manager (PDM.dll) to be installed on the local machine; this is available through various Microsoft products including the free 'Microsoft Script Debugger'"
(refer to: http://sparxsystems.com/enterprise_architect_user_guide/13.0/automation/debug_scripts.html)
The issue is: Microsoft Script Debugger as is - is depricated and here is the list (not complete for sure), where PDM is part of:
* Office 2000-2007
* Visual Studio
* Visual Studio Remote Tools (PDM stays installed even after uninstall of the Remote Tools)
Depending on the used operating system of Microsoft you will find Process Debug Manager (PDM.DLL) in the following folders:
Windows Vista, Windows 7, Windows 8, Windows 8.1 (64bit)
C:\Program Files (x86)\Internet Explorer\pdm.dll
Windows Vista, Windows 7, Windows 8, Windows 8.1 (32bit)
C:\Program Files\Internet Explorer\pdm.dll
Windows 10 _before_ v1607
Windows 10 (64bit)
C:\Windows\SysWow64\F12\pdm.dll
Windows 10 (32bit)
C:\Windows\System32\F12\pdm.dll
This file (pdm.dll) must be registerd manually using regsvr32.
Windows 10 v1607:
in this version manual installation of pdm.dll is not possible anymore. So you have to install a Microsoft Product that contains PDM.dll.
I recommend using the "Remote Tools for Visual Studio 2015 Update 3"
32bit: https://go.microsoft.com/fwlink/?LinkId=615469&clcid=0x407
64bit: https://go.microsoft.com/fwlink/?LinkId=615470&clcid=0x407
After installation you can uninstall them - because PDM.DLL resists and can be used by Enterprise Architect.
How to use the Enterprise Architect VBScript Library
The Enterprise Architect VBScript Library is an open source library of VBScripts written to be used in Enterprise Architect.
This article explains how to download, import and use the library in Enterprise Architect.
Initial Import
The Enterprise Architect VBScript Library contains some scripts to load and save scripts from/to your file system, but before we can use those we have to import an initial set of scripts to get started.
After downloading the file select menu option Project|Data Management|Import Reference Data and choose the downloaded file. Make sure to select Automation scriptsand click Import.
This will import the minimum set of scripts required to load other scripts from the file system
Download library from GitHub
From the Enterprise Architect VBScript Library project page on GitHub you can either choose to download the library as a zip file, or download the repository in GitHub desktop.
Load library into Enterprise Architect
One of the scripts in the initial set is the scriptLoadScripts in the group Script Management. If you execute this script you can choose the library folder from the library downloaded from GitHub.
The script will then scan the entire folder tree and it will load any .vbs file it can find.
For starters it might be interesting to only load the Frameworks scripts as they have the most chance of being useful to anyone.
If the LoadScripts script finds a script that already exists in Enterprise Architect it will ask to overwrite the existing scripts.
In order to know in which group the script belongs it will look for a the group indicator in the script.
1
|
'[group=Script Management] |
This will tell the script that this script should go in the group Script Management. If the script indicator is absent it will assume the group name is the name of the folder where it was found.
After loading the scripts into EA make sure to press the refresh button to make the scripts appear in the GUI.
Saving all your scripts
In the script management group there also a script to save all your scripts to the file system.
In order to control where the script should go you can add the path indicator to the script like this
1
|
'[path=\Framework\Tools\Script Management] |
The path indicator will control where to place the script relative to the chosen folder.
If the path indicator is absent the name of the script group will be used as name of the folder.
Being able to save and load the scripts from/to the file system now allows us to use version control on these scripts.
The library structure
The library is structured in two main parts.
- Projects
Contains an assortment of various scripts written for various projects. - Framework
Contains the framework scripts that are meant to be used by other scripts
- Utils
Contains helper scripts and classes such as TextFile, SQL, XML etc.. - Wrappers
Contains the wrapper classes for EA elements such as TaggedValue, Script, ScriptGroup
- Utils
The scripts in the projects folder can be used for inspiration, but it is mainly the scripts in the Framework part that are useful when writing scripts.
Using the library
The first thing you need to do when you want to use any of the framework classes is to include the framework in your script
1
|
!INC Wrappers.Include |
This will include the “Include” script that takes care of including all the other scripts of the framework, including those of the Utils folder.
Then you can use the classes defined in the library. For eaxample, if you want to have the user select a directory you can use following code
1
2
3
4
|
'get the folder from the user dim folder set folder = new FileSystemFolder set folder = folder.getUserSelectedFolder( "" ) |
The classes in the library contain both properties as operations. You can use the properties as you would expect from “real” classes.
1
2
3
4
5
|
'show messagebox with the name of each subfolder dim subfolders, subfolder for each subfolder in folder.SubFolders msgbox "subfolder name: " & subfolder.Name next |
Contributing
Have you written any VBScripts for Enterprise Architect you would like to share? If you would like to contribute to the Enterprise Architect VBScript library you can email me at This email address is being protected from spambots. You need JavaScript enabled to view it.
Automatically trace elements to domain model in Enterprise Architect
This script will search the text in the comments, scenario’s and linked document of the selected elements for terms in the domain model. If it finds a match it will create a trace from your selected element to the element in the domain model.
The idea is that when we write descriptions and scenario’s we often use terms already defined in the domain model, so it would be good if we had a real trace from the element in the domain model and the element using it in its description.
But it is hard to keep the descriptions and scenario’s in sync with the traces to the domain model. This script does the hard part for us and keeps those traces in sync. All you need to do is type your description and run the script. The script will find the referenced elements in the domain model and create a trace link to it. It will also remove any automatic traces that are not valid anymore.
Next to the Name, Notes, and the Linked Document, this script will also search the scenarios, both theScenario Description, as the structured Scenario Steps. In case of a Scenario Step the script will insert to the name of the domain model element in the Uses column.
Note that the script is case sensitive. That is the reason why RoomType does not appear in the uses column. Enterprise Architect itself isn’t that picky, and it underlines Roomtype anyway because it finds a relationship to RoomType.
In order to execute the script you have to select either one or more elements in the project browser, or select a package in the project browser.
Then select Script|Link To Domain Model
Free download
The script
In the first part we ask the user to select the domain model package.
If you want to use this script on a particular model you may want to replace that by a hard coding the Domain models GUID into the script.
Since this script may run for a while on a large model, we also create an output tab so we can inform the user of our progress.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
sub main 'let the user select the domain model package dim response response = Msgbox ( "Please select the domain model package" , vbOKCancel+vbQuestion, "Selecte domain model" ) if response = vbOK then dim domainModelPackage as EA.Package set domainModelPackage = selectPackage() if not domainModelPackage is nothing then Repository.CreateOutputTab "Link to Domain Model" Repository.ClearOutput "Link to Domain Model" Repository.EnsureOutputVisible "Link to Domain Model" 'link selected elements to the domain model elements linkSelectionToDomainModel(domainModelPackage) 'tell the user we are done Repository.WriteOutput "Link to Domain Model" , "Finished!" , 0 end if end if end sub |
Next we create a dictionary of all classes in domain model package and all of the sub-packages recursively.
1
2
3
4
5
6
7
8
|
'first get the pattern from all the classes in the domain model dim dictionary Set dictionary = CreateObject( "Scripting.Dictionary" ) 'create domain model dictionary 'tell the user what we are doing Repository.WriteOutput "Link to Domain Model" , "Creating domain model dictionary" , 0 addToClassDictionary domainModelPackage.PackageGUID, dictionary |
Based on this dictionary we can create one large Regular Expression that will tell us which of the terms in the dictionary are used in a certain text.
1
2
3
4
5
6
7
8
9
|
' and prepare the regex object dim pattern 'create the pattern based on the names in the dictionary pattern = createRegexPattern(dictionary) Dim regExp Set regExp = CreateObject( "VBScript.RegExp" ) regExp.Global = True regExp.IgnoreCase = False regExp.Pattern = pattern |
Then we check what is selected in the project browser. If the user has selected one or more elements we start process those elements. If a package is selected then we process the elements in the selected package.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
' Get the type of element selected in the Project Browser dim treeSelectedType treeSelectedType = Repository.GetTreeSelectedItemType() ' Either process the selected Element, or process all elements in the selected package select case treeSelectedType case otElement ' Code for when an element is selected dim selectedElements as EA.Collection set selectedElements = Repository.GetTreeSelectedElements() 'link the selected elements with the linkDomainClassesWithElements dictionary,regExp,selectedElements case otPackage ' Code for when a package is selected dim selectedPackage as EA.Package set selectedpackage = Repository.GetTreeSelectedObject() 'link use domain classes with the elements in the selected package linkDomainClassesWithElementsInPackage dictionary, regExp,selectedPackage case else ' Error message Session.Prompt "You have to select Elements or a Package" , promptOK end select |
Here’s the complete code for the script.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
|
option explicit !INC Local Scripts.EAConstants-VBScript ' ' Script Name: Link to Domain Model ' Author: Geert Bellekens ' Purpose: Link elements with classes in the domain model based on their name. ' Date: 15/11/2015 ' sub main 'let the user select the domain model package dim response response = Msgbox ( "Please select the domain model package" , vbOKCancel+vbQuestion, "Selecte domain model" ) if response = vbOK then dim domainModelPackage as EA.Package set domainModelPackage = selectPackage() if not domainModelPackage is nothing then Repository.CreateOutputTab "Link to Domain Model" Repository.ClearOutput "Link to Domain Model" Repository.EnsureOutputVisible "Link to Domain Model" 'link selected elements to the domain model elements linkSelectionToDomainModel(domainModelPackage) 'tell the user we are done Repository.WriteOutput "Link to Domain Model" , "Finished!" , 0 end if end if end sub 'this is the actual call to the main function main function linkSelectionToDomainModel(domainModelPackage) 'first get the pattern from all the classes in the domain model dim dictionary Set dictionary = CreateObject( "Scripting.Dictionary" ) 'create domain model dictionary 'tell the user what we are doing Repository.WriteOutput "Link to Domain Model" , "Creating domain model dictionary" , 0 addToClassDictionary domainModelPackage.PackageGUID, dictionary 'tell the user what we are doing Repository.WriteOutput "Link to Domain Model" , "Interpreting dictionary" , 0 ' and prepare the regex object dim pattern 'create the pattern based on the names in the dictionary pattern = createRegexPattern(dictionary) Dim regExp Set regExp = CreateObject( "VBScript.RegExp" ) regExp.Global = True regExp.IgnoreCase = False regExp.Pattern = pattern ' Get the type of element selected in the Project Browser dim treeSelectedType treeSelectedType = Repository.GetTreeSelectedItemType() ' Either process the selected Element, or process all elements in the selected package select case treeSelectedType case otElement ' Code for when an element is selected dim selectedElements as EA.Collection set selectedElements = Repository.GetTreeSelectedElements() 'link the selected elements with the linkDomainClassesWithElements dictionary,regExp,selectedElements case otPackage ' Code for when a package is selected dim selectedPackage as EA.Package set selectedpackage = Repository.GetTreeSelectedObject() 'link use domain classes with the elements in the selected package linkDomainClassesWithElementsInPackage dictionary, regExp,selectedPackage case else ' Error message Session.Prompt "You have to select Elements or a Package" , promptOK end select end function 'this function will get all elements in the given package and subpackages recursively and link them to the domain classes function linkDomainClassesWithElementsInPackage(dictionary,regExp,selectedPackage) dim packageList set packageList = getPackageTree(selectedPackage) dim packageIDString packageIDString = makePackageIDString(packageList) dim getElementsSQL getElementsSQL = "select o.Object_ID from t_object o where o.Package_ID in (" & packageIDString & ")" dim usecases set usecases = getElementsFromQuery(getElementsSQL) linkDomainClassesWithElements dictionary,regExp,usecases end function function linkDomainClassesWithElements(dictionary,regExp,elements) dim element as EA.Element 'loop de elements for each element in elements 'tell the user what we are doing Repository.WriteOutput "Link to Domain Model" , "Linking element: " & element.Name, 0 'first remove all automatic traces removeAllAutomaticTraces element 'match based on notes and linked document dim elementText 'get full text (name +notes + linked document + scenario names + scenario notes) elementText = element.Name elementText = elementText & vbNewLine & Repository.GetFormatFromField( "TXT" ,element.Notes) elementText = elementText & vbNewLine & getLinkedDocumentContent(element, "TXT" ) elementText = elementText & vbNewLine & getTextFromScenarios(element)
|