15 Extending the Domain to Include Capture

This chapter describes how to extend a domain with Oracle WebCenter Capture using the Oracle Fusion Middleware Configuration Wizard.

This chapter includes the following sections:

• Section 15.1, "Overview of Extending the Domain to Include Capture"

• Section 15.2, "Enabling VIP6 on WCCHOST1 and VIP7 on WCCHOST2"

• Section 15.3, "Extending the Domain for Capture"

• Section 15.4, "Restarting the Administration Server"

• Section 15.5, "Completing Postconfiguration and Verification Tasks for Capture"

• Section 15.6, "Configuring Oracle HTTP Server for the WLS_CPT Managed Servers"

• Section 15.7, "Configuring Node Manager for the WLS_CPT Managed Servers"

• Section 15.8, "Configuring Server Migration for the WLS_CPT Managed Servers"

• Section 15.9, "Backing Up the Installation"

Note:

Before starting the setup process, read the Oracle Fusion Middleware Release Notes for your platform for additional installation and deployment information.

15.1 Overview of Extending the Domain to Include Capture

The Capture system is installed using the WebLogic Server home (WL_HOME) and Oracle home (ORACLE_HOME) locations created in Chapter 7, "Installing the Software for an Enterprise Deployment," on a shared storage.

Extend the domain to include Capture. Table 15-1 lists the steps for configuring Capture and other tasks required for extending the domain with Capture Managed Servers.

Table 15-1 Steps for Extending the Domain with Capture

Step	Description	More Information
Prepare for extending the domain for Capture	Enable a virtual IP address mapping for each of the host names for the Capture WebLogic Server cluster.	Section 15.2, "Enabling VIP6 on WCCHOST1 and VIP7 on WCCHOST2"
Extend the domain for Capture	Extend the domain you created in Chapter 9, "Creating a Domain for an Enterprise Deployment."	Section 15.3, "Extending the Domain for Capture"
Propagate the domain configuration to the Capture Managed Servers	Propagate the start scripts and classpath configuration from the Administration Server's domain directory to the Managed Server domain directories.	Section 15.5.2, "Propagating the Domain Configuration to WLS_CPT1 and WLS_CPT2"
Configure JMS persistence stores	Configure the location for the JMS persistence stores as a directory that is visible to both Capture Managed Servers.	Section 15.5.5, "Configuring JMS Persistence Stores for Capture"
Configure a default persistence store	Configure a default persistence store for transaction recovery.	Section 15.5.6, "Configuring a Default Persistence Store for Transaction Recovery"
Start the Capture Managed Servers	Start the WLS_CPT1 and WLS_CPT2 Managed Servers.	Section 15.5.3.2, "Starting the Capture Managed Servers"
Verify the configuration of GridLink data sources and Oracle Notification Service (ONS)	Follow these instructions to verify that the configuration of GridLink data sources and ONS is correct.	Section 15.5.4, "Validating GridLink Data Sources for Capture"
Add the listen addresses for the Capture Managed Servers	Add the host names of the WLS_CPT1 and WLS_CPT2 Managed Servers (WCCHOST1VHN3 and WCCHOST2VHN3) to the SocketHostNameSecurityFilter parameter list.	Section 15.5.7, "Adding the Capture Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content"
Complete the Capture configuration	Complete the initial configuration of Capture and performing other postinstallation tasks.	Section 15.5.3, "Completing the Initial Capture Configuration"
Configure Oracle HTTP Server with the extended domain	Configure the Oracle HTTP Server with the Managed Servers, and set the WLS Cluster address for CPT_Cluster.	Section 15.6, "Configuring Oracle HTTP Server for the WLS_CPT Managed Servers"
Set the front-end HTTP host and port for Capture.	Configure the front-end HTTP host and port for CPT_Cluster.	Section 15.6.1, "Setting the Front-End HTTP Host and Port"
Validate access to WebCenter Content through Oracle HTTP Server	Verify the URLs to ensure that appropriate routing and failover is working from Oracle HTTP Server to CPT_Cluster.	Section 15.6.2, "Validating Access Through the Load Balancer"
Configure Node Manager for Capture	Specify the Capture Managed Server names, host names, and cluster name for migration.	Section 15.7, "Configuring Node Manager for the WLS_CPT Managed Servers"
Configure server migration for the Capture Managed Servers.	Specify the Capture Managed Server names, host names, and cluster name for migration.	Section 15.8, "Configuring Server Migration for the WLS_CPT Managed Servers"
Back Up the Capture configuration	Back up the newly extended domain configuration.	Section 15.9, "Backing Up the Installation"

