This chapter describes how to install and configure an Oracle WebCenter Content Managed Server with the WebCenter Content user interface, an Oracle WebCenter Content Server interface that is based on the Oracle Application Development Framework (Oracle ADF).
This chapter includes the following sections:
Section 12.1, "About Configuring Content Server with the WebCenter Content User Interface"
Section 12.2, "Installing and Configuring Oracle WebCenter Content 11g (11.1.1.8)"
Section 12.3, "Installing Oracle Application Development Framework 11g (11.1.2)"
Section 12.4, "Installing the WebCenter Content User Interface Application"
Section 12.5, "Deploying the WebCenter Content User Interface Application"
Section 12.7, "Accessing the WebCenter Content User Interface"
You can configure Content Server with the WebCenter Content user interface in addition to the native 11g user interface, which Content Server uses by default. The WebCenter Content user interface resides in a separate domain from Content Server and runs on a different port, 16225 by default.
This separate domain requires its own Oracle Fusion Middleware home, which can reside on the same machine as the Middleware home for Content Server or on a separate machine. You could choose to have multiple instances of the WebCenter Content user interface server interact with Oracle WebCenter Content Server (previously known as Oracle UCM Content Server).
Note:
The Webcenter Content user interface cannot use the same Content Server as Oracle WebCenter Portal because of the folder component dependencies. The triggering issue is the folder component, and the incompatibility extends to any Content Server that uses FrameworkFolders.
This chapter uses the following terminology:
The first Middleware home contains Oracle WebCenter Content and is referred to as the Oracle WebCenter Content Middleware home (WCC_MW_HOME in path names).
The first domain contains WebCenter Content and is referred to as the Oracle WebCenter Content domain (WCC_DOMAIN in path names). This domain is associated with the Oracle WebCenter Content Middleware home.
The second Middleware home contains the WebCenter Content user interface and is referred to as the WebCenter Content user interface Middleware home (WCCUI_MW_HOME in path names).
The second domain contains the WebCenter Content user interface and is referred to as the WebCenter Content user interface domain (WCCUI_domain in path names). This domain is associated with the WebCenter Content user interface Middleware home.
The two Middleware homes and domains can reside on the same host or on different hosts. The only additional requirement to run both domains on the same host is to use a different Administration Server port for each domain. To distinguish between the two Administration Server ports, this chapter refers to them as the WebCenter Content Administration Server port (WCC_ADMINSERVER_PORT) and the WebCenter Content user interface Administration Server port (WCCUI_ADMINSERVER_PORT).
The WebCenter Content user interface domain requires its own Middleware home because changes are made to the Oracle ADF stack that are specifically required for the WebCenter Content user interface.
To configure Content Server with the WebCenter Content user interface, you need to perform these procedures:
Before you can configure Content Server with the WebCenter Content User Interface, you need to install and configure Oracle WebCenter Content 11gR1 (11.1.1.8), as these chapters describe:
You can install a new Oracle WebCenter Content 11gR1 (11.1.1.8.0 MLR3) application or use an existing Oracle WebCenter Content 11gR1 (11.1.1.8.0) installation that is configured as this section describes.
All of the operations in this section pertain to the WebCenter Content Middleware home and, therefore, the WebCenter Content domain. The following steps summarize the installation and configuration procedures for Oracle WebCenter Content in the first of two Middleware homes:
For the first domain (in the WebCenter Content Middleware home), follow the instructions in Chapter 2, "Installing Oracle WebCenter Content," to install these products:
Oracle Database 11g Release 2
Repository Creation Utility (RCU)
Oracle WebLogic Server in a Middleware home
Oracle WebCenter Content 11g (11.1.1.8)
Using RCU, create the Oracle WebCenter Content Server - Complete schema and the Metadata Services (MDS) schema, as described in Section 2.2, "Creating Oracle WebCenter Content Schemas with the Repository Creation Utility."
Create a WebLogic Server domain that includes a WebCenter Content Managed Server (using the Oracle Universal Content Management - Content Server template) and, optionally, an Inbound Refinery Managed Server (using the Oracle Universal Content Management - Inbound Refinery template), as described in Section 3.2, "Creating an Oracle WebLogic Server Domain."
Configure Content Server, as the following sections describe:
Section 12.2.1, "Enabling WebCenter Content User Interface Components"
This configuration is required for using the WebCenter Content user interface.
Section 12.2.2, "Setting up the Remote Intradoc Client (RIDC)"
This configuration is required for using the WebCenter Content user interface.
Section 12.2.3, "Generating Thumbnails and Web-Viewable Renditions"
This configuration is optional, to enhance the WebCenter Content user interface experience.
Section 12.2.4, "Configuring Extended Features in Content Server"
This configuration is optional, to set up standard Content Server features.
Before you can use the WebCenter Content user interface, you must enable these Content Server components: AutoSuggestConfig, DynamicConverter, and FrameworkFolders. You can enable them through the Content Server Component Manager interface, as follows:
Log in to Content Server as a WebCenter Content administrator.
From the Administration tray or menu, choose Admin Server, then Components.
On the Component Manager page, select all three components under WebCenter Content UI Components:
AutoSuggestConfig
DynamicConverter
FrameworkFolders
Click Update, and then click OK to confirm enabling the component.
Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."
The WebCenter Content user interface uses the IDC socket protocol to communicate with Content Server. To enable this communication, you must set the IntradocServerPort and SocketHostAddressSecurityFilter values in the WCC_domain/ucm/cs/config/config.cfg configuration file for Content Server, in the WebCenter Content domain.
The following example shows how to set these values:
IntradocServerPort=port_number SocketHostAddressSecurityFilter=IP addresses of permitted UI hosts separated by a bar symbol (|) For example: IntradocServerPort=4444 SocketHostAddressSecurityFilter=123.456.789.0 If you want to open this up to all hosts in the network, use this setting: SocketHostAddressSecurityFilter=*.*.*.*
For more information about the config.cfg file, see "The config Directory" in Oracle Fusion Middleware Developing with Oracle WebCenter Content.
If you want to obtain thumbnail images and web-viewable renditions of files from the WebCenter Content user interface, you can configure Inbound Refinery to provide them. You can set up an Inbound Refinery provider for thumbnails and file conversions, such as PDF Export, through the native 11g user interface.
For information about generating thumbnails and web-viewable renditions, see "Configuring Inbound Refinery" in Oracle Fusion Middleware Managing Oracle WebCenter Content.
Some Content Server features are supported but not necessarily required by the WebCenter Content user interface. For example, Access Control Lists (ACLs) and Accounts are not configured out of the box. If these features are enabled on Content Server, however, the WebCenter Content user interface provides access to the additional functionality.
For information about enabling ACLs in Content Server, see "Managing Access Control List Security" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
For information about enabling Accounts in Content Server, see "Managing Accounts" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
You can set up one of the three indexing configurations for Content Server: Oracle Text Search, Database metadata, or Database full text. For information about how to do this, see "Configuring the Search Index" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
These standard Content Server settings are not specific to the WebCenter Content user interface. For information about other extended features in Content Server, see Oracle Fusion Middleware Administering Oracle WebCenter Content.
Install and configure Oracle Application Development Framework (Oracle ADF) 11gR1 (11.1.2) in an 11gR1 (11.1.1.6.0) Middleware home with Oracle WebLogic Server. This will include installing Oracle WebLogic Server 11gR1 (10.3.6 only) to create the Middleware home followed by installing Oracle ADF and then two Oracle ADF OPatch files. If your site is going to use Oracle WebCenter Content: Desktop with the WebCenter Content user interface, you also need to install a patch to support compatibility mode in Desktop 11.1.1.8.
All the operations in this section pertain to the WebCenter Content user interface Middleware home and, therefore, to the WebCenter Content user interface domain. In the following commands, WCCUI_MW_HOME refers to the WebCenter Content user interface Middleware home, which includes the Oracle ADF installation.
For the second domain, do these steps:
Install Oracle WebLogic Server 11gR1 (11.1.1.6.0) to install an 11.1.1.6.0 Middleware home. This will be the WebCenter Content user interface Middleware home (WCCUI_MW_HOME).
Install Oracle Application Development Framework 11gR1 (11.1.1.6.0):
Obtain the Oracle Application Development Framework 11gR1 (11.1.1.6.0) media, as described in Section 1.2.2, "Software Downloads for Oracle WebCenter Content Installation and Configuration."
Unzip the ZIP file containing Oracle ADF to a temporary location, media_loc.
Run the installer, using the following command:
UNIX command:
media_loc/Disk1/runInstaller -jreLoc WCCUI_MW_HOME/jrockit_160_24_D1.1.2-4
Windows command:
media_loc\Disk1\runInstaller -jreLoc WCCUI_MW_HOME\jrockit_160_24_D1.1.2-4
If you have an Oracle WebCenter Content 11.1.1.8.0 installation that was previously configured to work with the WebCenter Content user interface, you need to roll back the Oracle Application Development Framework 11gR1 (11.1.2.2.0) OPatch 13656274.
Obtain the Oracle Application Development Framework 11gR1 (11.1.2.4.0) OPatch 16546129 - (16546129_11.1.1.6.0_Generic.zip) from My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com.
Unzip the patch ZIP file into a temporary folder, temp_location, and run the following command:
UNIX command:
WCCUI_MW_HOME/oracle_common/OPatch/opatch apply -jre ${JAVA_HOME}/jre -oh $WCCUI_MW_HOME/oracle_common/ temp_location/16546129
Windows command:
WCCUI_MW_HOME\oracle_common\OPatch\opatch apply -jre %JAVA_HOME%\jre -oh %WCCUI_MW_HOME%\oracle_common\ temp_location\16546129
In the command, JAVA_HOME is WCCUI_MW_HOME/jrockit_160_24_D1.1.2-4 (the location of the JDK).
If you have an Oracle WebCenter Content 11.1.1.8.0 installation that was previously configured to work with the WebCenter Content user interface, you need to roll back the Oracle Application Development Framework 11gR1 (11.1.2.2.0) OPatch 13656372.
Obtain the Oracle Application Development Framework 11gR1 (11.1.2) OPatch 16546157 - (p16546157_11.1.1.6.0_generic.zip) from https://support.oracle.com.
Unzip the patch ZIP file into a temporary folder, temp_location, and run the following command:
UNIX command:
WCCUI_MW_HOME/oracle_common/OPatch/opatch apply -jre ${JAVA_HOME}/jre -oh $WCCUI_MW_HOME/oracle_common/ temp_location/16546157
Windows command:
WCCUI_MW_HOME\oracle_common\OPatch\opatch apply -jre %JAVA_HOME%\jre -oh %WCCUI_MW_HOME%\oracle_common\ temp_location\16546157
In the command, JAVA_HOME is WCCUI_MW_HOME/jrockit_160_24_D1.1.2-4 (the location of the JDK).
(Optional) For MDS customizing of the WebCenter Content user interface, obtain patch number 16020846, version 11.1.2.4.0 (p16020846_111240_Generic.zip), from https://support.oracle.com.
(Optional) Unzip the patch ZIP file into a temporary folder, temp_location, and run the following command:
UNIX command:
WCCUI_MW_HOME/oracle_common/OPatch/opatch apply -jre ${JAVA_HOME}/jre -oh $WCCUI_MW_HOME/oracle_common/ temp_location/16825232
Windows command:
WCCUI_MW_HOME\oracle_common\OPatch\opatch apply -jre %JAVA_HOME%\jre -oh %WCCUI_MW_HOME%\oracle_common\ temp_location\16825232
In the command, JAVA_HOME is WCCUI_MW_HOME/jrockit_160_24_D1.1.2-4 (the location of the JDK).
The WebCenter Content user interface artifacts are in a ZIP file called WccADFUI.zip, which you can obtain from the WebCenter Content Oracle home in the first Middleware home. The file location is WCC_ORACLE_HOME/ucm/Distribution/WccADFUI/WccADFUI.zip.
This ZIP file includes these WebCenter Content user interface artifacts:
The application EAR file, WccAdf.ear
The domain extension configuration template
Custom Oracle Weblogic Scripting Tool (WLST) commands for managing the connections to Oracle WebCenter Content Server
Support scripts for deployment and management of the application
To install the WebCenter Content user interface application:
Create the directory WCCUI_MW_HOME/oracle_common/webcenter/wccadf, in the WebCenter Content user interface (second) Middleware home.
Copy the WCC_ORACLE_HOME/ucm/Distribution/WccADFUI/WccADFUI.zip file to the WCCUI_MW_HOME/oracle_common/webcenter/wccadf/ directory.
Expand the ZIP file in the WCCUI_MW_HOME/oracle_common/webcenter/wccadf/ directory.
All of the operations in this section pertain to the WebCenter Content user interface Middleware home and, therefore, to the WebCenter Content user interface domain.
To deploy the WebCenter Content user interface application:
Register the Oracle Metadata Services (MDS) repository in the application:
Run WLST from the WebCenter Content user interface Middleware home:
UNIX command:
WCCUI_MW_HOME/oracle_common/common/bin/wlst.sh
Windows command:
WCCUI_MW_HOME\oracle_common\common\bin\wlst.sh
Run the following commands in offline mode:
wls:/offline> archive = getMDSArchiveConfig('WCCADF_EAR_LOCATION')
wls:/offline> archive.setAppMetadataRepository(repository='mds-mds_repo_name', partition='partition_name', type='DB', jndi='jdbc/mds/mds_repo_name')
wls:/offline> archive.save()
In the archive.setAppMetadataRepository command, mds_repo_name is the name of the repository, and partition_name is a name for the partition to be created.
For example:
archive =
getMDSArchiveConfig("/scratch/ADFMW/oracle_common/webcenter/wccadf/WccAdf.ear")
archive.setAppMetadataRepository(repository='mds-WCCUIMDSREPO', partition='MDS_PARTITION', type='DB', jndi='jdbc/mds/WCCUIMDSREPO')
archive.save()
In the WebCenter Content user interface Middleware home, place the WebCenter Content user interface domain template, oracle.ucm.cs_adf_template_11.1.1.jar, in the following directory:
WCCUI_MW_HOME/oracle_common/common/templates/applications/
Run the configuration wizard on this Middleware home:
WCCUI_MW_HOME/oracle_common/common/bin/config.sh
Create a new Weblogic Server domain, WCCUI_DOMAIN, using the following template:
Oracle WebCenter Content - Web UI - 11.1.1.0
Dependent components (JRF and EM) will be automatically enabled. This will create a new domain and a Managed Server for the WebCenter Content user interface application. You will not need any data sources to be set up for this application.
Upgrade the Oracle ADF shared libraries in the WebCenter Content user interface domain to Sherman Update 2:
Run WLST from WCCUI_MW_HOME/oracle_common/common/bin/wlst.sh.
Run the following command in offline mode:
wls:/offline> upgradeADF('DOMAIN_HOME');
For example:
wls:/offline> upgradeADF('/scratch/ADFMW/Middleware/user_projects/domains/WCCUI_domain')
Target Library "jsf#2.0@1.0.0.0_2-0-2" to JRF "AdminServer"
Target Library "jsf#2.0@1.0.0.0_2-0-2" to JRF "WCCADF_server1"
Register the target Managed Server with the MDS repository, and create the metadata partition:
Start the Oracle WebLogic Server Administration Server in the WebCenter Content user interface domain, which is in the WebCenter Content user interface Middleware home (WCCUI_MW_HOME), as described in Part , "Starting the Administration Server."
If you have installed both domains on the same host, the port for the Administration Server in the WebCenter Content user interface domain will not be the default Administration Server port.
Run WLST from WCCUI_MW_HOME/oracle_common/common/bin/wlst.sh, and connect to the WebLogic Server instance in interactive mode:
wls:/offline> connect() Please enter your username : weblogic Please enter your password : Please enter your server URL: [t3://localhost:7001] :t3://host:port of admin server where the WebCenter Content user interface Managed Server is running
Run the following commands:
wls:/mydomain/serverConfig> registerMetadataDBRepository('mds_repo_name', 'Oracle', 'db_host_name', 'db_port_number', 'db_name', 'mds_schema_username', 'mds_schema_password', 'target_server')
wls:/mydomain/serverConfig> createMetadataPartition(repository='mds-mds_repo_name', partition='partition_name')
The target server in the preceding command is the WebCenter Content user interface Managed Server.
For example:
registerMetadataDBRepository('WCCUIMDSREPO', 'Oracle','my_db_server', '1521', 'my_db', 'WCCUI_MDS', 'password', 'WCCADF_server1')
createMetadataPartition(repository='mds-WCCUIMDSREPO', partition='MDS_PARTITION')
If you are upgrading an Oracle WebCenter Content 11.1.1.8.0 installation that was previously configured to work with the WebCenter Content user interface, the mds_repo_name and partition_name values should be the same as the mds_repo_name and partition_name values created during the installation of Oracle WebCenter Content 11.1.1.8.0. You can obtain these values from the Fusion Middleware Control URL of the 11.1.1.8.0 installation.
Restart the Administration Server in the WebCenter Content user interface domain, by stopping and then starting it, as described in Part , "Restarting a Managed Server."
If you have installed both domains on the same host, the port for the Administration Server in the WebCenter Content user interface domain will not be the default Administration Server port.
If you are upgrading Oracle WebCenter Content to 11.1.1.8.0 MLR3 from an existing 11.1.1.8.0 installation, redeploy the WccAdfCustomSkin.jar and WccAdfStandardSkin.jar files:
Log in to the WebLogic Server Administration Console in the WebCenter Content user interface domain as an administrator.
Under Domain Structure on the left, click Deployments.
In the Deployments table, select the libraries WccAdfCustomSkin.jar and WccAdfStandardSkin.jar from the list of deployments, and click the Delete button to delete these libraries.
Redeploy both of the skin jar files.
1. Click the Install at the top or bottom of the Deployments table.
2. Select the WccAdfCustomSkin.jar and WccAdfStandardSkin.jar files, and click Next.
3. Target the libraries to the WCCADF_server1 Managed Server and the Administration Server, and click Finish.4. Restart the Administration Server in the WebCenter Content user interface domain.
Start the WCCADF_server1 Managed Server in the WebCenter Content user interface domain.
Associate the WebCenter Content user interface to Content Server through the connection architecture:
Set the variable WL_HOME to the location of the WebLogic Server instance. For example:
WL_HOME=WCCUI_MW_HOME/wlserver_10.3
Go to WCCUI_MW_HOME/oracle_common/webcenter/wccadf/ConnArchWlstResources/common/bin/.
Run the custom WLST command manageconnwlst.sh, which is present in this directory:
wls:/offline> connect() Please enter your username :weblogic Please enter your password : Please enter your server URL [t3://localhost:7001] :t3://host:port of WebCenter Content user interface Managed Server
Update the RIDC connection to the WebCenter Content user interface Managed Server:
wls:/mydomain/serverConfig>updateRIDCConnection('ADF_UI_APP_NAME','WccAdfDefaultConnection',connUrl='idc://contentserver_host:intradoc_port',credUsername='ucm_admin_user')
In the command, ADF_UI_APP_NAME is the Oracle WebCenter Content - Web UI application.
For example:
connect('weblogic','password','t3://myuihost.example.com:16225')
updateRIDCConnection('Oracle WebCenter Content - Web UI', 'WccAdfDefaultConnection',connUrl='idc://mycshost.example.com:4444', credUsername='weblogic')
At this point the WebCenter Content user interface application instance has been set up and associated with the WebCenter Content Managed Server that was installed on the first machine.
Restart the Content Server Managed Server, as described in Section 10.3, "Restarting a Managed Server."
Restart the WebCenter Content user interface Managed Server, as described in Section 10.3, "Restarting a Managed Server."
Content Server and the WebCenter Content user interface will need to access the same user directory. Standard LDAP offerings such as Oracle Internet Directory and Active Directory can be shared across domains. You can choose to configure a single sign-on solution using Oracle Access Manager or Oracle Single Sign-On, using the standard guidelines for such integration.
For more information about LDAP options, see Section 3.9, "Reassociating the Identity Store with an External LDAP Authentication Provider."
Out of the box, the WebCenter Content user interface requires one WebCenter Content administrator user to function:
The administrator user was specified in the credUsername parameter of the updateRIDCConnection() WLST command that was used to connect to the WebCenter Content user interface Managed Server, in Section 12.5, "Deploying the WebCenter Content User Interface Application," Step 9d.
You will need a user with the chosen name in the LDAP store or stores. Without this administrator user, the WebCenter Content user interface deployment will not work.
The user must have Administrators rights for the WebCenter Content Managed Server.
You can access the WebCenter Content user interface through the following URL:
http://ui-host:wccui-port/wcc/faces/wccmain
The WebCenter Content user interface application runs on port 16225 by default.
To complete the workflow configuration for the WebCenter Content user interface, you need to set UseDatabaseWfInQueue=true and EmailNotificationType=ContentUI in the config.cfg file for Content Server, restart the Managed Servers, and verify the configuration. The UseDatabaseWfInQueue configuration variable enables the WebCenter Content user interface to filter workflows assigned to a user. The EmailNotificationType configuration variable specifies where the links in notification emails point for workflows and subscriptions in different Content Server user interfaces, and its default value is NativeWebUI.
To complete the workflow configuration:
Add UseDatabaseWfInQueue=true (or UseDatabaseWfInQueue=1) to the WCC_DOMAIN/ucm/cs/config/config.cfg file.
Make sure that the WCC_DOMAIN/ucm/cs/config/config.cfg file contains the EmailNotificationType variable with either of the following settings:
To generate emails with links that point only to the WebCenter Content user interface, set EmailNotificationType=ContentUI in config.cfg.
To generate emails with links that point to both the WebCenter Content user interface and the native 11g user interface, set EmailNotificationType=ContentUI,NativeWebUI in config.cfg.
Restart the Content Server Managed Server, as described in Section 10.3, "Restarting a Managed Server."
Click the alert that appears on the Content Server home page after restart: Click to complete workflow setup.
Ensure that Content Server returns a success message: Workflow setup is now complete.
Restart the WebCenter Content user interface Managed Server, as described in Section 10.3, "Restarting a Managed Server."
For more information about workflows, see ”Managing Workflows” in Oracle Fusion Middleware Managing Oracle WebCenter Content.