Java - Helmut-Ortmann/EnterpriseArchitect_ScriptDotNet GitHub Wiki
Java
If you know how to develop and run Java, it's simple. Add one line in the EA VB Script to call your Java Class:
' Call your Java Class
' - **%EA_SCRIPT_HOME%** is your Java Script folder with all *.dll, *.jar, *.class
' - **"SparxSystems.RepositoryInterface"** is the Java Class to call
' - you may use 4 parameters for different things to do
result = RunCommandJava("%EA_SCRIPT_HOME%", "SparxSystems.RepositoryInterface", " ", " "," ", " ")
Prerequisites
- Java SDK 32 bit installed
- %JDK32_HOME% is the path to 32 bit SDK
Installation
- Clone 'EnterpriseArchitect_ScriptDotNet'
- Adapt and run ScriptJava\SetEnvProductive.bat
- Environment Variables
- EA_SCRIPT_HOME Folder with all the *.dll, *.jar, *.class
- JDK32_HOME Folder with the Java SDK 32 bit
- Restart EA to ensure the changed Envirenment Variables are used
- Environment Variables
- Install in EA the VB Scripts (if you don't use the delivered EA model):
- RunCommandVb.vbs
- Java.vbs
EA Environment Hybridscripting
Try
- Open the delivered EA Repository 'ScriptDotNet.eap'
- Open Scripting Window, Spezialize, Scripting
- Run Script Jave
- Group: ScriptDotNetNormal
- Script: Jave
- EA outputs into the System Output Window
EA Script-Types
In the EA Script-Groups you create VB Scripts which later appear in Context Menues.
Group | Description | ContextMenu of |
---|---|---|
Browser | Works from Browser | Browser |
Diagram | Works from Diagram | Diagram |
ModelSearch | Result row in Search Window | Selected rows in Search Window |
ModelSearch | Result row in Search Window | no |
Search | Should be a Search, entry 'Script' in Category Search Window | no |
Import/Export EA Scripts
- Configure
- Transfer
- Export Referenced Data
- Import Referenced Data
- Transfer
Glossary
- VS Visual Studio 2017
References
- EA Script Group Properties
- EA Community, Use C#, VB, F#, Java for your VB Scripting
- Metrics
- Python
- SPARX Webinar Hybrid Scripting
- SPARX Tutorial Hybrid Scripting
- Where is the exe?
- Why LINQ beats SQL