4 Installing Back-End Components

WebCenter Web 2.0 Services are a major part of Oracle WebCenter, allowing you to create a dynamic and interactive environment for users. Some of these services, such as Worklist, Documents, and Search, require you to install and configure back-end components to integrate with Oracle WebCenter itself. This chapter describes how to complete these installation tasks. It also includes the instructions for configuring an LDAP-based identity store.

This chapter includes the following sections:

4.1 Introduction to Oracle WebCenter Web 2.0 Services

WebCenter Web 2.0 Services enables your application users to perform common tasks such as online communication, document management, and advanced searching, tagging, and linking operations. WebCenter Web 2.0 Services can be organized into three groups: social networking services, personal productivity services, and shared services. Figure 4-1 illustrates the classification of WebCenter Web 2.0 Services.

Figure 4-1 Classification of WebCenter Web 2.0 Services

Description of Figure 4-1 follows
Description of "Figure 4-1 Classification of WebCenter Web 2.0 Services"

Table 4-1 describes the various WebCenter Web 2.0 Services and lists the back-end components that must be installed to integrate these services into your WebCenter applications.

Table 4-1 Back-End Requirements for WebCenter Web 2.0 Services

Service Description Back-End Component Required

Social Networking Services

Enables users to maximize productivity through collaboration.

  

Discussions

Provides the ability to create and participate in threaded discussion

Oracle WebCenter Discussions

Announcements

Enables users to post, personalize, and manage announcements.

Oracle WebCenter Discussions

Instant Messaging and Presence (IMP)

Provides the ability to observe the online presence status of other authenticated users (whether online, offline, busy, or idle) and to contact them instantly.

Communication server such as Oracle WebLogic Communication Services 11g or Microsoft Live Communication Server 2005

Blog

Enables blogging functionality within the context of an application.

Oracle WebCenter Wiki and Blog Server

Wiki

Provides the ability for geographically diverse teams to originate and collaborate on web documents.

Oracle WebCenter Wiki and Blog Server

Shared Services

Provides features for both social networking and personal productivity.

  

Documents

Provides content management and storage capabilities, including content upload, file and folder creation and management, file check out, versioning, and so on.

Content repositories such as Oracle Content Server 10.1.3.4.1 or Oracle Portal 11g

Links

Provides the ability to view, access, and associate related information; for example, you can link to a solution document from a discussion thread.

Oracle Database 10.2.0.3 or later

Lists

Enables users to create, publish, and manage lists. (Available only in WebCenter Spaces)

Oracle Database 10.2.0.3 or later

Page

Provides the ability to create and manage pages at run time.

None

Tags

Provides the ability to assign one or more personally relevant keywords to a given page or document.

Oracle Database 10.2.0.3 or later

Events

Provides group calendars, which users can use to schedule meetings, appointments, and any other type of team get-together. (Available only in WebCenter Spaces)

Oracle Database 10.2.0.3 or later

Personal Productivity Services

Focuses on the requirements of an individual, rather than a group.

  

Mail

Provides easy integration with IMAP and SMTP mail servers to enable users to perform simple mail functions such as viewing, reading, creating, and deleting messages, creating messages with attachments, and replying to or forwarding existing messages.

Mail server based on IMAP4 and SMTP, such as Microsoft Exchange Server 2003

Notes

Provides the ability to "jot down" and retain quick bits of personally relevant information. (Available only in WebCenter Spaces)

Oracle Database 10.2.0.3 or later

Recent Activities

Provides a summary view of recent changes to documents, discussions, and announcements.

Oracle Database 10.2.0.3 or later

RSS

Provides the ability to publish content from WebCenter Web 2.0 Services as news feeds in RSS 2.0 and Atom 1.0 formats. In addition, the RSS service enables you to publish news feeds from external sources on your application pages.

Oracle Database 10.2.0.3 or later

Search

Provides the ability to search tags, services, an application, or an entire site.

Oracle Secure Enterprise Search (Oracle SES) 10.1.8.2, updated with Oracle SES 10.1.8.3 and Oracle SES 10.1.8.4 patch sets

Worklist

Provides a personal, at-a-glance view of business processes that require attention. These can include a request for document review and other types of business process that come directly from enterprise applications.

