The socket protocol communicates to Oracle WebCenter Content Server over the Intradoc socket port.

1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Portal.
2. From the WebCenter Portal menu, select Settings and then Service Configuration.
3. On the WebCenter Portal Services Configuration page, from the list of services select Content Repository.
4. Click Add.
5. In the Connection Name field, enter a unique name for the WebCenter Content Server connection.

   Tip:

   The name must be unique (across all connection types) within WebCenter Portal.

6. The Repository Type is Oracle Content Server.
7. Select Active Connection to make this the default WebCenter Content Server connection for WebCenter Portal.

   You can create connections to multiple WebCenter Content Server instances; all connections are used. One connection must be the default connection. The default connection is the one used by WebCenter Portal to store portal-related documents.

   If this is the default connection for WebCenter Portal, some additional configuration is required. For more information, see Setting Connection Properties for the Default Oracle WebCenter Content Server Connection Using Fusion Middleware Control.

   Note:

   Deselecting this option does not disable the connection. If a connection is no longer required, you must delete the connection.

8. From the RIDC Socket Type dropdown list, select Socket.
9. In the Server Host field, enter the host name of the machine where WebCenter Content Server is running.

   For example: mycontentserver.example.com.

10. In the Server Port field, enter the port specified for the WebCenter Content Server’s incoming provider.

    This property corresponds to the IntradocServerPort setting in the WebCenter Content Server configuration file, which defaults to 4444.

    Tip:

    You can find the current value by logging into WebCenter Content Server and navigating to Administration > Admin Server > General Configuration > Additional Configuration Variables > IntradocServerPort.

11. In the Connection Timeout field, enter the length of time (in milliseconds) to attempt to log in to WebCenter Content Server before issuing a connection timeout message.

    This value is also used as the socket timeout for the underlying RIDC connection for all service requests.

    If the Connection Timeout is not set, the following values are used:

    • Login timeout — the default concurrency timeout configured for the oracle.webcenter.content resource (30 seconds or 30000 milliseconds).

    • RIDC socket timeout — the default RIDC socket timeout (60 seconds or 60000 milliseconds).

    Tip:

    It is recommended that you do not specify a value less than 60000 milliseconds for the Connection Timeout, as this would reduce the RIDC socket timeout and increase the likelihood that long running requests time out. For example, timeouts may occur during long running searches, long file uploads, or long copy operations.

12. From the Authentication Method dropdown list, select:

    • Identity Propagation if WebCenter Content Server uses the same identity store as WebCenter Portal to authenticate users.

      If you select this option, you must also specify the appropriate Web Server context root for Content Server.

    • External Application if WebCenter Content Server uses an external application to authenticate users. Select this option if you want to use public, shared, or mapped credentials.

      If you select this option, you must also specify the appropriate Associated External Application.

13. (Only if Authentication Method is Identity Propagation) In the Web Server context root for Content Server field, enter the web server context root for WebCenter Content Server if WebCenter Content Server is front-ended with Oracle HTTP Server (OHS).

    Use the format /contextRoot. For example, /cs.

    Oracle recommends that you access WebCenter Portal through Oracle HTTP Server (OHS) if you want to use Content Presenter to create or edit Site Studio content. Without Oracle HTTP Server (and WebContextRoot configuration), it is still possible to create or edit Site Studio content from within Content Presenter, but the create and edit actions launch new browser windows (or tabs) rather than opening within the Content Presenter task flow.

14. (Only if Authentication Method is External Application) From the Associated External Application dropdown list, select the application to use to authenticate users with WebCenter Content Server.

    Tip:

    If the application has not yet been registered with WebCenter Portal, select Create New to register it now. For more information, see Registering External Applications Using Fusion Middleware Control.

15. In the Administrator User Name field, enter the user name of a user with administrative rights for this WebCenter Content Server instance. For example, wccadmin.

    This user is used to fetch content type information based on profiles and track document changes for cache invalidation purposes.

16. In the Administrator Password field, enter the password for the user specified in the Administrator User Name field.
17. In the Cache Invalidation Interval field, enter the time (in minutes) to allow between checks for external WebCenter Content Server content changes.

    WebCenter Portal automatically clears items that have changed from the cache. The minimum interval is 2 minutes.

    By default, cache invalidation is disabled so no periodic check is made for content changes (shown as 0).

18. In the Maximum Cached Document Size, enter a maximum cacheable size (in bytes) for WebCenter Content Server binary documents.

    Documents larger than this size are not cached by WebCenter Portal.

    The default is 102400 bytes (100KB).

    Tip:

    Tune this value based on your machine’s memory configuration and the types of binary documents that you expect to cache. Be aware that, unless Coherence is enabled, there is no maximum total size for the cache.

    If you are using Coherence, you can additionally specify the total amount of memory to be used for binary caches. For this reason, using Coherence for any type of production environment is strongly recommended, and is a requirement for High Availability (HA) environments.

    Note:

    Most documents stored in WebCenter Content Server are considered binary content, that is, images, plain text, Word documents, and so on. The only exception is Site Studio content, which is stored in CDF data files and cached separately in a Virtual Content Repository (VCR) cache (or node cache).

19. Click Test to verify if the connection you created works.
20. Click OK to save the connection.
21. To start using the connection, you must restart the managed server on which WebCenter Portal is deployed (WC_Portal by default).

