Configuration Properties

How to Set Configuration Properties

On the Plug-ins tab in SAS Management Console, navigate to Application ManagementConfiguration ManagerSAS Application InfrastructureVisual Analytics. Expand nodes as needed, right-click on the appropriate node, and select Properties.
- Set suite-level properties on the Visual Analytics node.
- Set explorer properties on the Visual Analytics Explorer node.
- Set alerts properties on the Visual Analytics Hyperlink Service node.
- Set SAS Mobile BI properties on the Visual Analytics Transport Service node.
- Set web viewer properties on the Visual Analytics Viewer node.
Note: For conciseness, version numbers are omitted from the instructions and figure in this topic.
On the Advanced tab of the appropriate Properties dialog box, add or set values.

To make changes take effect, restart the SAS Web Application Server. One approach is to restart all instances from your equivalent of SAS-configuration-directory/Web/Scripts/AppServer/.

UNIX	`appsrvconfig.sh restart`
Windows	`appsrvconfig.cmd restart`

For details and alternatives, see Understanding SAS Web Application Server Management and Using Configuration Manager in the SAS Intelligence Platform: Middle-Tier Administration Guide.

Suite-Level Properties

Tip

Use the Visual Analytics node (except where otherwise specified).

App.AllowGuest

enables or disables guest access. Valid values are true and false. See Supporting Guest Access.

Note: In new deployments, this property is set on the Visual Analytics Transport Service node and the Visual Analytics Viewer node, not at the suite level.

Tip

To enable or disable guest access for the home page, set this property on the Application Management

Configuration Manager

SAS Application Infrastructure

Visual Analytics Hub node.

las.caching.key.lifetime

sets the duration of time (in seconds) for which a LASR security key is cached in the middle tier. The default is 180 seconds (3 minutes). Do not set a custom value unless you are directed to do so by SAS Technical Support.

las.caching.permission.lifetime

sets the duration of time (in seconds) for which permission information is cached by the LASR authorization service. The default is 900 seconds (15 minutes). Do not set a custom value unless you are directed to do so by SAS Technical Support.

las.caching.user.lifetime

sets the duration of time (in seconds) for which user information is cached by the LASR authorization service. The default is -1 (the cache does not have a time-based expiration period). With the default setting, user objects remain in the cache until the requesting user’s session ends. Do not set a custom value unless you are directed to do so by SAS Technical Support.

lasrmgmt.server.monitor.refresh

sets the refresh interval (in seconds) for the LASR management service’s information cache. This setting affects timing on the LASR Servers and LASR Tables tabs. The default is 60. The default value provides a trade-off (among responsiveness, consumption of system resources, and currency of information) that is appropriate for most deployments.

Note: If you set this property to 0, no caching of LASR management service information occurs. When the cache is disabled, changes to a server’s tables limit take effect immediately, and information is retrieved on demand for each request. Response time for an information request is increased.

va.AuditingEnabled

specifies whether applications write audit records. Valid values are true and false. The default is false.

CAUTION:

Audit data can consume significant amounts of disk space and processing capacity.

If you enable auditing, it is essential that you manage the sizes of tables that contain audit data. See How to Safely Enable Auditing.

va.baseSchedulingFolder

specifies the name of the parent folder for jobs and flows that are used in report distribution. The default is /System/Applications/SAS Visual Analytics/ScheduledDistribution. See Supporting Report Distribution.

Note: To schedule a report, users must have WriteMemberMetadata access to the specified base folder.

va.ComparisonEpsilon

specifies a small number to be used to account for floating-point rounding error in the following numeric comparisons: equals, not equals, less than, greater than, less than or equals, greater than or equals. Valid values are doubles. The default is 1e-12. In the unusual circumstance in which users find that some values are being compared as equal when they should not be (or vice versa), consider changing this value. The epsilon comparison is relative to the size of the numbers that are being compared (it is not absolute). When the following expression is true, a and b are considered to be equal:

ABS(a-b) <= epsilon * MAX(ABS(a), ABS(b))

va.dataServer.PublicLibrary

identifies the standard library for your configured data server. If you change the name of the library, you must also update this property.

va.defaultLASRLibrary

identifies the predefined LASR library for the Visual Analytics LASR server. This property is no longer in use.

va.defaultPublicFolder

identifies the standard metadata location for LASR tables that are generated by data import and load activities (for example,

/Shared Data/SAS
                                    Visual Analytics/Public/LASR

). If you change the name of the referenced folder, you must also update this property.

va.defaultWorkspaceServer

identifies the suite-level default SAS Application Server. If you change the name of the referenced server (for example, SASApp), you must also update this property. See Which Server is Used?.

va.distribution.email.aggregate.attachments.mb

sets a maximum combined size (in megabytes) for all attachments in a report distribution email. If this property is not defined, the default value of 20 is in effect. If a value of -1 is specified for this property, no limit is in effect. See Supporting Report Distribution.

va.distribution.email.attachment.mb

sets a maximum size (in megabytes) for an individual attachment in a report distribution email. Initially, a value of -1 is specified, so no limit is in effect. If this property is not defined, the default value ( 20) is in effect. See Supporting Report Distribution.

va.extractRelationshipData

enables periodic extraction of data about relationships among SAS Visual Analytics objects. Relationship data is extracted from the relationship service to the autoload data directory (drop zone) for administrative reporting. Valid values are true and false. The default is false. See Reports for Administrators.

va.GeoMapMaxResolution

for an alternate OpenStreetMap server (specified in the property va.GeoMapServerUrl), sets the resolution value for the farthest out zoom level in each geo map. The default is 156543.0339.

va.GeoMapNumResolutions

for an alternate OpenStreetMap server (specified in the property va.GeoMapServerUrl), sets the number of levels in each geo map. The default is 18.

Tip

Each level corresponds to an increment by which a user can zoom in. Adding a level doubles the resolution and quadruples the number of tiles. In general, a value higher than 23 is not practical.

va.GeoMapServerUrl

specifies a comma-delimited list of URL addresses that reference alternate OpenStreetMap servers (for example,

http://serverA.org, http://serverB.org,
                                    http://serverC.org

). To use the OpenStreetMap servers that SAS hosts, leave the value for this property blank. See OpenStreetMap Server.

va.IgnoreMissingInCountDistinct

determines whether missing values are ignored in counts when the Distinct operator is used. Valid values are true and false. The default is false (missing values are included in distinct counts).

Note: This property affects count behavior in the designer and viewers, but not in the explorer.

va.LASRMonitor.HostPort

specifies the machine name and port for the process that monitors a distributed SAS LASR Analytic Server. The value is in the format host:port (for example, machine.company.com:9971).

va.lastActionLogPath

specifies the location of last action logs. See Get Server Information and Get Table Information. The standard location is within the SAS configuration directory at /Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/Monitoring/Logs. In a multi-machine deployment, the specified location exists on the middle-tier host.

va.MaxTiesToIncludeOnRank

sets the maximum number of identically ranked values that can be returned in a rank operation. Valid values are integers. The default is 100.

va.monitoringPath

specifies the location for certain process ID files and logs. The standard location is within the SAS configuration directory at /Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/Monitoring. The specified location must exist on a workspace server host.

Note: To specify a custom directory for monitoring artifacts for a particular SAS LASR Analytic Server, set an extended attribute for that server. See VA.MonitoringPath.

va.publicLASRLibrary

identifies the general purpose library for data import and load activities (for example,

Visual
                                    Analytics Public LASR

). If you change the name of the referenced library, you must also update this property.

va.publicLASRServer

