This chapter contains the following sections:
The desktopconfig.properties file defines server-specific parameters that the Desktop reads during initialization. Any changes to this file require a server restart in order to go into effect. By default, this file is in the /var/opt/SUNWportal/portals/<portal_id>/config directory.
You cannot customize the parameters, which are marked as Internal. So, you can only configure the debug level and the base directory for additional classes. The parameters available in the desktopconfig.properties file and their description are:
Default desktop type used by the ErrorProvider when DesktopAppContext is available but DesktopContext is not available.
Prefix used for all desktop cookies.
Value of this cookie is <portal_id>.<instance_id>. If Portal Server and Access Manager are running on separate nodes and both of them are available at load-balancer URLs, such cookie will not set by the Portal Server. Although Portal Server works with some performance hit in terms of resource consumption and response times. The recommended value, if used, is <cookiePrefixPropertyValue>.lb.cookie.
Defines number of seconds between scans (checking for changes) of the template files in the /var/opt/SUNWportal/portals/<protalid>/config directory. This interval can improve the performance and scalability because the server uses the cached information between scans. The default value is 30 seconds.
DP scan interval controls how often DP updates done by someone other than the user. For example, Administrator is selected before serving portal request. If a DP document (user or shared) is present in the cache, and DP scan interval has not yet elapsed, then the cached copy will be used and the check for modified DP documents does not happen.
The values are:
-1 — Scan happens only when user logs in or membership changes.
0 — Scan happens for every request.
n — After n seconds from previous scan, any updates to user DP or shared DP will be reflected in system behavior.
This property tells, which type of DP documents should be present as community request parameter to Desktop when membership is determined for DP merge. Contributor types can be separated by | as in communitymc.properties.
Provider class loader re-validate time interval in seconds, for authless anonymous session only.
Maximum number of event generations.
This is the Application Server execution mode. To turn the parallel execution of the portlets in Application Server off, set this parameter to off.
JSP Scratch directory is used for placing compiled JSPs.
Used only on application server. For more information on jspCompileWARClassPath, see the desktopconfig.propertiesfile in the /var/opt/SUNWportal/portals/<portal_id>/config directory.
Root directory under which all template files are located.
This is the community template base directory.
Root directory under which the customer is allowed to place provider classes, whether those are overriding the bundled providers, or their own new providers (usually the case). They must be placed in this directory, either in a jar at the top level, or in a com (or whatever) package directory.
This chapter contains the following sections:
In the default installation, the search.conf file is in the /var/opt/SUNWportal/searchservers/<searchserver_id>/config directory. The search.conf file lists all the specific search values you have set. The /var/opt/SUNWportal/samples/config directory contains a sample search.conf file.
The default install assigns $CSROOT to /var/opt/SUNWportal/searchservers/search1, $CSBIN to /var/opt/SUNWportal/bin, and $CSLIB to /var/opt/SUNWportal/lib.
search.conf File Parameters
Defined at installation. Server identifier string, mainly for backward compatibility with Search Server.
Defined at installation. Location of binaries.
Defined at installation. Location of database (used by server).
Defined at installation. Location of database (used by indexer).
Limits the number of server threads that can access the database at any one time. You can change this value for performance reasons, but it should be set to about 1.25 times the number of index threads for best performance.
The logical database name. You can change this value to another database including an external one.
Directory where database transaction logs are kept.
Enables or disables document level security. Can be reset in the administration console under Server Settings.
Security manager class name. Do not edit.
Whether to use group in addition to user role for security control.
Logs internal server activity. Defined at installation. Can be reset in the administration console under Server Advanced Settings.
Sets the default log level. Can be reset in the administration console under Server Advanced Settings.
Checks for number of servers aliased to the same address. Can be reset in the administration console under Robot Simulator.
Checks for any server redirects. Can be reset in the administration console under Robot Simulator.
Defined at installation. Contents generated by the Search server when you define an import agent in the administration console under Database Import.
Defined at installation.
Log of RDM server requests. Defined at installation. Can be reset in the administration console under Server Advanced Settings.
Disables RDM request logging. Can be reset in the administration console under Server Advanced Settings.
If true, server records how many documents are found in each browse category.
Whether to browse for documents at the root of the category tree.
Search engine logfile. Defined at installation. Can be reset in the administration console under Server Advanced Settings.
Maximum number of documents in each index batch.
Number of search query threads. Should be set to 3-6 threads per CPU that you wish to utilize.
Number of search index threads. Usually left at 1.
The format of the search engine index. Do not edit.
The blocking factor used during index merges. Do not edit.
Format of the search dictionary. Do not edit.
Controls the timeout (milliseconds) of slow wildcard searches.
-1 means unlimited.
Enable search result highlighting.
Maximum number of dynamic summary passages to generate.
Size of context (in words) around each highlight passage.
Search weights assigned to different document fields. Can be a comma separated list.
Log file for the indexer process. Defined at installation. Can be reset in the administration console under Server Advanced Settings.
The default Search Engine Schema. Defined at installation.
The RDM server description returned by server description requests. Defined at installation.
Server instance root directory. Defined at installation. Can be reset in the administration console under Server Settings.
The logical name of the taxonomy index database.
Polling interval for automatic taxonomy reloads.
The RDM Taxonomy definition. Edit using the Category Editor under Categories. Defined at installation.
Defined at installation. Can be reset in the administration console under Robot Crawling.
Number of milliseconds between refreshes of the Robot Control page of the administration console.
List of available choices, defining the maximum number of categories displayed per page.
-1 = display all tree.
Maximum number of elements in the category editor drop down select list of target categories.
The following parameters are not used:
Filters Check Virtual.
Reports exclude gv queries.
reports exclude browse.
rlog max logs.
The Sun Java System Portal Server 7.1 registers its services into the Sun Java System Sun Java System Access Manager Service Management Services (SMS) framework. This occurs during the pre-installation of the Portal Server 7.1 and post-installation for Sun Java System Access Manager software.
In general, any service-related data that is not server-specific is stored in the Sun Java System Access Manager directory. Server-specific data can be stored in properties files that are local to the specific server.
SMS provides a mechanism for services to define and manage their configuration data by using an Extensible Markup Language (XML) file that adheres to the SMS Document Type Definition (DTD). The definition of the configuration parameters through the XML file is called the schema for the service. Each Portal Server 7.1 service (Desktop, Rewriter, and Search) has its own XML and properties files for presenting and modifying service specific data.
Within the Sun Java System Access Manager framework, Portal Server 7.1 defines services related to the following functional areas:
The SunPortalRewriterService includes data associated with the Rewriter component, including the named rule sets that control the rewriting operation. The Rewriter API makes reference to the named rule sets that are stored in the directory.
In addition, the Portal Server 7.1 also uses other DTDs to define LDAP attribute values for the display profile and the Rewriter ruleset.
The Display Profile Document Type Definition (DTD) defines how the Display Profile is structured. The underlying data format for a display profile document is XML. It is intended to define the display configuration for the Desktop. It does that by defining provider, portlet, and channel objects, and their properties. The Rewriter ruleset DTD defines the structure of the ruleset. The Rewriter includes a default ruleset.
The file paths for the various XML, DTD, and schema files used to define the services of the Portal Server 7.1 (in the first column) and the service which uses the corresponding file (in the second column) are:
ldif file available in desktop directory.