|Bookshelf Home | Contents | Index | PDF|
The size of the connection pool determines the number of available Siebel Analytics Server connections and the number of available threads for processing physical queries. A logical query may generate multiple physical queries, each of which could go to different connections.
Siebel Analytics Server creates a number of server threads up to the specified maximum using the parameter SERVER_THREAD_RANGE. All the threads available at any time are used to process queries from one or more sessions as needed.
NOTE: Usually, individual users have only one open request per session at the same time. Application programs and Siebel Analytics Web, however, typically have more than one open at the same time. In general, the default value of 500 should be sufficient for most environments, but this parameter should be tuned based on the application environment and the client tools in use.
For each Siebel Analytics Server request, SERVER_THREAD_RANGE specifies configuration information for thread allocation. The lower number in the range specifies the number of threads initially allocated, and the higher number in the range specifies the maximum number of threads to be allocated. The thread pool grows and shrinks in 5 thread increments until the upper or lower bound is reached. If there are fewer threads than sessions, sessions share the available number of threads on a first come-first served basis.
NOTE: For the parameters MAX_QUERY_PLAN_CACHE_ENTRIES, MAX_DRILLDOWN_INFO_CACHE_ENTRIES, and MAX_DRILLDOWN_QUERY_CACHE_ENTRIES, the default values are set to 1024 by default. These values should not be raised without consulting Siebel Support.
Controls the number of cached compiler query plans. The query plan cache is an internal performance feature that increases the speed of the query compilation process by caching plans for the most recently used queries.
Controls the number of cached Action Link information entries per repository. This increases the speed of computing Action Link information by caching the Action Link information for the most recently used queries.
The default value is 20. Because this parameter affects internal operations for localized versions of the Siebel Analytics software, it is recommended that you do not change this value unless instructed to do so.
Specifies the number of management threads to allocate for managing Siebel Analytics Server client/server communications. The default client/server communication method for Siebel Analytics Server is TCP/IP.
To support this method, a Port field has been added to the Enter Logon Information screen in Siebel Analytics ODBC Wizard. (Siebel Analytics D/COM support is limited; it is recommended that you use TCP/IP by default.)
Each client process consumes a management thread. If you plan to run multiple Analytics Web client instances or multiple third-party client instances, increase the number of management threads to match the number of client instances. When the number of running client instances exceeds the number of management threads allocated, worker threads are consumed.
NOTE: Do not disable the RPC Service. If you attempt to start Siebel Analytics Server on a machine where the RPC services or processes are not running, the application does not start and a log is not generated.
When using the Analytics ODBC Wizard to set up ODBC data sources for the Siebel Analytics Server, the port number specified in the Port field on the Enter Logon Information screen should match the port number specified here. If you change the port number in the configuration file, remember to reconfigure any affected ODBC data sources to use the new port number.
Controls the behavior for when a division by zero occurs. When set to YES, then a NULL value is returned. When set to NO, then the query is terminated and an appropriate error is returned to the user.
NOTE: When CLUSTER_PARTICIPANT is set to YES, this server needs to have a valid, configured NQClusterConfig.INI file in the Config subdirectory, located in the Siebel Analytics software installation directory. For more information, see NQClusterConfig.INI File Reference.
When the parameter CLUSTER_PARTICIPANT is set to YES, REPOSITORY_PUBLISHING_DIRECTORY specifies the location of the repository publishing directory shared by all Siebel Analytics Servers participating in the cluster. There is no default value for this parameter.
When a repository is updated in online mode, it is published to this location. All clustered servers examine this location upon startup for any repository changes. This needs to be a valid location visible to all servers in the cluster even if you anticipate that no repositories are updated in online mode.
The directory should reside on a shared file system. The directory needs to be a valid fully-qualified directory pathname, with double quotes ( " ) surrounding the pathname. Both UNC and mapped directories are supported. Do not specify a relative path name, or the Repository subdirectory (located in the Siebel Analytics software installation directory) as the location of the repository publishing directory.
This REPOSITORY_PUBLISHING_DIRECTORY parameter is required on every Siebel Analytics Server that is to participate in the cluster. The Siebel Analytics Server designated as the master server for online repository changes (from he MASTER_SERVER parameter in the NQClusterConfig.INI file) needs to have read and write access to this directory. The Siebel Analytics Servers in the cluster (from the SERVERS parameter in the NQClusterConfig.INI file) need to have read and write access to this directory as well. All entries need to reference the same actual directory, although different names can be specified to accommodate differences in drive mappings.
When the parameter CLUSTER_PARTICIPANT is set to YES, REQUIRE_PUBLISHING_DIRECTORY specifies that the repository publishing directory (from the parameter REPOSITORY_PUBLISHING_DIRECTORY) needs to be available in order for this Siebel Analytics Server to start up and join the cluster.
When set to YES, if the publishing directory is not available at startup or if an error is encountered while the server is reading any of the files in the directory, an error message is logged in the NQServer.log file and the server shuts down.
To allow this Siebel Analytics Server to start up and join the cluster even if the publishing directory is not available, set this value to NO. When set to NO, the server joins the cluster and a warning message is logged in the NQServer.log file. Any online repository updates is not reflected in the server's Repository directory (located in the Siebel Analytics software installation directory). This could result in request failures, wrong answers, and other problems. However, this could be useful in situations where online repository editing is done infrequently and the goal is to keep the cluster operational even if some servers have stale repositories.
When DISCONNECTED is set to YES, only Mobile Clients running on the same machine as the Mobile Siebel Analytics Server are able to connect to it. Any Mobile Client running on a different machine is unable to connect to the Mobile Analytics server.
Specifies whether the Siebel Analytics Server should be automatically restarted after a crash. Automatic restart is applies only to an Analytics Server platform; it does not apply to a clustered Analytics server environment, or to a Mobile Analytics server. The default is YES.
|Siebel Analytics Platform Installation and Configuration Guide|