4 Preparing Back-End Components for WebCenter Services

4.3.1.1 Oracle Content Server - Prerequisites

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

• Create the OCSERVER schema for Oracle Content Server by using RCU. For information, see Section 2.1.3, "Create Schemas for Oracle WebCenter."

• Install Oracle HTTP Server. Oracle Content Server and Oracle HTTP Server must be installed on the same system. For information about installing Oracle HTTP Server, see the Oracle Fusion Middleware Installation Guide for Web Tier.

4.3.1.2 Oracle Content Server - Installation

You can install Oracle Content Server by using either of the following approaches:

• During Oracle WebCenter installation. Oracle Content Server installation is integrated with Oracle WebCenter installation. Therefore, you can choose to install Oracle Content Server 10.1.3.5.1 while installing Oracle WebCenter. For information, see Section 2.8, "Installing Oracle WebCenter."

• Through a standalone installation. You may want to choose this option if you need to install Oracle Content Server on a different system than the one on which Oracle WebCenter is installed.

To install Oracle Content Server separately:

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

   For information about the installation procedure, 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 to upgrade Oracle Content Server 10.1.3.3.3 and prepare it to work with Oracle WebCenter. This script is available in the root directory of the UCM media shipped with Oracle WebCenter.

   The wc_contentserverconfig configuration script installs the following:

   • Oracle Content Server 10.1.3.5.1

   • Folders_g 10.1.3.5.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 for AutoNumberPrefix to IDC_Name, if not set already.

   • 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.

   • Sets EnableIdcProfileField=1. This entry makes the server create a new metadata field named xIdcProfile and configure the field to use a view of profile trigger values called ProfileTriggerValues. The server then sets the profile trigger to the xIdcProfile metadata field, if not already set.

To run the wc_contentserverconfig WebCenter configuration script:

1. Navigate to the webcenter-conf directory, which is in the root directory of the UCM media shipped with Oracle WebCenter.

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 UCM 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, you can restart the service by choosing Start, Settings, Control Panel, Administrative Tools, and 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, you can restart the service by choosing Start, Settings, Control Panel, Administrative Tools, and 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

If you choose to use Oracle Content Server as your external content repository, you must configure it with an LDAP-based identity store. For identity propagation, Oracle Content Server and Oracle WebCenter must use the same LDAP identity store. You can optionally configure Oracle Content Server for full-text search support. It is recommended that you use the OracleTextSearch option for enabling full-text search. To provide additional security for connections between WebCenter applications or components, you can enable Secure Sockets Layer (SSL) on Oracle Content Server.

For information about configuring Oracle Content Server, see the "Oracle Content Server - Configuration" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

You must configure Oracle Content Server to work with Oracle HTTP Server. Oracle HTTP Server configuration enables you to manage Oracle Content Server through a browser or add content on the server through WebDAV. This section describes how to configure Oracle Content Server to work with Oracle HTTP 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. In the config.cfg file, add the SocketHostAddressSecurityFilter entry, if not already present. The file is located in the content_server_dir/config directory. Set the entry to a pipe-delimited list of all hosts allowed to access Oracle Content Server.

   For example:

   SocketHostAddressSecurityFilter=127.0.0.1 | allowed_host_IP

   Where: allowed_host_IP refers to IP addresses of all hosts allowed to connect to Oracle Content Server through a TCP socket port. 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 the entry is not there in the file. See step 2 for values of this entry.

4. Restart Oracle Content Server and Admin Server.

To configure Oracle HTTP Server for Oracle Content Server:

1. Open the httpd.conf file. This file is available at the following path:

   OHS_ORACLE_HOME/instances/instance_name/config/OHS/ohs_name/httpd.conf
   

   Where:

   • OHS_ORACLE_HOME is the Oracle HTTP Server installation directory

   • instance_name is the instance where Oracle HTTP Server is running

   • ohs_name is the server name of Oracle HTTP Server

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

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

3. Restart Oracle Content Server.

4. Restart Oracle HTTP Server.

   For example, you can use the following command:

   OHS_ORACLE_HOME/instances/instance_name/bin/opmnctl stopall /opmnctl startall
   

4.3.1.4 Oracle Content Server - Integration

After configuring Oracle Content Server, you must set up content repository connections to the server to enable integration of the Documents service into your WebCenter applications. For information about how you can register content repositories and manage connections for WebCenter Spaces and any other WebCenter application deployed to a managed server, see the "Managing Content Repositories" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up content repository connections within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Documents Service" and "Integrating Content" chapters in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

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 about how you can register content repositories and manage connections for WebCenter Spaces and any other WebCenter application deployed to a managed server, see the "Managing Content Repositories" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up content repository connections within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Documents Service" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4.7.2.1 Deploying sca_CommunityWorkflows.jar

You can deploy sca_CommunityWorkflows.jar by using any of the following methods based on your preference:

• Oracle WebLogic Scripting Tool (WLST)

  For information, see the "Oracle SOA Suite Custom WLST Commands" chapter in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

• Ant

  For information, see the "Deploying SOA Composite Applications" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

• Oracle Enterprise Manager Fusion Middleware Control

  This section describes how to deploy the JAR by using Fusion Middleware Control.

To deploy the sca_CommunityWorkflows.jar by using Fusion Middleware Control:

1. To start Fusion Middleware Control, enter the URL in the following format in your web browser:

   http://host_name.domain_name:port_number/em
   

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

2. Enter the Oracle Fusion Middleware administrator user name and password 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.

3. Under WebLogic Domain in the navigation panel on left, right-click your SOA domain, select SOA Deployment, and then Deploy. (Figure 4-1)

   Figure 4-1 Deploying the Composite to a SOA Managed Server

   
   Description of "Figure 4-1 Deploying the Composite to a SOA Managed Server"
   
   

4. On the Select Archive page, enter the path to sca_CommunityWorkflows.jar. (Figure 4-2)

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

   SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows.jar

   Figure 4-2 Deploying the Composite - Select Archive Page

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

5. Click Next.

6. On the Select Target page, select the Managed Server to which you want to deploy the SOA composite application. (Figure 4-3)

   Figure 4-3 Deploying the Composite - Select Target Page

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

7. Click Next.

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

   Figure 4-4 Deploying the Composite - Confirmation Page

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

9. Click Deploy.

   After the composite is successfully deployed, it is listed under your Oracle SOA Managed Server. (Figure 4-5)

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

   
   Description of "Figure 4-5 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 either use WLST or Fusion Middleware Control.

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-6)

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

   SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear

   Figure 4-6 Specifying the Path to WebCenterWorklistDetailApp.ear

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

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

   Figure 4-7 Selecting Target Server

   
   Description of "Figure 4-7 Selecting Target Server"
   
   

5. Click Next.

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

   Figure 4-8 Specifying Application Attributes

   
   Description of "Figure 4-8 Specifying Application Attributes"
   
   

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

   Figure 4-9 Deploying WebCenterWorklistDetailApp.ear

   
   Description of "Figure 4-9 Deploying WebCenterWorklistDetailApp.ear"
   
   

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

   Figure 4-10 Deployed EAR Application

   
   Description of "Figure 4-10 Deployed EAR Application"