Setup

The Setup tab holds a number of settings related to how the TARGIT Server should behave.

A number of miscellaneous setup options are available to configure the TARGIT environment according to the administrator’s preferences.

You now have these options to customize the look and behavior of the client:

Number format. The default setting is to use client-side number formatting.  The thousand separators and decimal separators will then be determined by the regional setting of the client computer. It is also possible to disable this feature and use the default language setting specified on the data warehouse. 

Data request cache. These are options for optimizing the client behavior. The following settings may be turned up or down for data request caching:

• Cache size limit (Mb): Makes it possible to set the maximum size for the disk space allowed for caching (in Mb, default 1024 Mb).
• Minimum free disk Space (Mb): Makes it possible to indicate the minimum size of free disk space required to enable the cache (in Mb, default 256 Mb).
• File count limit: Makes it possible to set the maximum number of files in the cache. (Default 1000 files).
• Idle file expiration (days): Makes it possible to indicate the number of days an idle cache file is kept before it is deleted (default 10 days).

Note that caching of data requests may be set to on or off on a database connection.

Currency Language. If you use the currency format when formatting numbers this is where you pick the currency language.

Splash screen. The Splash screen is the Introduction screen seen by end-users when they log on to a TARGIT client.

• Display: May be set to Disabled, Default or Custom. Information on how to use the Splash screen settings are displayed when hovering the i to the right of the field.
• URL: The URL for the custom website to display may be entered.
• Menu name: The name of the Menu item that reopens the splash screen may be entered.
• Enforce display in clients: End-users have an option to “Do not show me this again”. If the display of the splash screen should be enforced (override the end-user setting), a check-mark may be set.

Client update. The default setting is to let TARGIT Windows client update automatically. This will happen the next time an end-user logs on to TARGIT after the TARGIT server has been updated.

• Shortcut name in Windows Start. An option to supply custom name to the shortcut that will be created. If nothing is submitted here, the shortcut name will become TARGIT (servername).
• Shortcut icon in Windows Start. An option to supply custom icon to the shortcut that will be created. If nothing is submitted here, the icon will be the standard TARGIT icon.
• Redirect to server. In case you need to install the TARGIT server on a new physical server, you can add the new server name here. The effect is that end-users logging on with the old server name will automatically be redirected to the new server.

The Back-end tab gives you these options concerning back-end properties:

Log Analysis requests to system database. With this option you may log information such as “Who has been logged on to which analysis at what time of the day” etc. The logged information is then perfectly suitable as source data for a new TARGIT Requests cube. Before enabling this feature an auxiliary connection must also be made to a designated log database.

Online License Update. Enabling this option will make the server contact a central TARGIT licensing server to check for any updated license. E.g. if a customer license have been updated with an additional 50 users, the Online License Update will automatically detect and install the new license.

Criteria request cache.

• Cache size limit (Mb): Makes it possible to set the maximum size for the disk space allowed for caching (in Mb, default 1024 Mb).
• Minimum free disk Space (Mb): Makes it possible to indicate the minimum size of free disk space required to enable the cache (in Mb, default 256 Mb).
• File count limit: Makes it possible to set the maximum number of files in the cache. (Default 1000 files).
• Idle file expiration (days): Makes it possible to indicate the number of days an idle cache file is kept before it is deleted (default 10 days). Note that caching of criteria requests may be set to on or off on a database connection.
• Multiple logins. By default, only one user can log in to the TARGIT Management client at any time. By enabling multiple logins, you override this limitation. Be aware of the risk of multiple users trying to change the same setting at the same time – the last user to save settings may potentially overwrite settings already done by a different user.

If other user are already logged in to the TARGIT Management client on the same server, this is the warning you will see:

This tab gives you the following options:

You must provide the address, e.g. exchange.company.com, to an SMTP server capable of sending outgoing e-mails.

Depending on the Administrative Alerts settings you may then receive more or less critical error messages.

The SMTP Server setting is also required for certain automated tasks such as sending out e-mails from TARGIT Notifications and sending out e-mails with attached, scheduled TARGIT Reports.

Some mail servers require a fully qualified domain name to be entered in the From field. If this field is left blank the sender will appear as antserver@computername.

Options in the Performance tab:

Maximum number of active threads. This setting determines the number of concurrent threads the TARGIT server will use to serve the clients. Each connected client will use its own thread. An active thread is defined as a thread currently processing a request. If the number of actual requests is higher than the number of available threads, the requests are queued.

Performance can be increased by raising the number of concurrent threads, but at the cost of system resources (memory, CPU power, disk access, etc.). If this setting is 0 there is no upper limit to the number of concurrent active threads.

Maximum number of Sentinels threads. The value is used to avoid that all processing power is used on searching for Sentinels.

Network Load Balancing. These settings are relevant only for TARGIT solutions with a large number of concurrent users, and where the TARGIT Server has been found to be the bottleneck. To reduce bottlenecks multiple TARGIT Servers may be configured in a Network Load Balancing setup.

End users will automatically be re-directed to the least loaded server in the NLB setup.

When the computer is restarted, in rare occasions, it may be necessary to force the TARGIT Server to hold back its starting procedure until other services have started. E.g. it may be necessary to put a dependency on the SQL Server Analysis Services service.

The Server Trace option enables you to log detailed information about requests into your Event Viewer.

This option should only be enabled for the purpose of troubleshooting errors. Remember to disable again when the problem has been solved – otherwise you would quickly fill up your Event log and possibly also degrade overall system performance.

The TARGIT Server login credentials (e.g. for accessing data on an SQL server) can be changed through Change Service Account.