Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Portal
11g Release 1 (11.1.1.6.0)

Part Number E12405-18
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

9 Setting WebCenter Portal Application Properties

This chapter includes the following sections:

Audience

The content of this chapter is intended for Fusion Middleware administrators (users granted the Admin role through the Oracle WebLogic Server Administration Console). See also, Section 1.8, "Understanding Administrative Operations, Roles, and Tools".

9.1 Setting Application Properties for the Spaces Application

The Spaces home page (in Fusion Middleware Control) is your starting place for configuring Spaces application deployments. Just like any other J2EE application, you can configure ADF, MDS, security policies and roles, and so on, from here. You can also configure back-end service connections, external applications, and portlet producers for the Spaces application. To access this page, see Section 6.2, "Navigating to the Home Page for the Spaces Application".

Additionally, there are several application-level settings for configuring Spaces workflows and Oracle SES search crawling in Spaces. Application settings are described in the following sections:

9.2 Setting Application Properties for Framework Applications

The J2EE Application Deployment home page (in Fusion Middleware Control) is your starting place for configuring application deployments developed with WebCenter Portal: Framework. Just like any other J2EE application, you can configure ADF, MDS, security policies and roles, and so on, from here. You can also configure back-end service connections, external applications, and portlet producers. To access this page, see Section 6.3, "Navigating to the Home Page for Framework Applications".

Additionally, there are several application-level settings for configuring proxy servers, search settings, and a notification channel for the Framework application. Application settings are described in the following sections:

See also, Appendix A, "Tuning Oracle WebCenter Portal Performance".

9.3 Specifying the BPEL Server Hosting Spaces Workflows

Spaces uses the BPEL server included with the Oracle SOA Suite to host internal workflows, such as space membership notifications, space subscription requests, and so on. To enable workflow functionality inside the Spaces application, a connection to this BPEL server is required.

Note:

Spaces workflows must be deployed on the SOA managed server that Spaces is configured to use. See also, "Back-End Requirements for Spaces Workflows" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.

To configure a connection to Spaces workflows:

  1. Login to Fusion Middleware Control, and navigate to the home page for WebCenter Portal: Spaces.

    See Section 6.2, "Navigating to the Home Page for the Spaces Application".

  2. From the WebCenter Portal menu, choose Settings > Application Configuration.

    Figure 9-1 Choosing the BPEL Server Where Spaces Workflows are Deployed

    Choosing the SOA Instance for WebCenter Spaces Workflows
  3. From the Connection Name dropdown, choose the name of the connection you require.

    The connections on offer are those currently configured for the Worklist service in Spaces.

    Ensure that you choose the connection that points to the SOA instance in which Spaces workflows are deployed. If that connection is not listed you must create it. To define the connection, see Section 23.4, "Setting Up Worklist Connections".

  4. Click Apply.

  5. Restart the managed server on which the Spaces application is deployed to effect this change.

    See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments".

9.4 Configuring Search Crawlers

Post deployment, administrators can configure search crawlers for Spaces or their Framework application. Both Spaces and Framework applications can use either Oracle Secure Enterprise Search (SES) or WebCenter Portal's own search adapters. Search crawler configuration for the Spaces application is slightly different to other Framework applications, so ensure that you follow the appropriate documentation for your application.

Spaces Application

Out-of-the-box, the Spaces application uses WebCenter Portal's own Search service for searching and returning Spaces content. If preferred, you can use Oracle Secure Enterprise Search (SES) to search and return unified results for most Spaces resources, including documents, discussions, announcements, spaces, lists, pages, wikis and blogs. To set up Oracle SES searching, see Section 22.6, "Configuring Oracle SES to Search Spaces Applications".

Framework Applications

By default, Framework applications are configured to use Oracle SES crawlers. If you do not want to use Oracle SES you can specify that WebCenter Portal's own search adapters are used instead. For details, see Section 22.5, "Configuring Oracle SES to Search Framework Applications".

9.5 Setting Search Options

Post deployment, administrators can fine-tune search settings to suit their WebCenter Portal application. For example, you can set suitable search timeouts and specify how many search results to return and display.

Note:

The following steps describe how to set search options using Fusion Middleware Control. You can set the same options using WLST commands, for details, see "setSearchConfig" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To set search parameters using Fusion Middleware Control:

  1. Login to Fusion Middleware Control, and navigate to the home page for your WebCenter Portal application:

    Section 6.2, "Navigating to the Home Page for the Spaces Application".

    Section 6.3, "Navigating to the Home Page for Framework Applications".

  2. From the WebCenter Portal menu, choose Settings > Application Configuration.

  3. Configure Search Settings as required.

    Element Description

    Oracle Secure Enterprise Search Data Group

    Specify the Oracle SES data group in which to search. If no value is provided, then everything in the Oracle SES instance is searched.

    Execution Timeout (ms)

    Enter the maximum time that a service is allowed to execute a search (in ms).

    Executor Preparation Timeout (ms)

    Enter the maximum time that a service is allowed to initialize a search (in ms).

    Results per Service - Saved Search Task Flows

    Enter the number of search results displayed, per service, in a Saved Search task flow.

    Results per Service - Search Page

    Enter the number of search results displayed, per service, for searches submitted from the main search page. Users can click Show All if they want to see all the results.

    Number of Saved Searches in Search Page

    Enter the number of saved searches displayed in the Saved Search list (on the main search page).


  4. Click Apply.

  5. Restart the managed server on which the Spaces application is deployed to effect this change.

    See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments".

9.6 Choosing a Channel for Notification Messages

In Spaces and Framework applications, users can subscribe to services and application objects in which they have a particular interest and are subsequently notified of changes and updates that affect their subscribed services and objects.

Notification messages can be routed through a BPEL server or a mail server and it is the system administrator's job to configure the channel that is used. For more information, see Section 19.2, "Setting Up Notifications".

9.7 Setting Up a Proxy Server

A proxy server is required if you want to enable external RSS news feeds and external links in Activity Stream task flows in your WebCenter Portal application. The RSS service and the Activity Stream service share the same proxy server settings.

You can set up a proxy server using Fusion Middleware Control or WLST.

This section includes the following subsections:

9.7.1 Setting Up a Proxy Server Using Fusion Middleware Control

To set up a proxy server using Fusion Middleware Control:

  1. Log on to Fusion Middleware Control and navigate to the home page for your WebCenter Portal application:

  2. Do one of the following:

    • For the Spaces application - From the WebCenter Portal menu, choose Settings > Application Configuration.

    • For a Frameowrk application - From the Application Deployment menu, choose WebCenter Portal > Application Configuration.

  3. In the Proxy Server section, enter the host name and the port number of the proxy server. For details, see Table 9-1.

    Table 9-1 RSS Proxy Server Details

    Field Description

    Proxy Host

    Enter the host name of the proxy server.

    Proxy Port

    Enter the port number on which the proxy server is running.


  4. Click Apply to save this connection.

  5. Restart the managed server to which your WebCenter Portal application is deployed. For more information, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Portal Application Deployments."

9.7.2 Setting Up a Proxy Server Using WLST

Use the WLST command setRssProxyConfig to specify the proxy host and port number used by RSS news feeds and Activity Stream task flows. For command syntax and examples, see the section, "setRssProxyConfig" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information about how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

Note:

To start using the new proxy details, you must restart the managed server in which your WebCenter Portal application is deployed. For more information, see the section, "Starting and Stopping WebLogic Managed Servers Using the Command Line" in Oracle Fusion Middleware Administrator's Guide.

Use the getRssProxyConfig command to find out the current proxy host and port used by RSS and Activity Stream task flows. If you want to delete the current proxy host and port settings, use the unsetRssProxyConfig command. For more information, see the section "RSS News Feeds" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

9.8 Exposing Spaces Templates From a Previous Release

Out-of-the-box, the Spaces application provides several templates for building spaces, including Team Site, Portal Site, Document Exchange, and more. For details, see "Working with Space Templates" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.

