F – DUO Configurator {appendix}

Overview

If running MYOB Exo 2018.1 or above MYOB stores connection info in sub-hives {registry} for each connection [and per workstation}. Furthermore, this information is stored in plain text except for the SQL Server password. Third party applications such as DUO can read this information and automatically create a connection list, but for each connection the SQL server password must be provided once and the system prompts for this.

If running DUO with Exo versions prior to 2018.1 you must create and configure the DUO4Exo.xml configuration file.

Tech Note: DUO accesses the database using software components in the Zeos library. This library is entirely contained within the DUO application at compile time. Zeos is released as open source at http://sourceforge.net/projects/zeoslib/. Under the licensing terms for Zeos we are obliged to acknowledge its use somewhere in our documentation.

Using Registry based settings (default)

MYOB Exo applications maintain connection info in registry, Usually in sub-hives of hive HKEY_CURRENT_USER\Software\Exonet6\ConnectionInfo. Each connection has its own sub-hive containing various settings

Appendix F - Installation – Connection Settings in Registry

On each workstation when first logging on to this connection, DUO will prompt for the SQL password. This is because it cannot decipher the encrypted password in setting PASSWORD above.

Appendix F - Installation – Request for SQL Server Password

This password will be stored in the same registry sub-hive as setting DUO PASSWORD.

Both PASSWORD and DUO PASSWORD are encrypted using both a Salt and a Pepper, which is one reason DUO cannot decrypt PASSWORD and requires its own entry.

By default, both Exo and DUO try various SQL Clients until it finds one that works. DUO uses the following in descending preferential order:

·         Microsoft SQL OleDB [MSOLEDBSQL]

·         Microsoft SQL Native Client [SQLNCLI11]

·         Microsoft DB-Library API [ntwdblib] (no longer supported by Microsoft)

·         Free TDS [dblib]

 

There are some optional (manually configured) registry settings available but most installations will not require these.

Registry Setting Name

Description {Essentials}

DUO_PROTOCOL

Force protocol to OleDB, MSSQL, FreeTDS, or SQLdb

DUO_PROVIDER

Force provider to MSOLEDBSQL.1 or SQLNCLI11.1, 

DUO_DRIVER

Name of driver DLL (if not OleDB)

DUO_DRIVERPATH

The location of the SQL driver DLL(s)

DUO_PROFILERPATH

If set, points at the folder location of SQL Profiler.exe

 

Using the DUO4Exo.xml via the Configurator

Database connection information and other initialisation information is stored in an file DUO4Exo.xml. Dyameta provides a copy of this file with name DUO4ExoBack.xml. The absence of  DUO4Exo.xml in the DUO4Exo.exe folder signals that registry settings should be used.

If you need to use the XML configuration method then copy DUO4ExoBack.xml to DUO4Exo.xml. This will be detected and an additional option becomes available from the login screen to access the configurator editor. Sselect Configuration ... in the Connect To ComboBox of the login screen. 

No username or password is required for this. The Login button changes to Setup

 

 

Appendix F - Installation - Accessing Configurator

The Configurator maintains entries in the DUO.xml file and therefore can be accesses without logging in to an explicit Exo database. 

It also encompasses the database connection editor functions.

Appendix F - Installation - Configurator

DUO

 The root of the tree contains site info such as version and path names. These used prior to logging on to an individual database. After logon, some of these settings will be updated from the settings in the database e.g. HelpURL

 Some of these entries can optionally be overridden at a computer level e.g. DriverPath.

Connections

Defines connections to databases and forms a list of databases available at the DUO login screen.

Hosts

Defines host SQL Server instances.  Used when defining connections.  This stores SQL server location and authentication information.

Connection types

Connection types (ConTypes) specify the MSSQL database connection protocol (method). These are settings are already provided by DUO and do not need editing.

The database driver DLL for at least one of these methods must be installed on your system.

Computers

Entries in the Computers section are optional overrides and usually your configuration will not include any.

In some cases, such as network security and/or topology, on some computers it may be necessary to look for files in a folder different from that specified in the root node of the DUO configuration. The following settings may be overridden per computer:

·         DriverPath          The location of the SQL driver DLL(s)

·         ExoPath               The location of your MYOB Exo programs e.g. Exonet.exe

·         HelpURL               The location of help files

Modules

These are the modules that are supported by DUO. These are settings are already provided by DUO and do not need editing.

Roles

On installation there are two roles defined being Default and Limited. You can create more if you wish.

Modules

Roles define what subset of Modules will be active for a session when the user logs in (see Roles combo-box on Login screen).  Because DUO has all functionality within a single executable the separation of modules is not done by choice of program. In MYOB Exo we see both single and hybrid of roles:

·         Executing JobCost.exe only provides JobCost functions, consumes only a Job Cost seat licence, and does not consume an MYOB Exo Core seat licence.

·         Normally, executing Exonet.exe only consumes a Core seat licence, however if the user has any CRM menu items on their Core menu then both a Core and a CRM seat licence is consumed.  This is a hybrid Role.

The following scenarios will not activate a Module for a user even if it is listed in the Role definition:

·         The database does not have a licence for the Module.

·         The user’s (logged on Staff) security profile setting DUO <ModuleName> Module Access Level is set to Prevent Access.

·         Note that the Default Security Profile  has the Access level of all modules set to Full Access except than the Designer Module which defaults to Read Only.

The Default Role contains all available Modules as does the Default Security Profile therefore unless other permutations are used, every logon will consume a licence seat count of all modules licensed to the database.


 

DUO for EXO     DUO for EXO     © Dyameta Technology Ltd                     Previous Topic           Next Topic           Home