Server Configuration

To configure your Data Server, you must be signed on to the system as an administrator with the requisite permissions to modify the database.

To access the server configuration settings, click Server configuration in the Functionality section on the Longview Server Manager home page. The Server configuration page opens with the Application tab in view.

The following tabs are accessible through the Server configuration page:

Application
Diagnostics
Events & data monitoring
Memory & pooling
Performance
Recalculation
System
System limits
Timeouts
User security
Web

Refresh button

At any time, you can click the Refresh button to refresh the Server configuration page with the current values in the lvsrvr.cfg file located on the Longview Data Server.

Search in Server Configuration

In each functionality page, you can use the Search field to easily find the items you need. The search functionality allows to filter a list based on the text you type in the Search box. The Search functionality is available for all the tabs in each page. If you switch between the tabs in a functionality page, and apply the Search filter, each tab will display only the matched items.

Additionally, the Search functionality allows you to search folders and files under the sub-folders. For example, if you want to search a log file with the name starting from "event", then in the Search box, start typing event. The Search box will display all the files under folders and sub folders with the name event. For more information, see the following image:

Searching log files under sub folders

To clear the search, delete the text in the Search box or click the Close button in the Search box.

Application

The Application tab presents you with a list of functionalities available in the application. In general, if a parameter is selected, it is on and available to users. If a parameter is cleared, it is off and unavailable.

Parameters on the Application tab

The following table lists the parameters that you can configure on the Application tab:

Setting	Default	Description
N-dimensional distribution (NDD)	Cleared	Specifies whether to use N-Dimensional Distribution in this system. For more information, see N-Dimensional Distribution.
Period activity calculation (PAC)	Cleared	Specifies whether to use Period Activity Calculation logic in this system. For more information, see Period Activity Calculation.
Retained earnings calculation (REC)	Cleared	Specifies whether to use Retained Earnings Calculation logic in this system. For more information, see Retained Earnings Calculation.
Year to date calculation (YTD)	Cleared	Specifies whether to use accounting year-to-date (YTD) logic in this system. For more information, see Year-to-date.
Foreign exchange (TRN)	Cleared	Specifies whether to use data translation in this system. For more information, see Translation.
Round foreign exchange results	Cleared	Specifies whether to use translation rounding in the system. If this parameter is selected, Foreign exchange (TRN) must also be selected.
Journal entries	Cleared	Specifies whether to use the Journal Entry Server in this system.
Intercompany eliminations (Elim)	Cleared	Specifies whether to use the Elimination Server in this system. If this parameter is selected, Journal entries must also be selected.
Model rules	Selected	Specifies whether to use server model rules in this system.
Validation rules	Selected	Specifies whether to use validation rules in this system.
Query rules	Selected	Specifies whether to use query rules in this system.
Rollup rules	Selected	Specifies whether to use rollup rules in this system. Selected — Rollup rules are used. The calculation of data areas is subject to inclusion or exclusion as set in the Use inclusion method for rollup rules parameter. Cleared — Rollup rules are not used (all data areas are calculated).
Use inclusion method for rollup rules	Cleared	Specifies the rollup rule method, in conjunction with the Rollup rules parameter. Selected (INCLUSION ) — Only the DataArea specified by a rollup rule rolls up. All other areas of the database do not roll up to their parents. Cleared (EXCLUSION ) — All areas of the database roll up, except for those specified by a rule. Areas specified by a rule do not roll up to their parents.
Use flows	Cleared	Specifies whether to use FLOWS dimension in this system.
File attachments Note: This parameter is applicable only up to version 25.1.	Selected	Specifies whether to allow users to attach files to a cell in web input templates and Data Grids. Note: This parameter must be selected if using the HTML5 Dashboard Designer.
Use web deployment	Selected	Specifies whether to deploy the Longview components using Web Deployment or Enterprise Deployment. Selected - Deploys the Longview components using ClickOnce. Cleared - Uses Enterprise Deployment to install and upgrade the Longview components. Note: Enterprise Deployment is not supported with legacy dashboard.
Workflow	Cleared	Specifies whether to enable Longview Workflow.
Use journal entry workflow	Cleared	Specifies whether users receive emails notifying them of journal entry activity. Selected — Sends users notification emails. If this parameter is selected, Journal entries must also be selected. Cleared — Disables email notifications.
Use HTML5 dashboard Note: This parameter is applicable only up to version 25.1.	Selected	Specifies whether the HTML5 dashboard is used. Selected — Dashboard is rendered using HTML5 and standards. Cleared — Dashboard is rendered using legacy HTML.
Data audit trail	Cleared	Specifies whether Data Audit Trail is enabled in this system. Data audit trail is used to query the database for records of what values in the database have been changed and by which users and to export those records to a text file. For more information, see the Longview Application Administrator Guide.
Metadata audit trail	Cleared	Specifies whether metadata audit trail is enabled in this system. Metadata audit trail captures metadata changes in the system, such as user and group maintenance, symbol maintenance and attribute maintenance. The changes are stored in the LV_AUDIT_METADATA table. This table can grow, and it is recommended that this table is archived occasionally.
Perform calculations on delta values	Selected	Specifies whether the system uses deltas when processing math logic to eliminate rounding errors caused by using the delta values for math processing. Selected — The system uses the difference in the deltas for math processing. Cleared — The system zeroes out the area to which users are submitting data, and then submits the new value.
Session locks	Selected	Specifies whether to use session-based locking for Application Framework. Selected — When an Application Framework session ends, when the timeout is reached or the connection is lost, all session locks are released. Cleared — Locks are maintained when an Application Framework session ends and must be deleted manually.

Diagnostics

Note: From the version 25.2, please refer to the Diagnostics page in the Longview Server Manager guide since the Diagnostics section no longer applies in 25.2 to the lvsrvr.cfg file.

Events & data monitoring

The Events & data monitoring tab allows you to set policies related to Event rules and the Data Server.

Parameters on the Events & data monitoring tab

The following table lists the parameters that you can configure on the Events & data monitoring tab:

