Skip Headers
Oracle® WebCenter Content Installation Guide
11g Release 1 (11.1.1)

Part Number E14495-07
Go to Documentation Home
Home
Go to Book List
Book List
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

6 Completing the Imaging Configuration

This chapter explains how to complete the initial configuration of Oracle WebCenter Content: Imaging in an Oracle WebLogic Server domain.

This chapter includes the following sections:

6.1 Completing the Initial Imaging Configuration

Before you complete the configuration of Imaging, your system needs to have Oracle WebCenter Content installed and configured. Imaging uses WebCenter Content for its repository.

You can use either WebCenter Content 11g or Oracle Universal Content Management (Oracle UCM) 10gR3 as the Imaging repository. For information about configuring WebCenter Content 11g, see Chapter 3, "Configuring Oracle WebCenter Content Applications," Chapter 4, "Completing the WebCenter Content Configuration," and Section 6.1.1.1, "Configuring WebCenter Content 11g to Work with Imaging." For information about using Oracle UCM 10gR3 as the repository, see Section 6.1.1.2, "Installing and Configuring Oracle UCM 10gR3 to Work with Imaging."

Note:

In a production system, Oracle WebCenter Content applications need to use an external Lightweight Directory Application Protocol (LDAP) authentication provider rather than the Oracle WebLogic Server embedded LDAP server, which is part of the default configuration. If you want to reassociate the identity store for Imaging with an external LDAP authentication provider, it is easier to do this before you complete the configuration of the Imaging Managed Server and before you connect it to the WebCenter Content 11g or Oracle UCM 10gR3 repository. For more information, see Section 3.9, "Reassociating the Identity Store with an External LDAP Authentication Provider."

The user who logs in first to an Imaging Managed Server is provisioned with full security throughout the server. When this user first logs in, Imaging provides a user interface to complete the configuration, including connecting to a repository or repositories and, optionally, to a workflow server.

If a value is specified in the DefaultSecurityGroup MBean before Imaging security is initialized, then when the first user logs in, the specified group is given full administrative permissions as well as the user logging in.

To complete the Imaging configuration, you need to perform all of the following tasks that apply to your system:

  1. Configuring a WebCenter Content Repository for Imaging

  2. Starting the Administration Server and the WebCenter Content Managed Server, as described in Chapter 9, "Verifying the Oracle WebCenter Content Configuration"

  3. Starting the Imaging Managed Server and Accessing the Web Client

  4. Connecting to a WebCenter Content Repository

  5. Configuring the GDFontPath MBean for a UNIX System

  6. Setting DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 11g

  7. Importing Definitions

6.1.1 Configuring a WebCenter Content Repository for Imaging

You can configure either WebCenter Content 11g or Oracle UCM (Oracle Content Server) 10g R3 as the repository for Imaging.

Note:

You will not be able to import or upload content to the Imaging system unless you have created a repository connection.

6.1.1.1 Configuring WebCenter Content 11g to Work with Imaging

WebCenter Content 11g is installed with Oracle WebCenter Content. When a WebCenter Content Managed Server and Imaging Managed Server are configured in an Oracle WebLogic Server domain on the same host machine, the configuration of WebCenter Content 11g to work with Imaging is automatic.

If WebCenter Content is installed in a domain that is later extended with Imaging, then WebCenter Content will not be reconfigured to work with Imaging until the next restart of the WebCenter Content Managed Server. In this case, you must restart WebCenter Content, as described in Section 9.3, "Restarting a Managed Server," before connecting to Oracle WebCenter Content Server from the Imaging web client, as described in Section 6.1.3, "Connecting to a WebCenter Content Repository."

If the WebCenter Content and Imaging Managed Servers are configured to run on different machines, configuring Imaging will not configure WebCenter Content to work with it. In this case, you must follow the manual configuration steps to configure WebCenter Content.