15.2 Enabling VIP6 on WCCHOST1 and VIP7 on WCCHOST2

The Capture system uses virtual host names as the listen addresses for the Managed Servers on which Capture is running. These virtual host names and corresponding virtual IP addresses are required to enable server migration for the Capture component. If you have not previously done so, you must enable a virtual IP address mapping from VIP6 to WCCHOST1VHN3 on WCCHOST1 and from VIP7 to WCCHOST2VHN3 on WCCHOST2, and you must correctly resolve the host names in the network system used by the topology, with either DNS Server or /etc/hosts resolution.

To enable the virtual IP addresses, follow the procedure described in Section 6.6, "Enabling Virtual IP Addresses" if you have not yet completed it. These virtual IP addresses and virtual host names are required to enable server migration for the Capture servers. You can configure server migration for the Capture servers later for high availability purposes. For more information about configuring server migration, see Chapter 17, "Configuring Server Migration for an Enterprise Deployment."

15.3 Extending the Domain for Capture

You extend the domain configured in Chapter 11, "Extending the Domain to Include WebCenter Content," to include Oracle WebCenter Capture. The instructions in this section are based on the assumption that the Capture deployment uses the same database service as the Oracle WebCenter Content deployment (wccedg.mycompany.com). However, a deployment can choose to use a different database service specifically for Capture.

Note:

Before performing these steps, back up the domain as described in the Oracle Fusion Middleware Administrator's Guide.

To extend the domain for Capture:

1. Make sure that the database where you installed the repository is running.

   For Oracle RAC databases, it is recommended that all instances are running, so that the validation check later on becomes more reliable.

2. Shut down all Managed Servers in the domain.

3. On WCCHOST1, change the directory to the location of the Fusion Middleware Configuration Wizard. This is within the Oracle Common home directory (domain extensions are run from the node where the Administration Server resides).

   cd ORACLE_COMMON_HOME/common/bin
   

4. Start the Fusion Middleware Configuration Wizard:

   ./config.sh
   

5. In the Welcome screen, select Extend an existing WebLogic domain, and click Next.

6. In the Select a WebLogic Domain Directory screen, select the WebLogic Server domain directory (ORACLE_BASE/admin/domain_name/aserver/domain_name), and click Next.

7. In the Select Extension Source screen (Figure 15-1), make these selections:

   • Select Extend my domain automatically to support the following added products.

   • Select Oracle WebCenter Capture.

     The following products are grayed out if they were selected when you created the domain (Section 9.3) or extended it for WebCenter Content (Section 11.2), Inbound Refinery (Section 12.2), Oracle SOA Suite components (Section 13.3), or Imaging (Section 14.3).

     • Basic WebLogic Server Domain

     • Oracle SOA Suite

     • Oracle WebCenter Content: Imaging Viewer Cache

     • Oracle WebCenter Content: Imaging

     • Oracle Universal Content Management - Inbound Refinery

     • Oracle Universal Content Management - Content Server

     • Oracle Enterprise Manager Plugin for IBR

     • Oracle Enterprise Manager

     • Oracle WSM Policy Manager

     • Oracle JRF

   Figure 15-1 Select Extension Source Screen for Capture

   
   Description of "Figure 15-1 Select Extension Source Screen for Capture"
   
   

   Click Next.

8. In the Configure JDBC Component Schema screen, which Figure 15-2 shows, do the following steps:

   1. Select Capture Schema and Capture MSD Schema. Do not select any of the other existing schemas.

   2. For the RAC configuration, you can select Convert to GridLink or Convert to RAC multi data source (described in Appendix A, "Using Multi Data Sources with Oracle RAC"). For the instructions given here, select Convert to GridLink.

      After you select a RAC configuration, all selected schemas are grayed.

      Figure 15-2 Configure JDBC Component Schema Screen for Capture

      
      Description of "Figure 15-2 Configure JDBC Component Schema Screen for Capture"
      
      

   3. Click Next.

