11 Extending the Domain to Include Imaging

This chapter describes how to extend a domain with Oracle WebCenter Content: Imaging using the Oracle Fusion Middleware Configuration Wizard. It contains the following sections:

• Section 11.1, "Overview of Extending the Domain for Imaging"

• Section 11.2, "Enabling VIP4 and VIP5 in WCCHOST1and WCCHOST2"

• Section 11.3, "Extending the Domain to Include Imaging"

• Section 11.4, "Disabling Host Name Verification for the WLS_IMG Managed Servers"

• Section 11.5, "Starting Node Manager on WCCHOST1 and WCCHOST2"

• Section 11.6, "Validating GridLink Data Sources for WCC_IMG1"

• Section 11.7, "Propagating the Domain Configuration to the Managed Server Domain Directories"

• Section 11.8, "Configuring a JMS Persistence Store for Oracle WebCenter Content: Imaging"

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

• Section 11.10, "Restarting the Administration Server"

• Section 11.11, "Starting the Imaging Managed Servers"

• Section 11.12, "Validating GridLink Data Sources for WLS_IMG2"

• Section 11.13, "Configuring System MBeans for Oracle WebCenter Content: Imaging"

• Section 11.14, "Enabling the Imaging Feature Set in Oracle WebCenter Content"

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

• Section 11.16, "Creating a Connection to Oracle WebCenter Content"

• Section 11.17, "Configuring BPEL CSF Credentials"

• Section 11.18, "Configuring a Workflow Connection"

• Section 11.19, "Configuring Oracle HTTP Server for the WLS_IMG Managed Servers"

• Section 11.20, "Setting the Frontend HTTP Host and Port"

• Section 11.21, "Validating Access Through Oracle HTTP Server"

• Section 11.22, "Configuring Node Manager for the WLS_IMG Managed Servers"

• Section 11.23, "Configuring Server Migration for the WLS_IMG Managed Servers"

• Section 11.24, "Backing Up the Installation"

Note:

Before starting the setup process, read the release notes for additional installation and deployment information. They are available on the Oracle Fusion Middleware Documentation Library at http://docs.oracle.com/cd/E23943_01/relnotes.htm.

11.1 Overview of Extending the Domain for Imaging

The Oracle WebCenter Content: Imaging system is installed using the WL_HOME and ORACLE_HOME locations created in Chapter 6, "Installing the Software for an Enterprise Deployment" on a shared storage. WCCHOST1 and WCCHOST2 mount MW_HOME and reuse the existing Oracle WebLogic Server, Oracle SOA Suite, and Oracle WebCenter Content binary installations. The pack and unpack utilities are used to bootstrap the domain configuration for the WLS_IMG1 and WLS_IMG2 servers in these two new nodes. As a result, you do not need to install any software in these two nodes. For the Imaging system to work properly, WCCHOST1 and WCCHOST2 must maintain the same system requirements and configuration that was required for installing Oracle Fusion Middleware in SOAHOST1 and SOAHOST2. Otherwise, unpredictable behavior in the execution of binaries may occur.

Extend the domain to include Imaging. Table 11-1 lists the steps for configuring Imaging and other tasks required for extending the domain with Imaging managed servers.

Table 11-1 Steps for Extending the Domain with Imaging