Oracle BPEL Process Manager (BPEL), which is installed as part of Oracle SOA Suite 11g

Note:

To integrate WebCenter Web 2.0 Services that rely on Oracle Database into your WebCenter applications, you must create the WEBCENTER schema. For information about installing an Oracle database and creating schemas, see Chapter 2, "Installing Oracle WebCenter."

4.2 Back-End Requirements for the Instant Messaging and Presence (IMP) Service

The Instant Messaging and Presence (IMP) service relies on a back-end communication server. Oracle WebCenter can be integrated with SIP-based communication servers and is certified with Microsoft Live Communications Server 2005.

4.2.1 Communication Server - Installation

For information about installing a communication server, refer to Microsoft documentation, which includes instructions for installing Microsoft Live Communications Server 2005.

To use Microsoft Live Communications Server 2005 as your communication server, you must also deploy the Oracle RTC web services for Microsoft Live Communications Server 2005. For information, see the "Microsoft Live Communications Server (LCS) Prerequisites" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4.2.2 Communication Server - Configuration and Integration

If an LDAP-based identity store is not used for your Oracle WebCenter environment, then you must create WebCenter users on your communication server. For information about creating users on a communication server, refer to the communication server's product documentation.

After installing and configuring your communication server, you must set up connections to the communication server to integrate the IMP service into your WebCenter applications. For information, see the:

4.3 Back-End Requirements for Content Integration and the Documents Service

The Documents service and content integration capabilities of Oracle WebCenter enable application developers to integrate content into their applications from local file systems and external content repositories. Oracle WebCenter supports content integration with the following external repositories:

  • Oracle Content Server 10.1.3.4.1

  • Oracle Portal 11g

Note:

WebCenter Spaces applications require the default content repository to be Oracle Content Server. Administrators may connect Oracle WebCenter Spaces to other content repositories such as Oracle Portal and local file systems to support additional Document task flows (Document Library, Document List, Recent Documents) that WebCenter Spaces may use.

4.3.1 Oracle Content Server Requirements

This section describes the requirements for using Oracle Content Server as an external repository for WebCenter applications.

4.3.1.1 Prerequisites for Installing Oracle Content Server

Before you install Oracle Content Server, you must perform the following tasks:

4.3.1.2 Oracle Content Server - Installation

You can choose to install Oracle Content Server while installing Oracle WebCenter. For information, see Section 2.8, "Installing Oracle WebCenter."

You can also choose to install only Oracle Content Server later, without installing Oracle WebCenter components. For example, you may want to install Oracle Content Server later on a different system instead of the one where Oracle WebCenter is installed.

To install Oracle Content Server separately:

  1. Install Oracle Content Server 10.1.3.3.3 from the Universal Content Management (UCM) media.

    For information, see the Content Server Installation Guide for Microsoft Windows or the Content Server Installation Guide for UNIX available here:

    http://download.oracle.com/docs/cd/E10316_01/owc.htm

  2. Run the WebCenter configuration script, wc_contentserverconfig, from the Oracle Content Server 10.1.3.4.1 media to prepare the server to work with Oracle WebCenter.

    This script installs the following:

    • Oracle Content Server 10.1.3.4.1 patch

    • Folders_g 10.1.3.4.1 component

    • WcConfigure component

      The WcConfigure component performs the following tasks to configure Oracle Content Server for Oracle WebCenter:

      • Sets configuration values for UseAccounts and IsAutoNumber to true and AutoNumberPrefix to IDC_Name, if not set.

      • Updates, if necessary, the JDBC password and its encoding from ClearText to Intradoc.

      • Adds the document type DOCUMENT.

      • Configures folders so that dDocType and dSecurityGroup are inherited, and the system default information is set as follows: dDocType=DOCUMENT and dSecurityGroup=Public.