To configure WebCenter Content 11g manually to work with Imaging:

  1. Start the WebCenter Content Managed Server, as described in Section 9.2, "Starting Managed Servers."

  2. Access Content Server, as described in Section 4.3.1, "Starting Content Server."

  3. Enable the IpmRepository component:

    1. Choose Admin Server from the Administration tray or menu.

    2. On the Content Admin Server Component Manager page, select Integration.

    3. Select IpmRepository, and click the Update button.

      This option is selected by default if the Oracle WebLogic Server domain was configured with Fusion Middleware Configuration Wizard. If this option is already selected, you can close the Component Manager without clicking Update or restarting Content Server.

    4. Click the OK button to enable this feature.

    5. Restart Content Server, as described in Section 9.3, "Restarting a Managed Server."

      If IpmRepository was already selected, you do not need to restart the server.

6.1.1.2 Installing and Configuring Oracle UCM 10gR3 to Work with Imaging

For an Oracle UCM 10gR3 repository, Imaging requires Oracle Universal Content Management 10gR3 (10.1.3.3.3), also referred to as Oracle Content Server 10gR3. After installing and configuring Oracle Content Server 10gR3, you need to update the system with the Content Server 10g Update Bundle. Both are required for Oracle UCM 10gR3 to work with Imaging 11g.

You can download both Oracle Content Server 10gR3 and the Content Server 10g Update Bundle from the Oracle Software Delivery Cloud or Oracle Technology Network (OTN). For more information about the software locations, see Section 1.2.2, "Software Downloads for Oracle WebCenter Content Installation and Configuration."

For information about installing and configuring Oracle UCM 10gR3, see the Oracle Content Server page on Oracle Technology Network at

http://www.oracle.com/technetwork/middleware/content-management/cs-088869.html

If you are using Imaging 11g with Oracle UCM 10gR3, make sure to update Oracle Content Server 10gR3 with the latest update patch.

6.1.1.2.1 Upgrading the JDK Version of Oracle UCM 10gR3

After you deploy Imaging to an Oracle WebLogic Server Managed Server, by creating or extending a domain, you need to upgrade the JDK version of your Oracle Content Server 10gR3 installation to the same JDK 1.6 version that Imaging uses. This is the JDK version that you specified for the Imaging Managed Server on the Configure Server Start Mode and JDK screen of the Fusion Middleware Configuration Wizard. For information about the JDK version that Imaging supports, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network at

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Refer to the Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Product Area, System Requirements and Supported Platforms for Imaging and WebCenter Content (xls).

For information about changing the JDK version that Oracle Content Server 10gR3 uses, see Oracle Universal Content Management Content Server Installation Guide, version 10gR3, for your operating system.

6.1.1.2.2 Configuring Oracle Content Server 10gR3 to Work with Imaging

You need to configure Oracle Content Server 10gR3 before it can work with Imaging. During the configuration, restart Oracle Content Server 10gR3 whenever prompted to do so.

