Skip Headers
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content
11g Release 1 (11.1.1)

Part Number E15483-11
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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

This chapter includes the following sections:

Note:

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

14.1 Overview of Extending the Domain to Include Imaging

The Imaging system is installed using the WL_HOME and ORACLE_HOME locations created in Chapter 7, "Installing the Software for an Enterprise Deployment," on a shared storage.

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

Table 14-1 Steps for Extending the Domain with Imaging

Step Description More Information

Prepare for extending the domain for Imaging

Enable a virtual IP address mapping for each of the host names for the Imaging WebLogic Server cluster.

Section 14.2, "Enabling VIP4 on WCCHOST1 and VIP5 on WCCHOST2"

Extend the domain for Imaging

Extend the domain you created in Chapter 9, "Creating a Domain for an Enterprise Deployment," with Oracle WebCenter Content: Imaging.

Section 14.3, "Extending the Domain with Imaging"

Disable host name verification for Imaging

Disable host name verification while setting up and validating the topology.

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

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 14.5.2, "Propagating the Domain Configuration to WLS_IMG1 and WLS_IMG2"

Configure JMS persistence stores

Configure the location for the JMS persistence stores as a directory that is visible to both Imaging Managed Servers.

Section 14.5.3, "Configuring JMS Persistence Stores for Imaging"

Configure a default persistence store

Configure a default persistence store for transaction recovery.

Section 14.5.4, "Configuring a Default Persistence Store for Transaction Recovery"

Restart the Administration Server for the domain

Stop and then restart the Administration Server.

Section 14.4, "Restarting the Administration Server"

Start the Imaging Managed Servers

Start the WLS_IMG1 and WLS_IMG2 Managed Servers.

Section 14.5.5, "Starting the Imaging 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 14.5.6, "Validating GridLink Data Sources for Imaging"

Configure System MBeans for Imaging

Configure the InputDirectories, SampleDirectory, and GDFontPath MBeans in the System MBean Browser.

Section 14.5.8, "Configuring System MBeans for Imaging"

Enable the Imaging feature set in WebCenter Content

Enable the IpmRepository component of Oracle WebCenter Content Server.

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

Configure the Imaging Viewer Cache

Set the Imaging viewer to use cached documents.

Section 14.5.10, "Configuring the Imaging Viewer Cache"

Encrypt cached documents

Encrypt cached documents if additional security is required.

Section 14.5.11, "Encrypting Cached Documents"

Add the listen addresses for the Imaging Managed Servers

Add the host names of the WLS_IMG1 and WLS_IMG2 Managed Servers (WCCHOST1VHN2 and WCCHOST2VHN2) to the SocketHostNameSecurityFilter parameter list.

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

Create a connection between the Imaging and WebCenter Content Managed Servers

Create a connection to Oracle WebCenter Content Server.

Section 14.5.13, "Creating a Connection to Content Server"

Configure the BPEL CSF credentials

Configure the required credentials to communicate with Oracle SOA Suite

Section 14.5.14, "Configuring a BPEL CSF Credential"

Configure a workflow connection for Imaging

Create and test a workflow connection.

Section 14.5.15, "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 14.6, "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 14.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 IMG_Cluster.

Section 14.6.2, "Validating Access Through the Load Balancer"

Configure the Imaging Managed Servers to use custom keystores

Configure Node Manager with the custom keystores for Imaging.

Section 14.7, "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 14.8, "Configuring Server Migration for the WLS_IMG Managed Servers"

Back up the Imaging configuration

Back up the newly extended domain configuration.

Section 14.9, "Backing Up the Installation"


14.2 Enabling VIP4 on WCCHOST1 and VIP5 on WCCHOST2

The Imaging system uses virtual host names as the listen addresses for the Managed Servers on which Imaging is running. These virtual host names and corresponding virtual IP addresses are required to enable server migration for the Imaging component. If you have not previously done so, you must enable a virtual IP address mapping from VIP4 to WCCHOST1VHN2 on WCCHOST1 and from VIP5 to WCCHOST2VHN2 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 Imaging servers. You can configure server migration for the Imaging servers later for high availability purposes. For more information about configuring server migration, see Chapter 17, "Configuring Server Migration for an Enterprise Deployment."

14.3 Extending the Domain with Imaging

