Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The Run Manager is accessed via a web browser interface regardless of whether it is installed as a local application or accessed on the cloud. It is optimised for use with Google Chrome.

Cloud Application

For authorised users, the Run Manager Cloud application can be accessed by visiting https://runmanager.ewater.org.au/ via your web browser.

To use the Run Manager Cloud, you must log in. This will occur automatically if you are logged in to eWater's Toolkit in your web browser. If not, you must log in manually using your Toolkit credentials (see Profile).

The Run Manager Cloud Application is currently configured to use Source version 4.7.0.8165 and makes two plugins available:

  • UrbanDeveloper
  • SubSource

Projects saved in a Source version later than 4.7.0.8165, or that require additional plugins, will not run.

Contents

Local Application

Installation

Local installation of eWater Run Manager requires the following additional software to be installed:

eWater Run Manager is distributed as a ZIP file that should be extracted to your local drive: eWaterRunManager_419.zip

Configuration

The eWater Run Manager application contains a number of sub-directories. Two of these, the Agent and Run Manager sub-directories, contain configuration files called appSettings.json. These files can be opened in a text editor and allow you to configure the Run Manager settings.
The default settings are already configured for local use, however the user will need to specify or review the eWater Source installation directory setting. This setting is the SourceDirectory setting in the Agent's appSettings.json configuration file. Generally, all other settings should be left at their default values. The Run Manager will need to be restarted for configuration changes to take effect.

When entering file paths, back slashes (\) must be escaped. i.e. use double back-slashes (\\).

Agent Settings file:

Agent appsettings.json
{
  "PollingPeriodMs": "10000",
  "SourceDirectory": "C:\\Source\\Source_4.5.0.7410\\"
}
  • PollingPeriodMs - How often agent will poll the server requesting for a job/task
  • SourceDirectory - The directory containing the version of Source to run 

eWater Run Manager settings file:

eWater Run Manager appsettings.json
{
  "BaseUrl": "http://localhost:5051",
  "LaunchBrowserOnStart":true,
  "AgentEndpoints": ["Local"]
}
  • BaseUrl - The browseable URL for the local version of Source Cloud
  • LaunchBrowserOnStart- Whether to open the Run Manager web application in a browser when "Source.Web.exe" is run
  • AgentEndpoints - Local agents are used

Launch eWater Run Manager

Launch the eWater Run Manager application by Source.Web.exe, which is located in the /Run Manager directory. This will launch the local eWater Run Manager application in your default web browser.

Your web browser may cache old versions of the eWater Run Manager website and fail to update when you run a new version. To ensure that this does not happen, always do a 'hard refresh' on the eWater Run Manager webpage after installing a new version. In Firefox and Chrome, the default shortcut for a hard refresh is Ctrl-F5.

  • No labels