This describes the type of server. The server type can be DATASERVER or DATASERVERWEBSERVICE.

Specifies the name of the data server (Longview Identifier or LID).

Identifies the location in which the servers will be started, and in which the Longview Data Server Log (lv_dataserver.log) will be saved, for example:

"C:\Longview7\DataServers\Longview"

This path must be enclosed in double quotation marks.

Specifies whether the system uses Oracle Global Temporary temp tables instead of regular temp tables (for Oracle databases only).

Specifies the username of the DBO of the Data Server database.

For information on configuring your system for database OS authentication, see the Longview Installation Guide.

Specifies the password for the DBO of the Data Server database.

Identifies the Data Server host name.

Identifies the name of the server on which the database is hosted.

Identifies the port number used by the Listener.

Usually, the value of this port is the value of port used by the Longview_LID service + 1.

Specifies 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.

For more information, see “Web”.

Specifies the Grid Listener Port number.

Specify the port through which the Longview Data Server connects to the database. This parameter applies to PostgreSQL environments only.

Specify the name of the database for PostgreSQL environments. By default, this value is blank and must be updated to specify the target PostgreSQL database.

Specifies the name of the SMTP server.

Specifies the name for the grid service when Grid Processing Type is DATASYNAPSE.

For more information, see “Application”.

Enables asynchronous IO for your grid environment when the value of Writer Async IO is TRUE, and the value of Writer Memory is a positive integer.

For more information, see “Performance”.

Specifies 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 Smart Client.

Specifies the host name or address of the Web Server that the Longview Smart Client should connect to.

Specify the secure listener port URL (HttpProxyServerListenerPortURL) for your HTTP Proxy Server. For example, "https://srvr1201sql01:8080/listenerportproxy/". If you specify a value for this parameter, connections between Longview Application Framework, Longview Apps, and Longview Tax can use a secure HTTP proxy connection.

Specify the secure admin port URL (HttpProxyServerAdminPortURL) for your HTTP Proxy Server. For example, "https://srvr1201sql01:8080/ adminportproxy/".

Specify the name of a Windows local group to use to stop and start the Longview Servers. If the group name contains a space, it must be enclosed in double quotes.

Note: Local Admin Group will not work with a Windows default local group.

Specifies the alternate language to use in your system, using a two letter ISO language code.

Specifies the location of the documentation folder. This path must be enclosed in double quotation marks.

Specifies the location of the help files folder. This path must be enclosed in double quotation marks.

Identifies the location in which all temporary files are saved; for example: "C:\Longview\Dataservers\Longview\tmp".

The recalculation uses this folder to create files that are needed for calculations. Once the recalculation completes successfully, these files are deleted. This path must be enclosed in double quotation marks.

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 Longview Data Server software folder. The file must also exist in the software folder, if applicable.

Specifies the location of the application framework binaries used for data events and model/procedure links. This path must be enclosed in double quotation marks.

Specify the location where log files generated for Events are stored. If you do not specify a value for this parameter, the Events tool does not display the Log Files column, which provides users with links to open log files.

Specify the location where error files generated for Events are stored. If you do not specify a value for this parameter, the Events tool does not display the Error Files column, which provides users with links to open error files.

Specify the location where history files generated for Events are stored. If you do not specify a value for this parameter, the Events tool does not display the HistoryFiles column, which provides users with links to open history files.

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.

Note: The location must be a path local to the server machine; do not specify a network drive.

For more information, see “Caching data in memory”.

This parameter applies only when Use Metadata Audit Trail is selected.

Specify the location where log files generated for Metadata Audit Reset operations are stored.

If you do not specify a value for this parameter, a log file will not be generated when a Metadata Audit Reset operation is performed.

This parameter specifies the location of where custom code files are stored. For example: web, templates and applications)

This path cannot be set to the dataservers working directory or a default folder within.

Note: If this parameter is not set it will continue to use the folders web, templates and applications in the severs working directory.

Specifies the time-out 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.

Specify 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.

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

Determines where, or if, documentation should be deployed.

• CLIENT—Documentation is deployed locally.
• EXTERNAL—Documentation is deployed to the location as specified in Documentation Folder.
• OFF—Documentation is not deployed.

Determines where, or if, help files should be deployed.

• CLIENT—Help files are deployed locally.
• EXTERNAL—Help files are deployed to the location as specified in Helpfile Folder.
• OFF—Help files are not deployed.

Specifies whether N-Dimensional Distribution is used in this system. For more information, see “N-Dimensional Distribution”.

