ENTERPRISE

<< Click to Display Table of Contents >>

Navigation:  »No topics above this level«

ENTERPRISE

Overview

The objective behind waterRIDE™’s Enterprise setup is to simplify both the management and rollout of the software across an organisation, as well as make the usage of waterRIDE by general users simpler. This encompasses the provision of centralised management of settings, user access levels and centralised project lists that allow the user the general to user to just "click and load", without needing to locate the projects on the LAN/WAN.

If you are using hosted waterRIDE CLOUD, Enterprise will be be automatically available.

Using the Enterprise framework, the following centralised behaviour can be configured:

License Server pathing – centralised configuration making license server relocation/specification simpler

Centralised project lists (provides end users with a simple list of all available waterRIDE™ projects – eliminates the need for users to locate projects on the LAN/WAN)

Configuration of the home button and master projects

Centralised username-based cascading software access permissions:

-ENTERPRISE (configuration only)

-DATA Manager

-Manager

-Viewer

Single waterRIDE™ installation for all versions (including centralised LAN/virtual install if desired)

Configuration of pervasive default searchbox (including using layers not in current project)

Configuration of internet/locally based address server searching

Centralised Report Figure templates

Common Palette and Hazard folders

 

Enterprise and DATA Manager are implicitly linked. You cannot (and it does not make sense to) run DATA Manager without and Enterprise configuration.

The Enterprise setup can only operate in conjunction with a license server.

 

Enterprise Configuration Description

In v8, the local wR_FLOOD_*.ini file (residing in the program files folder on each machine) could be used to store common settings such as license server paths and searchbox details. The downside of this approach was that if any setting was changed, each client would need to have its INI file updated with the change.

waterRIDE 10 introduced support for Enterprise configuration through a centralised wR_FLOOD.ini file, residing somewhere on the network. The local INI file need only point to the enterprise folder and settings can be read from the global wR_FLOOD.ini file.

clip0656

In this way, changes can be made to the enterprise INI file and automatically "rolled out" to each client.