9. In the Configure GridLink RAC Component Schema screen (Figure 15-3), do the following steps:

   1. Select Capture Schema and Capture MSD Schema. Leave the other data sources as they are.

      Figure 15-3 Configure GridLink RAC Component Schema Screen for Capture

      
      Description of "Figure 15-3 Configure GridLink RAC Component Schema Screen for Capture"
      
      

   2. Enter values for the following fields, specifying the connection information for the GridLink RAC database that was seeded through RCU:

      • Driver: Select Oracle driver (Thin) for GridLinkConnections; Versions:10 and later.

      • Service Name: Enter the service name of the Oracle RAC database in lowercase letters, followed by the domain name; for example, wccedg.mycompany.com.

      • Username: Enter the complete user name for the database schema owner of the corresponding component.

        This book uses WCC as the prefix of user names for the database schemas.

      • Password: Enter the password for the database schema owner.

      • Select Enable FAN.

      • Enable SSL: Leave this option deselected.

        If you select SSL to enable Oracle Notification Service (ONS) notification encryption, provide the appropriate Wallet File and Wallet Password details.

      • Service listener: Enter the Oracle Single Client Access Name (SCAN) address and port for the Oracle RAC database being used. The protocol should be TCP.

        Oracle recommends that you use a SCAN address to specify the Service Listener (and OSN Host) so you do not need to update a GridLink data source containing a SCAN address if you add or remove Oracle RAC nodes. To determine the SCAN address, query the remote_listener parameter in the database:

        SQL>show parameter remote_listener;
         
        NAME              TYPE        VALUE
        -----             ------      -------
        remote_listener   string      db-scan.mycompany.com :1521
        

        Note:

        For Oracle Database 11g, use the virtual IP address and port of each database instance listener, as in these examples:

        custdbhost1-vip.mycompany.com (port 1521) 
        
        custdbhost2-vip.mycompany.com (1521)
        

        For Oracle Database 10g, use multi data sources to connect to an Oracle RAC database. For information about configuring multi data sources, see Appendix A, "Using Multi Data Sources with Oracle RAC."

      • ONS Host: Enter here also the SCAN address for the RAC database and the ONS remote port, as reported by the database:

        [orcl@CUSTDBHOST1 ~]$ srvctl config nodeapps -s
        ONS exists: Local port 6100, remote port 6200, EM port 2016
        

        Note:

        For Oracle Database 11g, use the host name and port of each database's ONS service, as in these examples:

        custdbhost1.mycompany.com (port 6200)
        
        custdbhost2.mycompany.com (6200)
        

   3. Click Next.

   Note:

   Leave the UCM Schema information as is.

10. In the Test JDBC Component Schema screen, select the CPT Schema row, then click Test Connections.

    The Connection Results Log displays the results. Ensure that the connection to the database that contains the schema was successful. If not, click Previous to return to the previous screen, correct your entry, and then retry the test.

    Figure 15-4 Test JDBC Component Schema Screen for Capture

    
    Description of "Figure 15-4 Test JDBC Component Schema Screen for Capture"
    
    

    Click Next when the connection is successful.

11. In the Optional Configuration screen, select the following options:

    • JMS Distributed Destination

    • Managed Servers, Clusters and Machines

    • Deployment and Services

    Click Next.

12. In the Select JMS Distributed Destination Type screen, select UDD from the drop-down list for the JMS modules of all Oracle Fusion Middleware components. Click Next. If an override warning appears, click OK to acknowledge it.

13. In the Configure Managed Servers screen, add the required Managed Servers.

    A server is created automatically. Rename this to WLS_CPT1 and add a new server called WLS_CPT2. Give these servers the attributes listed in Table 15-2. Do not modify the other servers that appear in this screen; leave them as they are.

    Table 15-2 Managed Servers for Capture

    Name	Listen Address	Listen Port	SSL Listen Port	SSL Enabled
    WLS_CPT1	WCCHOST1VHN3	16400	n/a	No
    WLS_CPT2	WCCHOST2VHN3	16400	n/a	No

    
    

    Click Next.

