Prev | Next |
Analyzer Script Editor
The Analyzer Script Editor has a straightforward user interface, with a tree view of the scripts on the left enabling easy navigation of the script groups, and a content view on the right in which you define and configure the scripts.
Access
From the 'Execution Analyzer' window, either:
- Double-click on a script to edit it or
- Right-click on a script and select the 'Edit' option
Ribbon |
Develop > Preferences > Analyzer > Edit Analyzer Scripts Execute > Tools > Analyzer |
Keyboard Shortcuts |
|
Execution Analyzer Scripts
Task - Page |
Action |
See also |
---|---|---|
Build - Build |
Enter the script or command to build the application. This can be an Apache Ant or Visual Studio command, but can also be tailored depending on your development environment. Note: Remember to select a parser to get directly to the source code in the event of any errors. The parser field is on the same page and offers support for many languages. |
Build Scripts |
Build - Clean |
Enter the script or command to clean the previous build. This is the command line you would normally issue to build your system. This can be an Apache Ant or Visual Studio command depending on your development environment. |
Cleanup Script |
Test - Test |
Enter the script or command to test the application. This is typically where an nUnit or jUnit invocation might be configured, but it just as easily could be any procedure or program. |
Test Scripts |
Test - Testpoints |
Specify where the output from a Testpoint run is sent. |
Testpoints Output |
Debug - Platform |
Specify the debugging platform, the application to be debugged, and the mode of debugging (attach to process or run). |
Debugging |
Debug - Tracepoints |
Specify where the output from Tracepoints encountered during a debug session are sent. |
Tracepoint Output |
Debug - Workbench |
For .NET projects, the assembly to load. Not required for Java. |
Workbench Setup |
Debug - Runtime Host |
Allows Enterprise Architect to launch the program to be debugged using a command line. This is typically used for Mono or Java programs that use a socket transport for debugging. This command is executed prior to the Debugger being run. The Port number specified in this command should be the same value passed to the 'Port' option in the Debug page. When the Debugger starts, it will attempt to connect to the runtime on this Port. If successful, it then binds any breakpoints and resumes the program,which it assumes to be suspended. Java and Mono both have command line options on the debugging transport to initially suspend the process till the Debugger connects. |
|
Source Control - Merge |
This is the script that executes when the 'Merge' option is chosen from the context menu of an Analyzer Script. It provides a place to run a program or shell script to examine the differences between source files. |
|
Source Control - Changes |
This is the script that executes when the 'Changes' option is chosen from the context menu of an Analyzer Script. It provides a place to run a source control program such as 'svn' that might list current changes to a source control repository. |
|
Source Control - History |
This is the script that executes when the 'History' option is chosen from the context menu of an Analyzer Script. It provides a place to run a source control program such as 'svn' that might list a history of changes to a source control repository. |
|
Source Control - Commit |
This is the script that executes when the 'Commit' option is chosen from the context menu of an Analyzer Script. It provides a place to run a source control program such as 'svn' that might commit changes to a source control Working Copy. |
|
Source Control - Working Copy |
This is the script that executes when the 'Working Copy' option is chosen from the context menu of an Analyzer Script. It provides a place to run a source control program such as 'svn' to perform actions on the current working copy of a source repository. |
|
Source Control - Repository |
This is the script that executes when the 'Repository' option is chosen from the context menu of an Analyzer Script. It provides a place to run a source control program such as 'svn' to perform actions on a source repository. |
|
Code Miner - Service |
In this section you can choose how the Code Miner service operates. You can choose either a remote server or to use libraries locally. |
Code Miner Script |
Code Miner - Libraries |
This section provides a place for the management of Code Miner libraries. Here, you can create libraries based on a project codebase or repository. Code Miner libraries created here can be searched using mFQL queries. Queries composed in mFQL can be used to search one or more libraries in a single operation. |
Code Miner Script |
Private Options - Services |
This is where the IP address and Port of Enterprise Architect Satellite services for Linux and Windows are configured. These services provide enterprise-wide support for system management functions and remote debugging scenarios. |
|
Run JavaScript |
This is the script that executes when the 'Run JavaScript' option is chosen from the context menu of an Analyzer Script. |
|
Run |
Enter a command to run an application. |
Run Script |
Deploy |
Enter a script or command to deploy the project. Build your jar file. Deploy to your device, an emulator or Tomcat server. Publish a web site. Its up to you. |
Deploy Script |
Recording |
Does your Sequence diagram resemble the national grid? Reduce the clutter with filters. Filters define exclusion zones in your code base that can cut down dramatically on any 'noise' that is being recorded. Even accurate noise is not always helpful. |
Recording Scripts |
Simulation |
Complete the configuration for Simulation Control. |
Model Simulation |