To run the wc_contentserverconfig WebCenter script:

  1. Navigate to the webcenter-conf directory, which is in the root directory on the Oracle Content Server 10.1.3.4.1 media.

  2. Run the following command:

    On UNIX:

    ./wc_contentserverconfig.sh content_server_dir path_to_source_directory

    Where, content_server_dir refers to the Oracle Content Server 10.1.3.3.3 installation directory and path_to_source_directory refers to the webcenter-conf directory on the Oracle Content Server 10.1.3.4.1 media.

    For example, wc_contentserverconfig.sh /myproducts/ucm /myproducts/ucmmedia/webcenter-conf.

    On Windows:

    wc_contentserverconfig.cmd content_server_dir path_to_source_directory

  3. Restart Oracle Content Server Admin Server and Oracle Content Server.

    On UNIX

    • To restart Admin Server: Run content_server_dir/admin/etc/idcadmin_restart

    • To restart Oracle Content Server: Run content_server_dir/etc/idcserver_restart

      Where, content_server_dir refers to the Oracle Content Server installation directory.

    For information about how to start, stop, or restart Oracle Content Server, see the Content Server Installation Guide for UNIX available here:

    http://download.oracle.com/docs/cd/E10316_01/owc.htm

    On Windows

    • To restart Admin Server: If Admin Server is running as a Windows service, then you can restart the service by choosing Start, Settings, Control Panel, Administrative Tools, and then Services. Then, right-click the applicable IDC Content Admin Service service and choose Restart.

    • To restart Oracle Content Server: If Oracle Content Server is running as a Windows service, then you can restart the service by choosing Start, Settings, Control Panel, Administrative Tools, and then Services. Then, right-click the applicable IDC Content Service service and choose Restart.

      If Oracle Content Server is running as an application, you can restart the server by simply closing the Oracle Content Server window and starting it again.

    For information about how to start, stop, or restart Oracle Content Server, see the Content Server Installation Guide for Microsoft Windows available here:

    http://download.oracle.com/docs/cd/E10316_01/owc.htm

4.3.1.3 Oracle Content Server - Configuration

Configuration of Oracle Content Server involves the following tasks:

  • Configuring Oracle Content Server to work with Oracle HTTP Server

  • Configuring Oracle Content Server to use an LDAP-based identity store

4.3.1.3.1 Configuring Oracle Content Server for Oracle HTTP Server

If you intend to manage Oracle Content Server through a browser or add content on the server through WebDAV, then you must configure Oracle Content Server to work with Oracle HTTP Server.

Note:

Oracle Content Server and Oracle HTTP Server must be installed on the same system.

Steps to be Performed on Oracle Content Server

To configure Oracle Content Server to work with Oracle HTTP Server:

  1. Shut down Oracle Content Server and the Admin Server, if running:

    To stop Oracle Content Server, run this command:

    content_server_dir/etc/idcserver_stop

    To stop the Admin Server, run this command:

    content_server_dir/admin/etc/idcadmin_stop

  2. Edit the content_server_dir/config/config.cfg file to add SocketHostAddressSecurityFilter, if this entry is not present in the file. This should be set to a pipe-delimited list of all hosts allowed to access Oracle Content Server.

    Example:

    SocketHostAddressSecurityFilter=127.0.0.1 | allowed_host_IP

    Where allowed_host_IP refers to IP addresses of all hosts allowed to connect through a TCP socket port to Oracle Content Server. This must include the network IP address of the server on which Oracle Content Server is installed.

  3. Edit the content_server_dir/admin/bin/intradoc.cfg file to add the SocketHostAddressSecurityFilter entry if it is not there in the file. See step 2 for values of this entry.

  4. Restart Oracle Content Server and Admin Server.

Steps to be Performed on Oracle HTTP Server

To configure Oracle HTTP Server for Oracle Content Server:

  1. Add the following entry to the httpd.conf file of Oracle HTTP Server:

    include content_server_dir/data/users/apache22/apache.conf

  2. Restart Oracle Content Server.

  3. Restart Oracle HTTP Server.

    For example, you can use the following command:

    OHS_server_dir/instances/instance1/bin/opmnctl stopall /opmnctl startall

    Where, OHS_server_dir is the Oracle HTTP Server installation directory and instance1 refers to the instance where Oracle HTTP Server is running.

4.3.1.3.2 Configuring LDAP-Based Identity Store

Oracle WebCenter only supports Oracle Content Server configured with LDAP-based identity store. For identity propagation, Oracle Content Server and Oracle WebCenter must use the same LDAP identity store. By default, Oracle Content Server is not set up with an LDAP-based identity store.

