17 Extending the Domain to Include WebCenter Content User Interface

You need to perform certain tasks in order to extend the enterprise deployment domain to include Oracle WebCenter Content User Interface software.

This chapter provides information on modifying system-level setting through MBeans and configuring http server with the WebCenter Content user interface cluster.

Extending the Domain for WebCenter Content User Interface

The instructions for extending the existing enterprise deployment domain with the Oracle WebCenter Content user interface software are detailed in this section.

Extending the domain involves the following tasks.

Starting the Configuration Wizard

Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain.

Note:

If you added any customizations directly to the start scripts in the domain, those are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh and configure it, 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:

  1. Stop any managed servers that are modified by this domain extension. Managed Servers that are not effected can remain on-line.
  2. For any managed servers to be modified, verify that the managed server shutdown has completed.
  3. Stop the Administration Server once all managed servers are in a steady state.
  4. Navigate to the following directory and start the WebLogic Server Configuration Wizard.
    cd $ORACLE_HOME/oracle_common/common/bin
./config.sh

Navigating the Configuration Wizard Screens to Extend the Domain

Follow the instructions in the following sections to create and configure the domain for the topology with static clusters.

Extending the Domain with Static Clusters

Follow the instructions in this section to create and configure the domain for the topology.

Note:

You can use the same 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 creation and configuration includes the following tasks:

Task 1   Selecting the Domain Type and Domain Home Location

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 Server domain home you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment.

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.

Task 2   Selecting the Configuration Template

On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:

  • Oracle WebCenter Content - Web UI - [wccontent]

    In addition, the following additional templates should already be selected, because they were used to create the initial domain:

    • Oracle Universal Content Management - Content Server - [wccontent]

    • Oracle SOA Suite - [soa]

    • Oracle Universal Content Management - Inbound Refinery - [wccontent]

    • Oracle WebCenter Enterprise Capture - [wccapture]

    • Oracle Enterprise Manager - [em]

    • Oracle WSM Policy Manager - [oracle_common]

    • Oracle JRF - [oracle_common]

    • WebLogic Coherence Cluster Extension - [wlserver]

Tip:

More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.

Task 3   Specifying JDBC Data Sources Information

Click Convert to GridLink, update the required database details, and then click Next.

Task 4   Specifying the Frontend Host

Specify wcc.example.com in the Frontend Host field.

Specify 0 as the Frontend HTTP Port and 443 as the Frontend HTTPS port.

Note:

By default, server instances in a cluster communicate with one another by 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.
Task 5   Providing the GridLink Oracle RAC Data Sources Details

On the GridLink Oracle RAC Data Sources screen, perform the following tasks.

In the SCAN, Host Name, and Port section:

  1. Select the SCAN check box.

  2. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.

  3. In the Port field, enter the SCAN listening port for the database (for example, 1521).

In the ONS Host and Port section: These values are not required when you are using an Oracle 12c database or later versions because the ONS list is automatically provided from the database to the driver.

Click Next.

Task 6   Testing the JDBC Data Sources

Click Next to continue.

Task 7   Providing the GridLink Oracle RAC Component Schema Details

Click Next to continue.

Task 8   Testing the JDBC Component Schema

Click Next to continue.

Task 9   Specifying Credentials for wccadfConnectUser

On the Credentials screen, enter the WebLogic user name(not weblogic_wcc) and password.

Click Next to continue.

Task 10   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

Topology

Task 11   Configuring Managed Servers

On the Managed Servers screen, a new Managed Server appears in the list of servers.

Perform the following tasks to modify the default Managed Server and create a second Managed Server:

  1. Rename the default Managed Server to WLS_WCCUI1.

  2. Click Add to create a new Managed Server and name it WLS_WCCUI2.

    Tip:

    The server names recommended here will be used throughout this document; if you choose different names, be sure to replace them as needed.

  3. Use the following table to fill in the rest of the columns for each Oracle WebCenter Content user interface Managed Server.

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.

Server Name Listen Address Listen Port Enable SSL SSL Listen Port Administration Port Server Groups

WLS_WCCUI1

WCCHOST1

Disabled

No

16226

9004

UCM-ADF-MGD-SVR

WLS_WCCUI2

WCCHOST2

Disabled

No

16226

9004

UCM-ADF-MGD-SVR
Task 12   Configuring a Cluster

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:

  1. Click the Add button.

  2. Specify WCCUI_Cluster in the Cluster Name field.

  3. From the Dynamic Server Groups drop-down list, select Unspecified.

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.

Task 13   Assigning Server Templates

Click Next to proceed to the next screen.