The socket protocol communicates to Oracle WebCenter Content Server over the Intradoc socket port. The socket-based communication can also be configured to run over SSL to provide extra security.

1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Portal.
2. From the WebCenter Portal menu, select Settings and then Service Configuration.
3. On the WebCenter Portal Services Configuration page, from the list of services select Content Repository.
4. Click Add.
5. In the Connection Name field, enter a unique name for the WebCenter Content Server connection.

   Tip:

   The name must be unique (across all connection types) within WebCenter Portal.

6. The Repository Type is Oracle Content Server.
7. Select Active Connection to make this the default WebCenter Content Server connection for WebCenter Portal.

   You can create connections to multiple WebCenter Content Server instances; all connections are used. One connection must be the default connection. The default connection is the one used by WebCenter Portal to store portal-related documents.

   If this is the default WebCenter Content Server connection for WebCenter Portal, some additional configuration is required. For more information, see Setting Connection Properties for the Default Oracle WebCenter Content Server Connection Using Fusion Middleware Control.

   Note:

   Deselecting this option does not disable the connection. If a connection is no longer required, you must delete the connection.

8. From the RIDC Socket Type dropdown list, select Socket SSL.
9. In the Server Host field, enter the host name of the machine where WebCenter Content Server is running.

   For example: mycontentserver.example.com.

10. In the Server Port field, enter the port specified for the WebCenter Content Server’s sslincoming provider.

    This property corresponds to the IntradocServerPort setting in the WebCenter Content Server configuration file, which defaults to 4444.

    Tip:

    You can find the current value by logging into WebCenter Content Server and navigating to Administration > Admin Server > General Configuration > Additional Configuration Variables > IntradocServerPort.

11. In the Connection Timeout field, enter the length of time (in milliseconds) to attempt to log in to WebCenter Content Server before issuing a connection timeout message.

    This value is also used as the socket timeout for the underlying RIDC connection for all service requests.

    If the Connection Timeout is not set, the following values are used:

    • Login timeout — the default concurrency timeout configured for the oracle.webcenter.content resource (30 seconds or 30000 milliseconds).

    • RIDC socket timeout — the default RIDC socket timeout (60 seconds or 60000 milliseconds).

    Tip:

    It is recommended that you do not specify a value less than 60000 milliseconds for the Connection Timeout, as this would reduce the RIDC socket timeout and increase the likelihood that long running requests time out. For example, timeouts may occur during long running searches, long file uploads, or long copy operations.

12. From the Authentication Method dropdown list, select:

    • Identity Propagation if WebCenter Content Server uses the same identity store as WebCenter Portal to authenticate users.

      If you select this option, you must also specify the appropriate Web Server context root for Content Server.

    • External Application if WebCenter Content Server uses an external application to authenticate users. Select this option if you want to use public, shared, or mapped credentials.

      If you select this option, you must also specify the appropriate Associated External Application.

13. (Only if Authentication Method is Identity Propagation) In the Web Server context root for Content Server field, enter the web server context root for WebCenter Content Server if WebCenter Content Server is front-ended with Oracle HTTP Server (OHS).

    Use the format /contextRoot. For example, /cs.

    Oracle recommends that you access WebCenter Portal through Oracle HTTP Server (OHS) if you want to use Content Presenter to create or edit Site Studio content. Without Oracle HTTP Server (and WebContextRoot configuration), it is still possible to create or edit Site Studio content from within Content Presenter, but the create and edit actions launch new browser windows (or tabs) rather than opening within the Content Presenter task flow.

14. (Only if Authentication Method is External Application) From the Associated External Application dropdown list, select the application to use to authenticate users with WebCenter Content Server.

    Tip:

    If the application has not yet been registered with WebCenter Portal, select Create New to register it now. For more information, see Registering External Applications Using Fusion Middleware Control.

15. In the Administrator User Name field, enter a user name with administrative rights for this WebCenter Content Server instance. For example, wccadmin.

    This user is used to fetch content type information based on profiles and track document changes for cache invalidation purposes.

16. In the Administrator Password field, enter the password for the user specified in the Administrator User Name field.
17. In the Key Store Location field, enter the location of the keystore that contains the private key used to sign the security assertions.

    The keystore location must be an absolute path.

    For example, D:\keys\keystore.xyz.

18. In the Key Store Password field, enter the password required to access the keystore.

    For example, T0PS3CR3T.

19. In the Private Key Alias field, enter the client private key alias in the keystore.

    The public key corresponding to this private key must be imported in the server keystore.

    Ensure that the alias does not contain special characters or white space.

    For example, enigma.

20. In the Private Key Password field, enter the password to use with the private key alias in the keystore.

    For example, c0d3bR3ak3R.

21. In the Cache Invalidation Interval field, enter the time (in minutes) to allow between checks for external WebCenter Content Server content changes.

    WebCenter Portal automatically clears items that have changed from the cache. The minimum interval is 2 minutes.

    By default, cache invalidation is disabled so no periodic check is made for content changes (shown as 0).