14. In the Configure Clusters screen, click Add to add the clusters as shown in Table 15-3. Do not modify the other clusters that appear in this screen; leave them as they are.

    Table 15-3 Cluster Configuration for Capture

    Name	Cluster Messaging Mode	Multicast Address	Multicast Port	Cluster Address
    CPT_Cluster	unicast	n/a	n/a	Leave empty

    
    

    Click Next.

15. In the Assign Servers to Clusters screen, add the following. Do not modify the other assignments that appear in this screen; leave them as they are.

    • CPT_Cluster:

      • WLS_CPT1

      • WLS_CPT2

    Click Next.

16. In the Configure Machines screen, open the Unix Machine tab. You should see the WCCHOST1 and WCCHOST2 machines and have the following entries:

    Table 15-4 Machines and Node Manager Listen Addresses

    Name	Node Manager Listen Address
    WCCHOST1	WCCHOST1
    WCCHOST2	WCCHOST2
    ADMINVHN	localhost

    
    

    Leave all other fields to their default values. Click Next.

17. In the Assign Servers to Machines screen, assign servers to machines as follows:

    • Assign WLS_CPT1 to WCCHOST1.

    • Assign WLS_CPT2 to WCCHOST2.

    Click Next.

18. In the Target Deployments to Clusters or Servers screen, make sure that targeting is done as follows:

    • The capture deployment is targeted only to CPT_Cluster.

    • NonJ2EEManagement Application is targeted only to AdminServer.

    Click Next.

19. In the Target Services to Cluster or Servers screen, click Next.

20. In the Configuration Summary screen, click Extend.

21. If a dialog window appears warning about conflicts in ports for the domain, click OK. This should be due to preexisting servers in the nodes and the warning can be ignored.

22. In the Creating Domain screen, click Done.

15.4 Restarting the Administration Server

You need to restart the Administration Server to make the domain extension changes take effect, using the Node Manager nmKill and nmStart commands through the Oracle WebLogic Scripting Tool (WLST), as described in Section 11.3, "Restarting the Administration Server." You can use the Administration Console instead of nmKill to stop the Administration Server. Log in to the Administration Console using the credentials for the weblogic_ecm user.

15.5 Completing Postconfiguration and Verification Tasks for Capture

The following sections describe how to do postconfiguration and verification tasks for Capture:

• Section 15.5.1, "Disabling Host Name Verification for the WLS_CPT Managed Servers"

• Section 15.5.2, "Propagating the Domain Configuration to WLS_CPT1 and WLS_CPT2"

• Section 15.5.3, "Completing the Initial Capture Configuration"

• Section 15.5.3.2, "Starting the Capture Managed Servers"

• Section 15.5.4, "Validating GridLink Data Sources for Capture"

• Section 15.5.5, "Configuring JMS Persistence Stores for Capture"

• Section 15.5.6, "Configuring a Default Persistence Store for Transaction Recovery"

• Section 15.5.7, "Adding the Capture Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content"

15.5.1 Disabling Host Name Verification for the WLS_CPT Managed Servers

For the enterprise deployment described in this guide, you set up the appropriate certificates to authenticate the different nodes with the Administration Server after you have completed the procedures to extend the domain for Capture. You must disable the host name verification for the WLS_CPT1 and WLS_CPT2 Managed Servers to avoid errors when managing the different WebLogic Server instances. For more information, see Section 9.4.5, "Disabling Host Name Verification."

You enable host name verification again once the enterprise deployment topology configuration is complete. For more information, see Section 16.3, "Enabling Host Name Verification Certificates for Node Manager."

15.5.2 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=ORACLE_BASE/admin/domain_name/aserver/domain_name -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=ORACLE_BASE/admin/domain_name/mserver/domain_name -template=edgdomaintemplateCPT.jar -app_dir=ORACLE_BASE/admin/domain_name/mserver/applications -overwrite_domain=true
   

   Notes:

   • Make sure to run unpack from the ORACLE_COMMON_HOME/common/bin/ directory, not from WL_HOME/common/bin/.

   • The ORACLE_BASE/admin/domain_name/mserver/ directory must exist before you run unpack. In addition, the ORACLE_BASE/admin/domain_name/mserver/applications/ directory must be empty.

4. Run the following command on WCCHOST1 to copy the template pack created in step 1 to WCCHOST2:

   scp edgdomaintemplateCPT.jar oracle@WCCHOST2:ORACLE_BASE/product/fmw/oracle_common/common/bin
   

