To run WebCenter Portal at moderate load, set the open-files-limit to 4096. If you encounter errors, such as running out of file descriptors, then increase the system limit.

For example, on Linux, you can use this command:

ulimit -n 8192

Refer to your operating system documentation to find out how to change this system limit.

To determine the correct setting for the JDBC data source, use the Oracle WebLogic Remote Console to monitor the running system database connection usage as described in Configuring Services. If the Waiting for Connection Failure rate is noticeably higher, and the Active Connections Current Count is close to reaching the maximum capacity, then consider increasing the capacity to avoid potential database connection contention.

However, if the Active Connections Current Count is routinely lower than the maximum capacity, consider reducing the capacity to save memory.

For more information, see Configuring Connection Pool Features in Administering JDBC Data Sources for Oracle WebLogic Server.

The following data source settings are WebCenter Portal defaults for data sources mds-SpacesDS and WebCenterDS. These settings can be adjusted depending on the application's usage pattern and load.

    <jdbc-connection-pool-params>
        <initial-capacity>10</initial-capacity> 
        <max-capacity>50</max-capacity> 
        <capacity-increment>1</capacity-increment> 
        <shrink-frequency-seconds>0</shrink-frequency-seconds> 
        <highest-num-waiters>2147483647</highest-num-waiters> 
        <connection-creation-retry-frequency-seconds>0</connection-creation-retry-frequency-seconds> 
        <connection-reserve-timeout-seconds>60</connection-reserve-timeout-seconds>
        <test-frequency-seconds>0</test-frequency-seconds> 
        <test-connections-on-reserve>true</test-connections-on-reserve> 
        <ignore-in-use-connections-enabled>true</ignore-in-use-connections-enabled>
       <inactive-connection-timeout-seconds>0</inactive-connection-timeout-seconds>
        <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name> 
        <login-delay-seconds>0</login-delay-seconds>
        <statement-cache-size>5</statement-cache-size> 
        <statement-cache-type>LRU</statement-cache-type> 
        <remove-infected-connections>true</remove-infected-connections> 
        <seconds-to-trust-an-idle-pool-connection>60</seconds-to-trust-an-idle-pool-connection> 
        <statement-timeout>-1</statement-timeout> 
        <pinned-to-thread>false</pinned-to-thread> 
    </jdbc-connection-pool-params>

For information on how to edit MDS data source settings, see Tuning Data Source Connection Pools in Administering JDBC Data Sources for Oracle WebLogic Server.

If clients connect to your server using relatively slow connections, that is, by using modems or VPN from remote locations, consider compressing the content before it downloads to the client. While content compression increases the load on the server, the client's download experience is much improved.

Several content compression methods are available. The following steps describe how to use the mod_deflate module from Apache.

For more information about the mod_deflate module, refer to: http://httpd.apache.org/docs/2.0/mod/mod_deflate.html.

The default session timeout for the WebCenter Portal application is 45 minutes. Administrators can customize the session time to suit their installation. For details see Specifying Session Timeout Settings in Using Portals in Oracle WebCenter Portal.

If you encounter the any of the following conditions, then you can increase the MDS cache size in the adf-config.xml file. The default MDS cache size is 100 MB.

• Error message JOC region full

• Frequent MDS database access after the page is warmed up

• Retained memory by ADF application is close to the max-size-kb

Post deployment, modify these properties through the System MBeans Browser. For more information, see Changing MDS Configuration Attributes for Deployed Applications in Administering Oracle Fusion Middleware.

The following is a sample snippet of the adf-config.xml file:

<cache-config> 
<max-size-kb>150000</max-size-kb> 
</cache-config>

Purging MDS data improves MDS queries. If your portal site changes frequently, you may want to purge old MDS data more often, by reducing the time between purges.

Consider setting the MDS auto-purge seconds-to-live parameter (as shown in the example below) to remove older versions of metadata automatically every hour. By default, old versions of metadata are automatically purged every hour, that is, the auto-purge seconds-to-live parameter is set to 3600 seconds (as shown in the example below).

If excessive metadata is accumulated and each purge is very expensive, reduce this interval in the adf-config.xml file.

By default, there is no auto-purge entry in the adf-config.xml file. Use the following sample snippet of the adf-config.xml file to modify auto-purge:

<mdsC:adf-mds-config version="11.1.1.000">
    <mds-config xmlns="http://xmlns.oracle.com/mds/config">
      <persistence-config>
        <metadata-namePortal>
           ...
        </metadata-namespace>
        <auto-purge seconds-to-live="3600"/>
      </persistence-config>

To ensure the initial purge does not impact ongoing user activities, consider using the following WLST command to induce an MDS purge immediately before the bulk of the user load hits the system:

The following example shows how to purge all documents in the application repository whose versions are older than 10 seconds:

wls:/weblogic/serverConfig>purgeMetadata(application='[AppName]',server='[ServerName]',olderThan=10)

