Administration Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This chapter describes how to configure server settings for BEA Liquid Data for WebLogic. It includes the following sections:
In a standalone (single server) domain, server settings apply to a single instance of Liquid Data server. In a clustered domain, to all Managed servers in the domain. Server settings include the repository directory, threads for application views and Web Services data sources, the security mode, whether to cache results for stored queries, the swap files directory for stored queries, and the classpath for custom functions.
Note: To change Liquid Data server settings, you must log in to the Administration Console with a username that belongs to the LDAdmin
group.
You can set configuration options on the Liquid Data server that apply to all processing on the selected server for any type of data source. This section describes the fields in the Administration Console and provides a procedure for configuring Liquid Data server settings. It contains the following sections:
The following table describes the fields in the Liquid Data console server page.
Full or relative path to the root directory of the Liquid Data repository that contains the data sources configured for this Liquid Data server. For relative paths, the path is relative to the current domain directory. For more information, see Server Repository Location. In a clustered environment, all managed Liquid Data servers must mount (on Unix) or be mapped to (on Windows), the volume containing the directory specified here. If the specified directory does not exist, Liquid Data will create it automatically. |
|
Classpath for libraries used by custom functions that do not reside in the Use semicolons to separate paths. File pathnames or URLs can be used. For example:
For information on how to configure custom function descriptions, see Configuring Access to Custom Functions and Server Repository File System Hierarchy. |
|
Maximum number of threads in the Liquid Data server pool used to handle query requests for application view, web service, and custom function data sources. The default setting is 20. The minimum setting is 1. If the specified value is invalid, then the server will use the default value of 20. Note: The maximum threads value that you specify here does not affect the WebLogic Server server thread pool. The value specified here applies only to the thread pool created and used by the Liquid Data query engine for processing requests on application view, web service, or custom function data sources. |
|
Maximum number of threads allowed for a single query. Use this to limit the number of threads spawned by a single query. No matter what the settings for the Maximum Number of Threads Per Query, the actual number of threads used will not exceed the maximum number of threads specified in Maximum Threads. The default setting is 4. The minimum setting is 1. If the specified value is invalid, then the server will use the default value of 4. Note: The maximum threads value that you specify here does not affect the WebLogic Server server thread pool. The value specified here applies only to the thread pool created and used by the Liquid Data query engine for processing requests on application view and web service data sources. |
|
Enables or disables (default) the caching of query results for stored queries. For more information about caching, see Enabling the Results Cache. |
|
Path of location of swap files that Liquid Data uses to manage large amounts of intermediate results data returned from a stored or ad-hoc query. If the Large Results flag is selected for the query, then Liquid Data uses swap files to temporarily store intermediate results on disk. Default is If the specified directory does not exist, Liquid Data will create it automatically. Note: If you change this setting, you must reboot the Liquid Data server in order for the change to take effect. |
Perform the following to configure Liquid Data server settings:
Figure 5-2 Configuring Liquid Data Server Settings
LDAdmin
group, then fill in the fields described in Table 5-1.
![]() ![]() |
![]() |
![]() |