5. Run the following unpack command on WCCHOST2 to unpack the propagated template to the WLS_CPT2 Managed Server domain directory:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./unpack.sh -domain=ORACLE_BASE/admin/domain_name/mserver/domain_name -template=edgdomaintemplateCPT.jar -app_dir=ORACLE_BASE/admin/domain_name/mserver/applications –overwrite_domain=true
   

   Notes:

   • Make sure to run unpack from the ORACLE_COMMON_HOME/common/bin/ directory, not from WL_HOME/common/bin/.

   • The ORACLE_BASE/admin/domain_name/mserver/ directory must exist before you run unpack. In addition, the ORACLE_BASE/admin/domain_name/mserver/applications/ directory must be empty.

   • The -overwrite_domain option in the unpack command allows unpacking a Managed Server template into an existing domain and existing applications directories. For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and EAR files in the Managed Server domain directory, they must be restored after this unpack operation.

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, as described in Section 11.3, "Restarting the Administration Server."

   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_ecm user.

15.5.3 Completing the Initial Capture Configuration

To complete the initial configuration of Capture in a WebLogic Server domain, use the weblogic_ecm system administrator to do these tasks:

1. Start the Capture Managed Server.

2. Assign roles to Capture users in Fusion Middleware Control.

3. Modify system-level settings through MBeans.

15.5.3.1 About Completing the Initial Capture Configuration

The system administrator who performs the installation and initial configuration must have system administration permissions, including access to Oracle Enterprise Manager Fusion Middleware Control and Oracle WebLogic Server. Before anyone can use Oracle WebCenter Capture, the system administrator needs to associate users from the LDAP identity store for the WebLogic Server domain with the Capture roles in Fusion Middleware Control.

To store groups and users, you can use the Oracle Internet Directory policy store. You can manage the policy store through Fusion Middleware Control.

The following Capture roles can be assigned to users:

• Capture Workspace Manager (CaptureWorkspaceManager)

• Capture Workspace Viewer (CaptureWorkspaceViewer)

• Capture User (CaptureUser)

The system administrator needs to assign the Workspace Manager both the CaptureWorkspaceManager and CaptureUser roles to provide access to the Workspace Console and the client. Only members of the CaptureUser role can use the Capture client. After an account has been granted the CaptureWorkspaceManager role, that account can sign in to the Workspace Console, create a workspace, and grant Capture access to other users who have been assigned Capture roles.

After starting the Capture Managed Server, the system administrator can modify system-level settings in Capture MBeans through Fusion Middleware Control or with Oracle WebLogic Scripting Tool (WLST) commands.

15.5.3.2 Starting the Capture Managed Servers

Start the Capture Managed Servers on WCCHOST1 and WCCHOST2.

To start the Capture Managed Servers:

1. Start the WLS_CPT1 Managed Server:

   1. Log in to the WebLogic Server Administration Console at http://ADMINVHN:7001/console.

   2. In the Domain Structure tree on the left, expand the Environment node, and then select Servers.

   3. On the Summary of Servers page, open the Control tab.

   4. Select WLS_CPT1 from the Servers column of the table.

   5. Click Start.

2. Access http://WCCHOST1VHN3:16400/dc-console to verify the status of WLS_CPT1. The Oracle WebCenter Capture login page appears. Enter your WebLogic Server administration user name and password to log in.

3. Start the WLS_CPT2 Managed Server:

   1. Log in to the WebLogic Server Administration Console at http://ADMINVHN:7001/console.

   2. In the Domain Structure tree on the left, expand the Environment node, and then select Servers.

   3. On the Summary of Servers page, open the Control tab.

   4. Select WLS_CPT2 from the Servers column of the table.

   5. Click Start.

4. Access http://WCCHOST2VHN3:16400/dc-console to verify the status of WLS_CPT2. The Oracle WebCenter Capture login page appears. Enter your WebLogic Server administration user name and password to log in.

15.5.3.3 Assigning Roles to Capture Users

Before anyone uses Capture, the system administrator (weblogic_ecm) needs to assign users from the LDAP credential store to the Capture roles in the policy store. You can do this through the Application Roles page in Fusion Middleware Control.