identifies the server that is associated with the va.publicLASRLibrary (for example,

Public
                                    LASR Analytic Server

va.SASGeomapCommunicationProtocol

sets the protocol for connections between SAS Visual Analytics and the OpenStreetMap servers that SAS hosts. Valid values are http and https.

va.SASGeomapEsriURL

references a supported Esri server. The value must be a URL that specifies a protocol, the server’s host name, and the REST endpoint of the server. See Esri Server.

va.SelfServe.MaxUploadSizeInMegabytes

sets the maximum file size (in megabytes) that a user can import. This property affects importing local files in the data builder, the explorer, and the designer. The default, 4096, corresponds to browser-based constraints. To further constrain import activities, set a lower value for this property. You cannot use this property to circumvent browser-based constraints.

va.SelfService.ImportGoogleRowLimit

sets a maximum number of rows for an import from Google Analytics. The default is 100000.

va.SelfService.ImportRowsHardCap

sets a maximum number of rows for a self-service import action. If this value is exceeded, no data is imported. No initial value is set (initially, no limit is imposed).

Note: Enforcing a threshold requires a query to the data provider for each import action, so setting a value for this property can negatively impact performance.

va.SelfService.ImportRowsSoftCap

sets the number of rows that triggers a warning message for a user who is performing a self-service import action. The message indicates that the import action might take a long time. No initial value is set (initially, no limit is imposed).

Note: Enforcing a threshold requires a query to the data provider for each import action, so setting a value for this property can negatively impact performance.

va.supportSharedThumbnails

determines whether the designer and explorer generate thumbnails (specific preview images). Valid values are true and false. The default is false (specific preview images are not generated).

Note: Generated thumbnails are displayed only if this property is also set to true on the Visual Analytics Hub software component. See Home Page: Configuration Properties.

Alerts Properties

Tip

Use the Visual Analytics Services

Visual Analytics Hyperlink Service node.

va.Alert.DefaultEvaluationIntervalMilliseconds

specifies the evaluation interval (how frequently the system makes a determination about whether the alert’s conditions have been met). The default is 600000 milliseconds (10 minutes).

Note: This property affects only alerts that do not use a custom interval. In the designer’s Edit Alert window, the Use the system default setting causes the value for this property to be used.

Note: Long intervals increase the risk of a missed incident (where the alert’s conditions are met intermittently between one evaluation and the next). Short intervals consume more resources and can negatively impact the performance of the entire SAS Visual Analytics suite of applications.

va.Alert.DefaultMaxEvaluationTimeMilliseconds

specifies how long an individual evaluation can run before it terminates and restarts. The default is 1800000 milliseconds (30 minutes).

va.Alert.EvaluationCycleMilliseconds

specifies how frequently the system verifies that alerts are running. The default is 30000 milliseconds (30 seconds). If a large number of alerts are registered, consider increasing the value to reduce the use of resources.

va.Alert.Eventgen.disabled

specifies whether alerts generate notifications. The default is false. To disable notifications, set this property to true.

va.Alert.SMS.showServerName

specifies whether to append Server: server-name to the end of an SMS text message that is generated by an alert. The default is true. If the server name is not useful in your environment, or if you want to reduce the possibility of message truncation, set this property to false.

va.AlertThreadPool.CoreSize

specifies the number of threads that are available in normal circumstances (for concurrent evaluation of alerts). The default is 3.

va.AlertThreadPool.IdleTimeoutSeconds

specifies how long excess threads can be idle before they are terminated. The purpose of terminating idle excess threads is to reduce the number of threads to the specified CoreSize. The default is 1800 seconds (30 minutes).

Note: This property is applicable only if the MaxSize is greater than the core size.

va.AlertThreadPool.MaxSize

specifies the maximum number of threads that can be used (for concurrent evaluation of alerts). If the load is heavy, additional threads are temporarily added to the CoreSize (up to the value that is set for this property). The default is 3.

va.AlertThreadPool.QueueSize

specifies the maximum number of tasks that can be queued. The default is 100000.

Explorer Properties

Tip

Use the Visual Analytics Explorer node.

vae.DecisionTreeTimeout

affects how long (in seconds) the explorer waits for a response after the explorer makes a decision tree request. The default is 300.

vae.PageRowCount

limits the amount of data that can be returned for a table visualization. If table sorting is enabled, the vae.PageRowCount limit is applicable only if its value exceeds the value that is specified for the vae.SortResultLimit property. The default is 10000.

Note: For example, if the value is 10000, then 10000 rows of data are returned to the client. If the user scrolls through the data, and passes the row that is numbered 10001, the client prompts the SAS LASR Analytic Server for the next 10000 rows.

vae.PathingPathLengthLimit

sets the server-side maximum path length for a Sankey diagram. The value specifies the maximum number of events (nodes) in a single path. If the longest path length equals or exceeds the specified value, the explorer displays a message indicating that the Sankey diagram excludes paths longer than the specified value. If this property is not defined, the default value ( 2000) is in effect.

Note: Client-side controls in the explorer interface provide additional, more stringent limits (to facilitate quick display of Sankey diagrams).

Note: Each path in a Sankey diagram has a limit of 32,767 characters for the event values. Depending on the width of an event, the effective path length limit might be less than the value that you specify for vae.PathingPathLengthLimit. A numeric value uses a width of 40 for this calculation.

vae.PathingTopKLimit

sets the server-side maximum number of paths that are selected by path ranking in a Sankey diagram. If this property is not defined, the default value ( 1000) is in effect.

vae.PathingTransactionIdsLimit

sets the server-side maximum number of unique values for the transaction identifier in a Sankey diagram. If this property is not defined, the default value ( 10000) is in effect.

vae.TableSortingEnabled

specifies whether users in the explorer can click on a column heading to sort the items. Valid values are true and false. The default is true.

Transport Service Properties

Note: For the most current and comprehensive information about transport service properties, see Configuration Properties: SAS Mobile BI in SAS Intelligence Platform: Middle-Tier Administration Guide. As a convenience, some information about transport service properties is provided here.

Tip

Some transport service properties affect multiple components, such as the modern web viewer and SAS Mobile BI.

Tip

Use the Visual Analytics Services

Visual Analytics Transport Service node.

Printing.Timeout

sets a maximum wait time (in milliseconds) that affects printing reports from applications such as the designer and the viewer. The default is 900000 milliseconds (15 minutes). To disable this property, set its value to 0.

Note: This setting does not affect the first phase of a print request, which generates a report package. This setting affects only the second phase of a print request, which uses a stored process call to execute the print routine.

viewerservices.data.default.interactive.drill.depth

determines how much data is sent to SAS Mobile BI for offline drilling. This property is applicable to visualizations that reference a hierarchy. The default is 3 (users can drill down three levels). If certain reports require users to have the ability to drill down more than three levels into a hierarchy, modify the value.

viewerservices.company.banner.logoUrl

this property is not currently supported.

viewerservices.company.banner.message

this property is not currently supported.

viewerservices.company.banner.title

this property is not currently supported.

viewerservices.default.max.cells.produced

sets the maximum number of data cells that can be delivered to SAS Mobile BI for a single data query. The default is 250000 data cells, which is sufficient for most environments and does not cause the web application server to crash. In very rare scenarios, you might need to modify the value.

Note: If the number of data cells in a query exceeds the value specified for this property, the data that is returned to SAS Mobile BI is truncated. Data in the displayed report is not complete.

viewerservices.enable.whitelist.support

controls which approach is used to manage access to SAS Mobile BI. Valid values are:

false	causes the blacklist to be enforced and the whitelist to be ignored. With this setting, all mobile devices can use SAS Mobile BI except for those devices that are on the blacklist. This is the default.
true	causes the whitelist to be enforced and the blacklist to be ignored. With this setting, only mobile devices that are on the whitelist can use SAS Mobile BI.

CAUTION:

Enabling the whitelist can disrupt existing users.

Make sure that all valid mobile devices are on the whitelist before you make the change.

Tip

As an alternative to setting this property explicitly, you can set it from within the administrator. See Change How Devices Are Managed.

viewerservices.image.default.max.bytes

sets the maximum size of images (PNG, BMP, JPEG, or GIF) that can be delivered to a mobile device. Larger images are resized on the server side before delivery. The default is 307200 (300 KB), which is sufficient for most environments. In very rare scenarios when you want to change this constraint, consider modifying the value. To entirely disable resizing of images in the middle tier, set the value to 0. However, to ensure faster download times and smaller memory footprints on the mobile device, do not increase the value of this property or set the value to 0.

Note: Users can customize image resizing on their devices by setting the Scale type option (under Insert

Other

Image). If the option is set to None, the user’s device is exempt from middle-tier resizing.

viewerservices.lasr.socketTimeout.milliseconds.interactions

sets the maximum wait time for when SAS Mobile BI attempts to contact SAS LASR Analytic Server. This property is applicable to live requests from a mobile device for tasks such as filtering, brushing, and drilling. The default is 30000 milliseconds (30 seconds), which is sufficient for most environments. If sessions between SAS Mobile BI and SAS LASR Analytic Server are timing out, consider modifying the value.

viewerservices.lasr.socketTimeout.milliseconds.subscribe

sets the maximum wait time for a response to a query in a subscribed report when SAS Mobile BI contacts the SAS LASR Analytic Server. The default is 300000 milliseconds (5 minutes), which is sufficient for most environments. If the queries within some reports take an excessive amount of time for completion, consider modifying the value.

viewerservices.offline.limit.days

specifies how long downloaded mobile report data remains available to a user who is not signed in to SAS Mobile BI. A user who is offline for the specified number of days must sign in before accessing any mobile report data. The default is 15. This property affects only those users who have the Limit Duration of Offline Access capability.

viewerservices.passcode.attempts

limits the number of sequential failed attempts to enter a passcode for SAS Mobile BI. The default is 5. If a user reaches the limit, the user is locked out of the app for 15 minutes. After the lockout interval, the user can again attempt to enter his or her passcode. If the user reaches the limit again, all custom content (data, reports, settings, and connection information) is removed from the mobile device.

Note: This property is applicable to only those users who are subject to the capability Require Passcode On Mobile Devices.

viewerservices.passcode.timeout

specifies, in minutes, how frequently a user must re-enter his or her passcode in SAS Mobile BI. The default is 15.

viewerservices.validate.schema.create

enables XML schema validation when reports are rendered in SAS Mobile BI. When this property is set to true, all actions that apply to the creation of reports are captured in the transport log. The default is false. Set this property only if SAS Technical Support instructs you to do so.

viewerservices.validate.schema.read

enables XML schema validation when reports are rendered in SAS Mobile BI. When this property is set to true, all actions that apply to opening and viewing reports are captured in the transport log. The default is false. Set this property only if SAS Technical Support instructs you to do so.

viewerservices.validate.schema.write

enables XML schema validation when reports are rendered in SAS Mobile BI. When this property is set to true, all actions that apply to the writing of reports are captured in the transport log. See Adjusting the Logging Configuration.The default is false. Set this property only if SAS Technical Support instructs you to do so.

Web Viewer Properties

Tip

Use the Visual Analytics Viewer node.

vav.ui.mode

enables an administrator to force the use of a particular presentation mode for the web viewer.

(unspecified)	If the vav.ui.mode property is not specified, the modern presentation mode is used, unless a user selects Classic (in his or her Default Appearance setting for the web viewer) or uses a web browser that does not support the modern presentation mode (for example, Microsoft Internet Explorer 9).
classic	Forces the use of the Flash presentation mode.
modern	Forces the use of the HTML5 presentation mode, unless your web browser does not support that mode.

Note: The modern presentation mode does not support right-to-left (RTL) languages.

Tip

To force the use of a particular presentation mode for the home page, set that application’s presentation mode property. See Home Page: Configuration Properties.

Configuration Properties

How to Set Configuration Properties

Suite-Level Properties

Alerts Properties

Explorer Properties

Transport Service Properties

Web Viewer Properties

See Also