|Oracle® Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide
Part Number E23614-02
This appendix describes updating the configuration file(s) changes the Oracle DataLens Server configuration and requires a server restart before the change will take effect.
Stop and re-start the server using the platform specific commands. During the Oracle DataLens Server downtime, active clients may fail to complete the current request.
You should not change any other properties in this file without first consulting with Oracle Consulting Services. Configuration files residing within the Oracle DataLens Server installation define the Oracle DataLens Server configuration. The Java Property file and XML document configuration file formats are used.
This file is a Java property file. Unlike typical Java properties files, where properties are identified by a simple "key", data lens configuration files utilize a "path" based property specification. The path is a dot-separated list of names identifying the object. Lower case names in the path correspond to the application logical object structure, and the leaf element (starting with a capital letter) specifies the property name. The property value is separated from the property identifier by an equal sign.
For example, the following property file fragment may be used to configure the Administration Web Pages Statistics display:
# Any Production or Administration Server can send statistics if this flag is # turned on. The Language server will not send statistics. Server.send.statistics=true
\config\server.cfg defines the basic Servlet executive behavior as defined by data lens. Under normal circumstances, this file should not be changed. In fact, most of the parameters here can be modified from the Oracle DataLens Web Server Administration pages.
Some useful options for the
server.cfg file are displayed in the following table.
||Any Oracle DataLens Server will send statistics if this flag is turned on.|
||Shows the number of failures that will be accumulated by project. 0 or no entry means do not accumulate at all.|
||Lifetime of login information stored in local cookies (default is 1 hour).|
||Background color to use for the charts and chart keys.|
||Set the number of parameterized domain instances that will be loaded into memory. A single domain with two instances might want to set instances to 3. 1 for the first parameterized domain, another for the second, and a third for both in memory.|
||Set the number of lines of data to keep in memory between the steps of a DSA. If the number of lines of data is greater than this parameter, then the data is written to disk between each step of the DSA, which hinders performance.|
SvrPaths.xml file defines the following parameters used by EDQP:
This environmental variable defines the location of the Oracle DataLens Server home directory. The following are the default directories:
On Linux and Unix -
On Windows -
This is 1 for Oracle DataLens Administration Servers and 2+ for Oracle DataLens Transform Servers. The value must be 0 when first created for Transform Servers; it is automatically updated by EDQP.
Uses the default,
$OPDQ_HOME/local, if not defined.
Defines the repository directory and is only needed on an Oracle DataLens Administration Server.
Uses the default,
reposDir/internal, if not defined.
Defines the directory that must be shared between the Oracle DataLens Administration Server and all Transform Servers.
Uses the default, sharedDir, if not defined.
Defines the number of seconds to check for changes to the
--> <SvrPaths> <serverID>1</serverID> <localDir></localDir> <reposDir>C:\datalens\server\data\repository</reposDir> <derbyDir></derbyDir> <sharedDir>C:\datalens\server\data\shared</sharedDir> <devDir></devDir> <qaDir></qaDir> <prodDir></prodDir> <logWatchSecs>0</logWatchSecs> </SvrPaths>