22. In the Maximum Cached Document Size, enter a maximum cacheable size (in bytes) for WebCenter Content Server binary documents.

    Documents larger than this size are not cached by WebCenter Portal.

    The default is 102400 bytes (100KB).

    Tip:

    Tune this value based on your machine’s memory configuration and the types of binary documents that you expect to cache. Be aware that, unless Coherence is enabled, there is no maximum total size for the cache.

    If you are using Coherence, you can additionally specify the total amount of memory to be used for binary caches. For this reason, using Coherence for any type of production environment is strongly recommended, and is a requirement for High Availability (HA) environments.

    Note:

    Most documents stored in WebCenter Content Server are considered binary content, that is, images, plain text, Word documents, and so on. The only exception is Site Studio content, which is stored in CDF data files and cached separately in a Virtual Content Repository (VCR) cache (or node cache).

23. Click Test to verify if the connection you created works.
24. Click OK to save the connection.
25. To start using the connection, restart the managed server on which WebCenter Portal is deployed (WC_Portal by default).

With JAX-WS, Oracle WebCenter Portal must authenticate with Oracle WebCenter Content Server for each connection rather than assuming any connection from WebCenter Portal is automatically a trusted connection.

1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Portal.
2. From the WebCenter Portal menu, select Settings and then Service Configuration.
3. On the WebCenter Portal Services Configuration page, from the list of services select Content Repository.
4. Click Add.
5. In the Connection Name field, enter a unique name for the WebCenter Content Server connection.

   Tip:

   The name must be unique (across all connection types) within WebCenter Portal.

6. The Repository Type is Oracle Content Server.
7. Select Active Connection to make this the default WebCenter Content Server connection for WebCenter Portal.

   You can create connections to multiple WebCenter Content Server instances; all connections are used. One connection must be the default connection. The default connection is the one used by WebCenter Portal to store portal-related documents.

   If this is the default content repository for WebCenter Portal, some additional configuration is required. For more information, see Setting Connection Properties for the Default Oracle WebCenter Content Server Connection Using Fusion Middleware Control.

   Note:

   Deselecting this option does not disable the connection. If a connection is no longer required, you must delete the connection.

8. From the RIDC Socket Type dropdown list, select JAX-WS.
9. In the Web Service URL field, enter the web service URL required to connect to WebCenter Content Server when using the JAX-WS protocol.

   Use the format http://host:port/webRoot

   For example, http://myhost.com:9044/idcnativews

10. In the Client Security Policy field, enter the client security policy to use.

    For example, oracle/wss10_saml_token_client_policy

    The JAX-WS client security policy can be any valid OWSM policy, but must match the security policy configured for WebCenter Content Server’s Native Web Services IdcWebLogin service.

    Tip:

    Leave this field blank if your environment supports Global Policy Attachments (GPA).

11. In the Connection Timeout field, specify the length of time (in milliseconds) to attempt to log in to WebCenter Content Server before issuing a connection timeout message.

    If the Connection Timeout is not set, the default concurrency timeout configured for the oracle.webcenter.content resource is used (30 seconds or 30000 milliseconds).

12. In the Administrator User Name field, enter a user name with administrative rights for this WebCenter Content Server instance. For example, wccadmin.

    This user is used to fetch content type information based on profiles and track document changes for cache invalidation purposes.

13. In the Administrator Password field, enter the password for the user specified in the Administrator User Name field.
14. In the Cache Invalidation Interval field, enter the time (in minutes) to allow between checks for external WebCenter Content Server content changes.

    WebCenter Portal automatically clears items that have changed form the cache. The minimum interval is 2 minutes.

    By default, cache invalidation is disabled so no periodic check is made for content changes (shown as 0).

15. In the Maximum Cached Document Size, enter a maximum cacheable size (in bytes) for WebCenter Content Server binary documents.

    Documents larger than this size are not cached by WebCenter Portal.

    The default is 102400 bytes (100KB).

    Tip:

    Tune this value based on your machine’s memory configuration and the types of binary documents that you expect to cache. Be aware that, unless Coherence is enabled, there is no maximum total size for the cache.

    If you are using Coherence, you can additionally specify the total amount of memory to be used for binary caches. For this reason, using Coherence for any type of production environment is strongly recommended, and is a requirement for High Availability (HA) environments.

    Note:

    Most documents stored in WebCenter Content Server are considered binary content, that is, images, plain text, Word documents, and so on. The only exception is Site Studio content, which is stored in CDF data files and cached separately in a Virtual Content Repository (VCR) cache (or node cache).

16. Click Test to verify if the connection you created works.
17. Click OK to save the connection.
18. To start using the connection, restart the managed server on which WebCenter Portal is deployed (WC_Portal by default).

Using the HTTPClient package, RIDC communicates with the web server attached to Oracle WebCenter Content Server.

1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Portal.
2. From the WebCenter Portal menu, select Settings and then Service Configuration.
3. On the WebCenter Portal Services Configuration page, from the list of services select Content Repository.
4. Click Add.
5. In the Connection Name field, enter a unique name for the WebCenter Content Server connection.

   Tip:

   The name must be unique (across all connection types) within WebCenter Portal.

6. The Repository Type is Oracle Content Server.
7. Do not select Active Connection.

   The HTTP protocol does not allow identity propagation, therefore it is not suitable to use for the default WebCenter Content Server connection for WebCenter Portal. That is, you should not use this protocol to connect to the back-end WebCenter Content Server repository that is being used to store portal-related documents.

8. From the RIDC Socket Type dropdown list, select Web.
9. In the Web URL field, enter the web server URL for WebCenter Content Server.

   Use the format http://host:port/webRoot/pluginRoot.

   For example, http://mycontentserver/cms/idcplug

   .