To assign Capture roles to the Workspace Manager:

1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

2. On the left, expand WebLogic Domain.

3. Right-click the domain name, choose Security, and then choose Application Roles.

   The Application Roles page opens.

   Figure 15-5 Application Roles for Capture

   
   Description of "Figure 15-5 Application Roles for Capture"
   
   

4. In the Application Stripe field, choose capture from the drop-down list, and then click the search icon.

   The search populates the table with roles for the Capture User, Capture Workspace Manager, Capture Viewer, and Capture User.

5. Edit the CaptureWorkspaceManager role.

6. Add a user to this role.

7. Edit the CaptureUser role.

8. Add the same user to this role, so that user has both the CaptureWorkspaceManager and CaptureUser roles.

For more information about how to assign roles to Capture users, see "Assigning Capture Roles in Oracle Enterprise Manager" in Oracle Fusion Middleware Administering Oracle WebCenter Capture.

15.5.3.4 Modifying System-Level Settings Through MBeans

You can modify system-level configuration settings for Capture, including system properties and SMTP settings for email, through the System Configuration page in Fusion Middleware Control. The settings on this page configure the Capture MBeans for the domain, which you can also modify with WLST commands.

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.

The following WLST commands also enable you to access or modify system-level settings:

• listCaptureConfig

• getCaptureConfig

• setCaptureConfig

For more information about these commands, see "Oracle WebCenter Capture Custom WLST Commands" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

15.5.4 Validating GridLink Data Sources for Capture

After the servers are started, verify that the GridLink data sources are correctly configured and that the ONS setup is correct. Perform this procedure for every GridLink data source created.

To verify the configuration of a GridLink data source for Capture:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree, expand Services, then click Data Sources.

3. Click the name of a GridLink data source that was created.

4. Click the Monitoring tab.

5. Click the Testing tab (Figure 15-6), select one of the servers, and click Test Data Source.

   Figure 15-6 Testing a GridLink Data Source for Capture

   
   Description of "Figure 15-6 Testing a GridLink Data Source for Capture"
   
   

   The test should be successful if the configuration is correct.

6. Repeat the test for every WebLogic Server instance that uses the GridLink data source.

To verify the configuration of ONS for a GridLink data source for Capture:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree, expand Services, then click Data Sources.

3. Click the name of a GridLink data source.

4. Click the Monitoring tab.

5. Click the ONS tab and then the Testing tab (Figure 15-7).

6. Select a server, and click Test ONS.

   Figure 15-7 Testing the ONS Configuration for Capture

   
   Description of "Figure 15-7 Testing the ONS Configuration for Capture"
   
   

   The test should be successful if the configuration is correct. If the ONS test fails, verify that the ONS service is running in the Oracle RAC database nodes:

   [orcl@CUSTDBHOST1 ~]$ srvctl status scan_listener
   SCAN Listener LISTENER_SCAN1 is enabled
   SCAN listener LISTENER_SCAN1 is running on node CUSTDBHOST1
   SCAN Listener LISTENER_SCAN2 is enabled
   SCAN listener LISTENER_SCAN2 is running on node CUSTDBHOST2
   SCAN Listener LISTENER_SCAN3 is enabled
   SCAN listener LISTENER_SCAN3 is running on node CUSTDBHOST2 
    
    
   [orcl@CUSTDBHOST1 ~]$ srvctl config nodeapps -s 
   ONS exists: Local port 6100, remote port 6200, EM port 2016 
    
    
   [orcl@CUSTDBHOST1 ~]$ srvctl status nodeapps | grep ONS
   ONS is enabled
   ONS daemon is running on node: CUSTDBHOST1
   ONS daemon is running on node: CUSTDBHOST2
   

7. Repeat the ONS test for every WebLogic Server instance that uses the GridLink data source.

15.5.5 Configuring JMS Persistence Stores for Capture

Configure the location for the JMS persistence stores as a directory that is visible from both nodes. By default, the JMS servers used by Oracle WebCenter Capture are configured with no persistence store and use the WebLogic Server store (ORACLE_BASE/admin/domain_name/mserver/domain_name/servers/server_name/data/store/ default). You must change each Capture JMS server persistence store to use a shared base directory.

