Administration Features and Functions > Configuring User Features
  
Configuring User Features
The following sections describe user configuration features.
Monitoring User Sessions
Use Session Master Maintenance (36.4.22) to view information about users who are currently logged in to the system through the QAD .NET UI. This information displays in the form of session records, each identified by a unique session ID that is generated by the system. (You can identify your current session ID by selecting Help|View Configuration and viewing the Session ID.) A session record is automatically created when a user successfully logs in to the system from the QAD .NET UI and is deleted when the user logs out.
Only some of the settings displayed on this screen apply to the QAD .NET UI sessions. You can ignore the following: Active Web, Number of Records, Security Profile, Active Telnet, Menu Substitution, and Context ID. The session context detail displays information about the current workspace (domain). One user session can be associated with multiple contexts if programs have been activated in more than one workspace. You can also monitor the status of sessions for maintenance programs, reports, and inquiries using Connection Manager.
Active Directory Authentication
The QAD .NET UI supports Microsoft’s Active Directory authentication. With Active Directory support, user passwords can be centrally managed.
To enable Active Directory authentication:
1 Define users so that the user IDs match the Windows user IDs. Assign temporary QAD passwords to new user IDs.
2 Locate the client-session.xml file on the home server. (By default, the file is located in the TomcatInstallDir/webapps/qadhome/configurations/default directory.)
3 In the client-session.xml file, set <QAD.Authentication.ActiveDirectory.Enabled> to true.
When a user first logs in to the QAD .NET UI, the system prompts the user to enter the temporary QAD password that was assigned to the user ID. Entering the temporary password then completes the Active Directory setup. The next time that the user logs in to the QAD .NET UI, the user must use their Windows user ID and password.
Note: In releases prior to QAD .NET UI 2.9.5 (2012 EE), when setting up Active Directory, you had to enable the Enforce OS User ID option in Security Control (mgurpmmt.p). Additionally, the passwords for user IDs had to be sent to blank. Starting with QAD .NET UI 2.9.5, these steps are no longer necessary.
Configuring Default Client Folder Name
By default, the QAD .NET UI client download is installed in a folder named C:\Program Files\QAD\QAD Enterprise Applications Version, where Version is the version of the product. Typically, this is the appropriate folder to use for client installations. If you prefer, however, you can change Version to a different value by modifying the options.js file on the Home Server in the TomcatInstallDir/webapps/qadhome/client directory. For example, for QAD Enterprise Applications 2011- Enterprise Edition, options.js includes:
var Vers=" 2011 EE"
With this setting, the QAD .NET UI client will be installed to C:\Program Files\QAD\QAD Enterprise Applications 2011 EE by default. However, if you change options.js to:
var Vers=" 2011 Special"
The QAD .NET UI client will be installed to C:\Program Files\QAD\QAD Enterprise Applications 2011 Special by default.
Shortcut Options
You can add startup options to the QAD .NET UI shortcut on your desktop:
1 Right-click the shortcut icon for the QAD .NET UI on your desktop.
2 Select the Shortcut tab in the Properties dialog.
3 You can now add options to the command in the Target field. By default, Target will have:
 
"C:\Program Files\QAD\QAD Enterprise Applications 2011 EE\QAD.Applications.exe"
 
4 You can add options, such as specifying the default user ID as “abc”:
 
"C:\Program Files\QAD\QAD Enterprise Applications 2011 EE\QAD.Applications.exe"
-user:abc
 
The following options are available:
 
Option
Description
-user
Specifies the user ID, as entered on the Login window’s User field.
-password
Specifies the password for the user, as entered on the Login window’s Password field. Use with caution.
-config-name
Specifies the environment configuration name, as entered on the Login window’s Log on to field.
-workspace
Specifies the name of the workspace you want to be in after you log in.
-guideme
Specifies whether Guide Me is enabled (-guideme.enabled:true or -guideme.enabled:false).
-log-level
Specifies the logging level or turns it off (-log-level:off).
-log-file
Specifies the location of the log file if you do not want to use the default location, which is %APPDATA%/QAD/shell.
-enable
Specifies a plugin to enable ( -enable:qad.plugin.example).
-param.url:file
Specifies the location of a local file that contains the options.
-param.url:http
Specifies the URL of a file that contains the options.
You can put these options in a file on your machine and reference them from the Target setting. Here is an example where the settings are in a file C:/params.pf:
"C:\Program Files\QAD\QAD Enterprise Applications 2011 EE\QAD.Applications.exe" -param.url:file:///c:/params.pf
The params.pf file is a simple text file that contains:
-config-name:test
-user:mfg
-password:(blank)
Instead of locating the file on a local drive, you can locate it on the network, accessible from a URL. For example:
"C:\Program Files\QAD\QAD Enterprise Applications 2011 EE\QAD.Applications.exe" -param.url:http://hostname/.../params.pf
E-mail Action Options
The Action/Email feature in programs running in Desktop mode allows you to create an e-mail with a QAD Shell URI (qadsh://) to a Desktop program. Prior to QAD .NET UI 2.9.5, there was an inconsistency in this feature because different e-mail clients handle the QAD Shell URI differently, some recognizing it and allowing the e-mail recipient to launch the link and some not recognizing it and instead requiring the recipient to copy the link and paste it into a web browser.
Starting with QAD .NET UI 2.9.5, options are available to:
Allow an administrator to set (using client-session.xml) whether they want the QAD Shell URI to be used directly (which is and has been the default) or if they want to wrap this QAD Shell URI in an HTTP URI (http://), which is more widely recognized by e-mail clients.
Provide an option to turn on or off the inclusion of the full URI in the email. (By default two links are put in the email; the first is the program label that links to the URI and the second is the full URI. This option controls the second link.)
Provide an option to create the link as text instead of HTML (for e-mail clients or settings that are text based).
These options are controlled by the following settings, which can be added to client-session.xml:
<EmailAction.UseHTTP>true</EmailAction.UseHTTP>
When set to true, the HTTP URI is used in the e-mail. When false, the direct QAD Shell URI is used.
<EmailAction.IncludeURI>true</EmailAction.IncludeURI>
When set to true, the full URI is added as a link in the e-mail. When set to false, it is not included.
<EmailAction.UseText>true</EmailAction.UseText>
When set to true, the link will be text. When set to false, the link will be HTML.