Run Editor¶
The Run Editor allows specifying what to load when starting MIKE OPERATIONS applications, by opening and editing the runtime.config file of the application.
The Run Editor is divided into a products panel on the left and a plugin panel on the right, showing plugins of the product.
Note
To decrease load times, use the Run Editor to disable managers and/or plugins if they are not used.
Ribbon¶
The ribbon contains buttons for managing the products and plugins.
open¶
Open a runtime.config file.
Save¶
Save changes to the config file.
Save as...¶
Save changes into another or new config file.
Edit¶
Edit a plugin.
Field | Description |
---|---|
Name | The name of the plugin. |
Type | The type of the plugin. |
Assembly | The assembly name (file name) containing the plugin. |
Add¶
Add plugins from a .deploy
file.
Disable¶
Disable a product or plugin in the runtime.config file.
Remove¶
Completely remove a product or plugin from the runtime.config.
Products¶
The products panel contains a list of all Producs (or managers) being loaded.
Plugins¶
A plugin is a component embedded into an assembly (dll). Each assembly can contain multiple components.
Plugin types¶
A plugin can be one of the following types.
Type | Description |
---|---|
DHI.Solutions.ScenarioManager.Interfaces.IAdapter | A model adapter avaiable in the scenario manager. |
DHI.Solutions.Generic.IModule | A module (manager), e.g. Time Series, GIS, Spreadsheet. |
DHI.Solutions.Generic.IDTO | A data transfer object, for accessing with data of a specific type in the database. |
DHI.Solutions.Generic.UI.IExplorerControl | An explorer in the user interface. |
DHI.Solutions.Generic.UI.IDataViewControl | A data view in the user interface. |
DHI.Solutions.Generic.UI.IToolStrip | A tool strip in the user interface. |
DHI.Solutions.Generic.ITool | A tool available in the tools explorer or from the list of tools. |
DHI.Solutions.Generic.UI.IPropertiesControl | A properties control. |
DHI.Solutions.Generic.UI.IMenu | A menu in the user interface. |
DHI.Solutions.Generic.ILoginProvider | For login to the application |
DHI.Solutions.DocumentManager.Interfaces.IDocumentDataProvider | Varius types of data providers are available for getting data from external data sources. Here a provider for getting documents. |
DHI.Solutions.GISManager.Interfaces.IGISProcessor | Various data processors are available. Here a processor for prosessing GIS data. |
DHI.Solutions.JobManager.Interfaces.IJobServiceProvider | Various service providers are available for connection to external services. |
Runtime.config files¶
The table below shows the runtime.config file used by the applications released with the MIKE OPERATIONS product suite.
Application | Runtime.config |
---|---|
MIKE Workbench | Runtime.config |
MIKE OPERATIONS Desktop | OperatorUI.Runtime.config |
Database Manager Utility | DHI.Solutions.Shell.exe |
Run Editor | DHI.Solutions.RunEditor.Runtime.config |
The runtime.config also shows the startup parameter used for running the applications.
E.g. running MIKE OPERATIONS Desktop should be executed using the following command DHI.Solutions.Shell.exe --app OperatorUI
.
The --app argument specifies what runtime.config to use.
Deploy files¶
A deploy file is a XML file containing information about files and plugins to include in the runtime.config file.
<?xml version="1.0" encoding="utf-8"?>
<files>
<file
Name="DHI.Solutions.TimeseriesManager.Tools.ImportTools.dll"
SourceDir="Tools\DHI.Solutions.TimeseriesManager.Tools.ImportTools\bin\$(Mode)"
TargetDir="Bin"
Distribute="No"
Action="">
<plugins>
<plugin
Name="DHI.Solutions.TimeseriesManager.Tools.ImportTools.ImportFromUSGSTool"
Type="DHI.Solutions.Generic.ITool"
Enabled="Yes" />
</plugins>
</file>
</files>
The deploy file above will load the ImportFromUSGSTool from the file DHI.Solutions.TimeseriesManager.Tools.ImportTools.dll
.