This chapter describes how to extend the enterprise deployment domain with the Oracle WebCenter Content software.
This chapter provides information on installing the WebCenter Content, extending the domain for WebCenter Content and completing post-configuration and verification tasks.
This section provides instructions for installing WebCenter Content in an enterprise deployment domain.
This section contains the following procedures.
To start the installation program:
When the installation program appears, you are ready to begin the installation.
The installation program displays a series of screens, in the order listed in the following table.
If you need additional help with any of the installation screens, click the screen name.
| Screen | Description |
|---|---|
|
Installation Inventory Screen |
If you did not create a central inventory when you installed the Oracle Fusion Middleware Infrastructure software, then this dialog box appears. Edit the Inventory Directory field so it points to the location of your local inventory, and then click OK. |
|
This screen introduces you to the product installer. |
|
|
Use this screen to specify the location of your Oracle home directory. For more information about Oracle Fusion Middleware directory structure, see "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware. |
|
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, you can refer to one of the documents in the Roadmap for Verifying Your System Environment section in Planning Your Oracle Fusion Middleware Infrastructure Installation. |
|
|
If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates. If you do not have one and are sure you want to skip this step, clear the check box and verify your selection in the follow-up dialog box. |
|
|
Use this screen to verify the installation options you selected. Click Install to begin the installation. |
|
|
This screen allows you to see the progress of the installation. Click Next when the progress bar reaches 100% complete. |
|
|
Review the information on this screen, then click Finish to dismiss the installer. |
If you have followed the EDG shared storage recommendations, there is a separate shared storage volume for product installations on WCCHOST2, and you must also install the software on WCCHOST2. For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
After you complete the installation, you can verify it by successfully completing the following tasks.
Review the contents of the installation log files to make sure that no problems were encountered. For a description of the log files and where to find them, see "Understanding Installation Log Files" in Installing Software with the Oracle Universal Installer.
The contents of your installation vary based on the options you selected during the installation.
The addition of Oracle WebCenter Content will add the following directory and sub-directories:
/u01/oracle/products/fmw/wccontent common plugins ucm wccadf /u01/oracle/products/fmw/wccapture capture common plugins
For more information about the directory structure you should see after installation, see "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware.
You can also view the contents of your Oracle home using the viewInventory script. For more information, see "Viewing the contents of an Oracle home" in Installing Software with the Oracle Universal Installer.
Before you can configure an Oracle WebCenter Content domain, you must install the required schemas in a certified database for use with this release of Oracle Fusion Middleware.
Follow the instructions in this section to install the schemas.
To start the Repository Creation Utility (RCU):
After you start the RCU, you can then use the wizard screens to select and install the required schemas for your Oracle Fusion Middleware product. Schema creation involves the following tasks.
Click Next.
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load Concurrently. This procedure assumes that you have the necessary privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option will generate a SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.
Provide the database connection details for RCU to connect to your database.
In the Host Name field, enter the SCAN address of the Oracle RAC Database.
Enter the DBMS/Service details.
Enter the Schema Owner and Schema Password details.
Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.
Select existing prefix, and select the prefix you created while configuring the initial domain.
From the list of schemas, select the WebCenter Content schema. This will automatically select the following schemas as dependencies:
Oracle WebCenter Content Server — Complete
Oracle WebCenter Enterprise Capture
Oracle WebCenter Content Server — Search Only
The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.
Tip:
For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.
For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.
Tip:
You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.
Click Next to proceed, then click OK in the dialog window confirming that prerequisite checking for schema creation was successful.
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
Tip:
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
On the Map Tablespaces screen, review the information, and then click Next to accept the default values.
Click OK in the confirmation dialog box.
Navigate through the remainder of the RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.
To verify that the schemas were created successfully, and to verify the database connection details, use SQL*Plus or another utility to connect to the database, using the OCS schema name and the password you provided.
For example:
./sqlplus SQL*Plus: Release 11.2.0.4.0 Production on Fri Nov 1 08:44:18 2013 Copyright (c) 1982, 2013, Oracle. All rights reserved. Enter user-name: WCCEDG_OCS Enter password: ocs_password Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL>
This section provides instructions for extending the existing enterprise deployment domain with the Oracle WebCenter Content software.
Extending the domain involves the following tasks.
Note:
If you added any customizations directly to the start scripts in the domain, those will be overwritten by the Configuration Wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.sh and configure it to, for example, add custom libraries to the WebLogic Server classpath, specify additional Java command-line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.
To start the Configuration Wizard:
Follow the instructions in this section to extend the domain for the topology.
Note:
You can use the procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.
Domain extension and configuration includes the following tasks:
On the Configuration Type screen, select Update an existing domain.
In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration domain home you created in as part of the initial domain.
For more information about the directory location variables, see File System and Directory Variables Used in This Guide.
Tip:
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:
Oracle Universal Content Management - Content Server - 12.2.1 [wccontent]
In addition, the following additional templates should already be selected, because they were used to create the initial Infrastructure domain:
Oracle Enterprise Manager - 12.2.1.0 [em]
Oracle JRF - 12.2.1.0 [oracle_common]
WebLogic Coherence Cluster Extension - 12.2.1.0 [wlserver]
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
On the Database Configuration Type screen, select RCU Data.
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.
Verify and ensure that credentials in all the fields are the same that you have provided while configuring the Oracle Fusion Middleware Infrastructure.
Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the RCU Data option, see "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
For more information about the other options on this screen, see "Datasource Defaults" in Creating WebLogic Domains Using the Configuration Wizard.
On the JDBC Component Schema screen, select all the UCM schemas (for WebCenter Content) in the table.
When you select the schemas, the fields on the page are activated and the database connection fields are populated automatically.
Click Convert to GridLink and click Next.
On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in the following table.
| Element | Description and Recommended Value |
|---|---|
|
SCAN, Host Name, and Port |
Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, |
|
ONS Host and Port |
In the ONS Host field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, |
|
Enable Fan |
Verify that the Enable Fan check box is selected, so the database can receive and process FAN events. |
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Tip:
For more information about the other options on this screen, see "Test Component Schema" in Creating WebLogic Domains Using the Configuration Wizard.
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
Managed Server, Clusters and Coherence
JMS File Store
On the Managed Servers screen, a new Managed Server for Oracle WebCenter Content appears in the list of servers.
Perform the following tasks to modify the default Oracle WebCenter Content Managed Server and create a second Managed Server:
Rename the default Managed Server to WLS_WCC1.
Click Add to create a new Managed Server and name it WLS_WCC2.
Tip:
The server names recommended here will be used throughout this document; if you choose different names, be sure to replace them as needed.
Use the information in the following table to fill in the rest of the columns for each Oracle WebCenter Content Managed Server.
| Server Name | Listen Address | Listen Port | Enable SSL | SSL Listen Port | Server Groups |
|---|---|---|---|---|---|
|
WLS_WCC1 |
WCCHOST1 |
16200 |
No |
Disabled |
UCM-MGD-SVR |
|
WLS_WCC2 |
WCCHOST2 |
16200 |
No |
Disabled |
UCM-MGD-SVR |
Tip:
More information about the options on the Managed Server screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
In this task, you create a cluster of Managed Servers to which you can target the Oracle WebCenter Content software.
You will also set the Frontend Host property for the cluster, which ensures that, when necessary, WebLogic Server will redirect Web services callbacks and other redirects to wcc.example.com on the load balancer rather than the address in the HOST header of each request.
For more information about the wcc.example.com virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.
Use the Clusters screen to create a new cluster:
Click the Add button.
Specify WCC_Cluster in the Cluster Name field.
Leave the Cluster Address field blank.
Note:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Clusters screen to assign WLS_WCC1 and WLS_WCC2 to the new cluster, WCC_Cluster:
In the Clusters pane, select the cluster to which you want to assign the servers; in this case, WCC_Cluster.
In the Servers pane, assign WLS_WCC1 to WCC_Cluster by doing one of the following:
Click once on the WLS_WCC1 Managed Server to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane.
Double-click on WLS_WCC1 to move it beneath the selected cluster in the clusters pane.
Repeat to assign WLS_WCC2 to WCC_Cluster.
Tip:
More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the port number value at 9991, as it was defined during the initial Infrastructure domain creation.
Note:
For Coherence licensing information, refer to "Oracle Coherence" in Oracle Fusion Middleware Licensing Information.
Use the Machines screen to add two new machines:
Click the Add button.
Enter WCCHOST1 in the Name field.
Enter the host name of WCCHOST1 for the Node Manage Listener address. Leave the Node Manager port to the default value of 5556.
Repeat the above steps for WCCHOST2.
Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain, as shown in the following table.
Click Next to proceed.
| Name | Node Manager Listen Address | Node Manager Listen Port |
|---|---|---|
|
WCCHOST1 |
The value of the WCCHOST1 host name variable. For example, |
5556 |
|
WCCHOST2 |
The value of the WCCHOST2 host name variable. For example, |
5556 |
|
ADMINHOST |
Enter the value of the ADMINVHN variable. |
5556 |
Use the Assign Servers to Machines screen to assign the Oracle WebCenter Content Managed Servers you just created to the corresponding machines in the domain.
Assign ADMINVHN to ADMINHOST.
Assign WLS_WCC1 to WCCHOST1, and assign WLS_WCC2 to WCCHOST2.
Tip:
More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
In the JMS File Stores screen, assign the following directory for each of the WebCenter Content Persistence stores including Content Server JMS file stores:
ORACLE_RUNTIME/domain_name/WCC_Cluster/jms
In this example, replace RUNTIME_HOME with the value of the variable for you environment. Replace WCC_Cluster with the name you assigned to the WebCenter Content cluster.
Select Direct-Write from the drop-down list for Synchronous Write Policy (for both the stores).
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain extension will not begin until you click Update.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen will show the following items about the domain you just configured:
Domain Location
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the configuration wizard.
Restart the Administration Server to ensure the changes you have made to the domain have been applied.
Perform post configuration and verification tasks such as propagating the extended to the domain directories, starting the Node Manager, configuring the Content Server on the Managed Server, and so forth.
The following sections describe how to do post-configuration and verifications tasks for WebCenter Content.
After you have extended the domain with the Oracle Content, and you have restarted the Administration Server on WCCHOST1, you can then propagate the domain changes to the domain directories and machines.
Use the following steps to create a template JAR file that contains the domain configuration information, which now includes configuration information about the Oracle HTTP Server instances:
After you create the Managed Server domain directory, there are two domain home directories and two corresponding Node Manager instances on WCCHOST1. You use one Node Manager to control the Administration Server, running from Administration Server domain home, and you use the other Node Manager to control the Managed Servers, running from the Managed Server domain home.
You must start the two Node Managers independently.
Follow these steps to start the Node Manager from the Managed Server home:
For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
http://admin.example.com/console.Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors.Content Server updates the cwallet.sso file located in the MSERVER_HOME/config/fmwconfig directory when it starts. This change needs to be propagated back to the Administration Server.
To do this, copy the file to ASERVER_HOME/config/fmwconfig on WCCHOST1 using the following command (all on a single line):
scp -p \ WCCHOST1:/MSERVER_HOME/config/fmwconfig/cwallet.sso \ WCPHOST1:/ASERVER_HOME/config/fmwconfig/cwallet.sso
Note:
If any operation is performed in a WLS_WCCn server that modifies thecwallet.sso file in the MSERVER_HOME/config/fmwconfig/ directory, the file will have to be immediately copied to the Administration Server domain configuration directory on WCCHOST1 at ASERVER_HOME/config/fmwconfig.After you have propagated the domain configuration to WCCHOST2, you can start the Node Manager for the MSERVER_HOME domain directory.
Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors.Using a text editor, add the following options to each cluster node's MSERVER_HOME/ucm/cs/bin/intradoc.cfg file, where the directories specified are on a direct-bus-attached-controlled local disk and not a remote file system, such as a UNIX/Linux mounted NFS or clustered file system (like OCFS2, GFS2, or GPFS):
TraceDirectory=MSERVER_HOME/servers/WLS_WCCN/logs EventDirectory=MSERVER_HOME/servers/WLS_WCCN/logs/event/ ArchiverDoLocks=true DisableSharedCacheChecking=true
The trailing N should match your nodes' server names, like WLS_WCC1 is for WCCHOST1 and WLS_WCC2 is for WCCHOST2, and so on.
These changes will take effect after a restart of all WebCenter Content Managed Servers, at the end of the procedure described in Configuring Service Retries for Oracle WebCenter Content.
Note:
The directories can reside in any local disk path that you have determined to have enough space to hold the WebCenter Content logs and any trace that you may configure. The preceding paths are a suggestion.The following parameter should be set in the Content Server config.cfg file to enable login retries during an Oracle RAC failover:
ServiceAllowRetry=true
If this value is not set, users will need to manually retry any operation that was in progress when the failover began.
You must configure the Credential map to grant the Content Server administrative roles to the WCCAdministrators LDAP group.
The WCCAdministrators LDAP group is created in the Provisioning an Enterprise Deployment Administration User and Group section completed earlier. This configuration of credential map ensures consistent use of the LDAP administrative user for all configuration, administration, and maintenance tasks.
WCCAdministrators group:If you are planning to use the WebCenter Content user interface (in addition to the native user interface for Content Server), you need to enable the Content Server parameters.
From the Administration tray or menu, choose Admin Server. Select Component Manager and enable the following parameters:
AutoSuggestConfig
DynamicConverter
FrameworkFolders
In addition, you need to set up the Remote Intradoc Client (RIDC) for communication between the WebCenter Content user interface and Content Server.
You can also set the following Content Server parameters for folders and searching, for the WebCenter Content user interface. To set the Content Server parameters for folders and searching for the WebCenter Content user interface:
From the Administration menu, select Administration Server.
Select General Configuration.
On the General Configuration page, add the following parameters in the Additional Configuration Variables tab:
FoldersIndexParentFolderValues=true
FldEnforceFolderFileNameUniqueness=true
FldEnforceCaseInsensitiveNameUniqueness=true
SearchIndexerEngineName=OracleTextSearch or SearchIndexerEngineName=DATABASE.METADATA
Select either one of the values - OracleTextSearch or DATABASE.METADATA.
The following sections provide instructions for configuring Oracle HTTP Server for the WebCenter Content Cluster.
wcc.example.com virtual server. To configure Oracle HTTP Server for the WLS_WCC Managed Servers:https://wcc.example.com/cs to verify that it is functioning properly.https://wcc.example.com/cs to verify that it is functioning properly.