1. Integrating and Extending Oracle Content Management
  2. Enabling Oracle Content Management Integrations
  3. Use Content Connectors
  4. Configure Oracle WebCenter Content Server and Oracle Content Management for the WCC Connector v2.0

Configure Oracle WebCenter Content Server and Oracle Content Management for the WCC Connector v2.0

An Administrator can register and configure Oracle WebCenter Content (WCC) and Oracle Content Management for the WCC connector v2.0 so site users can pull content from the WebCenter Content server into their sites.

The following topics describe the WebCenter Content connector v2.0 and how to use it:

Verify Network Accessibility for a WCC Connector v2.0

The communication between Oracle Content Management and WebCenter Content Server takes place over JAX-WS protocol, so the Oracle Content Management instance and WebCenter Content Server need to be on the same network for them to work together.

  • For the Oracle Content Management public cloud, the WebCenter Content Server should be accessible from the Public networks.
  • For the Oracle Content Management private cloud, the WebCenter Content Server should be accessible from that private network.

Check WebCenter Content Server Readiness

Enable SSL

The Oracle Content Server should be accessible over HTTPS protocol.

Access the content server sign-in page using the following URL, which will render the sign-in page in the browser:

Login Page: https://<host_name>:<port>/cs/login/login.htm


Description of enable-ssl.png follows
Description of the illustration enable-ssl.png

Enable Jax-WS

JAX-WS should be enabled on Oracle Content Server for the connector to work. This is the basic prerequisite.

JAX-WS should be enabled on Oracle Content Server for the connector to work. This is the basic prerequisite. To verify this, access the content server instance using the following URL. This will render the WSDL in the browser.

https://<host_name>:<port>/idcnativews/IdcWebLoginPort?WSDL

Set Up a Security Policy

We will communicate with the WebCenter Content Server using the JAX-WS communication channel. The JAX-WS endpoints must be secured using the OWSM policies.

We will use the oracle/wss_username_token_over_ssl_service_policy server-side policy. Any client that communicates with the WebCenter Content Server must enter both a user name and a password. If these values are incorrect, then the handshake with the WebCenter Content Server will not be established.

Take the following steps to configure the server-side policy:

  1. Check the OWSM policy attached to JAX-WS.

    To check the policy attached, access https://<host_name>:<port>/idcnativews/IdcWebLoginPort?WSDL. You should see the policy name in the URI attribute of the <wsp:PolicyReference> field in the WSDL. 

    <binding name="IdcWebLoginSoapHttp" type="tns:IdcWebLogin">
  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  <wsp:PolicyReference xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#wss_username_token_over_ssl_service_policy" wsdl:required="false"/>
  2. If the attached policy is oracle/wss_username_token_over_ssl_service_policy, then ignore the steps that follow.
    Description of wcc-enterprise-manager.png follows
    Description of the illustration wcc-enterprise-manager.png
  3. If the attached policy is a different one, then first detach that policy, and then attach the policy oracle/wss_username_token_over_ssl_service_policy. The steps to attach or detach a policy follow. If no policy is attached, then follow the steps.
    Description of ucm-web-services.png follows
    Description of the illustration ucm-web-services.png

Take the following steps to Attach an OWSM Policy:

  1. Go to the WebCenter Content Server Enterprise Manager:
    http://<host_name>:<port>/em
    Sign in with your administrator credentials (weblogic/<password>)
  2. On the Target Navigation page, choose Application Deployments -> Oracle UCM Native Web Services -> oracle UCM Native Web Service(UCM_Server1).
  3. Choose Application Deployment -> Web Services.
  4. On the IdcWebLoginPort (Web Services Endpoint) page, click Attach/Detach Policies.
    Description of attach-detach-policies.png follows
    Description of the illustration attach-detach-policies.png
  5. In the directly attached policies section, if there is any policy other than oracle/wss_username_token_over_ssl_service_policy attached, first detach it. Then attach the oracle/wss_username_token_over_ssl_service_policy policy:
    1. Click the policy whose category is Security, select it, and then click Detach.

      Notice that this policy will go away from the Directly Attached Policies list.


      Description of detach-policy.png follows
      Description of the illustration detach-policy.png
    2. Attach the oracle/wss_username_token_over_ssl_service_policy.

      Under Available Policies, search for oracle/wss_username_token_over_ssl_service_policy. In the result section, select oracle/wss_username_token_over_ssl_service_policy, and then click the Attach button.


      Description of attach-policy.png follows
      Description of the illustration attach-policy.png
  6. Verify that oracle/wss_username_token_over_ssl_service_policy is under Directly Attached Policies, click Validate, and then click OK. After the popup closes, click the Return button. No restart is required.
    Description of validate-policy.png follows
    Description of the illustration validate-policy.png
  7. Access https://<host_name>:<port>/idcnativews/IdcWebLoginPort?WSDL.

    You should see the policy oracle/wss_username_token_over_ssl_service_policy being attached to the IdcWebLoginPort in the wsu:Id attribute of the <wsp:Policy> field. This confirms that the policy is attached correctly. 

    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" 
xmlns:tns="http://idcnativews.webservices.idcservlet/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="IdcWebLoginService" 
targetNamespace="http://idcnativews.webservices.idcservlet/">
  <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns="http://schemas.xmlsoap.org/ws/2004/09/policy" 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" wsu:Id="wss_username_token_over_ssl_service_policy">
  8. Also, verify that the https://<host_name>:<port>/idcws/GenericSoapPort?WSDL wsdl loads successfully.

Run the Indexer and File Formats Wizard

To complete the configuration of an Oracle WebCenter Content server, you need to run the Indexer for search results and the File Formats Wizard for IBR configuration.