To configure JMS persistence stores for Capture:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree on the left, expand the Services node, and then click the Persistence Stores node.

3. On the Summary of Persistence Stores page, click Lock & Edit.

4. Click New, and then Create File Store.

5. Enter a name (for example, CPTJMSServer1Store, which allows you identify the service it is created for) and target WLS_CPT1. Enter a directory that is located in shared storage so that it is accessible from both WCCHOST1 and WCCHOST2 (ORACLE_BASE/admin/domain_name/cpt_cluster_name/jms).

6. Click OK and activate the changes.

7. In the Domain Structure tree on the left, expand the Services node, and then click the Messaging->JMS Servers node.

8. On the Summary of JMS Servers page, click the CaptureJmsServer1 JMS server (represented as a hyperlink) in the Name column of the table.

9. On the settings page for the JMS server, click Lock & Edit.

10. In the Persistent Store drop-down list, select CPTJMSServer1Store.

11. Click Save and Activate.

12. Repeat the steps and create CPTJMSServer2Store for CaptureJMSServer2.

15.5.6 Configuring a Default Persistence Store for Transaction Recovery

Each server has a transaction log which stores information about committed transactions that are coordinated by the server that may not have been completed. WebLogic Server uses this transaction log for recovery from system crashes or network failures. To leverage the migration capability of the Transaction Recovery Service for the servers within a cluster, store the transaction log in a location accessible to the server.

Note:

Preferably, this location should be a dual-ported SCSI disk or on a Storage Area Network (SAN).

To set the locations of the default persistence stores for the Capture Managed Servers:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree on the left, expand the Environment node, and then click the Servers node.

3. On the Summary of Servers page, click WLS_CPT1 (represented as a hyperlink) in the Name column of the table. The settings page for the WLS_CPT1 server opens with the Configuration tab active.

4. Open the Services tab.

5. Click Lock & Edit.

6. In the Default Store section of the page, enter the path to the folder where the default persistence store will store its data files. The directory structure of the path is as follows:

   ORACLE_BASE/admin/domain_name/cpt_cluster_name/tlogs
   

7. Click Save and activate the changes.

8. Repeat the step for the WLS_CPT2 server.

Note:

To enable migration of the Transaction Recovery Service, specify a location on a persistent storage solution that is available to other servers in the cluster. Both WCCHOST1 and WCCHOST2 must be able to access this directory. This directory must also exist before you restart the server.

15.5.7 Adding the Capture Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content

The settings of allowable hosts, configured for Oracle WebCenter Content Server in Section 14.5.12, "Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content," also applies to Capture with an addition of listeners for the Capture Managed Servers. If this is the first time Content Server allowable hosts are added (in the case of a non-Imaging Oracle WebCenter Content enterprise deployment setup), then the following configuration needs to be done from Content Server.

Add the host names of the WLS_CPT1 and WLS_CPT2 Managed Servers (WCCHOST1VHN3 and WCCHOST2VHN3, respectively) to the SocketHostNameSecurityFilter parameter list.

To add the Capture server listen addresses to allowed hosts in Oracle WebCenter Content:

1. Open the file ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/config/config.cfg in a text editor.

2. Remove or comment out the following line:

   SocketHostAddressSecurityFilter=127.0.0.1|WCCHOST1-IP|WCCHOST2-IP|WEBHOST1-IP|WEBHOST2-IP
   

3. Add the following two lines to include the WLS_CPT1 and WLS_CPT2 listen addresses in the list of addresses that are allowed to connect to Oracle WebCenter Content:

   SocketHostNameSecurityFilter=localhost|localhost.mycompany.com|WEBHOST1|WEBHOST2|WCCHOST1|WCCHOST2|WCCHOST1VHN1|WCCHOST2VHN1|WCCHOST1VHN2|WCCHOST2VHN2|WCCHOST1VHN3|WCCHOST2VHN3|ucminternal.mycompany.com|load-balancer-host-name
   AlwaysReverseLookupForHost=Yes
   

   Note:

   The load balancer host name is the one that was used to configure the virtual servers in Section 3.3, "Load Balancers."

4. Save the modified config.cfg file, and restart the Oracle WebCenter Content servers, using the WebLogic Server Administration Console, for the changes to take effect.