Specifies whether Period Activity Calculation (PAC) logic is used in this system. For more information, see “Period Activity Calculation”.

Specifies whether Retained Earnings Calculation (REC) logic is used in this system. For more information, see “Retained Earnings Calculation”.

Specifies whether data translation is used in this system. For more information, see “Translation”.

Specifies whether accounting year-to-date (YTD) logic is used in this system. For more information, see “Year-to-date”.

Specifies whether the Elimination Server is used in this system. If Intercompany Eliminations (Elim) is selected, Journal Entries must also be selected.

Specifies whether the Journal Entry Server is used in this system.

Specifies whether to use server model rules.

• Selected—Server model rules are used.
• Cleared—Server model rules are not used.

Specifies whether to use this type of server rule.

• Selected—Query rules are used.

Specifies whether to use this type of server rule.

• 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.)

Specifies whether to use this type of server rule.

• Selected—Validation rules are used.
• Cleared—Validation rules are not used.

Specifies whether translation rounding is used in the system. If Round Foreign Exchange Results is selected, Foreign Exchange (TRN) must also be selected.

Specifies whether grid processing should be used when running restatements.

Specifies whether to allow users to attach files to a cell in web input templates and Data Grids.

Specifies whether to enable caching data in memory if the MemoryCacheSizes.txt 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.

Specifies whether workflow should be used.

Specifies whether or not users receive emails notifying them of JE activity.

• Selected—Users receive notification emails.
• Cleared—Users do not receive notification emails.

If Use JE Workflow is selected, Journal Entries must also be 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 difference in the deltas is used for math processing.
• Cleared—The system zeroes out the area to which you are submitting data, and then submits the new value.

Specifies the rollup rule method, in conjunction with the Rollup Rules parameter.

• Selected—Only the DataArea specified by a rollup rule rolls up. All other areas of the database do not roll up to their parents.
• Cleared—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.

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.

Specifies whether or not the use of 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.

Specify 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.

Specify whether to track and store batch and event activity for a given data area.

If you select this option, you must specify at least one dimension for Data Area Monitoring Dimensions. Optionally, you can also specify a dimension for Report Status Dimension.

Specify 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’s Guide.

Specifies how system responds to a data submission error.

• Selected—The user does not see an error message. Errors are reported to the Longview Data Server Log (lv_dataserver.log) only.
• Cleared—The user sees a server error message when connecting.

Specifies whether the parent data table is partitioned.

Specifies whether event rules are used in the system.

Specifies the size of the queue to be used by the Model Server in processing event messages.

Specify 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).

The default value for this parameter is 0:05.

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.

This parameter applies only if Data Event Sequencing is not used.

Specifies 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). The default value is 30.

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.

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.

This parameter applies only if Data Area Monitoring is selected. Specify the dimensions for which to enable data area monitoring. Separate multiple dimensions with a comma. For example, ACCOUNTS, TIMEPERIODS, ENTITIES.

This parameter applies only if Data Area Monitoring is selected. Specify the dimension for which to enable report 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, report status is not tracked.

Specifies the protocol used between the web server and the web agent:

• IPC—Shared memory
• TCP—TCP/IP

Specifies whether to use gzip standard compression whenever applicable.

Specifies whether to enable third party authentication.

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

Specifies the HTTP variable used for third party authentication (valid only if Third Party Authentication is selected).

Specifies the path that the web server will use to find the cgi or dll file serving as the communication bridge between the web server and the data server. This path must be relative to the document root configured for the web server. 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. This path must be enclosed in double quotation marks.

Specifies the default sign off page when the user connects through the web interface. Should be set to a URL of the page to display. Normally this is set to a custom sign off page but any valid URL address will be accepted.

If this parameter does not start with http://, the Sign on dialog opens again.

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.

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.

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.

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.

This parameter applies only if Password Complexity Checking is selected.

Specify 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.

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.

Specify 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.