You can extend the domain created in Chapter 9, "Creating a Domain for an Enterprise Deployment", and then extended with WebCenter Content, Inbound Refinery, Capture, and Oracle SOA Suite, to include Oracle WebCenter Content: Imaging. The instructions in this section are based on the assumption 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 for 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. 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 14-1), make these selections:

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

    • Select these products:

      Oracle WebCenter Content: Imaging Viewer Cache

      Oracle WebCenter Content: Imaging

      (If you select one of the preceding products, the other one is automatically selected.)

      Notes:

      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), or Oracle SOA Suite components (Section 13.3).

      • Basic WebLogic Server Domain

      • Oracle SOA Suite

      • 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 14-1 Select Extension Source Screen for Imaging

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

    Click Next.

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

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

      Figure 14-2 Configure JDBC Component Schema Screen for Imaging

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

    3. Click Next.

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

    1. Make sure IPM Schema is selected. Leave the other data sources as they are.

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

      Description of Figure 14-3 follows
      Description of "Figure 14-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 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 Release 1 (11.1), 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, SOA Infrastructure, User Messaging Service, OWSM MDS Schema, and SOA MDS Schema information as is.

  10. 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 14-4 Test JDBC Component Schema Screen for Imaging

    Description of Figure 14-4 follows
    Description of "Figure 14-4 Test JDBC Component Schema Screen for Imaging"

    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_IMG1 and add a new server called WLS_IMG2. Give these servers the attributes listed in Table 14-2. Do not modify the other servers that appear in this screen; leave them as they are.

    Table 14-2 Managed Servers for Imaging

    Name Listen Address Listen Port SSL Listen Port SSL Enabled

    WLS_IMG1

    WCCHOST1VHN2

    16000

    n/a

    No

    WLS_IMG2

    WCCHOST2VHN2

    16000

    n/a

    No


    Click Next.

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

    Table 14-3 Cluster Configuration for Imaging

    Name Cluster Messaging Mode Multicast Address Multicast Port Cluster Address

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

    • IMG_Cluster:

      • WLS_IMG1

      • WLS_IMG2

    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 14-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_IMG1 to WCCHOST1.

    • Assign WLS_IMG2 to WCCHOST2.

    Click Next.

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

    • The usermessagingserver and usermessagingdriver-email deployments are 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 only to SOA_Cluster, except for the oracle.soa.workflow.wc library, which should be targeted to both SOA_Cluster and IMG_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 pre-existing servers in the nodes and the warning can be ignored.

  22. In the Creating Domain screen, click Done.

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

14.5 Completing Postconfiguration and Verification Tasks for Imaging

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

14.5.1 Disabling Host Name Verification for the WLS_IMG 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 Imaging. You must disable the host name verification for the WLS_IMG1 and WLS_IMG2 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."

14.5.2 Propagating the Domain Configuration to WLS_IMG1 and WLS_IMG2

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 Imaging 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=edgdomaintemplateIMG.jar -template_name=edgdomain_templateIMG
    
  3. Run the following unpack command on WCCHOST1 to propagate the template created in the preceding step to the WLS_WCC1 domain directory:

    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
    

    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 edgdomaintemplateIMG.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_IMG2 Managed Server domain directory:

    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
    

    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." Log in to the Administration Console using the credentials for the weblogic_ecm user.

14.5.3 Configuring JMS Persistence Stores for 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 WebLogic Server store (ORACLE_BASE/admin/domain_name/mserver/domain_name/servers/server_name/data/store/ default.).

To change the Imaging JMS server persistence store to use a shared base directory:

  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, 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 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 IpmJmsServer1 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 IMGJMSServer1Store.

  11. Click Save and Activate.

  12. Repeat the steps and create IMGJMSServer2Store for IpmJmsServer2.

14.5.4 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 Imaging 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_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 persistence 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.

14.5.5 Starting the Imaging Managed Servers

Start the Imaging Managed Servers on WCCHOST1 and WCCHOST2.

To start the Imaging Managed Servers:

  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 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_IMG1 from the Servers column of the table.

    5. Click Start.

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

  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 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_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 WebLogic Server administration user name and password to log in.

Note:

These instructions are based on the assumption that the host name verification displayed previously for the Oracle WSM or Oracle SOA Suite Managed Servers in WCCHOST2 and that the Node Manager is already running on WCCHOST2.

14.5.6 Validating GridLink Data Sources for Imaging

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

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

    Figure 14-5 Testing a GridLink Data Source for Imaging

    Description of Figure 14-5 follows
    Description of "Figure 14-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 Monitoring tab.

  5. Click the ONS tab and then the Testing tab (Figure 14-6).

  6. Select a server, and click Test ONS.

    Figure 14-6 Testing the ONS Configuration for Imaging

    Description of Figure 14-6 follows
    Description of "Figure 14-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
    
  7. Repeat the ONS test for every WebLogic Server instance that uses the GridLink data source.