Task 14   Configuring Dynamic Servers
Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.

  1. Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.

  2. Confirm the Server Template selection is Unspecified.

  3. Click Next.

Task 15   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign WLS_WCCUI1 and WLS_WCCUI2 to the new cluster, WCCUI_Cluster:

  1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, WCCUI_Cluster.

  2. In the Servers pane, assign WLS_WCCUI1 to WCCUI_Cluster by doing one of the following:

    • Click the WLS_WCCUI1 Managed Server once to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane.

    • Double-click WLS_WCCUI1 to move it beneath the selected cluster in the clusters pane.

  3. Repeat to assign WLS_WCCUI2 to WCCUI_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.

Task 16   Configuring Coherence Clusters

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.

Task 17   Verifying the Existing Machines

Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.

Click Next to proceed.

Task 18   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Oracle WebCenter Content user interface Managed Servers you just created to the corresponding machines in the domain.

Assign WLS_WCCUI1 to WCCHOST1, and assign WLS_WCCUI2 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.

Task 19   Configuring Virtual Targets

Click Next to proceed to the next screen.

Task 20   Configuring Partitions

Click Next to proceed to the next screen.

Task 21   Reviewing Configuration Summary

Click Update to proceed to the next screen.

Task 22   Reviewing Configuration Progress

After all the processes are complete, click Next to proceed to the next screen.

Task 23   Reviewing Your Configuration Specifications and Configuring the Domain

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

Task 24   Writing Down Your Domain Home and Administration Server URL

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 you need the Administration Server URL to access the WebLogic Remote Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the configuration wizard.

Task 25   Start the Administration Server

Start the Administration Server to ensure the changes you have made to the domain have been applied.

After you have completed extending the domain with static clusters, go to Propagating the Domain Configuration to WLS_WCCUI1 and WLS_WCCUI2.

Update the WebLogic Servers Security Settings

This section contains information about WebLogic Servers security settings.

Follow the steps described in Updating the WebLogic Servers Security Settings and update SSL settings for the WLS_WCCUI1 and WLS_WCCUI2 servers.

Propagating the Domain Configuration to WLS_WCCUI1 and WLS_WCCUI2

You need to perform the following steps in order to propagate the domain configuration to the WebCenter Content user interface Managed Servers.

To propagate the start scripts and classpath configuration from the Administration Server's domain directory to the Managed Server domain directory:
  1. Create a copy of the Managed Server domain directory and the Managed Server applications directory.
  2. Run the following pack command on WCCHOST1 to create a template pack:
    cd ORACLE_COMMON_HOME/common/bin

./pack.sh -managed=true -domain=ASERVER_HOME -template=edgdomaintemplateWCCUI.jar -template_name=edgdomain_templateWCCUI
  3. Run the following unpack command on WCCHOST1 to propagate the template created in the preceding step to the WLS_WCCUI1 domain directory:
    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME -template=edgdomaintemplateWCCUI.jar -app_dir=APPLICATION_HOME -overwrite_domain=true
  4. Run the following command on WCCHOST1 to copy the template pack created in step 1 to WCCHOST2:
    scp edgdomaintemplateWCCUI.jar oracle@WCCHOST2:ORACLE_COMMON_HOME/common/bin
  5. Run the unpack command on WCCHOST2 to unpack the propagated template to the WLS_WCCUI2 domain directory.
    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME -template=edgdomaintemplateWCCUI.jar -app_dir=APPLICATION_HOME -overwrite_domain=true
  6. Restart the Administration Server to make these changes take effect, stopping it with the nmKill command, or with the Administration Console, and then starting it with the nmStart command. Before the restart, stop all Managed Servers in the domain through the Administration Console, and then start them after the restart. Log in to the Administration Console using the credentials for the weblogic user.

Modifying System-Level Settings Through MBeans

To ensure high availability, modify system-level configuration settings for WebCenter Content user interface through the System Configuration page in Fusion Middleware Control. The settings on this page configure the WebCenter Content user interface MBeans for the domain.

For information about how to modify system-level settings in Fusion Middleware control, see Modifying System Configuration Settings in Oracle Fusion Middleware Administering Oracle WebCenter Capture.