Setting	Value	Description
Use event rules	Selected or Cleared Default: Selected	Specifies whether to enable Event-based rules in this system.
Data event sequencing	Selected or Cleared Default: Cleared	Specifies whether to use sequencing for events. If you use data event sequencing, the Default actions time interval setting is ignored. For more information on data event sequencing, see the Longview Application Administrator Guide.
Event queue max	Numeric value Valid range: 32 to 100000000 Default: 5000	Specifies the size of the queue to be used by the Model Server in processing event messages.
Maximum active data events	Numeric value Valid range: 0 – 999 Default: 999	Specifies the maximum number of active data events to allow in an event sequence iteration.
Maximum persistent event rules	Numeric value Valid range: 0 – 999 Default: 999	Specifies the maximum number of event rules that can be set as persistent. If you do not want to use persistent event rules, set this parameter to 0. For more information on persistent event rules, see the Longview Application Administrator Guide. Note: Setting event rules as persistent increases memory consumption on the data server. If you do not allocate enough memory, specifying event rules as persistent may cause your system performance to degrade instead of improving.
Maximum data event iteration time	Numeric value Valid range: 0 -1440 Default: 2:00	Specifies the maximum time, in the format mm:ss, that the Management Server will wait for the current iteration to complete before starting the next iteration. The minimum value allowed for this parameter is 00:01 and the maximum is 1440 minutes (one day).
Default actions time interval	Numeric value Valid range: 0 – 1440 Default: 00:05	This parameter applies only if Data event sequencing is not used. Specify the minimum amount of time that must pass before the same event action may be triggered again. The format for this value is mm:ss, where mm is the number of minutes, and ss is the number of seconds. The seconds value is optional. The minimum value for this parameter is 0 minutes, and the maximum is a combined value of 1440 minutes (one day).
Data area monitoring	Selected or Cleared Default: Cleared	Specifies whether to track and store batch and event activity for a given data area. If you select this parameter, you must specify at least one dimension for Data area monitoring dimensions. Optionally, you can also specify a dimension for report status tracking (Data area status dimension).
Data area status dimension	The name of a dimension in your system	This parameter applies only if Data area monitoring is selected. Specifies the dimension for which to enable data area status tracking. The dimension must be included in those specified for Data area monitoring dimensions. For example, Entities. If you do not specify a dimension for this parameter, data area status is not tracked.
Data area monitoring dimensions	Comma-delimited list of dimensions	This parameter applies only if Data area monitoring is selected. Specifies the dimensions for which to enable data area monitoring. Separate multiple dimensions with a comma. Spaces are not supported. For example, Accounts,Entities,TimePer.

Memory & pooling

The Memory & pooling tab allows you to configure memory and pooling of your system.

Parameters on the Memory & pooling tab

The following table lists the parameters that you can configure on the Memory & pooling tab:

Setting	Value	Description
Data cache	Numeric value Valid range: 1024 - 2048000 Default: 102400	Specifies the amount of RAM (in KB) reserved in the KSA for data cache files. Increase this value to allocate more memory to this cache (memory is allocated only if the Store calculated data in cache files parameter is selected). The size of this cache affects performance of queries when using data cache files.
Hierarchy server memory	Numeric value Valid range: 1024 -1245184 Default: 10240	Specifies the amount of RAM (in KB) reserved in the KSA for the Management Server. This parameter depends on the number of symbols and parent/child relationships. To identify the minimum amount, see the Longview Data Server Log (lv_dataserver.log) after the Management Server has started. It must be higher than the minimum amount required, or the server will not start. It should also be high enough to allow for expected growth in the size of the hierarchy. However, setting this value excessively high wastes memory. This value does not affect performance.
NDD memory	Numeric value Valid range: 1024 – 2048000 Default: 1024	Specifies the amount of RAM (in KB) reserved in the KSA for N-Dimensional Distribution (NDD). This parameter depends on the number of symbols configured for NDD.
Math server memory	Numeric value Valid range: 1024 – 2097151 (approximately 2 GB) Default: 102400 Optimal: 262144	Specifies the maximum amount of RAM (in KB) to be used by each Math Server in the Math Server Pool. Once the Math Server pool reaches that memory for a job, it transfers the data to the writer pool. Leave enough for operating system overhead and the RDBMS (if it resides on the same machine). To calculate the total possible memory consumption during a restatement or recalculation, multiply this number by the Number of math servers value. To speed up math operations (rollup, accounting, and model), you can increase this parameter to increase the overlap percentage, resulting in fewer redundant writes to the database tables. It will also help reduce the temporary disk space usage. However, make sure your system has enough memory to support the setting.
Foreign exchange memory	Numeric value Valid range: 1024 – 1024000 Default: 10240	Specifies the amount of RAM (in KB) reserved in the KSA for translation logic. This parameter depends on the number of different translation rates used, and is used only if Foreign exchange (TRN) is selected on the Application tab.
Rules	Numeric value Valid range: 10 – 102400 Default: 10240	Specifies the amount of RAM (in KB) reserved in the KSA for the Management Server. This parameter depends on the number and complexity of server rules, and is used only if Model rules is selected on the Application tab.
Writer memory	Numeric value Valid range: 10240-2097151 Default: 102400	Specifies the amount of RAM (in KB) reserved for the writers. This parameter is only used on Windows platforms, and only if Writer async IO is selected on the Recalucation tab.
Number of server agents	Numeric value Up to version 25.1: Valid range: 0 - 250 Default: 10 Valid range: 0 - 250 Default: 40	Specifies the number of agents required to handle connections from Longview. If you use a value of 0 (in other words, a dedicated server) Longview will use one agent for each connection, rather than using a pool of agents.
Number of web agents	Numeric value Up to version 25.1: Valid range: 0 - 250 Default: 10 Valid range: 0 - 250 Default: 40	Specifies the number of web agent workers to spawn.
Number of journey entry workers	Numeric value Valid range: 1 – 100 Default: 1	Specifies the number of workers in the Journal Entry (JE) Pool.If the journal entry portion of a recalculation or restatement runs too slowly, you can increase this value to attempt to improve performance.
Number of math servers	Numeric value Valid range: 1-100000 Default: 1	Specifies the number of Math Servers required to handle math logic. Longview suggests that you set this value to the total number of CPUs on the server machine for optimal performance. The recalculation or restatement attempts to take full advantage of all available Math Servers in the pool. You can specify this parameter as the number of CPUs in the server machine. If the math portion of a recalculation or restatement runs too slowly, increase this value. Note: Increasing this number beyond the numbers of CPUs in your system will have less impact and may slow it down.
Number of submission servers	Numeric value Valid range: 1-100000 Default: 2	Specifies the number of Submission Servers required to handle data submissions.
Number of writer servers	Numeric value Valid range: 1-100000 Default: 2	Specifies the number of Writer Servers required to handle data written to the database. You can increase this value if your system is partitioned at the leaf level. The recalculation takes full advantage of all available writers in the pool. The writers are responsible for merging and sorting temporary files created by the Math Server, then loading the result into a Longview data table. You can set this parameter to a value as large as possible without causing disk bottlenecks on the server machine. In practice, many data tables may actually be small, with only a few large ones. In this case, the recalculation will likely not benefit from a Number of writer servers value larger than the number of large data tables (since these are the loads likely to take the longest, any additional writers will be idle). Increasing this parameter causes more concurrent table loads to happen during a recalculation or restatement. Increase this value to keep as many disks and controllers busy as possible during the load portion of the recalculation or restatement.