Step	Description	More Information
Prepare for extending the domain for Imaging	Enable a VIP mapping for each of the host names.	Section 11.2, "Enabling VIP4 and VIP5 in WCCHOST1and WCCHOST2"
Extend the domain for Imaging	Extend the Imaging domain you created in Chapter 8, "Creating a Domain for an Enterprise Deployment."	Section 11.3, "Extending the Domain to Include Imaging"
Disable host name verification for Imaging	Disable host name verification while setting up and validating the topology.	Section 11.4, "Disabling Host Name Verification for the WLS_IMG Managed Servers"
Start Node Manager on the WebCenter Content managed servers	Run the setNMProps.sh script and then start Node Manager on WCCHOST1 and on WCCHOST2.	Section 11.5, "Starting Node Manager on WCCHOST1 and WCCHOST2"
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 11.6, "Validating GridLink Data Sources for WCC_IMG1"
Propagate the domain configuration to the Imaging managed servers	Propagate the start scripts and classpath configuration from the Administration Server's domain directory to the managed server domain directories.	Section 11.7, "Propagating the Domain Configuration to the Managed Server Domain Directories"
Configure a JMS persistence store	Configure the location for the JMS persistence stores as a directory that is visible to both Imaging managed servers.	Section 11.8, "Configuring a JMS Persistence Store for Oracle WebCenter Content: Imaging"
Configure a default persistence store	Configure a default persistence store for transaction recovery.	Section 11.9, "Configuring a Default Persistence Store for Transaction Recovery"
Restart the Administration Server for the domain	Stop and then restart the Administration Server.	Section 11.10, "Restarting the Administration Server"
Start the Imaging managed servers	Start the WLS_IMG1 and WLS_IMG2 managed servers.	Section 11.11, "Starting the Imaging Managed Servers"
Configure System MBeans for Imaging	Configure the InputDirectories, SampleDirectory, and GDFontPath MBeans in the System MBean Browser.	Section 11.13, "Configuring System MBeans for Oracle WebCenter Content: Imaging"
Enable the Imaging feature set in WebCenter Content	Enable the IpmRepository component of Content Server.	Section 11.14, "Enabling the Imaging Feature Set in Oracle WebCenter Content"
Add the listen addresses for the Imaging managed servers	Add the host names of the WLS_IMG1 and WLS_IMG2 managed servers (WCCHOST1VHN1 and WCCHOST2VHN1) to the SocketHostNameSecurityFilter parameter list.	Section 11.15, "Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content"
Create a connection between Imaging and Oracle WebCenter Content	Create a connection to Oracle WebCenter Content Server.	Section 11.16, "Creating a Connection to Oracle WebCenter Content"
Configure the BPEL CSF credentials	Configure the required credentials to communicate with Oracle SOA Suite	Section 11.17, "Configuring BPEL CSF Credentials"
Configure a workflow connection for Imaging	Create and test a workflow connection.	Section 11.18, "Configuring a Workflow Connection"
Configure Oracle HTTP Server with the extended domain	Configure the Oracle HTTP Server with the managed servers, and set the WLS Cluster address for IMG_Cluster.	Section 11.19, "Configuring Oracle HTTP Server for the WLS_IMG Managed Servers"
Set the front end HTTP host and port for Imaging.	Configure the front end HTTP host and port for IMG_Cluster.	Section 11.20, "Setting the Frontend 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 IMG_Cluster.	Section 11.21, "Validating Access Through Oracle HTTP Server"
Configure the Imaging managed servers to use custom key stores	Configure Node Manager with the custom key stores for Imaging.	Section 11.22, "Configuring Node Manager for the WLS_IMG Managed Servers"
Configure server migration for the Imaging managed servers.	Specify the Imaging managed server names, host names, and cluster name for migration.	Section 11.23, "Configuring Server Migration for the WLS_IMG Managed Servers"
Back Up the Imaging Configuration	Back up the newly extended domain configuration.	Section 11.24, "Backing Up the Installation"

11.2 Enabling VIP4 and VIP5 in WCCHOST1and WCCHOST2

The Oracle WebCenter Content: Imaging system uses a virtual host name as the listen addresses for the managed server on which it is running. These virtual host names and corresponding virtual IPs are required to enable server migration for the Oracle WebCenter Content: Imaging component. You must enable a VIP (VIP4/VIP5) mapping to WCCHOST1VHN1 on WCCHOST1 and WCCHOST2VHN1 on WCCHOST2, and must also correctly resolve the host names in the network system used by the topology (either by DNS Server or hosts resolution).

To enable the VIPs, follow the example described in Section 9.2, "Enabling SOAHOST1VHN1 on SOAHOST1 and SOAHOST2VHN1 on SOAHOST2."

11.3 Extending the Domain to Include Imaging

You extend the domain configured in Chapter 10, "Extending the Domain to Include Oracle WebCenter Content" to include Oracle WebCenter Content: Imaging. The instructions in this section assume that the Imaging 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 Imaging.

Note:

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

To extend the domain to include Oracle WebCenter Content: Imaging:

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. On SOAHOST1, 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
   