You must configure Oracle Content Server to use an external LDAP-based identity store. You can also optionally configure Oracle Content Server for enabling full-text search and Secure Socket Layer (SSL). For information about LDAP configuration and other settings, see the "Content Repository Prerequisites" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4.3.1.4 Oracle Content Server - Integration

After configuring Oracle Content Server, you must set up content repository connections to the server to integrate the Documents service into your WebCenter applications. For information, see the:

4.3.2 Oracle Portal Installation

Oracle Portal offers a complete and integrated framework for building, deploying, and managing enterprise portals.

4.3.2.1 Oracle Portal - Installation

You must install Oracle Portal 11g to use it as a content repository for your Oracle WebCenter applications. For information about how to install Oracle Portal 11g, see Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer.

4.3.2.2 Oracle Portal - Integration

After installing Oracle Portal, you must set up content repository connections to use Oracle Portal. For information, see the:

4.4 Back-End Requirements for the Mail Service

The Mail service relies on a mail server, such as Microsoft Exchange Server 2003, that supports IMAP4 and SMTP protocols. To install a mail server, refer to the documentation of the required product.

To enable WebCenter users to access the mail service from within a WebCenter application, it is essential that users created on the mail server correspond with the users created in the embedded LDAP of Oracle WebLogic Server or any other identity store, which Oracle WebCenter is configured to use. For information about adding users on a mail server, refer to the product documentation of your server. For more information about adding users to an identity store, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

After setting up a mail server, you must register the mail server with your application and create connections to the mail server. For information, see the:

4.5 Back-End Requirements for the Search Service

The Search service does not require any back-end installation to search for content created inside Oracle WebCenter applications by other WebCenter Web 2.0 Services. However, you can extend WebCenter searches to external content repositories by using Oracle Secure Enterprise Search (Oracle SES). Oracle SES is a crawler-based service that can search a multitude of sources, structured and unstructured, in a variety of file formats, indexed or real-time.

4.5.1 Oracle SES - Installation

To install Oracle SES, you must perform the following tasks:

  1. Install Oracle SES 10.1.8.2.

    For information about how to install Oracle SES 10.1.8.2, refer to the Oracle Secure Enterprise Online Documentation Library 10g Release 1 (10.1.8.2) available here on OTN:

    http://www.oracle.com/technology/documentation/ses.html

  2. Apply the Oracle SES 10.1.8.3 patch set.

  3. Apply the Oracle SES 10.1.8.4 patch set.

    You can download patch sets from http://metalink.oracle.com.

4.5.2 Oracle SES - Integration

After installing Oracle SES, you must create connections to the server from your WebCenter application. For information, see the:

4.6 Back-End Requirements for the Worklist Service

The Worklist service relies on the Oracle BPEL Process Manager (BPEL) server, which is included with Oracle SOA Suite.

To integrate the Worklist service into your applications, you must install Oracle SOA Suite. For information about how to install Oracle SOA Suite, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite.

After installing Oracle SOA Suite, you can integrate the Worklist service into your applications by setting up connections to the BPEL server. No further configuration is required on Oracle SOA or Oracle WebCenter. For information about setting up connections, see the:

Note:

For WebCenter users to store and retrieve tasks from a BPEL server, it is essential that their user names on both the WebCenter application and the BPEL server are identical.

You can achieve this by using a shared LDAP-based identity store or by creating identical user credentials (same user name and password) in the identity stores used by the WebCenter application and the BPEL server.

4.7 Back-End Requirements for WebCenter Spaces Workflows

WebCenter Spaces provides several pre-built workflows to handle group space membership notifications, group space subscription requests, and so on. To enable workflows on WebCenter Spaces, you must perform the following tasks:

  1. Install Oracle SOA Suite (See Section 4.7.1, "Oracle SOA Suite - Installation")

  2. Deploy WebCenter Spaces workflows on the Oracle SOA server (See Section 4.7.2, "Oracle SOA Server - Workflow Deployment")

  3. Secure the Web Service connection between the Oracle SOA server and WebCenter Spaces (See Section 4.7.3, "Oracle SOA and Oracle WebCenter - WS-Security Configuration")

  4. Configure the BPEL server connection for WebCenter Spaces workflows (See Section 4.7.4, "Oracle WebCenter - BPEL Server Connections")