10. In the Connection Timeout field, specify the length of time (in milliseconds) to attempt to log in to WebCenter Content Server before issuing a connection timeout message.

    This value is also used as the socket timeout for the underlying RIDC connection for all service requests.

    If the Connection Timeout is not set, the following values are used:

    • Login timeout — the default concurrency timeout configured for the oracle.webcenter.content resource (30 seconds or 30000 milliseconds).

    • RIDC socket timeout — the default RIDC socket timeout (60 seconds or 60000 milliseconds).

    Tip:

    It is recommended that you do not specify a value less than 60000 milliseconds for the Connection Timeout, as this would reduce the RIDC socket timeout and increase the likelihood that long running requests time out. For example, timeouts may occur during long running searches, long file uploads, or long copy operations.

11. From the Associated External Application dropdown list, select the application to use to authenticate users with WebCenter Content Server.

    Tip:

    If the application has not yet been registered with WebCenter Portal, select Create New to register it now. For more information, see Registering External Applications Using Fusion Middleware Control.

12. In the Administrator User Name field, enter a user name with administrative rights for this WebCenter Content Server instance. For example, wccadmin.

    This user is used to fetch content type information based on profiles and track document changes for cache invalidation purposes.

13. In the Administrator Password field, enter the password for the user specified in the Administrator User Name field.
14. In the Cache Invalidation Interval field, enter the time (in minutes) to allow between checks for external WebCenter Content Server content changes.

    WebCenter Portal automatically clears items that have changed form the cache. The minimum interval is 2 minutes.

    By default, cache invalidation is disabled so no periodic check is made for content changes (shown as 0).

15. In the Maximum Cached Document Size, enter a maximum cacheable size (in bytes) for WebCenter Content Server binary documents.

    Documents larger than this size are not cached by WebCenter Portal.

    The default is 102400 bytes (100KB).

    Tip:

    Tune this value based on your machine’s memory configuration and the types of binary documents that you expect to cache. Be aware that, unless Coherence is enabled, there is no maximum total size for the cache.

    If you are using Coherence, you can additionally specify the total amount of memory to be used for binary caches. For this reason, using Coherence for any type of production environment is strongly recommended, and is a requirement for High Availability (HA) environments.

    Note:

    Most documents stored in WebCenter Content Server are considered binary content, that is, images, plain text, Word documents, and so on. The only exception is Site Studio content, which is stored in CDF data files and cached separately in a Virtual Content Repository (VCR) cache (or node cache).

16. Click OK to save the connection.
17. Click Test to verify if the connection you created works.
18. To start using the connection, restart the managed server on which WebCenter Portal is deployed (WC_Portal by default).

FrameworkFolders provides a hierarchical folder interface similar to a conventional file system, for organizing and locating some or all of the content in Oracle WebCenter Content Server. In addition, it enables you to use WebCenter Content Server mobile applications to access content in portals and leverage the ADF content UI.

1. Log on to WebCenter Content Server as an administrator.
2. From the Main menu, choose Administration, then Admin Server, then Component Manager.
3. On the Component Manager page, select the FrameworkFolders check box.
4. Click Update.
5. Click Advanced Component Manager.
6. On the Advanced Component Manager page, ensure that:

   • FrameworkFolders is listed in the Enabled Components section

   • Folders_g is listed in the Disabled Components section

7. Restart the WebCenter Content Server instance.

You must enable the WebCenterConfigure component to configure Oracle WebCenter Content Server for Oracle WebCenter Portal.

1. Log on to WebCenter Content Server as an administrator.
2. From the Main menu, choose Administration, then Admin Server, then Component Manager.
3. On the Component Manager page, select the WebCenterConfigure check box.

   Tip:

   On the Component Manager page, you can choose to select other components like Digital Asset if you plan to use them as you'll otherwise need to enable them later.

4. Click Update.
5. Click Advanced Component Manager.
6. On the Advanced Component Manager page, ensure that WebCenter Configure is listed in the Enabled Components section.
7. Restart the WebCenter Content Server instance.

Before Oracle WebCenter Content Server can send files to Inbound Refinery for conversion, you must set up an outgoing provider from WebCenter Content Server to the Inbound Refinery with the Handles Inbound Refinery Conversion Jobs option checked.