Modify the required parameters:
  1. To set the AdfScopeHaSupport parameter, complete the following steps:

    1. From the WebLogic Domain menu, select System MBean Browser.

    2. From the left navigation, go to Application Defined MBeans > oracle.adf.share.config > Domain:WCC server name > Application: Oracle WebCenter Content - Web UI > ADFConfig > ADFConfig > ADFConfig > ADFcConfiguration.

    3. Set the AdfScopeHaSupport parameter to true.

    4. Click Apply.

  2. To set the ClusterCompatible and TemporaryDirectory parameters, complete the following steps:

    1. From the WebLogic Domain menu, select System MBean Browser.

    2. From the left navigation, go to Application Defined MBeans > oracle.adf.share.config > Domain:WCC server name > Application: Oracle WebCenter Content - Web UI > ADFConfig > ADFConfig > ADFConfig > WccAdfConfiguration.

    3. Set the ClusterCompatible parameter to true.

    4. Set the TemporaryDirectory parameter to /u01/oracle/config/domains/WCCDomain/WCCUI_Cluster/tempdir.

    5. Click Apply.

  3. To set the PropConnectionUrl parameter, complete the following steps:

    1. From the WebLogic Domain menu, select System MBean Browser.

    2. From the left navigation, go to Application Defined MBeans > oracle.adf.share.connections > Domain:WCC server name > Application: Oracle WebCenter Content - Web UI > ADFConnections > ADFConnections > WccConnection > WccAdfServerConnection.

    3. Set the PropConnectionUrl parameter to idc://wccinternal.example.com:6300.

    4. Click Apply.

  4. To set the ApplicationUrl parameter, complete the following steps:

    1. From the WebLogic Domain menu, select System MBean Browser.

    2. From the left navigation, go to Application Defined MBeans > oracle.adf.share.connections > Domain:WCC server name > Application: Oracle WebCenter Content - Web UI > ADFConfig > ADFConfig > ADFConfig > WccAdfConfiguration.

    3. Set the ApplicationUrl parameter to https://wcc.example.com:443.

    4. Click Apply.

Configuring Oracle HTTP Server with the WebCenter Content User Interface Cluster

Configure Oracle HTTP Server with the WebCenter Content User Interface Cluster, set the front-end HTTP Host and Port for the cluster, and validate access through the load balancer.

This section contains the following tasks.

Configuring Oracle HTTP Server for the WLS_WCCUI Managed Servers

To configure Oracle HTTP Server for the WLS_WCCUI Managed Servers:
  1. For each of the web servers on WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/wcc_vh.conf and ORACLE_INSTANCE/config/OHS/ohs2/moduleconf/wcc_vh.conf files:
    # ADF UI
<Location /wcc>
  WebLogicCluster WCCHOST1:16226,WCCHOST2:16226
  WLSRequest ON
  WLCookieName WCCSID
  WLProxySSL ON
  WLProxySSLPassThrough ON
</Location>
  2. Restart both Oracle HTTP Servers.

Setting the Front-End HTTP Host and Port for the WebCenter Content User Interface Cluster

To set the front-end HTTP host and port for the WCC UI cluster:
  1. Log in to the WebLogic Server Administration Console.
  2. Go to the Change Center section and click Lock & Edit.
  3. Expand the Environment node in the Domain Structure tree on the left.
  4. Click Clusters.
  5. On the Summary of Clusters page, select WCCUI_Cluster.
  6. Open the HTTP tab.
  7. Set the following values:

    • Frontend Host: wcc.example.com

    • Frontend HTTPS Port: 443

  8. Click Save.
  9. Click Activate Changes in the Change Center section of the Administration Console.
  10. Restart the servers to make the front-end host directive in the cluster take effect.

Validating Access Through the Load Balancer

Verify URLs to ensure that appropriate routing and failover is working from the HTTP Server to WCCUI_Cluster. To verify the URLs:
  1. While WLS_WCCUI2 is running, stop WLS_WCCUI1 from the WebLogic Server Administration Console.
  2. Access https://wcc.example.com/wcc to verify that it is functioning properly. (You will not be able to retrieve reports or data because the Capture server is down.)
  3. Start WLS_WCCUI1 from the WebLogic Server Administration Console.
  4. Stop WLS_WCCUI2 from the WebLogic Server Administration Console.
  5. Access https://wcc.example.com/wcc to verify that it is functioning properly.
You can verify the cluster node to which you were directed after the traffic balancing provided through your load balancer and then again through the web tier.

Completing the Workflow Configuration

To complete the workflow configuration for the WebCenter Content user interface, you need to 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:
  1. Make sure that the WCCHOST1/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.

  2. Restart the Content Server Managed Server, using the WebLogic Server Administration Console.
  3. 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: The setup for workflow in queue was successful.

  4. Restart the WebCenter Content user interface Managed Server, using the WebLogic Server Administration Console for the WebCenter Content user interface domain.
or more information about workflows, see ”Managing Workflows” in Oracle Fusion Middleware Managing Oracle WebCenter Content.