Note:

For WebCenter users to store and retrieve tasks from a BPEL server, it is essential that their user names on both the WebCenter application and the BPEL server are identical.

You can achieve this by using a shared LDAP-based identity store or by creating identical user credentials (same user name and password) in the identity stores used by the WebCenter application and the BPEL server.

4.7.1 Oracle SOA Suite - Installation

To use WebCenter Spaces workflows, you must install Oracle SOA Suite. For information about how to install Oracle SOA Suite, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite.

4.7.2 Oracle SOA Server - Workflow Deployment

To prepare an Oracle SOA server to support WebCenter Spaces workflows, you must deploy WebCenter Spaces workflows on the Oracle SOA managed server that WebCenter Spaces is configured to use. This involves deploying the following files:

  • sca_CommunityWorkflows_rev1.0.jar, the CommunityWorkflows composite application that contains the business logic. This composite is located at the following path in your Oracle SOA installation:

    SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows_rev1.0.jar

  • WebCenterWorklistDetailApp.ear, the WebCenterWorklistDetailApp application that contains the task detail pages. The application is located at the following path in your Oracle SOA installation:

    SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear

4.7.2.1 Deploying sca_CommunityWorkflows_rev1.0.jar

You can deploy sca_CommunityWorkflows_rev1.0.jar by using the following methods:

To deploy the sca_CommunityWorkflows_rev1.0.jar by using Fusion Middleware Control:

  1. Start Fusion Middleware Control.

  2. Navigate to the following URL: http://host_name.domain_name:port_number/em

    For example: http://myhost.mycompany.com:7001/em

  3. Enter administrator user name and password for the farm and click Login.

    Only the Fusion Middleware administrator can log on to Fusion Middleware Control. The default user name for the administrator user is weblogic. This is the account you can use to log on to Fusion Middleware Control for the first time.

  4. Under WebLogic Domain, right-click the SOA domain, select SOA Deployment, and then Deploy. (Figure 4-2)

    Figure 4-2 Deploying the Composite on SOA Managed Server

    Description of Figure 4-2 follows
    Description of "Figure 4-2 Deploying the Composite on SOA Managed Server"

  5. On the Select Archive page, enter the following path to sca_CommunityWorkflows_rev1.0.jar:

    SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows_rev1.0.jar

    Figure 4-3 Deploying the Composite - Select Archive Page

    Description of Figure 4-3 follows
    Description of "Figure 4-3 Deploying the Composite - Select Archive Page"

  6. Click Next.

  7. On the Select Target page, select the managed server to which you want to deploy the composite application. (Figure 4-4)

    Figure 4-4 Deploying the Composite - Select Target Page

    Description of Figure 4-4 follows
    Description of "Figure 4-4 Deploying the Composite - Select Target Page"

  8. Click Next.

  9. On the Confirmation page, select Deploy as default revision. (Figure 4-5)

    Figure 4-5 Deploying the Composite - Confirmation Page

    Description of Figure 4-5 follows
    Description of "Figure 4-5 Deploying the Composite - Confirmation Page"

  10. Click Deploy.

    After the composite is successfully deployed, a confirmation message is displayed. (Figure 4-6)

    Figure 4-6 Composite Deployed to an Oracle SOA Managed Server

    Description of Figure 4-6 follows
    Description of "Figure 4-6 Composite Deployed to an Oracle SOA Managed Server"

For more information about deploying, redeploying, and undeploying SOA applications, see the "Deploying SOA Composite Applications" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

4.7.2.2 Deploying WebCenterWorklistDetailApp.ear

To deploy the WebCenterWorklistDetailApp.ear application, you can use Oracle Enterprise Manager Fusion Middleware Control or WLST.

For information about deploying Java EE applications by using WLST, see the "Deploying Applications" chapter in the Oracle Fusion Middleware Administrator's Guide.