1. From the WebCenter Content Server Administration menu, select Providers.
2. In the Create a New Provider section of the Providers page, click Add in the outgoing row.
3. Enter values for these fields:

   • Provider Name: Any short name with no spaces describing the Inbound Refinery instance the outgoing provider is for. It is a good idea to use the same name as the Inbound Refinery Instance Name.

   • Provider Description: A description of the outgoing provider.

   • Server Host Name: The name of the host machine where the Inbound Refinery instance is running (for example, myhost.example.com).

   • HTTP Server Address: The address of the Inbound Refinery instance (for example, http://myhost.example.com:16250 where 16250 is the web port).

   • Server Port: The IntradocServerPort value for the Inbound Refinery instance. This value was entered on the post-installation configuration page, and can be found on the Inbound Refinery configuration information page under Server Port. You can also find it in the MW_HOME/user_projects/domains/ucm_domain/ucm/ibr/config/config.cfg file as IntradocServerPort.

     To display the Inbound Refinery configuration information page:

     1. Log in to WebCenter Content Server and choose Administration > Configuration for instanceName.

     2. Click Server Configurations to display the server configurations.

     Or log into the IBR at Administration > Admin Server > General Configuration.

   • Instance Name: The instance name for Inbound Refinery (the IDC_Name value in the config.cfg file). This value was entered on the post-installation configuration page as Server Instance Name. To find the instance name, log into the Inbound Refinery, and navigate to Administration -> Configuration for instanceName.

   • Relative Web Root: The web root of the Inbound Refinery instance (for example, /ibr/).

4. Under Conversion Options, check Handles Inbound Refinery Conversion Jobs. Do not check Inbound Refinery Read Only Mode.
5. Click Add.
6. Restart WebCenter Content Server.
7. Go back to the Providers page, and check that the Connection State value is good for the provider.

   If the value is not good, double-check that you entered all the preceding entries correctly, and check that the WebCenter Content Server and Inbound Refinery instances can ping each other.

To tell Oracle WebCenter Content Server which files to send to Inbound Refinery to be converted, you need to select the file formats.

1. From the WebCenter Content Server Administration menu, select Refinery Administration and then File Formats Wizard.

   Note:

   Refinery Administration is not listed when there is no valid outgoing provider to an Inbound Refinery instance.

   WebCenter Content Server displays the File Formats Wizard page. This page configures which file formats will be sent to Inbound Refinery for conversion when they are checked into WebCenter Content Server.

2. Select the file formats that you want to be converted.

   Make sure you check all the file types you want sent to Inbound Refinery for conversion. Do not check HTML, and also do not check wiki and blog unless you have enabled their conversion through the WebCenterConversions component as described in Enabling the Conversion of Wikis and Blogs into PDFs.

3. Click Update.

Enabling the conversion of wikis and blogs into PDFs requires you to first install the WebCenterConversions component, then configure OpenOffice, which converts HTML to PDF, in the Inbound Refinery server and Oracle WebCenter Content Server respectively.

1. Install the WebCenterConversion component:
   1. Log in to the Inbound Refinery server.
   2. Click Administration and then select Admin Server.
      The Inbound Refinery Admin Server page displays.
   3. In the Component Manager, click the advanced component manager link.
      The Advanced Component Manager page displays.
   4. In the Install New Component section, select the path to the WebCenterConversions.zip, then click Install.
      The WebCenterConversions.zip can be found under MW_HOME/wcportal/install/.
      The WebCenterConversion component displays in the Disabled Components box.
   5. Select WebCenterConversion and click Enable.
   6. Restart the Inbound Refinery server.
2. Enable Inbound Refinery to integrate with OpenOffice:
   1. Log in to the Inbound Refinery server again.
   2. Click Administration and then select Admin Server.
      The Inbound Refinery Admin Server page displays.
   3. In the Component Manager, select the OpenOfficeConversion check box.
   4. Restart the Inbound Refinery server.
3. Enable the WebCenterConversion component:
   1. In the Inbound Refinery server, under Conversion Settings, click the Conversion Listing link.
      This displays the Conversion Listing page.
   2. In the Conversions table, select the Accept check box for HtmToPDFOpenOffice, and click Update.
      The Wiki and Blog options will now appear in WebCenter Content Server's File Formats Wizard in the associated WebCenter Content Server instance.
4. Enable Wikis and Blogs to be converted to PDFs in WebCenter Content Server:
   1. Log in to WebCenter Content Server.
   2. Expand the Administration node, then Refinery Administration, and then click File Formats Wizard.
   3. Under Select File Types, select the Wiki and Blogs check boxes and click Update.
5. Enable the PDF conversion in Inbound Refinery:
   1. Log in to the Inbound Refinery server again.
   2. Select Conversion Settings, and then select Primary Web Rendition.
   3. Check the Convert to PDF using Open Office option.
   4. Click Update.

You can optionally set the maximum and minimum amount of time for which Inbound Refinery will process the different conversion operations.

1. Log on to the Inbound Refinery server.
2. Under Settings, select Timeouts.
3. Specify the minimum and maximum timeout settings for the various conversion operations as required.
4. Click Update.

If you want Site Studio to be displayed in Content Presenter using inline frames rather than in separate windows, and Oracle WebCenter Portal and Oracle WebCenter Content Server are not in the same domain (in terms of their web address), you must configure the Oracle HTTP Server (OHS).

1. Open the mod_wl_ohs.conf file and make sure it points to the right WebCenter Content Server instance.

   The default location of this file is: OHS_HOME/Oracle_WT1/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf

2. Update the connection property of the Content Server to webContextRoot='/cs'.

   Note:

   This setting should never be set if OHS is not set up or is not working correctly.

3. Configure OHS by updating the mod_wl_ohs.conf file with the WebCenter Content Server and adfAuthentication protected URI information.

   For example:

   <Location /cs>
   SetHandler weblogic-handler
   WeblogicHost example.com
   WeblogicPort 9400
   </Location>
   
   <Location /adfAuthentication>
   SetHandler weblogic-handler
   WeblogicHost example.com
   WeblogicPort 9400
   </Location>

   If your WebCenter Content Server is configured with the Oracle AutoVue VueLink servlet, include the additional entry:

   <Location /vuelink>
   SetHandler weblogic-handler
   WeblogicHost example.com  # Same as /cs entry
   WeblogicPort 9400    # Same as /cs entry
   </Location>

http://host:OHSPort/webcenter

http://my.example.com:7777/webcenter

Oracle WebCenter Content: Desktop provides convenient access to Oracle WebCenter Content Server files from a number of familiar desktop applications, such as Windows Explorer, Microsoft Office applications (Word, Excel, and Powerpoint), email clients (Microsoft Outlook and Lotus Notes), and web browsers (Internet Explorer, Mozilla Firefox, and Google Chrome).

A file store for data management is used in Oracle WebCenter Content Server instead of the traditional file system for storing and organizing content.

1. Log in to the WebCenter Content Server instance as system administrator.
2. Select Administration, then Providers.

   The Providers Page displays.

3. Click Info in the Action column next to the DefaultFileStore provider.

   The File Store Provider Information Page displays.

4. Specify a name for the rule (for example, DBStorage) and select JDBC Storage.
5. Click OK.

   The Edit File Store Provider Page displays.

6. Click Update.
7. Restart the WebCenter Content Server instance.

As an additional step to configuring and managing Oracle WebCenter Content Server and the other servers in the domain in which it resides, you may want to consider using Oracle WebLogic Server Node Manager. Node Manager lets you start and stop WebLogic Server instances remotely, monitor them, and automatically restart them after an unexpected failure.

To ensure the Content Manager task flow works and displays proper translations on non-English locales, you need to configure Content Server for localization.

1. Log on to WebCenter Content as an administrator.
2. From the Main menu, choose Administration, and then Localization.
3. Select the check boxes for the required locales.
4. Click Update.

By default, the Rich Text Editor wraps HTML source at 68 characters. This may cause some multibyte symbols to wrap incorrectly. If you encounter this problem, you can disable text wrapping in the Rich Text Editor.

1. Export the latest configuration file blog-wiki-config.xml.xml from MDS:

   exportMetadata(application='webcenter', server='WC_Portal', toLocation='/scratch/aime1', docs='/oracle/webcenter/doclib/config/mdssys/cust/site/webcenter/blog-wiki-config.xml.xml')
   

2. If the configuration file is not found, create it at the path specified in Step 1, then edit the file to add the following code:

   <?xml version='1.0' encoding='UTF-8'?>
   <mds:customization version="11.1.1.64.86" xmlns:mds="http://xmlns.oracle.com/mds" motype_local_name="adf-blogwiki-config" motype_nsuri="http://xmlns.oracle.com/webcenter/blogwiki/config">
   <mds:modify element="(xmlns(mds_ns1=http://xmlns.oracle.com/webcenter/blogwiki/config))/mds_ns1:adf-blogwiki-config/mds_ns1:properties/mds_ns1:property[@name='wiki.markup.enabled']">
   <mds:attribute name="value" value="false"/>
   </mds:modify>
   </mds:customization>
   

3. Edit the configuration file to change the value of element text.wrap.length to 0:

   <mds:modify element="(xmlns(mds_ns1=http://xmlns.oracle.com/webcenter/blogwiki/config))/mds_ns1:adf-blogwiki-config/mds_ns1:properties/mds_ns1:property[@name='text.wrap.length']"><mds:attribute name="value" value="0"/></mds:modify>
   

4. Import the updated file to MDS:

   importMetadata(application='webcenter', server='WC_Portal', fromLocation='/scratch/aime1', docs='/oracle/webcenter/doclib/config/mdssys/cust/site/webcenter/blog-wiki-config.xml.xml')

A default connection between Oracle WebCenter Portal and Oracle WebCenter Content Server may be automatically configured when WebCenter Portal first starts up, however, you should test the connection and check that it has been appropriately configured for your environment.

When Oracle WebCenter Portal first starts up, a set of default data is seeded in the default Oracle WebCenter Content Server. The data seeded in WebCenter Content Server for a WebCenter Portal instance is based on several properties that are set on the default WebCenter Content Server connection.

Portal Server Identifier = /WebCenter1
Security Group = WC1

The Content Presenter task flow enables Oracle WebCenter Portal users with Page-Edit permissions to customize the selection and presentation of content. In Content Presenter you can select a single item of content, contents under a folder, a list of items, or a query for content and then select a Content Presenter template with which to render that content on a page in WebCenter Portal.

By changing the Oracle WebCenter Content Server's Cache Invalidation Interval, you can enable the cache to be monitored by the cache sweeper utility.

The cache sweeper queries for changes in WebCenter Content Server, flagging the cache as "dirty" if there have been any changes. This causes the application to retrieve a new copy of the document from WebCenter Content Server that replaces the cached version.

By default, the initial value for the Cache Invalidation Interval is set to 0 (minutes). This means that the sweeper has been turned off. To turn the sweeper on, you need to set a value (in minutes). The minimum value that can be set is 2 (minutes). You can do this from the Cache Details page in Fusion Middleware Control or using a WLST command.

This section includes the following topics:

• Modifying the Cache Invalidation Interval Using Fusion Middleware Control

• Modifying the Cache Invalidation Interval Using WLST

Once the sweeper is turned on, only cache objects that have been changed will be invalidated.

1. Log in to the WebCenter Content Server console application, and under the Administration menu item, select System Audit Information.

   If your console is using the left menu display option, the Administration link will be located there.

2. Under the Tracing Sections Information, add in only system and requestaudit in the Active Sections. Check Full Verbose Tracing, check Save, then click the Update button. Once this is done, select the View Server Output menu option. This will change the browser view to display the log. This is all that is needed to configure WebCenter Content Server.

   For example, the following is the View Server Output with the cache invalidation interval set to 2 (minutes) Note the time stamp:

   requestaudit/6 08.30 09:52:26.001  IdcServer-68    GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.016933999955654144(secs)
   requestaudit/6 08.30 09:52:26.010  IdcServer-69    GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.006134999915957451(secs)
   requestaudit/6 08.30 09:52:26.014  IdcServer-70    GET_DOCUMENT_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.004271999932825565(secs)
   
   ... other trace info ...
   
   requestaudit/6 08.30 09:54:26.002  IdcServer-71    GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.020323999226093292(secs)
   requestaudit/6 08.30 09:54:26.011  IdcServer-72    GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.017928000539541245(secs)
   requestaudit/6 08.30 09:54:26.017  IdcServer-73    GET_DOCUMENT_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.010185999795794487(secs)
   

3. Once the tracing logs are reporting correctly, the next step is set up Oracle WebCenter Portal to test the sweeper. You can do this by setting up two pages with Content Presenter task flows, with each task flow using a different custom Content Presenter display template, and assigning each page a different contributor data file (document in the cache).

   When the WebCenter Portal pages containing the content is loaded in the browser for the first time, you can see the tracing information in the Content Server output viewer. For example:

   requestaudit/6 08.30 11:51:12.030 IdcServer-129 CLEAR_SERVER_OUTPUT [dUser=weblogic] 0.029171999543905258(secs)
   requestaudit/6 08.30 11:51:12.101 IdcServer-130 GET_SERVER_OUTPUT [dUser=weblogic] 0.025721000507473946(secs)
   requestaudit/6 08.30 11:51:26.592 IdcServer-131 VCR_GET_DOCUMENT_BY_NAME [dID=919][dDocName=DF_UCMCACHETESTER]
   [dDocTitle=DF_UCMCacheTester][dUser=weblogic][RevisionSelectionMethod=LatestReleased][IsJava=1] 0.21525299549102783(secs)
   requestaudit/6 08.30 11:51:27.117 IdcServer-132 VCR_GET_CONTENT_TYPES [dUser=wccadmin][IsJava=1] 0.5059549808502197(secs)
   requestaudit/6 08.30 11:51:27.146 IdcServer-133 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.03360399976372719(secs)
   requestaudit/6 08.30 11:51:27.169 IdcServer-134 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.008806000463664532(secs)
   requestaudit/6 08.30 11:51:27.204 IdcServer-135 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.013265999965369701(secs)
   requestaudit/6 08.30 11:51:27.384 IdcServer-136 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.18119299411773682(secs)
   requestaudit/6 08.30 11:51:27.533 IdcServer-137 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.1519480049610138(secs)
   requestaudit/6 08.30 11:51:27.634 IdcServer-138 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.10827399790287018(secs)
   requestaudit/6 08.30 11:51:27.687 IdcServer-139 VCR_GET_CONTENT_TYPE [dUser=wccadmin][IsJava=1] 0.059702999889850616(secs)
   requestaudit/6 08.30 11:51:28.271 IdcServer-140 GET_USER_PERMISSIONS [dUser=weblogic][IsJava=1] 0.006703000050038099(secs)
   requestaudit/6 08.30 11:51:28.285 IdcServer-141 GET_ENVIRONMENT [dUser=wccadmin][IsJava=1] 0.010893999598920345(secs)
   requestaudit/6 08.30 11:51:30.433 IdcServer-142 GET_SERVER_OUTPUT [dUser=weblogic] 0.017318999394774437(secs)
   requestaudit/6 08.30 11:51:41.837 IdcServer-143 VCR_GET_DOCUMENT_BY_NAME [dID=508][dDocName=113_ES]
   [dDocTitle=Landing Home][dUser=weblogic][RevisionSelectionMethod=LatestReleased][IsJava=1] 0.15937699377536774(secs)
   requestaudit/6 08.30 11:51:42.781 IdcServer-144 GET_FILE [dID=326][dDocName=WEBCENTERORACL000315][dDocTitle=Duke][dUser=anonymous][RevisionSelectionMethod=LatestReleased][dSecurityGroup=Public][xCollectionID=0] 0.16288499534130096(secs)
   

   The highlighted sections show where the two example data files DF_UCMCACHETESTER and 113_ES were called by the WebCenter Portal VCR connection to WebCenter Content Server. Note the VCR_GET_DOCUMENT_BY_NAME invocation.

   On subsequent refreshes of these two pages, you will notice (after you refresh WebCenter Content Server's View Server Output) that there are no further traces of the same VCR_GET_DOCUMENT_BY_NAME invocations. This is because the pages are getting the documents from the cache.

4. The next step is to go through the back door and change one of the documents through the Content Server console. To do this, locate the data file document, and from the Content Information page, select Edit Data File.

   This invokes the Site Studio Contributor, where you can make some modifications.

   When you refresh the Content Server View Server Output, the tracing displays the operations performed on the document.

   requestaudit/6 08.30 11:56:59.972 IdcServer-255 SS_CHECKOUT_BY_NAME [dID=922][dDocName=DF_UCMCACHETESTER][dUser=weblogic]
   [dSecurityGroup=Public] 0.05558200180530548(secs)
   requestaudit/6 08.30 11:57:00.065 IdcServer-256 SS_GET_CONTRIBUTOR_CONFIG [dID=922][dDocName=DF_UCMCACHETESTER]
   [dDocTitle=DF_UCMCacheTester][dUser=weblogic][dSecurityGroup=Public][xCollectionID=0] 0.08632399886846542(secs)
   requestaudit/6 08.30 11:57:00.470 IdcServer-259 DOC_INFO_BY_NAME [dID=922][dDocName=DF_UCMCACHETESTER]
   [dDocTitle=DF_UCMCacheTester][dUser=weblogic][dSecurityGroup=Public][xCollectionID=0] 0.02268899977207184(secs)
   requestaudit/6 08.30 11:57:10.177 IdcServer-264 GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.007652000058442354(secs)
   requestaudit/6 08.30 11:57:10.181 IdcServer-263 GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.01868399977684021(secs)
   requestaudit/6 08.30 11:57:10.187 IdcServer-265 GET_DOCUMENT_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.009367000311613083(secs)
   (internal)/6 08.30 11:57:26.118 IdcServer-266 File to be removed: /oracle/app/admin/domains/webcenter/ucm/cs/vault/~temp/703253295.xml
   (internal)/6 08.30 11:57:26.121 IdcServer-266 File to be removed: /oracle/app/admin/domains/webcenter/ucm/cs/vault/~temp/703253295.xml
   requestaudit/6 08.30 11:57:26.122 IdcServer-266 SS_SET_ELEMENT_DATA [dID=923][dDocName=DF_UCMCACHETESTER]
   [dDocTitle=DF_UCMCacheTester][dUser=weblogic][dSecurityGroup=Public][xCollectionID=0][StatusCode=0][StatusMessage=Successfully checked in content item 'DF_UCMCACHETESTER'.] 0.3765290081501007(secs)
   requestaudit/6 08.30 11:57:30.710 IdcServer-267 DOC_INFO_BY_NAME [dID=923][dDocName=DF_UCMCACHETESTER]
   [dDocTitle=DF_UCMCacheTester][dUser=weblogic][dSecurityGroup=Public][xCollectionID=0] 0.07942699640989304(secs)
   requestaudit/6 08.30 11:57:30.733 IdcServer-268 SS_GET_CONTRIBUTOR_STRINGS [dUser=weblogic] 0.0044570001773536205(secs)
   

   After refreshing the first page, you should see that the updates have been applied. Note that the refresh time may vary since the Cache Invalidation Interval (set to 2 minutes) is not determined by when changes occur. The sweeper just runs every two minutes.

   When you refresh the WebCenter Content Server View Server Output, for this example, the tracing displays the following information:

   requestaudit/6 08.30 11:59:10.171 IdcServer-270 GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.00952600035816431(secs)
   requestaudit/6 08.30 11:59:10.179 IdcServer-271 GET_FOLDER_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.011118999682366848(secs)
   requestaudit/6 08.30 11:59:10.182 IdcServer-272 GET_DOCUMENT_HISTORY_REPORT [dUser=wccadmin][IsJava=1] 0.007447000127285719(secs)
   requestaudit/6 08.30 11:59:16.885 IdcServer-273 VCR_GET_DOCUMENT_BY_NAME [dID=923][dDocName=DF_UCMCACHETESTER]
   [dDocTitle=DF_UCMCacheTester][dUser=weblogic][RevisionSelectionMethod=LatestReleased][IsJava=1] 0.0786449983716011(secs)
   

   After the specified Cache Invalidation Interval time, the sweeper is invoked (tracked by the GET_ calls). Since a change has been noted, the next call is to the VCR_GET_DOCUMENT_BY_NAME to retrieve a new version of the modified data file.

   Navigating back to the second page and viewing the server output, there are no further VCR_GET_DOCUMENT_BY_NAME to retrieve the data file. This simply means that the data file was just retrieved from the cache. Looking at the example server output, we can see that there was only one request for the VCR_GET_DOCUMENT_BY_NAME:

   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor Request Audit Report over the last 120 Seconds for server webcenteroraclelocal16200****
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor -Num Requests 8 Errors 0 Reqs/sec. 0.06666944175958633 
   Avg. Latency (secs) 0.02762500010430813 Max Thread Count 2
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor 1 Service VCR_GET_DOCUMENT_BY_NAME 
   Total Elapsed Time (secs) 0.09200000017881393 Num requests 1 Num errors 0 Avg. Latency (secs) 0.09200000017881393
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor 2 Service GET_PERSONALIZED_JAVASCRIPT 
   Total Elapsed Time (secs) 0.054999999701976776 Num requests 1 Num errors 0 Avg. Latency (secs) 0.054999999701976776
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor 3 Service GET_FOLDER_HISTORY_REPORT 
   Total Elapsed Time (secs) 0.028999999165534973 Num requests 2 Num errors 0 Avg. Latency (secs) 0.014499999582767487
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor 4 Service GET_SERVER_OUTPUT 
   Total Elapsed Time (secs) 0.017999999225139618 Num requests 1 Num errors 0 Avg. Latency (secs) 0.017999999225139618
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor 5 Service GET_FILE 
   Total Elapsed Time (secs) 0.013000000268220901 Num requests 1 Num errors 0 Avg. Latency (secs) 0.013000000268220901
   requestaudit/6 08.30 12:08:00.021 Audit Request Monitor ****End Audit Report*****