Concurrency management includes global settings that impact the entire WebCenter Portal and the service and resource specific settings that only impact a particular service.

You can define deployment-specific overrides or additional configuration in the adf-config.xml file. For example, you can specify resource-specific (producers) values that are appropriate for a particular deployment.

The following code snippet describes the format of the global, service, and resource entries in the adf-config.xml file:

<concurrent:adf-service-config 
  xmlns="http://xmlns.oracle.com/webcenterportal/concurrent/config"> 
  <global         
      queueSize="SIZE" 
      poolCoreSize="SIZE" 
      poolMaxSize="SIZE" 
      poolKeepAlivePeriod="TIMEPERIOD" 
      timeoutMinPeriod="TIMEPERIOD" 
      timeoutMaxPeriod="TIMEPERIOD" 
      timeoutDefaultPeriod="TIMEPERIOD" 
      timeoutMonitorFrequency="TIMEPERIOD" 
      hangMonitorFrequeny="TIMEPERIOD" 
      hangAcceptableStopPeriod="TIMEPERIOD" /> 
  <service 
      service="SERVICENAME" 
      timeoutMinPeriod="TIMEPERIOD" 
      timeoutMaxPeriod="TIMEPERIOD" 
      timeoutDefaultPeriod="TIMEPERIOD" /> 
  <resource 
      service="SERVICENAME" 
      resource="RESOURCENAME" 
      timeoutMinPeriod="TIMEPERIOD" 
      timeoutMaxPeriod="TIMEPERIOD" 
      timeoutDefaultPeriod="TIMEPERIOD" /> 
</concurrent:adf-service-config> 

Where:

SIZE: A positive integer. For example: 20.

TIMEPERIOD: Any positive integer followed by a suffix indicating the time unit, which must be one of: ms for milliseconds, s for seconds, m for minutes, or h for hours. For example: 50ms, 10s, 3m, or 1h. The following are examples of default settings for different services. These settings are overwritten with any service-specific configurations in the connections.xml file or the adf-config.xml files:

<concurrent:adf-service-config 
  xmlns="http://xmlns.oracle.com/webcenter/concurrent/config"> 
  <service service="oracle.webcenter.community" timeoutMinPeriod="2s" timeoutMaxPeriod="50s" timeoutDefaultPeriod="30s"/>
  <resource service="oracle.webcenter.community" 
      resource="oracle.webcenter.doclib" 
      timeoutMinPeriod="2s" timeoutMaxPeriod="10s" timeoutDefaultPeriod="5s"/> 
  <resource service="oracle.webcenter.community" 
      resource="oracle.webcenter.collab.calendar.community" 
      timeoutMinPeriod="2s" timeoutMaxPeriod="10s" timeoutDefaultPeriod="5s"/> 
  <resource service="oracle.webcenter.community" 
      resource="oracle.webcenter.collab.rtc" 
      timeoutMinPeriod="2s" timeoutMaxPeriod="10s" timeoutDefaultPeriod="5s"/> 
  <resource service="oracle.webcenter.community" 
      resource="oracle.webcenter.list" 
      timeoutMinPeriod="2s" timeoutMaxPeriod="10s" timeoutDefaultPeriod="5s"/> 
  <resource service="oracle.webcenter.community" 
      resource="oracle.webcenter.collab.tasks" 
      timeoutMinPeriod="2s" timeoutMaxPeriod="10s" timeoutDefaultPeriod="5s"/> 
</concurrent:adf-service-config>

<global queueSize="20"/>
    <resource service="foo" resource="bar" timeoutMaxPeriod="5s"/>

You can use the Enterprise Manager System MBean Browser to view, add, modify, and delete the concurrency configuration based on your usage pattern. To access the MBean Browser, see Accessing the System MBean Browser in Administering Oracle WebCenter Portal.

To manage the overall resource usage for mail, you can tune the Connection Timeout property:

• Default: 10 seconds

• Minimum: 0 seconds

• Maximum: 45 seconds

Post deployment, modify the Connection Timeout property through Fusion Middleware Control or by using WLST. For details, see:

• Modifying Mail Server Connection Details Using Fusion Middleware Control in Administering Oracle WebCenter Portal

• Modifying Mail Server Connection Details Using WLST in Administering Oracle WebCenter Portal

The following is a sample code snippet of the connections.xml file to change the default timeout to 5 seconds:

<Reference name="MailConnection"
className="oracle.adf.mbean.share.connection.webcenter.mail.MailConnection">
  <StringRefAddr addrType="connection.time.out">
      <Contents>5</Contents>
  </StringRefAddr>
</Reference>

To manage the overall resource usage for RSS news feeds, you can adjust the refresh interval and timeout in the adf-config.xml file.

If you must modify these properties, post deployment, use the System MBeans Browser.

The following is a sample snippet of the adf-config.xmlfile:

<rssC:adf-rss-config>
       <rssC:RefreshSecs>3600</rssC:RefreshSecs>
       <rssC:TimeoutSecs>3</rssC:TimeoutSecs>
       <rssC:Configured>true</rssC:Configured>
</rssC:adf-rss-config>

If you are experiencing performance issues post login, especially in the area of permission checks, you may need to tune the policy store parameters as described in OPSS PDP Service Tuning Parameters. Depending on your use case scenarios, performance of WebCenter Portal can be improved by modifying the following parameters:

• Set oracle.security.jps.policystore.rolemember.cache.warmup.enable to True

• Modify oracle.security.jps.policystore.rolemember.cache.size based on the number of active portals in your WebCenter Portal deployment.

  Note:

  Only modify this parameter if your WebCenter Portal deployment expects to have more than 3000 active portals.

• Set oracle.security.jps.policystore.policy.cache.size to 5 times the expected number of portals.

When you configure an identity store for WebCenter Portal, you can choose to configure either an SSL port or a non-SSL port. If you choose an SSL port, by default, the JNDI connections are not pooled causing increased response time and decreased performance when looking up users, groups, or other identity store entities. To address this, do the following:

For Oracle Virtual Directory (OVD), the only object class against which attributes are looked up is inetOrgPerson (and it's parent object classes). Since the Profile Gallery can display attributes not defined in inetOrgPerson, all the additional attributes not covered in inetOrgPerson would require an additional round trip to the identity store.For best performance when using OVD in a production environment, Oracle recommends that you add the following configuration entry (in bold) to the domain-level jps-config.xml file:

        <!-- JPS WLS LDAP Identity Store Service Instance -->
        <serviceInstance name="idstore.ldap"
         provider="idstore.ldap.provider">
            <property name="idstore.config.provider"
value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/>
            <property name="CONNECTION_POOL_CLASS"
value="oracle.security.idm.providers.stdldap.JNDIPool"/>
 
          <extendedProperty>
            <name>user.object.classes</name>
            <values>
               <value>top</value>
               <value>person</value>
               <value>inetorgperson</value>
               <value>organizationalperson</value>
               <value>orcluser</value>
               <value>orcluserv2</value>
               <value>ctCalUser</value>
            </values>
          </extendedProperty>
        </serviceInstance>

When the Portal Server is connected to Active Directory, logging in to Portal is delayed. To avoid delays and to enable best performance while using Active Directory in a production environment, Oracle recommends you complete the following configuration:

To manage the overall resource usage for a Web producer, you can tune the Connection Timeout property:

• Default: 30000 ms

• Minimum: 5000 ms

• Maximum: 60000 ms

Post deployment, modify the Connection Timeout property through Fusion Middleware Control or by using WLST. For details, see:

• Editing WSRP Producer Registration Details Using Fusion Middleware Control in Administering Oracle WebCenter Portal.

• Editing Producer Registration Details Using WLST in Administering Oracle WebCenter Portal.

The following is a sample snippet of the connections.xml file:

<webproducerconnection producerName="wc-WebClipping" urlConnection="wc-WebClipping-urlconn" timeout="10000" establishSession="true" mapUser="false"/>

To specify the default WSRP requiresRewrite flag to use when generating Resource URLs for portlet-served resources, set the portlet container runtime option (specified in portlet.xml) as follows: com.oracle.portlet.defaultServedResourceRequiresWsrpRewrite

This setting is used for all ResourceURLs created by the portlet, unless overridden by the presence of the oracle.portlet.server.resourceRequiresRewriting request attribute when the ResourceURL methods write() or toString() are called. This setting is also used to specify the WSRP requiresRewriting flag on the served resource response, but can be overridden by the presence of the oracle.portlet.server.resourceRequiresRewriting request attribute when the portlet's serveResource() method returns.

Valid values:

• unspecified: (Default) The requiresRewrite URL flag is not given a value, and the requiresRewriting response flag for a serveResource operation is based on the MIME type of the response.

• true: The requiresRewrite URL flag and requiresRewriting response flag is set to true, indicating that the resource should be rewritten by the consumer.

• false: The requiresRewrite URL flag and requiresRewriting response flag is set to false, indicating that the resource does not necessarily need to be rewritten by the consumer, though the consumer may choose to rewrite the resource.

To specify the default WSRP requiresRewrite flag to use when encoding URLs for resources not served by the portlet, set the Portlet container runtime option (specified in portlet.xml) as follows: com.oracle.portlet.defaultProxiedResourceRequiresWsrpRewrite.

This setting is used for all URLs returned by the PortletResponse.encodeURL() method, unless overridden by the presence of the oracle.portlet.server.resourceRequiresRewriting request attribute when the PortletResponse.encodeURL() method is called.

Valid values:

• true: (Default) The requiresRewrite URL flag is set to true, indicating that the resource should be rewritten by the consumer.

• false: The requiresRewrite URL flag is set to false, indicating that the resource does not necessarily need to be rewritten by the consumer.