To configure Oracle Content Server 10gR3 to work with Imaging:

  1. Update the IP address filter:

    1. On the system where Oracle UCM 10gR3 is installed, run the following command:

      • UNIX command: UCM_ORACLE_HOME/bin/SystemProperties

      • Windows command: UCM_ORACLE_HOME\bin\SystemProperties

    2. With your system's DISPLAY environment variable set to a valid X Server, click the Server tab in the display.

    3. In the IP Address Filter field, add a vertical bar (|) followed by the IP address of the system where Imaging is installed.

      For example: 192.0.2.1|192.0.2.130

      The IP address is required for the Imaging system to have access to the Oracle UCM 10gR3 system without authentication.

    4. Click OK.

      This change will require a restart of Oracle Content Server 10gR3, which you can do at the end of this procedure, after installing the Oracle UCM 10gR3 components.

  2. Open the Oracle UCM 10gR3 web client in a web browser (http://managedServerHost:managedServerPort/location, such as http://myhost.example.com:8000/idc), and log in.

  3. Open the Administration tray.

  4. Upgrade the default file store:

    1. Under Administration, select Providers.

    2. Select Info in the Action column of the DefaultFileStore row.

    3. When asked if you want to upgrade the file store, click Upgrade, and then click Update in the Edit File Store Provider dialog box.

      Oracle UCM 10gR3 does the upgrade automatically.

    Imaging content is not accessible in a web store. Oracle Content Server 10gR3 traditionally uses a weblayout directory on a file system to store content in a format for viewing in a web browser, but this feature does not have much use in an Imaging solution and uses extra disk space. After the file store upgrade, you should disable the weblayout functionality in Oracle Content Server 10gR3 for any file store provider configured for use as an Imaging volume.

  5. Configure system properties:

    1. Confirm that the SearchIndexerEngineName variable matches the type of Oracle UCM 10gR3 system to use (DATABASE.METADATA, DATABASE.FULLTEXT, or OracleTextSearch).

    2. Under Administration tray, select Admin Server.

    3. Click idc.

    4. Select General Configuration, on the left.

    5. Select Automatically assign a content ID on check in.

    6. Specify an Auto Number Prefix value, such as ucm1.

    7. Set the EnableIdcProfileField variable to 1 by adding the following line to the Additional Configuration Variables box:

      EnableIdcProfileField=1
      
    8. Click Save.

  6. Install Oracle UCM 10gR3 components:

    1. Select Component Manager, on the left.

    2. In the Install New Component section, click Browse, browse to the /extras directory, and select any components you want to install.

    3. Click Open.

    4. Click Install.

      If the Component Manager redirects your request to port 80, you can reconfigure your web server to use port 80.

      Restart Oracle Content Server 10gR3 when prompted.

    5. Fill in any necessary details for each component you selected, and then click Continue.

      The menu displays several selections, some of which are checked. You can accept the default selections.

    6. Click here to return to the Component Manager.

    7. In the Install New Component section, click Browse.

    8. Browse to the WC_CONTENT_ORACLE_HOME/ipm/lib directory, and select IpmRepository.zip.

    9. Click Open.

    10. Click Install.

      Restart Oracle Content Server 10gR3 when prompted.

    11. Click Continue.

    12. Click here to return to the Component Manager.

    13. In the Install New Component section, click Browse and browse to the /extras directory.

    14. Select any components in the /extras directory and IpmRepository.

    15. Click Enable.

    16. Fill in any necessary details for each component you selected, and then click Continue.

      Restart Oracle Content Server 10gR3 when prompted.

    17. Click here to return to the Component Manager.

    18. From the Options list on the left, select Start/Stop Content Server.

    19. Select Restart.

    20. Ensure that Oracle Content Server 10gR3 is running after you restart it.

6.1.1.2.3 Adding the Administrator User and Administrators Group to Oracle UCM 10gR3

You need to add the administrator user to Oracle UCM 10gR3 and assign it to the Administrators group before this user can perform administration tasks on Oracle UCM.

To add the administrator user and Administrators group to Oracle UCM 10gR3:

  1. In the Oracle UCM 10gR3 web client, select Admin Applets under Administration.

  2. Click User Admin.

  3. On the Security tab, select Permissions By Role.

  4. Select Add New Role.

  5. In the Role Name field, enter Administrators.

  6. Click OK.

  7. Click Close.

  8. Click Add.

  9. For Authorization Type: Local, click OK.

  10. Create the administrator user, and enter the password.

  11. Click the Roles tab.

  12. Click Add Role.

  13. Select Administrators, and then click OK.

  14. Click OK.

  15. Close the User Admin applet.

6.1.1.3 Configuring a File Store Provider for Content Storage

An administrator can configure a file store provider in Content Server 11g to control how and where files are stored and managed within Content Server. Instead of storing all content on a single file system, you can use a file store provider to store content across multiple file systems as well as within a database. The File Store Provider component is installed and enabled by default with WebCenter Content installation and configuration.

For Imaging, you should add a file store provider to use instead of the default file store provider. Also, you should disable the traditional web layout functionality for the file store.

The default storage provider configuration that is created during the installation of WebCenter Content is not intended for production document volumes. This default configuration is adequate for proof-of-concept or demonstration systems of fewer than 10,000 documents. Production system configurations require more advanced options to be chosen.

You can configure a file store provider for Oracle Database.

If your WebCenter Content installation uses a Microsoft SQL Server or IBM DB2 database, do not configure a file store provider. If you are configuring a WebCenter Content Managed Server with one of these databases, you need to disable the file store provider that is enabled by default for Content Server.

For more information, see "Configuring a File Store System" in the Oracle WebCenter Content System Administrator's Guide for Content Server.

6.1.1.3.1 Configuring a File Store Provider

A file store provider can be a combination of any media supported by Content Server. Because the document storage location is not defined by the media being used for storage, the term volume is used to represent a storage location when an application is defined in the Imaging user interface. Imaging connects to a volume defined and configured in Content Server by an administrator. You cannot use Imaging to create or define a volume.

A Content Server administrator can configure a file store provider. For more information, see "File Store Administration Interface" in the Oracle WebCenter Content System Administrator's Guide for Content Server.

6.1.1.3.2 Disabling Web Layout Functionality for Imaging

Content Server traditionally uses a /weblayout directory on a file system to store content in a format for viewing in a web browser, even if the main storage volume is set up in a database. This file system store is useful for making content retrieval faster for a web site or for storing a secondary file that describes the primary content item, but it does not have much use in an Imaging solution. Files copied to a /weblayout directory in an exclusively Imaging solution would never get used, taking up unnecessary storage space. Oracle recommends disabling the web layout functionality for any file store provider that is configured for use as an Imaging volume.

An administrator can disable the web layout functionality by selecting the Is Webless File Store option on the Add/Edit Storage Rule page for a file store provider in Content Server. For more information, see "Add/Edit Storage Rule Page" in the Oracle WebCenter Content System Administrator's Guide for Content Server.

6.1.2 Starting the Imaging Managed Server and Accessing the Web Client

After you start the Administration server and the Imaging and WebCenter Content Managed Servers, you can access the Imaging web client.

To access the Imaging web client:

  1. Start the Imaging Managed Server, as described in Section 9.2, "Starting Managed Servers."

  2. Access the web client at this URL: http://managedServerHost:16000/imaging

    Log in with the administrator user name and password.

    Note:

    This first user to connect to the Imaging system is registered as the Imaging administrator.

6.1.3 Connecting to a WebCenter Content Repository

Before Imaging can use the WebCenter Content repository, you need to configure a connection to Content Server. You can create a connection to it from Imaging.

To connect to a WebCenter Content repository:

  1. Open a web browser, and navigate to this web site:

    http://managedServerHost:16000/imaging

  2. Log in with the administrator user name and password.

  3. Navigate to the Manage Connections tray, and choose Create Content Server Connection from the list.

  4. Enter a name for the connection on the Basic Information page and, optionally, a description, and then click Next.

  5. You can change the selections and on the Connection Settings page:

    • SSL: Selected for secure SSL communications

    • Server Port: The IDC port of the WebCenter Content instance, 4444 for Imaging by default

    • Use Local Content Server: Selected by default if Content Server is on the same machine as the Imaging server.

      If the servers are not installed on the same machine, you will need to configure the Content Server machine name as part of the Content Server Pool.

  6. Click Next.

  7. Enter a Connection Security value for the connection.

    Select which users and groups should have permission to access, modify, delete, or grant others access to this connection definition. At least one user or group must have the grant access permission.

  8. Click Next.

  9. At the Summary screen, click Submit.

6.1.4 Configuring the GDFontPath MBean for a UNIX System

For conversions to work correctly on a UNIX operating system, it needs to have TrueType fonts available. If these fonts are not available on your system, you need to install them. To set the font path on a UNIX operating system, you need to configure the GDFontpath MBean. You can configure it through the System MBean Browser in Oracle Enterprise Manager Fusion Middleware Control.

To configure the GDFontPath MBean for a UNIX system:

  1. Access the Imaging domain in Fusion Middleware Control at the following URL:

    http://adminServerHost:adminServerPort/em
    

    For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:

    http://myHost.example.com:7001/em
    

    To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.

  2. In the navigation tree on the left, expand Application Deployments, and then click imaging (IPM_server1).

  3. On the Application Deployment menu, select System MBean Browser.

  4. In the navigation tree on the System MBean Browser page, under Configuration MBeans, close the com.bea folder.

  5. Expand the oracle.imaging folder, under Application Defined MBeans.

  6. Expand the Server: IPM_server1 and config folders.

  7. Click config.

  8. Set the value of the GDFontPath attribute to the location of your True Type Fonts (TTF) files; for example:

    /usr/share/X11/fonts/TTF
    

    For systems on which Oracle WebLogic Server includes a JDK, you can find some TTF files in the JDK/jre/lib/fonts directory.

    Some standard font locations on different UNIX platforms follow:

    • Solaris SPARC: /usr/openwin/lib/X11/fonts/TrueType

      Note:

      For document conversions on a Solaris SPARC platform, Imaging requires the GNU Compiler Collection (GCC) package 3.4.2 or later in the /usr/local/packages directory.

      Install this package on the Solaris operating system that will run Imaging. You can download GCC from the Sunfreeware web site at

      http://www.sunfreeware.com
      

      You also need to set the LD_LIBRARY_PATH environment variable to /usr/local/packages/gcc-3.4.2/lib before starting the Imaging Managed Server. If you are using a later version of GCC, set that version instead of 3.4.2.

    • AIX: /usr/lpp/X11/lib/X11/fonts/TrueType

    • HP-UX Itanium: /usr/lib/X11/fonts/TrueType

    • Linux: /usr/lib/X11/fonts/TrueType

  9. Click Apply.

  10. Restart Imaging, as described in Section 9.3, "Restarting a Managed Server."

6.1.5 Setting DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 11g

In an Exalogic environment with Solaris 11g, you need to set the DISPLAY environment variable for the Imaging Viewer to work correctly in basic mode.

To set DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 11g:

  1. Open a new terminal window and run this command:

    xhost +
    
  2. In the Imaging terminal, set the DISPLAY environment variable to the server where Imaging is running and the port, in this format:

    servername:port
    
  3. Restart Imaging, as described in Section 9.3, "Restarting a Managed Server."

6.1.6 Importing Definitions

At this point in the installation process, you can use the Import tool to import previously exported Imaging definitions (applications, searches, and inputs).

6.2 Configuring the Full-Text Features in the WebCenter Content Repository

Imaging supports two types of full-text searching under WebCenter Content: DATABASE.FULLTEXT and OracleTextSearch. Imaging can use the full-text features if you configure full-text searching in the WebCenter Content repository first. For DATABASE.FULLTEXT systems, after the indexes are rebuilt, nothing needs to be done on the Imaging side. OracleTextSearch, however, requires that the index be rebuilt any time an application with FullText enabled is created, deleted, or has modifications that involve field definitions.

For more information on configuring full-text searching, see Section 4.4, "Configuring OracleTextSearch for Content Server."

For additional full-text configuration options, see "Configuring the Search Index" in the Oracle WebCenter Content System Administrator's Guide for Content Server.

After full-text is enabled in WebCenter Content, you will need to create an application and check the FullText option on the application. For more information, see "Specifying General Properties" in Oracle WebCenter Content Administrator's Guide for Imaging.

6.3 Connecting to a Workflow Server

A connection to a workflow server will be necessary for your solution to retrieve your task list. Imaging connects to a workflow server when application fields are mapped to workflow payload elements. To connect, the provider, port, and credential information is passed using Web Services Inspection Language (WSIL). WSIL uses the HTTP protocol and a specific XML format to allow for the discovery of the web service end points on a server. Imaging follows links in the WSIL that meet certain criteria to discover deployed composites.

The connection can be to an Oracle Business Process Management (Oracle BPM) or Business Process Execution Language (BPEL) server. For Imaging to take advantage of BPM and Oracle BPEL Process Manager within an existing domain, the domain must be extended with Oracle BPM Suite - 11.1.1.0. When Oracle BPM Suite was installed, it automatically selected Oracle SOA Suite - 11.1.1.0 as its dependency. If you want to use Oracle BPEL Process Manager and not Oracle BPM, you can extend the domain with an Oracle SOA Suite installation and configuration. For more information about the installation and configuration steps for Oracle SOA Suite and Oracle BPM, see Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

For more information about connecting to a workflow server, see "Creating a Workflow Connection" in Oracle WebCenter Content Administrator's Guide for Imaging.

After you have created a workflow connection, enter the name of that connection in the AXF_SOLUTION_ATTRIBUTES table for your solution. For example, the parameter key for a Business Process Execution Language (BPEL) server is named BPEL_CONNECTION, and the HelloBPEL sample script uses the connection name test.

6.4 Setting Imaging System Security

On a new Imaging system, the first user to log in is automatically granted full permissions. Typically, this initial user associates other users or groups, after which his or her permissions are changed or revoked as needed.

Note:

If you configure Imaging for use with Oracle Access Manager, you must protect the imaging/faces/ directory. Failure to do so would prevent access to the Imaging Viewer.

If security provider changes are made after this initial user login to Imaging, take the following steps to reset Imaging system security. For example, if you later change the security configuration to point to an Oracle Internet Directory provider or a Microsoft Active Directory provider, you must reset Imaging system security.

  1. Manually create or migrate users and groups to the new external security provider, using utilities as needed.

    For more information, see Section 3.9, "Reassociating the Identity Store with an External LDAP Authentication Provider."

  2. Run the refreshIPMSecurity() WLST MBean command.

    For more information, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

    Note:

    During the refresh, users or groups for whom matching identifying information is not found are ignored. As security changes are made, invalid users or groups are removed from the Imaging database.

6.5 Installing and Configuring Oracle Application Extension Framework

Oracle Application Extension Framework (AXF) is automatically installed with Imaging. For information about configuring and using AXF and the AXF database tables, see Oracle WebCenter Administrator's Guide for Application Adapters.

For Oracle Application Extension Framework (AXF) to work with Imaging Managed Servers that run in a cluster or other distributed configuration, you need to configure the Java Object Cache (JOC) to be distributed to all of the Managed Servers.

To verify that the AXF infrastructure is properly installed, two simple solutions, HelloWorld and HelloBpel, are included with AXF. HelloWorld is a basic solution that returns a Hello string. The HelloBpel solution includes a BPEL process to verify the BPEL integration.

6.5.1 Configuring the Java Object Cache for AXF in Distributed Imaging Managed Servers

For Oracle Application Extension Framework (AXF) in Imaging Managed Servers that run in a cluster, you need to configure a Java Object Cache (JOC) to be distributed to all of the Managed Servers. You can use HA Power Tools from the Oracle WebLogic Server Administration Console to configure the JOC for all of the Imaging Managed Servers that run in distributed mode.

Note:

After configuring the Java Object Cache, restart all affected Managed Servers for the configurations to take effect. For more information, see Section 9.3, "Restarting a Managed Server."

In the following instructions, MW_HOME represents the path to a Middleware home, where Oracle Fusion Middleware is installed, and DomainHome represents the path to the Oracle home for an Oracle WebLogic Server domain.

To configure the Java Object Cache for a cluster of distributed Managed Servers:

  1. Enable HA Power Tools in the Oracle WebLogic Server Administration Console:

    1. Copy the following two WAR files from the MW_HOME/oracle_common/hapowertools directory to the DomainHome/console-ext directory:

      • powertools-core.war

      • powertools-configurejoc.war

      For example:

      cd middlewarehome
      cp oracle_common/hapowertools/powertools-co* user_projects/domains/base_domain/console-ext/
      
    2. Restart the Oracle WebLogic Server Administration Server.

      For more information, see Section 9.1, "Starting the Administration Server," and Section 9.3, "Restarting a Managed Server."

    3. Access the Oracle WebLogic Server Administration Console (at http://adminServerHost:adminServerPort/console), and click the name of your domain in the left navigation tree.

      The HA Power Tools tab appears on the Settings page for the domain.

  2. Configure the distributed cache:

    1. On the Settings page for your domain in the Administration Console, click the HA Power Tools tab.

    2. On the Configure JOC tab, select Configure JOC for Clusters.

    3. In the Cluster Name field, choose a cluster name from the list.

    4. In the Discover Port field, enter the listener port number for the cluster.

    5. In the Hosts field, enter the names of all the Managed Server hosts, separated by commas.

    6. Click the Configure JOC button.

  3. Restart the cluster of Managed Servers.

  4. Verify the JOC distributed cache mode:

    1. From the Middleware home on the host for one of the Managed Servers, run the CacheWatcher utility, as in the following example:

      java -classpath oracle_common/modules/oracle.javacache_11.1.1/cache.jar:oracle_common/modules/oracle.odl_11.1.1/ojdl.jar
      oracle.ias.cache.CacheUtil watch -config=user_projects/domains/base_domain/config/fmwconfig/servers/IPM_server2/javacache.xml
      

      In this example, the class paths for the two JAR files are relative to the current directory (MW_HOME).

      The javacache.xml file is the file used by one of the Imaging servers that is participating in the JOC distributed cache. For a distributed Java cache with either virtual or physical IP addresses, the listener address needs to be set in javacache.xml. Each of the files should contain all the distributor location entries but only one <listener-address> entry, set to the same port number for every cache member, as follows:

      <listener-address port="portNumber1" host="hostName1"/> 
       <distributor-location ssl="true" port="portNumber1" host="hostName1"/> 
       <distributor-location ssl="true" port="portNumber1" host="hostName2"/> 
       <distributor-location ssl="true" port="portNumber1" host="hostName3"/> 
       <distributor-location ssl="true" port="portNumber1" host="hostName4"/> 
      
    2. Enter the lc command to list the cache information:

      INFO: JOC is initialized from oracle.ias.cache.CacheUtil.main, . . .
      cache> lc
      
    3. In the output from the lc command, check that the Distributor Table shows an entry for each member of the distributed cache.

    4. Enter the exit command to stop the CacheWatcher utility.

For more information, see "Using HA Power Tools" and "Running CacheWatcher" in Oracle Fusion Middleware High Availability Guide.

6.5.2 Verifying the AXF Installation with HelloWorld

Follow these steps to enable the HelloWorld solution:

  1. As user who owns the Imaging schema, run the insertHelloCommand.sql script from the following directory:

    • UNIX path:
      MW_HOME
      /WC_CONTENT_ORACLE_HOME/axf/drivers/HelloWorld/dbscripts

    • Windows path:
      MW_HOME
      \WC_CONTENT_ORACLE_HOME\axf\drivers\HelloWorld\dbscripts

    Note:

    For IBM DB2 only, add the following line to beginning of the insertHelloCommand.sql script before you run it:
    CONNECT TO soadb USER am3_ipm USING oracle;
    
  2. Access the driver page of the AXF web application using the following URL:

    http://host:port/imaging/faces/Driver.jspx
    
  3. Enter the following values:

    • Solution Namespace: HelloWorld

    • Command Namespace: Hi

    • User Name: jcooper

      Note:

      This user name is valid only if you are using the application server's built-in jazn.xml security
  4. Click Execute Command.

    An AXF response should display with a populated Conversation ID. If the response is returned, the AXF infrastructure is functioning correctly, and commands can be added and executed.

6.5.3 Verifying the AXF Installation with HelloBpel

The HelloBpel solution includes a BPEL Process and a SQL script to set up the HelloBpel SolutionNamespace for use by that process. The BPEL Process and database script can be found in the installation package under the following directory:

  • UNIX path:
    MW_HOME
    /WC_CONTENT_ORACLE_HOME/axf/drivers/HelloBpel

  • Windows path:
    MW_HOME
    \WC_CONTENT_ORACLE_HOME\axf\drivers\HelloBpel

To enable the HelloBpel solution:

  1. Run one of the following HelloBPEL SQL scripts:

    • UNIX scripts:

      MW_HOME/WC_CONTENT_ORACLE_HOME/axf/drivers/HelloBpel/dbscripts
      
      /oracle/insertHelloBPELData.sql
      
      MW_HOME/WC_CONTENT_ORACLE_HOME/axf/drivers/HelloBpel/dbscripts
      
      /sqlserver-db2/insertHelloBPELData.sql
      
    • Windows scripts:

      MW_HOME\WC_CONTENT_ORACLE_HOME\axf\drivers\HelloBpel\dbscripts
      
      \oracle\insertHelloBPELData.sql
      
      MW_HOME\WC_CONTENT_ORACLE_HOME\axf\drivers\HelloBpel\dbscripts
      
      \sqlserver-db2\insertHelloBPELData.sql
      

    If your database is Oracle, then run the script from the oracle directory.

    If your database is IBM DB2 or Microsoft SQL Server, then run the script from the sqlserver-db2 directory.

    For IBM DB2 only, before you run the HelloBPEL SQL script, make the following changes to it:

    • Add this line to beginning of the script:

      CONNECT TO soadb USER am3_ipm USING oracle;
      
    • Change the following line to specify whatever the actual BPEL Connection is in the Oracle IPM Manage Connections section:

      Insert into AXF_SOLUTION_ATTRIBUTES (SOLUTION_NAMESPACE,PARAMETER_KEY,PARAMETER_VALUE) values ('HelloBPEL','BPEL_CONNECTION','test');
      
  2. Run the insertHelloBPELData.sql script.

  3. With Oracle JDeveloper 11g, open HelloBPEL.jws from following directory:

    • UNIX path:
      MW_HOME
      /WC_CONTENT_ORACLE_HOME/axf/drivers/HelloBpel/bpel

    • Windows path:
      MW_HOME
      \WC_CONTENT_ORACLE_HOME\axf\drivers\HelloBpel\bpel

    Deploy the process to your BPEL server. For assistance with this task, consult the Oracle JDeveloper documentation.

    Note:

    The HelloBPEL sample solution assigns instances to a group named California by default. You need to add the California group to the myrealm security realm through the Oracle WebLogic Server Administration Console.

    If you are using an alternate identity store, such as Oracle Internet Directory, you can change the group assignment by modifying the HelloBpelHumanTask.task file within Oracle JDeveloper before deployment.

  4. Access the driver page of the AXF web application using the following URL:

    http://host:port/imaging/faces/Driver.jspx
    
  5. In the AXF Command Driver screen, enter the following values:

    • Solution Namespace: HelloBPEL

    • Command Namespace: StartHelloBPEL

    • User Name: A valid Imaging user; for example, weblogic

    The preceding Imaging user needs to be part of a group named California. If this group does not exist, then create it, and add the user to the group.

  6. Click Execute Command.

    A response should be displayed in the response screen.

  7. Click Execute Response, and log in when prompted.

    The AXF Task List screen should be displayed. If there are no tasks in the TaskList, open the BPEL Console, create a new instance of HelloBPELProcess, and refresh the Task List.

6.6 Installing and Configuring Oracle Document Capture and Oracle Distributed Document Capture

Oracle Document Capture provides high-volume production scanning from a central location, while Oracle Distributed Document Capture provides a user-friendly web interface that enables distributed enterprises to capture images easily from remote locations.

For information about installing and configuring Oracle Document Capture, see the Oracle Document Capture Installation Guide and Oracle Document Capture Administrator's Guide.

For information about installing and configuring Oracle Distributed Document Capture, see the Oracle Distributed Document Capture Installation Guide and Oracle Distributed Document Capture Administrator's Guide.

The Imaging 11g Commit Driver is required to commit documents from either capture application to WebCenter Content. For information about using the Imaging 11g Commit Driver, see the Oracle Distributed Document Capture Installation Guide or Oracle Distributed Document Capture Administrator's Guide.