14.5.7 Validating Deployment of the Imaging Viewer Cache

After the Imaging servers are started, verify that the Viewer Cache was deployed correctly.

To validate deployment of the Imaging Viewer Cache:

  1. In the WebLogic Server Administration Console, click Deployments under Domain Structure on the left.

  2. In the imaging-vc row of the Deployments table, confirm that the State value is Active and the Health value is OK.

    If the State or Health value is different for imaging-vc, you need to redeploy the feature before proceeding.

14.5.8 Configuring System MBeans for Imaging

You can configure the following system MBeans for Imaging:

  • InputDirectories

  • SampleDirectory

  • GDFontPath

To configure system MBeans for Imaging:

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

    Figure 14-7 System MBean Browser

    Description of Figure 14-7 follows
    Description of "Figure 14-7 System MBean Browser"

  2. In the navigation tree on the left, expand the farm domain name, then WebLogic Domain, then the domain name, then IMG_Cluster, and then WLS_IMG1.

  3. At the top, 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. On the right, set the InputDirectories MBean to specify the path to the input files: ORACLE_BASE/admin/domain_name/img_cluster_name/input_files.

    All Oracle WebCenter Content servers involved must be able to resolve this location (that is, through 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 System. Check with your system administrator. The default is likely /usr/share/X11/fonts/TTF or /usr/lib/X11/fonts/TTF.

  10. Click Apply.

14.5.9 Enabling the Imaging Feature Set in Oracle WebCenter Content

Enable the Imaging feature set in the Oracle WebCenter Content Server Component Manager.

To enable the Imaging feature set in Oracle WebCenter Content:

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

  2. From the Administration tray or menu, choose Admin Server, then Component Manager.

  3. On the Component Manager page, under Integration, select IpmRepository.

  4. Click Update to enable the IpmRepository component, and confirm the action:

    1. In the paragraph at the top of the Component Manager page, click advanced component manager.

    2. On the Advanced Component Manager page, verify that IpmRepository is in the Enabled Components box.

  5. Restart the Managed Server, as described in Section 9.4.3, "Starting the Administration Server on WCCHOST1," and then restart all Managed Servers in the Oracle WebCenter Content cluster, using the WebLogic Server Administration Console.

14.5.10 Configuring the Imaging Viewer Cache

The Imaging viewer can cache documents on the server outside of the repository to increase rendering speed on the client machine. Security for the cached documents is controlled by authentication for the server on which they are stored. If the server is considered secure, no additional security is necessary.

If additional security is required, you can encrypt cached documents, as described in Section 14.5.11, "Encrypting Cached Documents." For information about when to use the precache option and how to optimize ingestion and rendering when processing a large number of documents, see "Balancing Ingestion and Rendering When Viewer Cache is Enabled" in Oracle Fusion Middleware Administering Oracle WebCenter Content: Imaging.

To set the Imaging viewer to use cached documents, you need to set the following system MBeans:

  • ViewerCachePath

  • ViewerCacheDays

  • ViewerCacheEnablePrecache

To configure these MBeans for the Imaging Viewer Cache, use the method described in Section 14.5.8, "Configuring System MBeans for Imaging," as follows:

  • Set the ViewerCachePath MBean to the location where documents should be cached, and click Apply:

    ORACLE_BASE/admin/domain_name/img_cluster_name/ViewerCache
    

    Note:

    The ViewerCachePath MBean should be set to a location available to all servers in the cluster. If the directory path is not available to all servers, then each server will cache documents locally, resulting in multiple instances of the entire cache.

  • Set the ViewerCacheDays MBean to 30, and click Apply.

    Note:

    This configuration value specifies the number of days cached images should be retained before they are purged from the cache. Setting ViewerCacheDays equal to 0 prevents the cache from being purged.

  • Set the ViewerCacheEnablePrecache MBean to true, and click Apply.

    Note:

    This configuration value specifies whether documents should be cached as soon as they are ingested into Imaging (precached).

  • If you are going to encrypt cached document, configure Imaging to encrypt them, as Section 14.5.11, "Encrypting Cached Documents," describes, and then set the ViewerCacheEnableEncryption MBean to true.

    Note:

    This is an additional option to encrypt the page images in the cache. The password credential must exist on the domain before you set the ViewerCacheEnableEncryption MBean. To add a password credential, use the method described in Section 14.5.11, "Encrypting Cached Documents."

For information about moving the viewer cache to a new location, see "Changing the Viewer Cache Path" in Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Content.

14.5.11 Encrypting Cached Documents

If additional security is required, you can configure Imaging to encrypt cached documents. Encryption makes additional processing necessary to decrypt a document for viewing and reduces rendering speed. Even if Imaging is configured to encrypt the cached documents, there is a brief period of time during caching when generated documents are not encrypted.

To enable encryption of cached documents, add a new password credential to the domain through Oracle Enterprise Manager Fusion Middleware Control, and set the ViewerCacheEnableEncryption MBean.

To enable encryption of cached documents:

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

  2. Select the WebLogic Server domain for Oracle WebCenter Content.

  3. From the WebLogic Domain menu, choose Security and then Credentials.

  4. Select the map oracle.imaging. If no map named oracle.imaging exists, click Create Map, enter oracle.imaging for the map name, and then select it.

  5. On the oracle.imaging map, click Create Key. Name the key viewer.cache, and select the type Password.

  6. Enter a user name. The user name does not need to exist in any system.

  7. Enter a password, confirm it, and then click OK.

  8. Set the ViewerCacheEnableEncryption MBean to true, as described in Section 14.5.8, "Configuring System MBeans for Imaging."

For information about disabling encryption, see "Disabling Encryption of Cached Documents" in Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Content.

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

Add the host names of the WLS_IMG1 and WLS_IMG2 Managed Servers (WCCHOST1VHN2 and WCCHOST2VHN2, respectively) to the SocketHostNameSecurityFilter parameter list.

To add the Imaging 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 lines to include the WLS_IMG1 and WLS_IMG2 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|ucminternal.mycompany.com|load-balancer-host-name
    AlwaysReverseLookupForHost=Yes
    

    Notes:

  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.

14.5.13 Creating a Connection to Content Server

Create a connection to Oracle WebCenter Content Server connection in Imaging.

To create a Content Server connection:

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

  2. On the left, 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, make these changes:

    • Unselect Use Local Content Server.

    • Set the Content Server port to 6300.

    • Add the ucminternal.mycompany.com load balancer address under Content Server Pool.

    If you get a Permission denied error, go back to Section 14.5.12, "Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content," and add name of the host that was denied to the list of allowable hosts.

    Click Next.

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

  6. Review the connection details and click Submit.

14.5.14 Configuring a BPEL CSF Credential

When connecting to a BPEL system from Oracle WebCenter Content: Imaging, you need to configure the required credential to communicate with Oracle SOA Suite.

To add a BPEL CSF credential:

  1. On WCCHOST1, change the directory to the common/bin/ location under the WebCenter Content Oracle home in WCCHOST1 (where your Administration Server 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, 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_ecm", password="password_for_credential")
    

    The key value in the command is the alias, which is used for the Credential Alias property of the BPEL connection definition in the 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 or password, or both, is later used when integrating the Oracle SOA Suite system with a central LDAP and single sign-on (SSO) system. For details on the sample users created, see Chapter 18, "Integrating with Oracle Identity Management."

  5. Restart the Oracle SOA Suite and Imaging Managed Servers, using the WebLogic Server Administration Console.

14.5.15 Configuring a Workflow Connection

Create and test a workflow connection for Imaging.

To configure a workflow connection:

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

  2. 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 steps:

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

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

    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.

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

To configure Oracle HTTP Server for the WLS_IMG 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:

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

14.6.1 Setting the Front-End HTTP Host and Port

You must set the front-end HTTP host and port for the Imaging cluster (IMG_Cluster).

To set the front-end HTTP host and port for the Imaging 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 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 front-end host directive in the cluster take effect.

14.6.2 Validating Access Through the Load Balancer

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

To verify the URLs:

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

  2. Access http://wcc.mycompany.com/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://wcc.mycompany.com/imaging to verify it is functioning properly.

  6. Start WLS_IMG2 from the WebLogic Server Administration Console.

14.7 Configuring Node Manager for the WLS_IMG 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_IMG 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 Imaging Managed Servers to the domain, perform the procedure in Section 16.3.5, "Configuring Managed Servers to Use the Custom Keystores," for Imaging.

14.8 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. For more details, see Chapter 17, "Configuring Server Migration for an Enterprise Deployment." For Imaging, use the following values for the variables in that chapter:

14.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 about database backup, see the Oracle Database Backup and Recovery User's 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 in WCCHOST1 to create the backup:

    tar -cvpf edgdomainback.tar ORACLE_BASE/admin/domain_name