3. Start the Fusion Middleware Configuration Wizard:

   ./config.sh
   

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

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

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

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

   • Select this product:

     Oracle WebCenter Content: Imaging - 11.1.1.0 [wcc]

     The following products should already be selected and grayed out. They were selected when you created the domain (Section 8.3) or extended it for Oracle SOA Suite components (Section 9.3) or WebCenter Content (Section 10.3).

     Basic WebLogic Server Domain - 10.3.6.0 [wlserver_10.3]

     Oracle SOA Suite for developers - 11.1.1.0 [soa]

     Oracle SOA Suite - 11.1.1.0 [soa]

     Oracle Universal Content Management - Content Server - 11.1.1.0 [wcc]

     Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

     Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]

     Oracle JRF - 11.1.1.0 [oracle_common]

   Figure 11-1 Select Extension Source Screen for Imaging

   
   Description of "Figure 11-1 Select Extension Source Screen for Imaging"
   
   

   Click Next.

7. In the Configure JDBC Component Schema screen, which Figure 11-2 shows, do the following:

   1. Select IPM Schema only (for Imaging). 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 11-2 Configure JDBC Component Schema Screen for Imaging

      
      Description of "Figure 11-2 Configure JDBC Component Schema Screen for Imaging"
      
      

   3. Click Next.

8. In the Configure GridLink RAC Component Schema screen (Figure 11-3), do the following:

   1. Select IPM Schema (for Imaging). Leave the other data sources as they are.

      Figure 11-3 Configure GridLink RAC Component Schema Screen for Imaging

      
      Description of "Figure 11-3 Configure GridLink RAC Component Schema Screen for Imaging"
      
      

   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 DEV 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 Release 1 (11.1), use the virtual IP and port of each database instance listener; for example:

        custdbhost1-vip.mycompany.com (port 1521) 
        

        and

        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 Release 1 (11.1), use the hostname and port of each database's ONS service; for example:

        custdbhost1.mycompany.com (port 6200)
        

        and

        custdbhost2.mycompany.com (6200)
        

   3. Click Next.

   Note:

   Leave the UCM Schema, SOA Infrastructure, User Messaging Service, OWSM MDS Schema, and SOA MDS Schema information as is.

9. In the Test JDBC Component Schema screen, select the IPM 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 11-4

   
   Description of "Figure 11-4 "
   
   

   Click Next when the connection is successful.

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

    • JMS Distributed Destination

    • Managed Servers, Clusters and Machines

    • Deployment and Services

    Click Next.

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

12. In the Configure Managed Servers screen, add the required managed servers.

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

    Table 11-2 Managed Servers

    Name	Listen Address	Listen Port	SSL Listen Port	SSL Enabled
    WLS_IMG1	WCCHOST1VHN1	16000	n/a	No
    WLS_IMG2	WCCHOST2VHN2	16000	n/a	No

    
    

    Click Next.

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

    Table 11-3 Clusters

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

    
    

    Click Next.

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

    • IMG_Cluster:

      • WLS_IMG1

      • WLS_IMG2

    Click Next.

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

    Table 11-4 Machines

    Name	Node Manager Listen Address
    SOAHOST1	SOAHOST1
    SOAHOST2	SOAHOST2
    ADMINVHN	localhost
    WCCHOST1	WCCHOST1
    WCCHOST2	WCCHOST2

    
    

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

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

    • Assign WLS_IMG1 to WCCHOST1.

    • Assign WLS_IMG2 to WCCHOST2.

    Click Next.

17. In the Target Deployments to Clusters or Servers screen, ensure the following targets:

    • usermessagingserver and usermessagingdriver-email should be targeted only to SOA_Cluster . (The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional.)

    • WSM-PM should be targeted only to SOA_Cluster.

    • The oracle.rules*, oracle.sdp.* and oracle.soa.* deployments should be targeted to SOA_Cluster only, except for the oracle.soa.workflow.wc library, which should be targeted to both the SOA_Cluster and the IMG_Cluster.

    Click Next.

18. In the Target Service to Cluster or Servers screen, click Next.

19. In the Configuration Summary screen, click Extend.

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

21. In the Creating Domain screen, click Done.

22. Restart the Administration Server to make these changes to take effect. See Section 11.10, "Restarting the Administration Server."

11.4 Disabling Host Name Verification for the WLS_IMG Managed Servers

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server (see Chapter 13, "Setting Up Node Manager"). If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the EDG topology configuration is complete, as described in Chapter 13, "Setting Up Node Manager."

To disable host name verification:

1. Log in to WebLogic Server Administration Console.

2. In the Administration Console, select WLS_IMG1, then SSL, and then Advanced.

3. Click Lock & Edit.

4. Set host name verification to None.

5. In the Administration Console, select WLS_IMG2, then SSL, and then Advanced.

6. Set host name verification to None.

7. Save and activate the changes.

11.5 Starting Node Manager on WCCHOST1 and WCCHOST2

To start Node Manager on WCCHOST1 and WCCHOST2 if Node Manager has not started already:

1. On both WEBHOST1 and WEBHOST2, run the setNMProps.sh script, which is located in the ORACLE_COMMON_HOME/common/bin directory, to set the StartScriptEnabled property to true before starting Node Manager:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./setNMProps.sh
   

   Note:

   You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 16.11.3, "Incomplete Policy Migration After Failed Restart of SOA Server."

   Note:

   If the Imaging managed server is sharing the MW_HOME in a local or shared storage with Oracle WebCenter Content, as suggested in the shared storage configuration described in Chapter 3, "Preparing the Network for an Enterprise Deployment," it is not required to run setNMProps.sh again. In this case, Node Manager has already been configured to use a start script and it is likely already running in the node for Oracle WebCenter Content.

2. Run the following commands on both WCCHOST1 and WCCHOST2 to start Node Manager:

   cd WL_HOME/server/bin
   
   ./startNodeManager.sh
   

11.6 Validating GridLink Data Sources for WCC_IMG1

Before you propagate the domain configuration to WCCHOST2, verify that every GridLink data source you created is correctly configured and that the Oracle Notification Service (ONS) setup is correct for each data source on each managed server.

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

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, and click the name of one of the servers.

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

   Figure 11-5 Testing a GridLink Data Source for Imaging

   
   Description of "Figure 11-5 Testing a GridLink Data Source for Imaging"
   
   

   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 Imaging:

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 ONS tab and then the Testing tab (Figure 11-6).

5. Select a server, and click Test ONS.

   Figure 11-6 Testing the ONS Configuration for Imaging

   
   Description of "Figure 11-6 Testing the ONS Configuration for Imaging"
   
   

   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
   

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

11.7 Propagating the Domain Configuration to the Managed Server Domain Directories

To propagate the domain configuration:

1. Run the pack command on SOAHOST1 to create a template pack using the following commands:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./pack.sh -managed=true -domain=ORACLE_BASE/admin/domain_name/aserver/domain_name -template=edgdomaintemplateIMG.jar -template_name=edgdomain_templateIMG
   

2. Run the following command on SOAHOST1 to copy the template pack created in the previous step to WCCHOST2:

   Note:

   Assuming that WCCHOST1 shares the ORACLE_HOME with SOAHOST1, the template will be present in the same directory in WCCHOST1; otherwise, copy it also to WCCHOST1.

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

3. Run the unpack command on WCCHOST1 to unpack the propagated template.

   Note:

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

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

   Note:

   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. Repeat step 3 for WCCHOST2.

11.8 Configuring a JMS Persistence Store for Oracle WebCenter Content: Imaging

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 Content: Imaging are configured with no persistence store and use the Oracle WebLogic Server store (ORACLE_BASE/admin/domain_name/mserver/domain_name/servers/server_name/data/store/default). You must change the Imaging JMS server persistence store to use a shared base directory as follows:

1. Log in to the Oracle WebLogic Server Administration Console.

2. In the Domain Structure window, 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, IMGJMSServer1Store, which allows you identify the service it is created for) and target WLS_IMG1. Enter a directory that is located in shared storage so that it is accessible from both WCCHOST1 and WCCHOST2 (ORACLE_BASE/admin/domain_name/img_cluster_name/jms).

6. Click OK and activate the changes.

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

8. On the Summary of JMS Servers page, click the IpmJmsServer1 JMS Server (represented as a hyperlink) from 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 IMGJMSServer1Store.

11. Click Save and Activate.

12. Repeat the steps and create IMGJMSServer2Store for IMGJMSServer2.

11.9 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. Oracle 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 location for the default persistence store for WLS_IMG1:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure window, expand the Environment node and then click the Servers node.