Regardless of the setting for Password Complexity Checking, passwords cannot contain any of the following characters—double quotation marks ( " ), pipes ( | ), or spaces.

If Password Complexity Checking is selected, a 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 nonalphanumeric characters ( ~ ! @ # $ % ^ & * _ - + = ` \ ( ) { } [ ] : ; ' < > , . ? / ).
• meet the length as specified for Password Minimum Length.
• not 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’.
• not contain any of the password dictionary strings, in either uppercase or lowercase. For more information, see Password Dictionary Location.

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.

Specifies the number of days until a password expires.

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 Password Days Before Expiry is set to 30, and Password Days Before Warning is set to 5, a password expiry warning is given on the twenty-fifth day (5 days before the value set in Password Days Before Expiry).

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.

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

A password cannot be reused until both the number of days set in Password Number of Days BeforeReusing and the number of changes set in Password Number of Changes Before Reuse have been exceeded.

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.

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

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.

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 Administrator’s Guide.

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.

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.

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.

Specify whether Ticket Security is enabled. Ticket Security refers to using a single-use ticket when launching Longview components via URL links.

• Selected - Use this value to enable Ticket Security
• Cleared - Use this value to disable Ticket Security

Note: Some 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.

The default value for this parameter is FALSE. Longview strongly recommends that TICKET_SECURITY is enabled.

Note: If this parameter is set to TRUE: •f 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.

Specify the number of minutes that a ticket is valid when launching Longview components via URL links. This number can range from 2 to 10.

The default value for this parameter is 2.

Specifies whether to validate a web session ID against the user’s IP address for each web action.

• Selected—Web IP Security is enabled.
• Cleared—Web IP Security is not enabled.

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.

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.

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.

Specifies the maximum number of data locks.

Specifies the maximum number of math iterations allowed.

Specifies the maximum number of schedule locks.

Specifies the maximum number of schedules allowed.

Specifies the maximum number of home page locks.

Specifies the maximum number of web panel locks.

Specifies the maximum number of sessions allowed at one time.

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.

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.

Specifies the maximum number of grid cursors.

Specifies the maximum number of grid output threads.

Specifies the maximum file size, in megabytes, for file attachments in web input templates. This setting applies only if FileAttachments is enabled on the Application page.

If this setting is greater than the maxAllowedContentLength attribute in your IIS web.config file, the IIS setting is used.

Specify 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.

Specifies the fetch size for datalink queries.

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

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

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

• Numeric value—Specify 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.

Specify 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).

Specify 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.

This option applies only to Oracle systems. If you select this option, 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 option, make sure the DBO can gather statistics on its own schema.

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.

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.

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.

Specifies the amount of RAM reserved in the KSA for data cache files. Increase this value to allocate more memory to this cache. The size of this cache affects performance of queries when using data cache files.

Specifies the amount of RAM 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.

Specifies the amount of RAM reserved in the KSA for N-Dimensional Distribution (NDD). This parameter depends on the number of symbols configured for NDD.

Specifies the maximum amount of RAM 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.

Specifies the amount of RAM reserved in the KSA for translation logic. This parameter depends on the number of different translation rates used, and is only used if Foreign Exchange (TRN) is selected on the Application page.

For more information, see “Application”.

Specifies the amount of RAM 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 page.

For more information, see “Application”.

Specifies the amount of RAM reserved for the writers. This is only used on Windows platforms, and only if Writer Async IO is set to TRUE on the General page.

For more information, see “General”.

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.

Specifies the number of web agent workers to spawn.

Specifies the number of workers in the journal entry (JE) pool. If the journal entry portion of a recalculation or restatement runs too slowly, increase this value.

Specifies the number of Math Servers required to handle math logic.

The recalculation or restatement attempts to take full advantage of all available Math Servers in the pool. 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.

Specifies the number of Submission Servers required to handle data submissions.

Specifies the number of Writer Servers required to handle data written to the database. 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.

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.

Specify the maximum number of active data events to allow in an event sequence iteration.

Enables web trace to assist in debugging web connection problems.

Specifies the path to where the trace file is stored, which must be on the web server. The trace file contains data that may help in debugging web connection problems.

For more information, contact Longview Support Services.

This field is valid only when Enable Web Trace is selected.

Specify the full path name of the output trace file. This path must be enclosed in double quotation marks.

Specify whether to include diagnostic service tracking information in the Longview Data Server Log (lv_dataserver.log).

These statistics are included for agents, web agents, and locking, management, and security servers.

Specify whether to include diagnostic service detail information in the Longview Data Server Log (lv_dataserver.log).

This includes process timing and memory usage information.

Specify whether to track and log service activity information. When this setting is selected, the system generates a separate .csv log file, per agent process, that contains diagnostic service tracking information.

Specify whether to include query statistic information in the Longview Data Server Log (lv_dataserver.log).

Specify whether to log query information. When this setting is selected, the system generates a separate .csv log file, per agent process, containing detailed information about all queries.

Specify whether to track and log RDBMS information. When this setting is selected, the system generates a separate .csv log file, per agent process, that contains RDBMS activity information.