Previous releases of Spaces supplied a different template set, namely Basic, Community Of Interest, and Group Project. While Oracle considers these templates deprecated, you can expose them in your latest Spaces version as follows:

  1. Log in to SQLPlus as DBA or another administrative user to the WebCenter Portal database.

  2. Execute one or more of the following commands:

    • To expose the Basic template:

      insert into WC_SPACE_HEADER values 
      
      ('webcenter', 'sdfcd3cd3_8a53_4a7c_872f_74de46969cef','Basic','Basic','Template for a Space with minimal initial content',
      
      'Y','N','N','N','N','N','N','N',1,'/oracle/webcenter/space/metadata/spacetemplate/Basic/images/wc_blank_icon.png',
      
      '/oracle/webcenter/space/metadata/spacetemplate/Basic/images/wc_blank_logo.png','Blank','system','30-OCT-09 12.00.00.000000000 AM',
      
      'weblogic','30-OCT-09 12.00.00.000000000 AM','','','','Y',0,0,1);
      
      
    • To expose the Community of Interest template:

      insert into WC_SPACE_HEADER values 
      
      ('webcenter', 's5dd6d6b3_7f5f_4f1c_8ee6_ce305469f1b3','ProjectSpace','Group Project','Template for a Space based on completing a project',
      
      'Y','N','N','N','N','N','N','N',1,'/oracle/webcenter/space/metadata/spacetemplate/ProjectSpace/images/wc_prj_icon.png',
      
      '/oracle/webcenter/space/metadata/spacetemplate/ProjectSpace/images/wc_prj_logo.png','project,group,team','system','30-OCT-09 12.00.00.000000000 AM',
      
      'weblogic','30-OCT-09 12.00.00.000000000 AM','','','','Y',0,0,1);
      
      
    • To expose the Group Project template:

      insert into WC_SPACE_HEADER values 
      
      ('webcenter', 'sb175bdde_4cb8_4da8_bcdb_eff13e59da2d','CommunityOfInterest','Community of Interest','Template for a Space based on a common interest',
      
      'Y','N','N','N','N','N','N','N',1,'/oracle/webcenter/space/metadata/spacetemplate/CommunityOfinterest/images/coi_icon.png',
      
      '/oracle/webcenter/space/metadata/spacetemplate/CommunityOfinterest/images/coi_logo.png','community','system','30-OCT-09 12.00.00.000000000 AM',
      
      'weblogic','30-OCT-09 12.00.00.000000000 AM','','','','Y',0,0,1);
      
      

The templates are available immediately. You are not required to restart the Spaces application.

9.9 Setting a Session Timeout for the Spaces Application

A default session timeout for a Spaces application is derived from the HTTP session timeout specified in web.xml. Out-of-the-box, the web.xml setting for <session-timeout> is 45 minutes.

Administrators can use the wcSessionTimeoutPeriod attribute in webcenter-config.xml to increase or decrease the session timeout if required.

To modify the session timeout for the Spaces application:

  1. Export the latest webcenter-config.xml from MDS.

    For example:

    exportMetadata(application='webcenter', server='WC_Spaces', toLocation='/tmp/mydata', docs='/oracle/webcenter/webcenterapp/metadata/mdssys/cust/site/webcenter/webcenter-config.xml.xml')
    

    The webcenter-config.xml file is created the first time you configure "General" settings through Spaces administration. See also, Appendix A, "webcenter-config.xml".

    Note:

    webcenter-config.xml is created in MDS the first time you configure "General" settings through Spaces Administration. If the file does not yet exist in MDS you can edit webcenter-config.xml directly. The file is located at: /oracle/webcenter/webcenterapp/metadata/webcenter-config.xml

  2. Open webcenter-config.xml.xml exported from MDS in a text editor and add the following snippet:

    <mds:replace node="wcSessionTimeoutPeriod(xmlns(mds_ns1=http://xmlns.oracle.com/webcenter/webcenterapp))/mds_ns1:value"/>
    <mds:insert after="wcSessionTimeoutPeriod(xmlns(mds_ns1=http://xmlns.oracle.com/webcenter/webcenterapp))/mds_ns1:type" parent="wcSessionTimeoutPeriod">
    <value xmlns="http://xmlns.oracle.com/webcenter/webcenterapp">15</value>
    </mds:insert>
    
  3. For value, enter the timeout you require (in minutes).

  4. Save and close webcenter-config.xml.xml.

  5. Import the updated webcenter-config.xml.xml file to MDSs.

    For example:

    importMetadata(application='webcenter', server='WC_Spaces', fromLocation='/tmp/mydata', docs='/oracle/webcenter/webcenterapp/metadata/mdssys/cust/site/webcenter/webcenter-config.xml.xml')