15 Extending the Domain to Include Capture

This chapter describes how to extend the enterprise deployment domain with Oracle WebCenter Enterprise Capture software.

Parent topic: Configuring the Enterprise Deployment

15.1 Overview of Extending the Domain to Include Capture

Oracle WebCenter Enterprise Capture provides organizations with a single system to capture both paper and electronic documents. This section provides a brief overview of Oracle WebCenter Enterprise Capture.

Capture supports both centralized and distributed image capture from a user-friendly web interface capable of using high-volume, production-level scanners. Support for the industry-standard TWAIN scanning interface enables Capture to use a wide variety of industry-leading document imaging scanners to digitize paper content. Existing electronic document files can be easily captured by users or automatically captured through an importing process that can monitor an email server or network folder. Once captured, documents are organized and indexed by applying metadata through manual or automated processes that use bar code recognition technology. After documents are completed, they are committed into a content management system. Capture is fully integrated with Oracle WebCenter Content to provide organizations with one system to capture, store, manage and retrieve their mission critical business content.

15.2 Extending the Domain for Capture

This section provides instructions for extending the existing enterprise deployment domain with the Capture software.

Extending the domain involves the following tasks.

15.2.1 Starting the Configuration Wizard

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:

  1. Shut down the domain completely before extending the domain. From the WebLogic Server Console, stop all managed servers and verify, and then stop the Administration Server.

    For more information, see the instructions for shutting down the Administration Server with Node Manager in Starting the Configuration Wizard on WCCHOST1.

  2. Navigate to the following directory and start the WebLogic Server Configuration Wizard. 
    cd ORACLE_HOME/oracle_common/common/bin
./config.sh

15.2.2 Navigating the Configuration Wizard Screens to Extend the Domain

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 Administration Server Domain for an Enterprise Deployment and while extending the domain with WebCenter Content, SOA and Inbound Refinery.

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 Enterprise Capture - 12.2.1 [wccapture]

    In addition, the following additional templates should already be selected, because they were used to create the initial domain. These templates are not required to run Capture. They are already selected as part of the enterprise deployment configuration.

    • Oracle Universal Content Mnagement - Content Server - 12.2.1 [wccontent]

    • Oracle SOA Suite - 12.2.1 [soa]

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

    • Oracle Enterprise Manager - 12.2.1.0 [em]

    • Oracle WSM Policy Manager - 12.2.1.0 [oracle_common]

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

Task 3    Specifying JDBC Component Schema Information

Click Convert to GridLink and click Next.

Task 4    Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, perform the following tasks.

  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 SCAN Port field, enter the SCAN listening port for the database (for example, 1521).

  4. In the ONS Host field, enter the SCAN address for the Oracle RAC database.

  5. In the ONS Port field, enter the ONS Remote port (for example, 6200).

Click Next.

Task 5    Testing the JDBC Connections

Click Next to continue.

Task 6    Selecting Advanced Configuration

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

  • Managed Server, Clusters and Machines

  • JMS File Store

Task 7    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_CPT1.

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

    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 information in the following table to fill in the rest of the columns for each Capture 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.

Table 15-1 Values Required for Each Capture Managed Server

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

WLS_CPT1

WCCHOST1

16400

No

Disabled

JRF-MAN-SVR CAPTURE-MGD-SVR WSM-PM-SVR

WLS_CPT2

WCCHOST2

16400

No

Disabled

JRF-MAN-SVR CAPTURE-MGD-SVR WSM-PM-SVR
Task 8    Configuring a Cluster

In this task, you create a cluster of Managed Servers to which you can target the Capture 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 CPT_Cluster in the Cluster Name field.

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 9    Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign WLS_CPT1 and WLS_CPT2 to the new cluster, CPT_Cluster:

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

  2. In the Servers pane, assign WLS_CPT1 to CPT_Cluster by doing one of the following:

    • Click the WLS_CPT1 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_CPT1 to move it beneath the selected cluster in the clusters pane.

  3. Repeat to assign WLS_CPT2 to CPT_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 10    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 0, as it was defined during the initial Infrastructure domain creation. Oracle Enterprise Capture does not use Coherence Clusters. This step is a part of the domain extension process.