It is mandatory to run the Indexer for a search to return results. Choose Administration → Admin Applets → Repository Manager → Indexer.

To show thumbnail for documents in the Oracle WebCenter Content v2.0 file picker window in Oracle Content Management, IBR must be configured for Oracle WebCenter Content Server. Choose Administration -> Refinery Administration -> File Formats Wizard.


Description of file-formats-wizard.png follows
Description of the illustration file-formats-wizard.png

Check Oracle Content Management Readiness

The WebCenter Content connector v 2.0 is deployed on an Oracle Content Management (OCM) managed server and can be accessed using the context root: /cec-connector/wccontent

Note:

The basic access authentication does not work for federated users. If that's the case, use token authentication to access the connector.
Basic authentication

To verify the deployment, go to the following link in the browser:

http://<host>:<port>/cec-connector/wccontent/rest/api
This gives the following response, which indicates the connector is deployed properly:
["v1"]
Token authentication
  1. Log into the OCM service: https://<host>:<port>/documents in your web browser.
  2. Once you're logged in, open another tab and go to this endpoint to get the token value from the response as shown in your browser.
    https://<host>:<port>/documents/web?IdcService=GET_OAUTH_TOKEN
  3. Use the Bearer token value retrieved in step 2 to make a request to the connector endpoint:
    GET https://<host>:<port>/cec-connector/wccontent/rest/api

    Make sure to include the authorization field in your header as shown below:

    Authorization: Bearer <tokenValue>

Configure the Oracle WebCenter Content Connector v2.0

Before you start using the Oracle WebCenter Content Connector v2.0 in an Oracle Content Management instance, the connector needs to be registered, configured, and enabled on the Oracle Content Management side.

To configure Oracle WebCenter Content Connector v2.0 for Oracle Content Management:

  1. Sign in to Oracle Content Management as an administrator.
  2. Go to Administration > Integrations > Content Connectors, locate the out-of-the-box connector Oracle WebCenter Content v2.0, and click Enable next to it.
    Description of webcenter-content-fields.png follows
    Description of the illustration webcenter-content-fields.png
  3. Enter a description and select the Allow asset type creation and Enable for end-users checkboxes.
  4. Enter details for Additional Fields:
    • WebCenter Content JAX-WS Connection URI: http://<host_name>:<port>/idcnativews
    • WebCenter Content Server JAX-WS Client Policy: oracle/wss_username_token_over_ssl_client_policy
    • WebCenter Content Server Web Context Root: /cs (This depends on Content Server setup.)
  5. Click Save.

Specify WebCenter Content Connector v2.0 Mappings

Selection of the Allow asset type creation option for Oracle WebCenter Content Connector v2.0 creates a WebCenter-Content-DigitalAsset asset asset type in Oracle Content Management by the administration user who is configuring the connector.


Description of wcc-mappings.png follows
Description of the illustration wcc-mappings.png

You can view the asset type on the Administration > Content > Asset Types page.


Description of asset-types.png follows
Description of the illustration asset-types.png

As an administrator for the asset repository, you can specify mappings for the connector type.

Enable Oracle WebCenter Content Connector v2.0 for an Asset Repository

Once the connector is configured and enabled, we need to enable it for the asset repository.

Selecting the connector automatically adds the associated asset type to the repository.

Description of wcc-edit-repository.png follows
Description of the illustration wcc-edit-repository.png

Use Oracle WebCenter Content Connector v2.0

To use Oracle WebCenter Content Connector v2.0, follow these steps:

  1. Go to the asset repository for which you have configured the connector, and click Add > Import from Oracle WebCenter Content v2.0

    This launches a WebCenter Content Sign In dialog.

    Description of wcc-sign.png follows
    Description of the illustration wcc-sign.png
  2. Enter your WebCenter Content Server credentials.

    These credentials will be securely stored on Oracle Content Management and can be reused for subsequent access. To clear the credentials, go to Add > Manage Sources > Connector > Revoke.

    After your credentials are authenticated, you will see a connector-picker dialog that lists content from the content server.

    Description of connector-picker-dialog.png follows
    Description of the illustration connector-picker-dialog.png
  3. Browse through the files and folders. You can also use search for specific items. Additionally, you can choose to view the listing in various layouts, like card, compact, and list.
    Description of files-and-folders.png follows
    Description of the illustration files-and-folders.png

    The dialog also supports pagination for a large number of files and folders. Select the file or files you are interested in, and click Ok.

  4. You can add to the asset repository. An intermediate dialog lists the files to be added and lets you choose the collection and channels. You can also specify tags for the content you are adding. Click Add.

    Once Add is successful, assets are added in the asset repository.


    Description of digital-assets.png follows
    Description of the illustration digital-assets.png

    The following image shows the assets and its attributes imported into Oracle Content Management.


    Description of asset-attribute.png follows
    Description of the illustration asset-attribute.png

Map to a Custom Asset Type

To map a custom asset type, you can reuse an existing asset type or create a new one and do the necessary mapping in the connector configuration screen.

For example, suppose we were to register a new Oracle WebCenter Content v2 connector for another WebCenter Content instance we want to wire to. We deselect Allow Content type creation and choose to use other asset type in the Oracle Content Management and perform the necessary mappings of the listed attributes.


Description of asset-data-fields.png follows
Description of the illustration asset-data-fields.png

Revoke Authorized Users

Once you provide the user credentials, they are stored in Oracle Content Management and passed to the connector during subsequent usage, which means the login challenge will not be given all the time.

If you need to sign in as a different user, then the signed-in authorized user needs to be revoked. To revoke an authorized user:

  1. Click Assets → Add → Manage Sources.
  2. Click Revoke next to a user name.
  3. Click OK to revoke the user.