Performance

The Performance tab allows you to set system limits in areas that can affect the timely execution of operations.

Parameters on the Performance tab

The following table lists the parameters that you can configure on the Performance tab:

Setting	Value	Description
Query fetch size	Numeric value Up to version 25.1: Valid range : 1000 - 32000 Default: 32000 Valid range: 1000 - 1024000 Default: 96000	Specifies the fetch size for data queries. A larger fetch size results in a better compression rate, and therefore better data query performance, especially over slow networks. However, more memory is consumed by agents during large data queries.
Query string data fetch size	Numeric value Valid range: 1000 – 16000 Default: 2500	Specifies the maximum size of string data to be returned in a query.
Range conversion limit	Numeric value, or AUTO Valid range: 0 – 16 Default: 0	Specifies the number of dimensions to which range conversion logic applies. Numeric value — Specifies the number of dimensions (from 0 to 16). AUTO — Specifies the number of dimensions minus 2. For example, if your system has 16 dimensions, this value will set the range conversion limit to 14. Range conversion logic is used to optimize the SQL statements generated when querying data from the database. The logic considers converting one dimension's query constraint to a parameter and repeatedly re-executing the statement with different parameter values, as this can be more efficient than a BETWEEN clause, which can sometimes return extra data that needs to be discarded. This parameter determines the maximum number of dimensions to consider (in index order) for the use of range conversion logic.
Range conversion max	Numeric value Valid range: 1-32000 Default: 32000	Specifies the maximum number of symbols to allow when considering the use of range conversion logic for a dimension. Range conversion logic is used to optimize the SQL statements generated when querying data from the database. The logic considers converting one dimension's query constraint to a parameter and repeatedly re-executing the statement with different parameter values, as this can be more efficient than a BETWEEN clause, which can sometimes return extra data that needs to be discarded. This parameter determines the maximum number of symbols to allow in a dimension being considered for range conversion (and therefore the maximum number of re-executions of the statement).
In clause max	Numeric value Valid range: 10-32000 Default: 10	Specifies the maximum number of symbols to allow when considering the use of an IN clause for a dimension. Range conversion logic is used to optimize the SQL statements generated when querying data from the database. The logic considers converting one dimension's query constraint to an IN clause explicitly listing the individual symbols requested, as this can be more efficient than a BETWEEN clause, which can sometimes return extra data that needs to be discarded. This parameter determines the maximum number of symbols to allow in an IN clause.
Maximum query rule data	Numeric value Value range: 0-1000000000 Default: 0	Specifies the maximum number of query rule records allowed in a single query. The default value (0) specifies that an unlimited number of query rule records are allowed.
Writer batch size	Numeric value Valid range: 500- 1000000000 Default: 50000	Specifies the batch size. When the value of writer batch size is reached, the writer transfers data from the temp table to the destination table. The higher this value, the better the throughput of the writer. However, there may be a penalty in size of database temporary space, rollback, and so on.
Writer hash value	Numeric value Valid range: 1 – 256 Default: 1	Specifies how to divide a Writer job destined for one table into multiple jobs, so that multiple writers can work on them concurrently. It is faster to have many processes updating one table in parallel than to have one process update the table with all records sequentially.
Temp batch size	Numeric value Valid range: 200 –1000000000 Default: 5000	Specifies the batch size when inserting records into temporary tables during submissions. The higher this value, the better the throughput of the writer. However, there may be a penalty in terms of the amount of memory required.
Gather Oracle statistics	Selected or Cleared Default: Cleared	This parameter applies only to Oracle systems. If selected, Oracle database statistics are gathered automatically on the temporary tables after they are created, which helps the Oracle optimizer make appropriate assumptions when choosing an access plan. Before you select this parameter, make sure the DBO can gather statistics on its own schema.

Setting

Value

Description

Query fetch size

Numeric value

Up to version 25.1: Valid range : 1000 - 32000 Default: 32000

Valid range: 1000 - 1024000

Default: 96000

Specifies the fetch size for data queries.

A larger fetch size results in a better compression rate, and therefore better data query performance, especially over slow networks. However, more memory is consumed by agents during large data queries.

Query string data fetch size

Numeric value

Valid range: 1000 – 16000

Default: 2500

Specifies the maximum size of string data to be returned in a query.

Range conversion limit

Numeric value, or AUTO

Valid range: 0 – 16

Default: 0

Specifies the number of dimensions to which range conversion logic applies.

Numeric value — Specifies the number of dimensions (from 0 to 16).
AUTO — Specifies the number of dimensions minus 2. For example, if your system has 16 dimensions, this value will set the range conversion limit to 14.

Range conversion logic is used to optimize the SQL statements generated when querying data from the database.

The logic considers converting one dimension's query constraint to a parameter and repeatedly re-executing the statement with different parameter values, as this can be more efficient than a BETWEEN clause, which can sometimes return extra data that needs to be discarded.

This parameter determines the maximum number of dimensions to consider (in index order) for the use of range conversion logic.

Range conversion max

Numeric value

Valid range: 1-32000

Default: 32000

Specifies the maximum number of symbols to allow when considering the use of range conversion logic for a dimension.

Range conversion logic is used to optimize the SQL statements generated when querying data from the database.

This parameter determines the maximum number of symbols to allow in a dimension being considered for range conversion (and therefore the maximum number of re-executions of the statement).

In clause max

Numeric value

Valid range: 10-32000

Default: 10

Specifies the maximum number of symbols to allow when considering the use of an IN clause for a dimension.

Range conversion logic is used to optimize the SQL statements generated when querying data from the database.

The logic considers converting one dimension's query constraint to an IN clause explicitly listing the individual symbols requested, as this can be more efficient than a BETWEEN clause, which can sometimes return extra data that needs to be discarded.

This parameter determines the maximum number of symbols to allow in an IN clause.

Maximum query rule data

Numeric value

Value range: 0-1000000000

Default: 0