15.6 Configuring Oracle HTTP Server for the WLS_CPT Managed Servers

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.

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 WCCHOST1VHN3:16400,WCCHOST2VHN3:16400
       SetHandler weblogic-handler
       WLCookieName JSESSIONID
       WLProxySSL ON
       WLProxySSLPassThrough ON
   </Location>
    
   # DC-Client
   <Location /dc-client>
       WebLogicCluster WCCHOST1VHN3:16400,WCCHOST2VHN3:16400
       SetHandler weblogic-handler
       WLCookieName JSESSIONID
       WLProxySSL ON
       WLProxySSLPassThrough ON
   </Location>
   

2. Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2:

   ORACLE_BASE/admin/instance_name/bin/opmnctl restartproc ias-component=ohsX
   

   For WEBHOST1, use ohs1 for ias-component and for WEBHOST2 use ohs2.

15.6.1 Setting the Front-End HTTP Host and Port

You must set the front-end HTTP host and port for the Capture cluster (CPT_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.mycompany.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.6.2 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 http://wcc.mycompany.com/dc-console to verify it is functioning properly. (Please note that you will not be able to retrieve reports or data since 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 http://wcc.mycompany.com/dc-console to verify it is functioning properly.

6. Start WLS_CPT2 from the WebLogic Server Administration Console.

15.7 Configuring Node Manager for the WLS_CPT Managed Servers

Oracle recommends using host name verification for communication between Node Manager and the servers in the domain. This requires the use of certificates for the different addresses communicating with the Administration Server and other servers.

If you have not already done so, configure the host names used by the WLS_CPT Managed Servers as listen addresses for host name verification as explained in Section 11.6, "Configuring Node Manager for Managed Servers."

At this point, after you have added the Capture Managed Servers to the domain, perform the procedure in Section 16.3.5, "Configuring Managed Servers to Use the Custom Keystores," for Capture.

15.8 Configuring Server Migration for the WLS_CPT Managed Servers

Server migration is required for proper failover of the Oracle WebCenter Capture components in the event of failure in any of the WCCHOST1 and WCCHOST2 nodes. For more details, see Chapter 17, "Configuring Server Migration for an Enterprise Deployment." For Capture, use the following values for the variables in that chapter:

• Server names:

  • WLS_SERVER1: WLS_CPT1

  • WLS_SERVER2: WLS_CPT2

• Host names:

  • HOST1: WCCHOST1

  • HOST2: WCCHOST2

• Cluster name:

  • CLUSTER: CPT_Cluster

15.9 Backing Up the Installation

After you have verified that the extended domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of problems in the further steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. At that point, the regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrator's Guide provides further details. For information on describing the Oracle HTTP Server data that must be backed up and restored, refer to the "Backup and Recovery Recommendations for Oracle HTTP Server" section in that guide. For information on how to recover components, see the "Recovery of Components" and "Recovery After Loss of Component" sections in the guide. For recommendations specific to recovering from the loss of a host, see the "Recovering Oracle HTTP Server to a Different Host" section in the guide. For information on database backup, see the Oracle Database Backup and Recovery Guide.

To back up the installation at this point:

1. Back up Oracle Web Tier on WEBHOST1:

   1. Shut down the instance using opmnctl.

      ORACLE_BASE/admin/instance_name/bin/opmnctl stopall
      

   2. Back up the Middleware home on Oracle Web Tier using the following command (as root):

      tar -cvpf BACKUP_LOCATION/web.tar MW_HOME
      

   3. Back up the Oracle instance on Oracle Web Tier using the following command:

      tar -cvpf BACKUP_LOCATION/web_instance_name.tar ORACLE_INSTANCE
      

   4. Start the instance using opmnctl:

      cd ORACLE_BASE/admin/instance_name/bin
      
      opmnctl startall
      

2. Back up the database. This is a full database backup (either hot or cold) using Oracle Recovery Manager (recommended) or operating system tools such as tar for cold backups if possible.

3. Back up the Administration Server and Managed Server domain directory to save your domain configuration. The configuration files all exist in the ORACLE_BASE/admin/domain_name/ directory. Run the following command on WCCHOST1 to create the backup:

   tar -cvpf edgdomainback.tar ORACLE_BASE/admin/domain_name