3. On the Summary of Servers page, click WLS_IMG1 (represented as a hyperlink) in the Name column of the table. The settings page for the WLS_IMG1 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 persistent stores will store its data files. The directory structure of the path is as follows:

   ORACLE_BASE/admin/domain_name/img_cluster_name/tlogs
   

7. Click Save and activate the changes.

8. Repeat the step for the WLS_IMG2 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.

11.10 Restarting the Administration Server

Restart the Administration Server to make these changes take effect. To restart the Administration Server, stop it first using the Administration Console and then start it again as described in Section 8.4.4, "Starting the Administration Server on SOAHOST1."

11.11 Starting the Imaging Managed Servers

To start the WLS_IMG1 managed server on WCCHOST1:

1. Start the WLS_IMG1 managed server:

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

   2. In the Domain Structure window, expand the Environment node and then select Servers.

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

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

   5. Click Start.

2. Access http://WCCHOST1VHN1:16000/imaging to verify the status of WLS_IMG1. The Oracle WebCenter Content: Imaging login page appears. Enter your Oracle WebLogic Server administration user name and password to log in.

   Verify that the PROCESSES initialization parameter for the database is set to a high enough value. See Section 5.2.3, "Initialization Parameters" for details. This error often occurs when you start servers that are subsequent to the first server.

3. Start the WLS_IMG2 managed server:

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

   2. In the Domain Structure window, expand the Environment node and then select Servers.

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

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

   5. Click Start.

4. Access http://WCCHOST2VHN1:16000/imaging to verify the status of WLS_IMG2. The Oracle WebCenter Content: Imaging login page appears. Enter your Oracle WebLogic Server administration user name and password to log in.

Note:

These instructions assume that the host name verification displayed previously for the Oracle WSM or Oracle SOA Suite managed servers in SOAHOST2 and that the Node Manager is already running on SOAHOST2.

11.12 Validating GridLink Data Sources for WLS_IMG2

After you finish configuring WLS_IMG1 and WLS_IMG2 and start the Administration Server and managed servers, verify that every GridLink data source you created is correctly configured and that the Oracle Notification Service (ONS) setup is correct for each data source on each managed server.

Note:

To verify that the GridLink data source you created is correctly configured, follow instructions given in Section 11.6, "Validating GridLink Data Sources for WCC_IMG1," but now for second server, WLS_IMG2.

11.13 Configuring System MBeans for Oracle WebCenter Content: Imaging

To configure the following system MBeans for Oracle WebCenter Content: Imaging:

• InputDirectories

• SampleDirectory

• GDFontPath

1. Log in to Oracle Fusion Middleware Control at http://ADMINVHN:7001/em (Figure 11-7).

   Figure 11-7 System MBean Browser

   
   Description of "Figure 11-7 System MBean Browser"
   
   

2. In the left pane, expand the farm domain name, then expand WebLogic Domain, then the domain name, then IMG_Cluster, and then click the WLS_IMG1 link.

3. At the top of the right-hand panes, click the WebLogic Server drop-down menu and choose System MBean Browser.

4. Expand Application Defined MBeans and then oracle.imaging.

5. Expand Server: WLS_IMG1 and then config.

6. Click the config bean link.

7. In the right pane, set the InputDirectories MBean to specify the path to the input files: ORACLE_BASE/admin/domain_name/img_cluster_name/input_files.

   Please note that all Oracle WebCenter Content servers involved must be able to resolve this location (that is, via the NFS mount point).

8. Set the SampleDirectory MBean: ORACLE_BASE/admin/domain_name/img_cluster_name/input_files/Samples.

   To process input files, the input agent must have the appropriate permissions for the input directory, and the input directory must allow file locking. The input agent requires that the user account that is running the WebLogic Server service have read and write privileges for the input directory and for all files and subdirectories in the input directory. These privileges are required so that the input agent can move the files to the various directories as it works on them. File locking on the share is needed by the input agent to coordinate actions between servers in the cluster.

9. Set the GDFontPath MBean to specify the path to the GD fonts for the X Windows environment. Check with your system administrator. The default is likely /usr/share/X11/fonts/TTF or /usr/lib/X11/fonts/TTF.

10. Click Apply.

11.14 Enabling the Imaging Feature Set in Oracle WebCenter Content

To enable the Imaging feature set in Oracle WebCenter Content:

1. Log in to Oracle Content Server at http://WCCHOST1:16200/cs.