Note:

For Coherence licensing information, refer to "Oracle Coherence" in Oracle Fusion Middleware Licensing Information.

Task 11    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 12    Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Capture Managed Servers you just created to the corresponding machines in the domain.

Assign WLS_CPT1 to WCCHOST1, and assign WLS_CPT2 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 13    Configuring the JMS File Store

In the JMS File Stores screen, assign the following directory for each of the WCC Persistence stores including UMS and BPM file stores:

ORACLE_RUNTIME/CPT_Cluster/jms

In this example, replace ASERVER_HOME with the value of the variable for you environment. Replace CPT_Cluster with the name you assigned to the Capture cluster.

Task 14    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 15    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 the URL is needed to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

Task 16    Start the Administration Server

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

15.3 Propagating the Domain Configuration to WLS_CPT1 and WLS_CPT2

Propagate the start scripts and classpath configuration from the Administration Server's domain directory to the Managed Server domain directory.

To propagate the domain configuration to the Capture Managed Servers:
  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=edgdomaintemplateCPT.jar -template_name=edgdomain_templateCPT
  3. Run the following unpack command on WCCHOST1 to propagate the template created in the preceding step to the WLS_CPT1 domain directory: 
    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME -template=edgdomaintemplateCPT.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 edgdomaintemplateCPT.jar oracle@WCCHOST2:ORACLE_COMMON_HOME/common/bin
  5. Run the unpack command on WCCHOST2 to unpack the propagated template to the WLS_CPT2 domain directory. 
    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME -template=edgdomaintemplateCPT.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.

15.4 Configuring Oracle HTTP Server for the Capture Cluster

To enable Oracle HTTP Server to route to CPT_Cluster, which contains the WLS_CPT1 and WLS_CPT2 Managed Servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster.

This section includes the following topics.

15.4.1 Configuring Oracle HTTP Server for the WLS_CPT Managed Servers

To configure Oracle HTTP Server for the WLS_CPT 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: 
    #DC-Console
<Location /dc-console>
   WebLogicCluster WCCHOST1:16400,WCCHOST2:16400
   WLSRequest ON
   WLCookieName JSESSIONID
   WLProxySSL ON
   WLProxySSLPassThrough ON
</Location>

#DC-Client
<Location /dc-client>
   WebLogicCluster WCCHOST1:16400,WCCHOST2VHN316400
   WLSRequest ON
   WLCookieName JSESSIONID
   WLProxySSL ON
   WLProxySSLPassThrough ON
</Location>
  2. Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2: 
    ./stopComponent.sh ohsn 
./startComponent.sh ohsn

    For WEBHOST1, use ohs1 (where n=1) and for WEBHOST2, use ohs2 (where n=2).

15.4.2 Setting the Front-End HTTP Host and Port for the Capture Cluster

To set the front-end HTTP host and port for the Capture 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 CPT_Cluster.
  6. Open the HTTP tab.
  7. Set the following values:

    • Frontend Host: wcc.example.com

    • Frontend HTTPS Port: 443

    • Frontend HTTP Port: 80

  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.

15.4.3 Validating Access Through the Load Balancer

Verify URLs to ensure that appropriate routing and failover is working from the HTTP Server to CPT_Cluster. To verify the URLs:
  1. While WLS_CPT2 is running, stop WLS_CPT1 from the WebLogic Server Administration Console.
  2. Access https://wcc.example.com/dc-console 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_CPT1 from the WebLogic Server Administration Console.
  4. Stop WLS_CPT2 from the WebLogic Server Administration Console.
  5. Access https://wcc.example.com/dc-console to verify that it is functioning properly.
  6. Start WLS_CPT2 from the WebLogic Server Administration Console.