To deploy WebCenterWorklistDetailApp.ear by using Fusion Middleware Control:

  1. Log on to Fusion Middleware Control as an administrator.

  2. Under WebLogic Domain, right-click the SOA domain, select Application Deployment, and then select Deploy.

  3. On the Select Archive page, enter the path to WebCenterWorklistDetailApp.ear. (Figure 4-7)

    You can find the application at the following location in your Oracle SOA installation:

    SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear

    Figure 4-7 Specifying the Path to WebCenterWorklistDetailApp.ear

    Description of Figure 4-7 follows
    Description of "Figure 4-7 Specifying the Path to WebCenterWorklistDetailApp.ear "

  4. On the Select Target page, select the Oracle SOA managed server. (Figure 4-8)

    Figure 4-8 Selecting Target Server

    Description of Figure 4-8 follows
    Description of "Figure 4-8 Selecting Target Server"

  5. Click Next.

  6. On the Application Attributes page, click Next. (Figure 4-9)

    Figure 4-9 Specifying Application Attributes

    Description of Figure 4-9 follows
    Description of "Figure 4-9 Specifying Application Attributes"

  7. On the Deployment Settings page, click Deploy. (Figure 4-10)

    Figure 4-10 Deploying WebCenterWorklistDetailApp.ear

    Description of Figure 4-10 follows
    Description of "Figure 4-10 Deploying WebCenterWorklistDetailApp.ear"

    After the composite is successfully deployed, a confirmation message is displayed and the application is shown in the Application Deployments tab.

    Figure 4-11 Deployed EAR Application

    Description of Figure 4-11 follows
    Description of "Figure 4-11 Deployed EAR Application"

4.7.3 Oracle SOA and Oracle WebCenter - WS-Security Configuration

WebCenter Spaces workflows deployed to the SOA server invoke the WebCenter Spaces Web Services deployed to Oracle WebCenter. To secure the Web Services call, you must set up security on Oracle SOA and Oracle WebCenter. This involves performing the following tasks:

4.7.4 Oracle WebCenter - BPEL Server Connections

To enable WebCenter Spaces workflows on WebCenter Spaces, a connection to the BPEL server hosting the workflows is required. For information, see the "Specifying the BPEL Server Hosting WebCenter Spaces Workflows" sections in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

See also, the "Registering Worklist Connections" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4.8 Configuring an LDAP-Based Identity Store

By default, WebCenter applications are configured to use a file-based embedded LDAP identity store for storing application-level user IDs, and a file-based LDAP policy store to store policy grants. Although secure, the embedded LDAP identity store is not a "production-class" store and should be replaced with an external LDAP-based identity store, such as Oracle Internet Directory, for enterprise production environments. Further, the default file-based policy store can only be used for single-node WebCenter configurations. For multi-node configurations, you must reassociate the policy and credential store with an external LDAP-based identity store. For information about how to install Oracle Identity Management, see Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

Note:

You can configure WebCenter Spaces applications and back-end components for WebCenter Web 2.0 Services to use a shared LDAP-based identity store. If you configure a shared LDAP-based identity store, then WebCenter Spaces application and the back-end components for WebCenter Web 2.0 Services must share the same LDAP-based identity store.

Table 4-2 lists the various back-end components that can be configured for Oracle WebCenter and specifies the out-of-the-box identity store support available for these components. The table also lists the LDAP configuration links where you can find information about how to configure a shared LDAP-based identity store for these back-end components.

Table 4-2 Links for Configuring a Shared LDAP-Based Identity Store

Back-End Component Out-Of-The-Box Support LDAP Configuration Links

Oracle WebCenter Discussions

Database

For information, see the "Securing the Discussions Server with WS-Security" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

WebCenter Spaces

Embedded LDAP store

For information, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Oracle WebCenter Wiki and Blog Server

Embedded LDAP store

For information, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Oracle Content Server

Database

Oracle Content Server must be configured to use the same LDAP identity store as Oracle WebCenter.

For information, see the:

Oracle SES

None

For information about configuring LDAP, see the "Security in Oracle Secure Enterprise Search" chapter in the Oracle Secure Enterprise Search Administrator's Guide. This guide is available in the Oracle Secure Enterprise Search Online Documentation Library 10g Release 1 (10.1.8.2). You can download the documentation library from the following URL on OTN:

http://www.oracle.com/technology/documentation/ses.html

Oracle SOA Suite (BPEL)

Embedded LDAP store

For information about configuring LDAP, see the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

For more information about configuring an identity store, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.