2. Open the Administration tray or menu, and choose Admin Server.

3. On the Component Manager page, enable the IpmRepository component.

4. Click Update and confirm the action.

5. Restart the managed server, and then restart all managed servers in the Oracle WebCenter Content cluster.

11.15 Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content

To add the host names of the WLS_IMG1 and WLS_IMG2 managed servers (WCCHOST1VHN1 and WCCHOST2VHN1, respectively) to the SocketHostNameSecurityFilter parameter list:

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|WCCHOST2|WEBHOST1|WEBHOST2
   

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

   SocketHostNameSecurityFilter=localhost|localhost.mycompany.com|WCCHOST1|WCCHOST2|WCCHOST1VHN1|WCCHOST2VHN1
   AlwaysReverseLookupForHost=Yes
   

4. Save the modified config.cfg file and restart the Oracle WebCenter Content servers for the changes to take effect.

11.16 Creating a Connection to Oracle WebCenter Content

To create a connection to Oracle WebCenter Content Server:

1. Log in to the WLS_IMG1 Imaging console at http://WCCHOST1VHN1:16000/imaging.

2. In the left-hand pane, click Manage Connections, and then Create Content Server Connection.

3. Enter a name and description for the new connection, and then click Next.

4. In the Connection Settings screen, do the following:

   • Make sure the Use Local Content Server checkbox is selected.

   • Set the Content Server port to 4444.

   • Add two servers to the Content Server pool:

     • WCCHOST1:4444

     • WCCHOST2:4444

   Click Next.

5. In the Connection Security screen, leave the default selections for the WebLogic user, and then click Next.

6. Review the connection details and click Submit.

11.17 Configuring BPEL CSF Credentials

When connecting to a BPEL system from Oracle WebCenter Content: Imaging, it is required to configure the required credential to communicate with Oracle SOA Suite. To add these credentials, use these steps:

1. On SOAHOST1, change directory to the common/bin location under the Oracle WebCenter Content home in SOAHOST1 (where your Administration Servers resides):

   cd WCC_ORACLE_HOME/common/bin
   

   (WCC_ORACLE_HOME is the Oracle home for Oracle WebCenter Content, which is MW_HOME/wcc in the EDG topology.)

2. Run the Oracle WebLogic Scripting Tool (WLST):

   ./wlst.sh
   

