Skip Headers
Oracle® Fusion Middleware WebCenter Sites: Installing and Configuring Supporting Software
11g Release 1 (11.1.1.8.0)

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

Go to previous page
Previous
PDF · Mobi · ePub

25 Integrating Oracle Access Manager with Oracle WebCenter Sites: Site Capture

If your WebCenter Sites installation is not using the Central Authentication Service (CAS) web application for authentication and single sign-on, follow the instructions in this chapter to integrate Oracle Access Manager (OAM) with the WebCenter Sites: Site Capture application.

This chapter contains the following sections:

25.1 Prerequisites

Before integrating Oracle Access Manager (OAM) with the Site Capture application, ensure that you have integrated OAM with WebCenter Sites. For instructions, see Chapter 23, "Integrating Oracle Access Manager with Oracle WebCenter Sites."

25.2 Configuring Oracle Access Manager for Integration with Site Capture

This section contains the following topics:

25.2.1 Adding Resources to Oracle Access Manager

Create the resource definitions listed in Table 25-1 for the WebCenter Sites application domain. These definitions are in addition to the resource definitions that were created during OAM integration with WebCenter Sites.

Table 25-1 Resources

Resource URL Protection Level Authentication Authorization

/<sites-context>/REST/roles

Unprotected

Public

All Allowed

/<sites-context>/custom/customCsResolver.jsp

Unprotected

Public

All Allowed

/resources/.../*

Excluded

   

25.2.2 Adjusting the root-context.xml File

The Site Capture application ships with the following files:

  • root-context.xml

  • oam_root-context.xml

By default, the Site Capture application uses the root-context.xml file. Before deploying the Site Capture installation, you must adjust the root-context.xml file.

To adjust the root-context.xml file for the Site Capture application

  1. Back up the root-context.xml file and then rename the file to root-context.xml.bak.

  2. Rename oam_root-context.xml file to root-context.xml file.

  3. Replace the tokens in Table 25-2 in the root-context.xml file (created in step 2):

    Table 25-2 Tokens in the root-context.xml file

    Token Description Example

    {ohs_host}

    Host of Oracle HTTP Server used for proxying requests to WebCenter Sites

    ohs.example.com

    {ohs_port}

    Port of Oracle HTTP Server used for proxying requests to WebCenter Sites

    7777

    {sites_context_root}

    Context root of WebCenter Sites application

    servlet

    {wl_oamtoken_host}

    Host of the WebLogic managed server where the oamtoken application is deployed

    oamtoken.example.com

    {wl_oamtoken_port}

    Port of WebLogic managed server where the oamtoken application is deployed

    8003

    {wl_oamserver_host}

    Host of the WebLogic managed server where the OAM application is deployed

    oam.example.com

    {wl_oamserver_port}

    Port of the WebLogic managed server where the OAM application is deployed

    14100

    {username}

    User name with authority to read the WebCenter Sites SystemUser table

    fwadmin

    {password}

    Above user's password

    xceladmin


  4. Deploy the Site Capture ROOT.war file. For instructions, see the section "Deploying Site Capture" in the Oracle Fusion Middleware WebCenter Sites Installation Guide.