Specifies the maximum number of query rule records allowed in a single query. The default value (0) specifies that an unlimited number of query rule records are allowed.

Writer batch size

Numeric value

Valid range: 500- 1000000000

Default: 50000

Specifies the batch size. When the value of writer batch size is reached, the writer transfers data from the temp table to the destination table.

The higher this value, the better the throughput of the writer. However, there may be a penalty in size of database temporary space, rollback, and so on.

Writer hash value

Numeric value

Valid range: 1 – 256

Default: 1

Specifies how to divide a Writer job destined for one table into multiple jobs, so that multiple writers can work on them concurrently.

It is faster to have many processes updating one table in parallel than to have one process update the table with all records sequentially.

Temp batch size

Numeric value

Valid range: 200 –1000000000

Default: 5000

Specifies the batch size when inserting records into temporary tables during submissions.

The higher this value, the better the throughput of the writer. However, there may be a penalty in terms of the amount of memory required.

Gather Oracle statistics

Selected or Cleared

Default: Cleared

This parameter applies only to Oracle systems. If selected, Oracle database statistics are gathered automatically on the temporary tables after they are created, which helps the Oracle optimizer make appropriate assumptions when choosing an access plan.

Before you select this parameter, make sure the DBO can gather statistics on its own schema.

Recalculation

The Recalculation tab allows you to configure recalculations and establish policies for their execution.

Parameters on the Recalculation tab

The following table lists the parameters that you can configure on the Recalculation tab:

Setting	Value	Description
Store calculated data in cache files	Selected or Cleared Default: Cleared	Specifies whether to store calculated data in cache files. Selected — Stores calculated data in cache files. Cleared — Loads all data to the database.
Use agent data cache	Selected or Cleared Default: Cleared	Specifies whether to store the data cache for agents and web agents in RAM. Selected — Stores the data cache for agents and web agents in RAM. Cleared — Stores the data cache for agents and web agents in the KSA along with other server data caches.
Compress temporary files	Selected or Cleared Default: Selected	Specifies whether to compress temporary files. Selected — Compresses temporary files, reducing disk space usage but slightly impacting CPU performance. Cleared — Disables compression of temporary files.
Load data table externally	Selected or Cleared Default: Cleared	Specifies whether a partition recalculation, restatement, or import should expect an external load to occur (for example, piped loading during a recalculation). Selected — The recalculation, restatement, or import truncates the tables, but does not load the resulting ASCII file (ftd_Pnnn.out). In this case, it is the responsibility of the Administrator to prepare the external load scripts. Cleared — The recalculation truncates the table and loads it (via SQL*Loader for Oracle, or via bulk insert for SQL server).
File type	BINARY or DELIMITEDASCII Default: BINARY	Specifies the type of output file a partition recalculation creates. BINARY — This file type produces the smallest and fastest loading file. DELIMITEDASCII — This file type produces a delimited ASCII file. It is preferable when you are troubleshooting and need to read the file’s contents.
File delimiter	Default: {	This parameter applies only if File type is set to DELIMITEDASCII. Specifies the character used as a delimiter in the ASCII file created during a partition recalculation. { — Uses the left brace as the delimiter. } — Uses the right brace as the delimiter. , — Uses the comma as the delimiter. ; — Uses the semicolon as the delimiter.
Hash dimension	Valid dimension name Default: AUTO	Specifies the dimension to be used to split up the leaf records into smaller jobs (hashing). Avoid specifying dimensions with single symbols that contain large percentages of data. The default value AUTO means splitting up the leaf records of the dimension with the largest number of symbols into smaller jobs. Sometimes this choice results in unbalanced performance, which can be detected by noting the last message from each Math Server during a recalculation or restatement. If some Math Servers complete long before others, the jobs are not balanced. If so, select a dimension in which the data is evenly distributed.
Hash value	Value range: 1 - 256 Default: 32	Specifies the number of jobs in a group, using hashing logic. If this value is greater than 1, the system subdivides Math Server jobs during a partition recalculation. This number can range from 1 to 256. For example, if this value is specified as 5, the recalculation divides the number of rows in the leaf tables into 5 sections to do the rollup, contributing to performance gains. Increase this value to create more jobs with each containing fewer records and to help balance the Math Servers, as described in Hash dimension. You may have to test this value when running your restatement to find the optimal value.
JE recalculation batch size	Numeric value Value range: 1000 - 128000 Default: 25000	Specifies the fetch size used by the Journal Entry Server during journal entry recalculations. A larger fetch size results in faster recalculations but consumes more memory.
Use grid processing	Selected or Cleared Default: Cleared	Specifies whether grid processing should be used when running restatements.
Grid listener port	Valid port number	Identifies the Grid Listener Port number.
Grid cursors maximum	Numeric value Valid range: 1 – 12 Default: 4	Specifies the maximum number of grid cursors.
Grid output maximum threads	Numeric value Valid range: 1 – 80 Default: 5	Specifies the maximum number of grid output threads.
Writer async IO	Selected or Cleared Default: Selected	Enables asynchronous IO for your grid environment when the parameter is selected, and the value of Writer memory on the Memory & pooling tab is a positive integer.

System

The System tab allows you to configure your system.

Parameters on the System tab

The following table lists the parameters that you can configure on the System tab:

Setting	Value	Description
Database server	Maximum length 253 characters Default: localhost	Identifies the name of the server on which the database is hosted.
Application server	Valid string Maximum length 253 characters	Identifies the host name or address of the Data Server that the Longview Smart Client should connect to. The GetSessionInfo web action returns this parameter to the Longview Smart Client or to Longview Tax.
Server listener port	Numeric value Valid range: 1000 – 65535 Default: 28000	This parameter is populated by the server installer and specifies the port number used by the Listener (client port). the port number used by the Listener (client port). Usually, the value of this port is the value of port used by the Longview_LID service + 1.
Java file name	Valid file	Specifies the name of the zip file containing the Java JDK. Example: "openjdk-12_windows-x64_bin.zip" Note: The file must exist in the software folder of the Longview Data Server’s working directory in zip file format.
SMTP server	Valid server name	Specifies the name of the SMTP server, if you are using email notification.
Alternate system language	EN or FR Default: FR	Specifies the alternate language to use in your system, using a two letter ISO language code.
Longview identifier policy	Selected or Cleared Default: Selected	Determines whether the system should use the Longview Identifier policy. Selected - The Client Longview Identifier (LID) must match the Server LID set as part of the installation process. For more information, see the Longview Installation Guide. Cleared - The Client LID can be different than the Server LID.
Server error action	IGNORE or WARNING Default: WARNING	Specifies how system responds to a data submission error. IGNORE - The user does not see an error message. Errors are reported to the Longview Data Server Log (lv_dataserver.log) only. WARNING - The user sees a server error message when connecting.
Use RDBMS temporary tables	Selected or Cleared Default: Cleared	Specifies whether the system uses Oracle Global Temporary temp tables instead of regular temp tables (for Oracle databases only).
Partition parent data tables	Selected or Cleared Default: Selected	Specifies whether the parent data table is partitioned.
Partition leaf and calculated data tables	Selected or Cleared Default: Selected	Specifies whether a data table is partitioned for leaf and calculated data.
Use memory cache	Selected or Cleared Default: Cleared	Specifies whether to enable caching data in memory if the MemoryCacheSizes.cfg file is present in the location specified by the Memory cache files location parameter. Note: Longview recommends caching data in memory only as part of a full-system performance strategy. Review Caching Data in Memory before implementing this feature.
Memory cache files location	Valid folder	This parameter applies only when Use memory cache is selected. Specifies the location of the memory cache folder containing the memory block files for caching data in memory. The default value for this parameter is the Data Server working directory, such as "C:\Longview\DataServers\LID" where LID is the Longview Identifier for the system. Note: The location must be a path local to the server machine. Do not specify a network drive. This functionality is only available for Longview Data Servers running on Windows O/S. For more information, see Caching Data in Memory.

System limits

The System limits tab allows you to set limits in your system.

Parameters on the System limits tab

The following table lists the parameters that you can configure on the System limits tab:

Setting	Value	Description
Maximum schedules	Numeric value Valid range: 1 – 5000 Default: 100	Specifies the maximum number of schedules allowed.
Maximum base data locks	Numeric value Valid range: 100-100000000 Default: 500	Specifies the maximum number of data locks allowed in the database.
Maximum schedule data locks	Numeric value Valid range: 100- 100000000 Default: 100	Specifies the maximum number of schedule locks.
Maximum homepage	Numeric value Valid range: 1 – 1024 Default: 1024	Specifies the maximum number of home page locks.
Maximum panels	Numeric value Valid range: 1 – 4096 Default: 1024	Specifies the maximum number of web panel locks.
Maximum sessions	Numeric value Valid range: 8 – 100000000 Default: 2000	Specifies the maximum number of sessions allowed at one time.
Math iterations	Numeric value Valid range: 100 -100000000 Default: 500	Specifies the maximum number of math iterations allowed.
Writer queue	Numeric value Valid range: 32 -100000000 Default: 50000	Specifies the maximum number of entries in Writer queue. If you have a high volume of submissions, make this value large enough to handle the backlog, but remember each leaf table can be handled by only one Submission Server at a time.
Elimination queue	Numeric value Valid range: 32-100000000 Default: 500	Specifies the maximum number of entries in the Elimination queue. If you have a high volume of submissions, make this value large enough to handle the backlog, but remember that each leaf table can be handled by only one Submission Server at a time.
Math queue	Numeric value Valid range: 32 -100000000 Default: 10000	Specifies the maximum number of entries in the Math queue. The value for Math queue does not change with changes in the Number of math servers value on the Memory & pooling tab. For example, if you specify 500 for Math queue, then regardless of number of Math Servers running (Number of math servers), there will be one queue with a maximum of 500 entries. If the queue becomes full, the 501st job returns an error. Use the following factors to calculate the optimum size of the math queue: volume of anticipated submissions during a peak period number of partitions (because submission jobs may be broken into many smaller partitioned jobs) Hash value used during a recalculation or restatement If you have a high volume of submissions, make this value large enough to handle the backlog, but remember that each leaf table can be handled by only one Submission Server at a time.
Submission queue	Numeric value Valid range: 32-100000000 Default: 500	Specifies the maximum number of entries in Submission queue. If you have a high volume of submissions, make this value large enough to handle the backlog, but remember each leaf table can be handled by only one Submission Server at a time.
Data cache compression level	Numeric value Valid range: 1 - 9 Default: 6	Specifies the compression level to use when generating data cache files. The range varies from 1 to 9; where 1 corresponds to the best speed and 9 corresponds to the best compression.
Maximum export file size	Numeric value Valid range: 1024 -2097151 Default: 2097151	Specifies the maximum size of any export file in KB.
Maximum file attachment size	Numeric value Validrange: 5 - 25 Default: 20	Up to version 25.1 this parameter applies only if File attachments is selected on the Application tab. Specifies the maximum file size in MB for file attachments in web input templates. If this setting is greater than the maxAllowedContentLength attribute in your IIS web.config file, the IIS setting is used. Note: From version 25.2, this parameter has no dependencies and is always applicable.
Auto archive log size	Numeric value Valid range: 0 – 400 Default: 50	Specifies the size in MB the lv_dataserver.log file can reach before it gets auto archived. When this value is set to 0, the lv_dataserver.log will not auto archive.

Timeouts

The Timeouts tab allows you to configure timeout periods in your system.

Parameters on the Timeouts tab

The following table lists the parameters that you can configure on the Timeouts tab:

Setting	Value	Description
Agent idle timeout	Numeric value Valid range: 1 – 1440 Default: 120	Specifies the timeout period (the number of minutes to wait if the agent is inactive). This parameter is not designed to be used as a method of disconnecting a user connection. It releases the agent after a specified period of inactivity but does not disconnect the actual user connection. This parameter applies to Longview Application Framework as well as Longview Tax and Longview Smart Client.
Web idle timeout	Numeric value Valid range: 5 -1440 Default: 120	Specifies the number of minutes to wait if the web agent is inactive, before releasing the web agent. This parameter applies to Longview Dashboard sessions. This parameter is not designed to be used as a method of disconnecting a user connection. It releases the web agent after a specified period of inactivity but does not disconnect the actual user connection.
Web idle timeout warning	Numeric value Valid range: 0 -1440 Default: 10	Specifies the number of minutes before timeout to send a warning to the user. This value must be less than the value set for Web idle timeout. Note: This parameter only applies to the legacy dashboard. It does not apply to HTML5 dashboard.
Web viewaction timeout	Numeric value Valid range: 0 – 1440 Default: 0	Specifies the number of minutes that a web request can run before it is terminated. If this parameter is set to 0, web requests can run for an unlimited amount of time.
Listener assignment timeout	Numeric value Valid range: 0 – 120 Default: 30	Specifies the number of seconds that listener server will wait for an agent/web agent to accept a RCP connect request. If timeout occurs, listener will try the next agent/web agent to accept the request. If this parameter is set to 0, it will wait for agent/web agent's reply infinitely.
Server timeout	Numeric value, in minutes Valid range: 1 – 120 Default: 10	Specifies the number of minutes to wait for a response before timing out on server startup or shutdown. The value set for this parameter has a specific impact on persistent event rules. If you attempt to stop the servers while a persistent event is running, the system waits until the event completes or the value set for Server Timeout is reached. The system behavior is dependent on what occurs first: If the persistent event completes before the value set for Server timeout is reached, the Management Server stops, and the server stop request continues. If the value set for Server timeout is reached before the persistent event completes, the server stop request is terminated and the servers continue to run. If additional events are triggered while the system is waiting, they are not started until the stop request is terminated. If the initial persistent event completes before the value set for Server timeout is reached, the additional events are not started, and the triggers are ignored. The Management Server stops, and the server stop request continues. Note: If you attempt to stop the servers while a non-persistent event is running, you receive a message that users are still connected, and the server stop request is terminated. For more information on persistent event rules, see the Longview Application Administrator Guide.
Database reconnect timeout	Numeric value Valid range: 0 – 60 Default: 10	This parameter applies to SQL servers only. This parameter, set in minutes, causes the server to check the connection each time it attempts to communicate with the database, and to reconnect if necessary. If the connection fails during a SQL operation, a regular error message is returned and the submission will not complete. The server will try to reconnect in the next operation. Reconnection will be attempted every five seconds for the duration of the time period (in minutes) defined by this parameter.
Database initiation timeout	Numeric value Valid range: 0 – 60 Default: 10	Specifies, in minutes, the amount of time that the server will retry connecting to the database, if the first attempt to connect failed. The server will attempt to reconnect every five seconds until the value set is exceeded.
Client keepalive timeout	Numeric value Valid range: 0 – 1440 Default: 0	Specifies the number of minutes a client socket waits after data is last sent before sending a TCP keepalive packet to the data server to verify that the connection is still available. If this parameter is set to 0, client sockets do not send TCP keepalive packets. Currently, this parameter applies to the following client components with or without using Longview HTTP Proxy: Longview Add-In for Office Longview Application Framework Longview Apps Longview Designer Longview Performance Manager Longview Tax Longview tools and editors

User security

The User security tab allows you to establish and manage protocols to protect the data in your system from unauthorized users.

Parameters on the User security tab

The following table lists the parameters that you can configure on the User security tab:

Setting Value Description

Setting	Value	Description
Password complexity checking	Selected or Cleared Default: Selected	Specifies whether the system enforces password complexity. Selected — Passwords must meet the password complexity restrictions. Cleared — Password complexity restrictions are not enforced. Passwords are still restricted by the value set for Password minimum length. Note: Passwords cannot contain any of the following characters: double quotation marks ( " ), pipes ( \| ), dollar sign ( $ ), square brackets ( [ ),( ] ) or spaces ( ), and cannot start with the at sign (@). When this parameter is selected, a password must meet all the following restrictions: The password must contain at least one character from each of the following categories — uppercase letters (A-Z), lowercase letters (a-z), base 10 digits (0-9), and special characters ( ~ ! @ # $ % ^ & * _ - + = ` \ ( ) { } [ ] : ; ' < > , . ? / ). The password must meet the length as specified for Password minimum length. The password cannot contain the whole Username, First Name, or Last Name of the user that the password is assigned to, in either uppercase or lowercase, if they are more than two characters in length. If any of the following characters ( . - _ # ! ` ~ @ ' ), or any spaces appear in the Username, First Name, or Last Name, these characters are treated as delimiters instead of consecutive characters. For example, the password for user ‘Jean-Paul’ cannot contain the strings ‘jean’ or ‘paul’ but can contain ‘pau’. The password cannot contain any of the password dictionary strings, in either uppercase or lowercase. For more information, see Password dictionary location.
Password minimum length	Numeric value Valid range: 1 – 63 Default: 8	Specifies the minimum length for passwords, in number of characters. Note: If Password complexity checking is selected, avoid setting this parameter to a value of 3 or less. Since password complexity restrictions require that passwords must contain at least one character from four different categories, passwords that are three or less characters in length will not be permitted.
Password days before expiry	Numeric value Valid range: 1 – 10000 Default: 30	Specifies the number of days until a password expires.
Password days before warning	Numeric value Valid range: 1 – 10000 Default: 5	Specifies when a password expiry warning is given. The value set in Password days before warning is the number of days before the value set in Password days before expiry. For example, if you set 30 to Password days before expiry, and 5 to Password days before warning, a password expiry warning is given on the twenty-fifth day (5 days before the value set in Password days before expiry).
Password force change after creating or resetting	Selected or Cleared Default: Selected	Specifies whether or not a password change is enforced. Selected — If a user logs on for the first time, or after a password is reset, the password must be changed. Cleared — Passwords do not have to be changed.
Password number of days before reusing	Numeric value Valid range: 0 – 3650 Default: 1	Specifies the number of days after a password is set or reset, until it can be reused.
Password number of changes before reuse	Numeric value Valid range: 0 – 1000 Default: 1	Specifies the number of password changes that must occur before a password can be reused. A password cannot be reused until both the number of days set in Password number of days before reusing and the number of changes set in Password number of changes before reuse have been exceeded.
Password failed attempts before lockout	Numeric value Valid range: 1-100 Default: 3	Specifies the number of times a user can enter an incorrect password before they are locked out of the system.
Account lock time	Numeric value Valid range: 0 – 1440 Default: 10	Specifies the time interval, in minutes, between when an account is locked (due to repeated failed password attempts, exceeding the number set in Password failed attempts before lockout), and when the account is unlocked. If account lock time is set to 0, the account is locked until the administrator resets the password.
Enable password reset	Selected or Cleared Default: Cleared	Specifies whether users can reset their passwords from the Longview Dashboard web Sign On dialog. Selected — Users can reset their passwords from the web Sign On dialog. Cleared — Users cannot reset their passwords from the web Sign On dialog. Note: For users to reset their passwords from the web Sign On dialog, they must have a unique email address as specified in their user settings. For more information, see the Longview Application Administrator Guide or the Longview Tax Implementer's Guide.
Password reset email address	Valid string Default: "lvWebAgent@longview.com	This parameter applies only if Enable password reset is selected. Specifies the email address that the password reset link is sent from when users reset their passwords from the web Sign On dialog. This parameter must be enclosed in double quotation marks.
Password reset email description	Valid string Default: "Longview Web Agent"	This parameter applies only if Enable password reset is selected. Specifies a description for the email address that the password reset link is sent from when users reset their passwords from the web Sign On dialog. This parameter must be enclosed in double quotation marks.
Password reset time limit	Numeric value Valid range: 0 – 1440 Default: 60	This parameter applies only if Enable password reset is selected. Specifies the time, in minutes, before the password reset link expires. The password reset link is provided when users reset their password from the web Sign On dialog.
Password dictionary location	Valid string	This parameter applies only if Password complexity checking is selected. Specifies the location where the dictionary files are stored. Dictionary files are text files that contain strings of characters that cannot be used in passwords if Password complexity checking is selected. Examples of strings commonly not allowed in passwords include abc, password, or your company name. If you do not specify a value for this parameter, passwords are not restricted by the strings in the dictionary files. This parameter must be enclosed in double quotation marks. For example, `"C:\Longview\CPM\DataServers\LVCPM\PasswordFiles"` The following rules apply to dictionary files: Strings must be at least three characters in length. Strings must be listed one per row in the text file. Password matches to dictionary files are not case-sensitive. For example, if the dictionary file contains Abc, the password 1aBCD is not permitted. Dictionary files adhere to the following naming convention: password_dictionary_FileName.txt Note: File extensions other than .txt can be used. For example, password_dictionary_LVWords.dct is a valid dictionary file name.
Third party authentication Note: This parameter is applicable only up to version 25.2	Selected or Cleared Default: Cleared	Specifies whether to enable third party authentication. Note: Users select Single Sign-On (Web) when signing on.
Third party HTTP variable Note: This parameter is applicable only up to version 25.2	Valid string Default: LONGVIEW_SSO_USER	This parameter applies only if Third party authentication is selected. Specifies the HTTP variable used for third party authentication.
SSO service url	Valid URL	Specifies the URL to the Longview SSO Web Service. The URL will either be setup for SAML or OpenID. For example: For SAML: "https://srvr1201sql01.domain.com/sso/saml" For OpenID: "https://srvr1201sql01.domain.com/sso/openid" Setting this parameter enables Longview to work with Federated SSO, ensuring secure and streamlined user authentication. For more information on setting up Longview SSO Service, see the Longview SSO Service Installation.

Password complexity checking

Selected or Cleared

Default: Selected

Specifies whether the system enforces password complexity.

Selected — Passwords must meet the password complexity restrictions.
Cleared — Password complexity restrictions are not enforced. Passwords are still restricted by the value set for Password minimum length.

Note: Passwords cannot contain any of the following characters: double quotation marks ( " ), pipes ( | ), dollar sign ( $ ), square brackets ( [ ),( ] ) or spaces ( ), and cannot start with the at sign (@).

When this parameter is selected, a password must meet all the following restrictions:

The password must contain at least one character from each of the following categories — uppercase letters (A-Z), lowercase letters (a-z), base 10 digits (0-9), and special characters ( ~ ! @ # $ % ^ & * _ - + = ` \ ( ) { } [ ] : ; ' < > , . ? / ).
The password must meet the length as specified for Password minimum length.
The password cannot contain the whole Username, First Name, or Last Name of the user that the password is assigned to, in either uppercase or lowercase, if they are more than two characters in length. If any of the following characters ( . - _ # ! ` ~ @ ' ), or any spaces appear in the Username, First Name, or Last Name, these characters are treated as delimiters instead of consecutive characters. For example, the password for user ‘Jean-Paul’ cannot contain the strings ‘jean’ or ‘paul’ but can contain ‘pau’.
The password cannot contain any of the password dictionary strings, in either uppercase or lowercase. For more information, see Password dictionary location.

Password minimum length

Numeric value

Valid range: 1 – 63

Default: 8

Specifies the minimum length for passwords, in number of characters.

Note: If Password complexity checking is selected, avoid setting this parameter to a value of 3 or less. Since password complexity restrictions require that passwords must contain at least one character from four different categories, passwords that are three or less characters in length will not be permitted.

Password days before expiry

Numeric value

Valid range: 1 – 10000

Default: 30

Specifies the number of days until a password expires.

Password days before warning

Numeric value

Valid range: 1 – 10000

Default: 5

Specifies when a password expiry warning is given. The value set in Password days before warning is the number of days before the value set in Password days before expiry.

For example, if you set 30 to Password days before expiry, and 5 to Password days before warning, a password expiry warning is given on the twenty-fifth day (5 days before the value set in Password days before expiry).

Password force change after creating or resetting

Selected or Cleared

Default: Selected

Specifies whether or not a password change is enforced.

Selected — If a user logs on for the first time, or after a password is reset, the password must be changed.
Cleared — Passwords do not have to be changed.

Password number of days before reusing

Numeric value

Valid range: 0 – 3650

Default: 1

Specifies the number of days after a password is set or reset, until it can be reused.

Password number of changes before reuse

Numeric value

Valid range: 0 – 1000

Default: 1

Specifies the number of password changes that must occur before a password can be reused.

A password cannot be reused until both the number of days set in Password number of days before reusing and the number of changes set in Password number of changes before reuse have been exceeded.

Password failed attempts before lockout

Numeric value

Valid range: 1-100

Default: 3

Specifies the number of times a user can enter an incorrect password before they are locked out of the system.

Account lock time

Numeric value

Valid range: 0 – 1440

Default: 10

Specifies the time interval, in minutes, between when an account is locked (due to repeated failed password attempts, exceeding the number set in Password failed attempts before lockout), and when the account is unlocked.

If account lock time is set to 0, the account is locked until the administrator resets the password.

Enable password reset

Selected or Cleared

Default: Cleared

Specifies whether users can reset their passwords from the Longview Dashboard web Sign On dialog.

Selected — Users can reset their passwords from the web Sign On dialog.
Cleared — Users cannot reset their passwords from the web Sign On dialog.

Note: For users to reset their passwords from the web Sign On dialog, they must have a unique email address as specified in their user settings. For more information, see the Longview Application Administrator Guide or the Longview Tax Implementer's Guide.

Password reset email address

Valid string

Default: "lvWebAgent@longview.com

This parameter applies only if Enable password reset is selected.

Specifies the email address that the password reset link is sent from when users reset their passwords from the web Sign On dialog. This parameter must be enclosed in double quotation marks.

Password reset email description

Valid string

Default: "Longview Web Agent"

This parameter applies only if Enable password reset is selected.

Specifies a description for the email address that the password reset link is sent from when users reset their passwords from the web Sign On dialog.

This parameter must be enclosed in double quotation marks.

Password reset time limit

Numeric value

Valid range: 0 – 1440

Default: 60

This parameter applies only if Enable password reset is selected.

Specifies the time, in minutes, before the password reset link expires. The password reset link is provided when users reset their password from the web Sign On dialog.

Password dictionary location

Valid string

This parameter applies only if Password complexity checking is selected.

Specifies the location where the dictionary files are stored. Dictionary files are text files that contain strings of characters that cannot be used in passwords if Password complexity checking is selected. Examples of strings commonly not allowed in passwords include abc, password, or your company name.

If you do not specify a value for this parameter, passwords are not restricted by the strings in the dictionary files.

This parameter must be enclosed in double quotation marks. For example, "C:\Longview\CPM\DataServers\LVCPM\PasswordFiles"

The following rules apply to dictionary files:

Strings must be at least three characters in length.
Strings must be listed one per row in the text file.
Password matches to dictionary files are not case-sensitive. For example, if the dictionary file contains Abc, the password 1aBCD is not permitted.

Dictionary files adhere to the following naming convention: password_dictionary_FileName.txt

Note: File extensions other than .txt can be used. For example, password_dictionary_LVWords.dct is a valid dictionary file name.

Third party authentication

Note: This parameter is applicable only up to version 25.2

Selected or Cleared

Default: Cleared

Specifies whether to enable third party authentication.

Note: Users select Single Sign-On (Web) when signing on.

Third party HTTP variable

Note: This parameter is applicable only up to version 25.2

Valid string

Default: LONGVIEW_SSO_USER

This parameter applies only if Third party authentication is selected.

Specifies the HTTP variable used for third party authentication.

SSO service url

Valid URL

Specifies the URL to the Longview SSO Web Service. The URL will either be setup for SAML or OpenID.

For example:

For SAML: "https://srvr1201sql01.domain.com/sso/saml"
For OpenID: "https://srvr1201sql01.domain.com/sso/openid"

Setting this parameter enables Longview to work with Federated SSO, ensuring secure and streamlined user authentication. For more information on setting up Longview SSO Service, see the Longview SSO Service Installation.

Web

The Web tab allows you to manage policies related to web access to the system.

Parameters on the Web tab

The following table lists the parameters that you can configure on the Web tab:

Setting	Value	Description
Web server	Valid string Maximum length 253 characters	Identifies the host name or address of the Web Server that the Longview Smart Client or Longview Tax should connect to.
Web agent protocol	IPC or TCP Default: IPC	Identifies the protocol used between the web server and the web agent: IPC — Shared memory TCP — TCP/IP
Web listener port	Numeric value Valid range: 1000 – 65535 Default: 28001	Identifies the port to use when the value of Web agent protocol is TCP. Usually, the value of this port is the value of the port used by the Longview_LID service - 1.
Client HTTP proxy server	Valid string	Identifies the secure listener port URL (HttpProxyServerListenerPortURL) for your HTTP Proxy Server. For example, "https://srvr1201sql01:8080/listenerportproxy/". For information on installing the HTTP Proxy Server, see Installing Longview HTTP Proxy Server.
Admin HTTP proxy server	Valid string	Identifies the secure admin port URL (HttpProxyServerAdminPortURL) for your HTTP Proxy Server. For example, "https://srvr1201sql01:8080/ adminportproxy/".
Web server bridge	Valid path Default: "/cgi-bin/LID/lvweb.cgi" where LID is the Longview Identifier for the system.	Identifies the path for the cgi or dll file serving as the communication bridge between the web server and Longview Data Server. This path must be relative to the document root configured for the web server and must be enclosed in double quotation marks. This value is used when resolving the WEBBRIDGE token in web content delivered to a user. Therefore, if it is not specified correctly, your web application will not work correctly.
Web HTTPS	Selected or Cleared Default: Cleared	Specifies whether Secure and HttpOnly attributes are added to the cookie header. When this parameter is selected, the Web Server uses Secure Sockets Layer (SSL). Selected — Secure and HttpOnly attributes are added to the cookie header. Cleared — Secure and HttpOnly attributes are not added to the cookie header. The Web cookie security and Web HTTPS parameters behave together in the following ways: If Web cookie security and Web HTTPS are both selected, the Web Server uses https (SSL), and cookies are used and have Secure and HttpOnly attributes set. If Web cookie security is selected and Web HTTPS is cleared, the Web Server uses http and cookies are used but do not have Secure and HttpOnly attributes set. If Web cookie security is cleared and Web HTTPS is selected, the Web Server uses https (SSL), and cookies are not used. If Web cookie security and Web HTTPS are both cleared, the Web Server uses http and cookies are not used.
Compress web content	Selected or Cleared Default: Selected	Specifies whether to use gzip standard compression whenever applicable.
Web IP security	Selected or Cleared Default: Cleared	Specifies whether to validate a web session ID against the user’s IP address for each web action. If you are using Longview HTTP Proxy Server, or any other proxy server, you must not select this parameter.
Web cookie security	Selected or Cleared Default: Selected	Specifies whether cookies are used to pass the web session ID and its key information. When this parameter is selected, the user’s browser must allow cookies.
Ticket security	Selected or Cleared Default: Cleared	Specifies whether ticket security is enabled. Ticket security refers to using a single-use ticket when launching Longview components via URL links. This parameter is not selected by default. Longview strongly recommends that it is enabled. If this parameter is selected, Web HTTPS must not be enabled. Note: Customers have experienced issues with cookie-based security and smart client components, due to changes made by Microsoft – while most of these issues appear to have been resolved, we are providing this alternative mechanism as an additional security layer and to protect against future cookie complications when launching Longview components via URL links. If this parameter is selected, if you are using out-of-box functionality, no other changes are required. However, if you have custom links on the Longview Homepage or legacy Dashboard which launch Longview components, then these links must be updated to work with the new feature. For more information, contact Longview Support Services.
Ticket security timeout	Numeric value Value range: 2 to 10 Default: 2	Specifies the number of minutes that a ticket is valid when launching Longview components via URL links.

Server Configuration

Refresh button

Search in Server Configuration

Application

Diagnostics

Events & data monitoring

Memory & pooling

Performance

Recalculation

System

System limits

Timeouts

User security

Web

Was this article helpful?