3. Run connect() and supply the user name, password, and Administration Server URL (t3://ADMINVHN:7001).

   wls:/offline> connect()
   

4. Create a CSF (Credential Store Framework) credential. This credential is the credential that Imaging will use to connect to the BPEL system. It should be a BPEL admin user. CSF credentials are user name/password pairs that are keyed by an alias and stored inside a named map in the CSF. Because of its integration with OWSM web services, Oracle WebCenter Content: Imaging is currently leveraging the standard OWSM CSF map named oracle.wsm.security. To create a credential, use the createCred WLST command:

   wls:/domain_name/serverConfig> createCred(map="oracle.wsm.security", key="basic.credential", user="weblogic", password="password_for_credential")
   

   The key in the command is the alias, which is used for the Credential Alias property of the BPEL connection definition in the Oracle WebCenter Content: Imaging administration user interface (also the Connection.CONNECTION_BPEL_CSFKEY_KEY property in the API). The alias basic.credential is used in the example because it is a standard default name used by OWSM and BPEL. However, the alias can be anything as long as it is unique within the map.

   Note:

   A new map will need to be created or the existing one updated if a different user and/or password is later used when integrating the Oracle SOA Suite system with a central LDAP and single sign-on (SSO) system. See Chapter 15, "Integrating with Oracle Identity Management" for details on the sample users created.

5. Run the list credentials command to verify that the credential was created:

   wls:/domain_name/serverConfig> listCred(map="oracle.wsm.security", key="basic.credential")
   {map=oracle.wsm.security, key=basic.credential}
   Already in Domain Runtime Tree
   
   [Name : weblogic, Description : null, expiry Date : null]
   PASSWORD: password_for_credential
   

11.18 Configuring a Workflow Connection

To configure a workflow connection:

1. Log in to the WLS_IMG1 imaging console at http://ECHMHOSTVHN1:16000/imaging.

2. From the navigator pane, under Manage Connections, click the Add icon and then Create Workflow Connection.

3. On the Workflow Connection Basic Information page, enter a name for the connection. The name will display in the Manage Connections panel. This field is required. Optionally, enter a brief description of the connection. The connection type defaults to Workflow Connection.

4. Click Next.

5. In the Workflow Connection Settings Page, do the following:

   1. In the HTTP Front End Address field, specify the host name or IP address, domain, and port number of the workflow server: http://soainternal.mycompany.com:80. This field is required.

   2. In the Credential Alias field, provide the credential alias created earlier as described in Section 11.17, "Configuring BPEL CSF Credentials."

   3. In the Provider field, enter your two Oracle SOA Suite server listen addresses separated by a comma: t3://SOAHOST1VHN1,SOAHOST2VHN1:8001

   4. Click the Test Connection button to confirm the connection parameters and see what composites exist on that BPEL machine.

   5. Click Next.

6. Modify the security grants if desired.

7. Click Next.

8. Click Submit.

11.19 Configuring Oracle HTTP Server for the WLS_IMG Managed Servers

To enable Oracle HTTP Server to route to IMG_Cluster, which contains the WLS_IMG1 and WLS_IMG2 managed servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster as follows:

1. On WEBHOST1 and WEBHOST2, add the following lines to ORACLE_BASE/admin/instance_name/config/OHS/component_name/mod_wl_ohs.conf:

   # Oracle WebCenter Content: Imaging Application
   <Location /imaging >
       WebLogicCluster WCCHOST1VHN1:16000,WCCHOST2VHN1:16000
       SetHandler weblogic-handler
       WLProxySSL ON
       WLProxySSLPassThrough ON
   </Location>
   
   # AXF WS Invocation
   <Location /axf-ws >
       WebLogicCluster WCCHOST1VHN1:16000,WCCHOST2VHN1:16000
       SetHandler weblogic-handler
       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.

11.20 Setting the Frontend HTTP Host and Port

You must set the frontend HTTP host and port for the Oracle WebLogic Server Imaging cluster (IMG_Cluster):

1. Log in to WebLogic Server Administration Console.

2. Go to the Change Center section and click Lock & Edit.

3. Expand the Environment node in the Domain Structure window.

4. Click Clusters.

5. On the Summary of Clusters page, select IMG_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 frontend host directive in the cluster take effect.

11.21 Validating Access Through Oracle HTTP Server

Verify URLs to ensure that appropriate routing and failover is working from the HTTP Server to the IMG_Cluster. To verify the URLs:

1. While WLS_IMG2 is running, stop WLS_IMG1 using the WebLogic Server Administration Console.

2. Access http://WEBHOST1:7777/imaging to verify it is functioning properly. (Please note that you will not be able to retrieve reports or data since the Imaging server is down.)

3. Start WLS_IMG1 from the WebLogic Server Administration Console.

4. Stop WLS_IMG2 from the WebLogic Server Administration Console.

5. Access http://WEBHOST1:7777/imaging to verify it is functioning properly.

6. Start WLS_IMG2 from the WebLogic Server Administration Console.

11.22 Configuring Node Manager for the WLS_IMG Managed Servers

It is assumed that the host names used by the WLS_IMG managed servers as listen addresses have already been configured for host name verification as explained in Section 10.15, "Configuring Node Manager for the WLS_WCC and WLS_IMG Managed Servers."

At this point, once the Imaging managed servers have been added to the domain, the procedure in Section 13.3.5, "Configuring Managed Servers to Use the Custom Keystores" should be performed so that the servers are configured to use custom key stores.

11.23 Configuring Server Migration for the WLS_IMG Managed Servers

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

• Server names:

  • WLS_SERVER1: WLS_IMG1

  • WLS_SERVER2: WLS_IMG2

• Host names:

  • HOST1: WCCHOST1

  • HOST2: WCCHOST2

• Cluster name:

  • CLUSTER: IMG_Cluster

11.24 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. Also refer to the Oracle Database Backup and Recovery Guide for information on database backup.

To back up the installation at this point:

1. Back up the 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 the web tier using the following command (as root):

      tar -cvpf BACKUP_LOCATION/web.tar MW_HOME
      

   3. Back up the Oracle instance on the 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 in SOAHOST1 to create the backup:

   tar -cvpf edgdomainback.tar ORACLE_BASE/admin/domain_name