Overview¶

Users need to login to the MIKE Workbench in order to work with the Workbench functionality and data. The login form appears when the MIKE Workbench opens.

Note: If this is your first time using the MIKE Workbench and you have not set up any users you can log in as the default administrative user. The user name is admin and the password is dssadmin.

Login parameters consist of the following:

Server connection which is an alias for various database parameters. To define server connections, click the “Setup…” button; see Manage server connections.
User name and password.
The name of the workspace within the server connection.

Select “Always use the same user name and password” to have the user name and password field pre-filled when starting the Workbench up. This is convenient if you always use the same user name and password.

Select “Always login with the above settings” to perform an automatic login with the entered parameters. This is convenient if you always log in to the same workspace with the same user name and password.

Connection Parameters¶

Manage server connections¶

Click the “Setup…” button on the Login form to open the Connection Manager.

The Connection Manager displays the existing connections and has the following possibilities.

The “Add…” button for adding a new connection.
The “Edit...” button for editing the selected connection.
The “Delete” button for deleting the selected connection.

Add or edit a server connection¶

Click the “Add…” or “Edit…” button on the Connection Manager to open the connection Setup menu.

The following parameters must be specified:

A server connection name. This name is used in Connection combo-box on the Login form.
The type of database.
The name of the server.
The port used for communication between the server and the Workbench. The default is 5432 for PostgreSQL, and 1521 for Oracle.
The name of the database.

If the Database Type is SQLite, Server and Port are automatically filled and cannot be changed. Additionally, the database field can be filled by browsing for the database file.

Workspace data exchange¶

Users can exchange data between workspaces through two standard Workbench tools – Data Export Tool and Data Import Tool. The two tools are available through the Tools Explorer

The data exchange concept is based on users exporting data entities from a source workspace to the file system and then importing them in a target workspace.

Note: Data exchange will during import restore the data entities in the same group folders as they had in the source workspace. This implies that data exchange can override data within the target workspace.

Export Data¶

Select the Export Data Tool (1) and click the Run button (2) in the tool’s propert control.
This will make the Export data to disk view available** Specify a folder (3) where the exported data entities can be stored.
Then drag and drop (4) the entities that shall be exported from the respective managers to the view.

Note: the entities are being exported as they are being dragged and dropped to the view

Import Data¶

Select the Import Data Tool (1) and click the Run button (2) in the tool’s propert control.
This will make the Import data fromdisk view available.
Select the folder (3) that contains the exported data.
The exported data entities will then be listed in the view.
Click the Start button (4) and the import of entities will start.

Workbench User Interface¶

The MIKE Workbench has an IDE-style user interface (UI) where all windows reside under a single parent window, referred to as the Shell.

The Shell contains dockable and collapsible child windows, tabbed windows and splitters for resizing of child windows.

There are four types of windows available: Explorers, Toolbox, Data views, and a Property control. The Toolbox and Property control are Shell controls that are always available, whereas the available Explorers and Data views depend on the system configuration of the Workbench.

The default windows docking configuration is displayed below, but the use may change this.

The MIKE Workbench is based on a plug-in architecture where content and functionality is added to the shell by loading one or more so-called Managers. Each manager may add one or more Explorer and/or Data views to the shell. Moreover, each manager may also supply a number of tools to the toolbox.

Explorers¶

Description

Illustration

Explorers are supplied the Managers that has been loaded into the system.

Each manager may add any number of explorers to the Shell, but typically a manager will add one or two Explorers.

Explorers are often used to retrieve all or a subset of the data entities owned by the manager from the database.

The exact functionality will vary from manager to manager, and there are no rules defining what an Explorer should do.

By default the explorers are docked in the left-hand side of the shell. If more than one explorer has been loaded, they will by default be grouped in a tab control.

The user may change this configuration by dragging and dropping either the individual tabs, or the entire tab control.

Data Views¶

In the default configuration, data views are located in the center of the application. Several data views may be opened and docked in many different configurations

The data view can be rearranged by drag dragging the data view tabs to the location indicators that appears when dragging, as illustrated below.

In the example above, the data views have been arranged in three so-called tab groups. The data view tab context menu has 4 entries:

Close – Will close the data view.
Prominent – This will maximize the tab, and hide all other data view tab groups.
Rebalance – This will bring back all other data view tab groups.
Move to next tab group – Moves the tab to the next tab group.

Property Control¶

When a user interface entity or tool is selected, the corresponding properties are displayed in the Property control. The properties can be edited, and changes will be applied instantaneously with no explicit save operation required.

Toolbox¶

Tools are components for analysing and processing selected data entities (such as time series or map layers). Tools are presented in a context sensitive manner in the Tools Explorer, e.g., time series relevant tools are made available only when time series are selected in the Time series explore and GIS tools are only presented when map layers are selected in GIS Explorer.

Editing tool settings¶

When a tool has been selected in the Tools explorer, the tool settings will appear in the Property control. The settings of the tool can be edited the same was as the properties of any other entity, and changes will be applied instantaneously with no explicit save operation required.

Saving tool settings¶

Description	Illustration
After configuring a tool, the settings can be saved for later use. This is done by clicking on the Save button in the property control.
After saving, the saved tool settings will be represented as a new node under the tool node Notice that the saved tool represents the settings, not the input items, and hence a saved tool can be executed on any supported input items. To run a saved tool, simply select it in the toolbox.

Running a tool¶

After configuring a tool it can be executed by clicking the “Run” button in the Property control toolstrip.

When clicking the button, a list of available output tools will be listed. Each output tool represents one possible way to visualise or save the result of the tool execution.

Select the appropriate output tool to execute the tool.

Tool sequences¶

Pending

Tool output configurations¶

Tool Output configurations are additional output when running tools.

Tool Name
The name of the tool that the output configuration should be available for
Configuration Name
The name of the tool output configuration
Presentation Tool
Select the presentation tool to use for displaying the result