TARGIT Administrator
This section is intended for users who administrate a TARGIT solution.
Setup - Front-End
Number Format
By default this setting is checked on new installations and therefore all formatting is done on the client side according to the login (or browser) language. If this setting is disabled all number formatting is done on the server according to the system language and all clients will see the same number formatting. An advantage of using client-side formatting is the reductions in query result size, especially with cross tables. Both the server and client-side formatting may be overwritten by changing the number formatting on the individual data objects in the clients.
The currency setting decides what currency is used when using the currency number format.
Note: When upgrading from versions prior to build 4062, client-side formatting is disabled to ensure backward compatibility.
Statistics
Anonymous usage statistics are sent to TARGIT for improving and selecting future features. The statistics contains a list of features that users use in the client (ribbon content, right-click menu content and so on), but does not point out individual users nor does it contain any customer data. Click the Privacy policy link for details.
Splash screen
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: If the display of the splash screen should be enforced, a check-mark may be set.
Data request cache
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.
Client update
Update clients automatically: When end-users log on with the TARGIT Desktop App, the client version is checked against the server version. If the server version is newer, the TARGIT Desktop App will automatically be updated to match the server version.
Shortcut name and icon: As an Administrator you have the option to define the name and the icon of the TARGIT Desktop App as it should appear in the end-user's Windows Start menu.
Redirect to server: If the TARGIT installation is moved from one server to another, this option can be used to automatically redirect logins from the old server to the new server.
Setup - Back-End
Logging
The logging option allows requests to be logged in the auxiliary database. By default analysis requests are logged when checking the 'Log Analysis requests to auxiliary database' option, but it is possible to add storyboard requests to the logging by checking the 'Log storyboard requests' option. The counter adjust button ‘Keep data for’ is used for specifying the number of months to keep the logged requests in the database. If 0 (zero) is selected, the requests are kept until they are removed manually. If logging is disabled after being enabled the logging stops as soon as the currently running requests stops. If logging is enabled again, the logging does not start for the currently logged on users - only the ones logging on later. If the Auxiliary connection is changed while logging is enabled, the log will continue to use the old connection - until logging is stopped and restarted or the TARGIT Server is restarted.
Online License Update
Automatic license update may be enabled and a one hour period may be selected for the update to take place. The current license is sent, at a random time within the given time period, to the licensing server and a check for an updated license is made. If an update is needed e.g. due to expiration or update to a later version, the license will automatically be updated.
Criteria request cache
The following settings may be turned up or down for criteria 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 criteria requests may be set to on or off on a database connection.
Multiple Logins
The default setting is that only one user can be logged on to the TARGIT Management client at a time. Use this setting to enable multiple simultaneous logins to the TARGIT Management client. However, if enabled, a warning will be displayed if a user attempts to log in while another user is already logged in. You will be warned that your work may potential be lost if another user is working on and saving the same settings that you are working on.
Setup - Alerts and Notifications
The Alerts and Notifications option is used to send e-mails if TARGIT Server errors occur and to specify the mail server to be used when scheduling notifications and Reports. It lets you specify the mail server to be used for outgoing mails. The server name may be followed by a colon and a port number.
Using SMTP authentication is possible, user name and password may be entered in the appropriate fields. It is also possible to enable SSL/TLS encryption if the server supports it.
Error reports by email are by default sent from ‘antserver@computer name’. Some mail servers however requires that sender address is a fully qualified domain name. An edit field allows specifying a correct sender address.
An example of an error could be that the TARGIT Server could not process a request or that the given request is invalid. When enabling the Administrative alerts option, it becomes possible to set an option to report different kinds of errors and write one or more e-mail addresses of the recipients.
Note: To send e-mails to external addresses the mail server needs to be configured to allow relay from the TARGIT Server. The simplest way to do this is to add the IP address of the TARGIT Server to the mail server's "Relay Allowed" list.
Setup - Performance
Performance
Maximum number of active threads determines the number of concurrent threads the TARGIT Server will use to serve the clients. Each client will use its own thread, but this setting can be used to limit the number of active threads. 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. Default is set to 4 times the number of CPU cores.
The maximum number of Sentinels threads may also be set and is used to specify how many threads should be used for searching for Sentinels. The default value is 1 on a single CPU server and half the number of CPU cores on a multi-core server. This is to avoid that all processing power is used on searching for Sentinels. The number may be changed, but no more threads than the number of CPU cores can be assigned to the Sentinel search even though a higher number may be entered. A value of 0 threads is the same as default.
Network Load Balancing
When multiple TARGIT Servers are configured in a Network Load Balancing (NLB) environment, this option may be enabled and the NLB parameters may be specified. The basic principle of operation is that requests may be rejected a maximum number of times, depending on the actual load of the TARGIT Server and below ‘Maximum Rejections’ setting. The actual thresholds triggering rejections may be based on either a CPU load percentage over a certain time period, on the number of Active Queries or a combination hereof. If both thresholds are set, request rejection will take place if one of them is fulfilled.
CPU Load
Check this to activate the threshold and specify the CPU percentage and time period that the actual CPU load has to be higher than in order to initiate a request rejection. The default values are 95% over 10 seconds.
Active Queries
Check this to activate the threshold and specify the Maximum Queries that will trigger a request rejection. The default value is four times the number of CPU cores on the server running the TARGIT Server.
Setup - Server Trace
Server trace consists of two options that will change the registry settings. Log requests logs analysis requests in the event log (this is in addition to the log in the auxiliary database if enabled in the Backend module). Log to file is only relevant when the TARGIT Server is running as a service. The option enables the possibility to log to a file (.LOG) rather than the application event log. The log file is date stamped and if the file exceeds 2GB during one day, more files are created. . LOG files are located in the folder: ...\ProgramData\ANTserver\TARGIT\LOG. MDX queries sent to the database may also be logged by checking the MDX check box.
Note: These options should only be used for debugging purposes, because of the large amount of data sent to the event log or log file. Logging data requests requires an Enterprise Server license.
Setup - Change Service Account
Choose the Service Account, according to your organisation's security policy, that should run the TARGIT Server.
Connections
Clicking the Connections module shows a list of current connections and their properties. Rightclicking a connection opens a menu with options to add, delete, disable and see the properties for the connection. When adding a new connection a new dialogue opens with options to create a MultiDimensional, Relational or Other connection.
Database setup dialogs for databases may have the following options:
Impersonation: (Windows Security Impersonation / Delegation)
Used to specify that user’s access to the database should be controlled by the cube security. This option is only active for Microsoft Analysis Services cubes, and when using Windows authentication. Using impersonation on a database connection has the disadvantage of not being able to use scheduling since the users' credentials are needed to do the impersonation and these credentials are not known when the scheduled job is executed. Microsoft Analysis Services 2005 has introduced an alternative to 'Standard' impersonation called 'Effective user'. By supplying just the user name (and not the password) Analysis Services will behave as if the user was authenticated and any security set up in the database will be considered. Furthermore, this allows scheduled jobs to be executed. Note that this requires the user that logs into Analysis Services (i.e. the user running the TARGIT Server) to have administrator rights.
Note: If TARGIT Server and Analysis Services are on separate servers, they must be on the same domain and the TARGIT Server PC must have “delegate” rights. Also note that the TARGIT login option “Specify credentials” does not work in connection with “Impersonate users” if TARGIT Server and Analysis Services are on separate servers, so in this case the Client PC’s must be on the same domain as the servers.
Non empty criteria
This property is enabled by default and ensures that dimensions on the criteria bar are filtered such that members causing empty results are removed from the dimensions displayed in the criteria bar. This option is only available in connection with Multi-Dimensional databases.
Non empty queries
This property is enabled by default and filters dimension members with empty results from the data set. This option is only available in connection with Multi-Dimensional databases.
Use subcubes
A subcube is a subset of a cube based on the criteria applied to the data set. The use of subcubes is enabled by default and will in most cases result in a performance increase. Use of subcubes has both pros and cons which should be considered. This option is only available in connection with MultiDimensional databases.
Max active connections
Used to limit the number of active connections to the backend database server.
Accumulated query time before reconnect (seconds)
In order to reduce Pivot Table Services memory requirements when accessing large databases, it is recommended to disconnect and reconnect from the database at certain intervals. The number of seconds of accumulated query time between each disconnect may be specified here. Default setting is 0 (zero) for no automatic disconnect / connect.
Generate SQL based on consistent data (Only relational databases)
This option indicates to the TARGIT Server if data are consistent or not. Specifically if all foreign keys lead to a proper result. This option is on by default, but can be cleared if data are known to be inconsistent, e.g. when connecting to a real-time source. Note that if this option is cleared the query performance may be reduced.
Check for Desktop and Touch notifications
This option is on by default. Clearing it prevents notifications from being displayed for Desktop and Touch when processing the data model related to the connection. If a connection is very often processed and the connection is not used for Desktop or Touch, performance may be improved by clearing this option, since the TARGIT Server does not have to check for notifications.
Cache data requests
Data request cache works in connection with data requests in order to reduce the time it takes to fetch and display data when data requests are repeated. Note that default is on on multidimensional database and Xbone connections and off on relational database connections. Every time a cube is processed, the cache is flushed in order to prevent outdated results, which means that cache on close to real-time connections may have little or no effect.
Data request cache files for the Windows client are placed in the following folder on the local computer:
<drive\path>\users\\Appdata\Local\Temp\cache\
Data request cache files for Web and Touch clients are placed on the server in folders similar to this:
<drive\path>\windows\temp\cache_\
The data request cache is updated in case of cube processing and when colors are changed.
Cache criteria requests on server
Criteria request cache works in connection with criteria requests in order to reduce the time it takes to fetch and display criteria when criteria requests are repeated. Note that default is on on multidimensional database and Xbone connections and off on relational database connections. Every time a cube is processed, the cache is flushed in order to prevent outdated results, which means that cache on close to real-time connections may have little or no effect.
Criteria request cache files are placed in the following folder on the server:
<drive\path>\Program Data\TARGIT\ANTserver\cache
The criteria request cache is updated when processing the cube, when changing colors and in case of changing forced criteria in roles or changing decorations.
Select Into SQL: (Only relational databases)
This field makes it possible to enter an SQL statement that the TARGIT Server uses when aggregation tables are created. The statement consists of SQL keywords and placeholders e.g. (SELECT INTO ). The TARGIT Server replaces the placeholders with SQL when working on the aggregation tables. Other SQL statements that copies data from one table to another may also be used (e.g. CREATE TABLE AS SELECT ).
License
When connected to a TARGIT Server and clicking the license module, a list of the license values is shown e.g. expiration date, version and number of named users for each application.
The license information may be altered by using one of the options under the license values; Download License, Import License and Check Online Now. A License is supplied as a 16 character License Key which may be entered here and used to download the license data from the license portal. In case the PC running the TARGIT Management application does not have access to the Internet, it is possible to download the license information from the license portal as an XML file which may then be used with above Import License option. Older license keys and license files may be used to register the license as long as the old key or file is valid and there is an update subscription for the license.
The last option is to check for license updates. This is done by sending the current license to the licensing server, which checks for updates. If an update is needed the license will automatically be updated.
Note: Incorrect License information will disable the TARGIT Server, and all other Server modules and settings will be unavailable.
Logins
The Logins module provides an overview of the logins for the license. For each of the licensed applications, the number of available, used and connected logins are shown. The Logins overview may be refreshed by right-clicking and selecting 'Refresh list'. For a more detailed view of the logins, double-click one of the applications for a view of logins to all applications or right-click an application and select to view logins for the selected application or for all applications. This opens a new window, where the list of users who have logged in is shown in the leftmost column. Users with a grey dot are not currently logged in and users with a green dot is currently logged in. Unfolding the plus-character next to each user reveals the logins performed for the user and for users currently logged in, another plus-character may be unfolded to see the IP-address of the user. For each of the logins, the last logon time, the user level and the client version of last login are shown in the other columns. Columns may be sorted by clicking them.
To the right of the logins overview filters may be applied. This is done by selecting the permission rights of the users who should be shown and/or select if disconnected, connected or both kind of users should be shown. The filters are applied instantly.
At the bottom of the window three buttons allow for a refresh of the logins, disconnecting users and deleting users. Deleting users may be used to free up some of the used logins and make room for new users.
Language
The language module is used for customizing business terms in relation to the TARGIT databases. The database terms, including names of databases, measures, dimensions and dimension levels may be translated. Also names of folders and files in TARGIT Smartpad Documents Shared section may be customized.
Each implemented language is represented by an entry in the list of languages. Double clicking a language entry opens a Language Properties dialog with options to edit business terms. A right-click menu is also available for opening the Language Properties dialog for the selected language.
The left column of the Language Properties dialog displays a tree structure for each database and Smartpad Documents, where nodes are preceded by plus or minus signs, which is used to expand or collapse the nodes. The tree may be browsed by using the arrows keys. The middle column ‘Translated Name’ of the Language Properties dialog is used for translation of the business terms. After having selected an original element of the database tree in the left column, pressing the Enter key will prepare the corresponding edit field in the middle column for entering the translation. Press the Enter key again to accept the translation. The right column ‘Translated Description’ is used to add a description of the business term. Content of this field will be displayed as a hint when the cursor is hovered over the field in Smartpad Source data tab or the folder or file in Smartpad Documents.
To edit a translated element, press F2 or Enter and type the translation. If the translation is the same as the original use the right-click menu and select 'Copy Original'.
The Suggestion field below the tree structures is filled if an identical original with a different translation is found anywhere in the list. This can be used to make the translations consistent and the suggestion can be applied by clicking the Apply button or right-click an entry in the language list and select 'Copy Suggestion' (Shortcut is Ctrl S). Other options in the right-click menu include 'Copy Default' (Ctrl D), which copies the translation of the default language and 'Copy Original' (Ctrl O), which copies the original text. 'Expand Recursive' expands all the nodes in the database tree and 'Remove Translation' removes the translation.
