7 Configuring Oracle Imaging and Process Management

7.1.1 Configuring an Oracle UCM Repository for Oracle I/PM

You can configure either Oracle Content Server 11g or Oracle Content Server 10g as the Oracle UCM Repository for Oracle I/PM.

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

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

7.1.2 Starting the Oracle I/PM Managed Server and Accessing the Web Client

After you start the Administration server and the Oracle I/PM and Oracle UCM Managed Servers, you can access the Oracle I/PM web client.

To access the Oracle I/PM web client:

1. Start the Oracle I/PM Managed Server, as described in Section 10.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 Oracle I/PM system is registered as the Oracle I/PM administrator.

7.1.3 Connecting to an Oracle UCM Repository

Before Oracle I/PM can use the Oracle UCM repository, you need to configure a connection to Oracle Content Server. You can create a connection to it from Oracle I/PM.

To connect to an Oracle UCM 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 Oracle UCM instance, 4444 for Oracle I/PM by default

   • Use Local Content Server: Selected by default if the Oracle UCM server is on the same machine as the Oracle I/PM server.

     If the servers are not installed on the same machine, you will need to configure the Oracle UCM 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.

7.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 Oracle I/PM 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, Oracle I/PM 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 Oracle I/PM. 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 Oracle I/PM 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

9. Click Apply.

10. Restart Oracle I/PM, as described in Section 10.3, "Restarting a Managed Server."

7.1.5 Allowing IMPORT Definitions

After you install Oracle Enterprise Content Management Suite and configure Oracle UCM and Oracle I/PM on Oracle WebLogic Server, you need to configure Oracle I/PM to allow IMPORT definitions.

To allow IMPORT definitions:

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, such as UM11g, on the Basic Information page, and optionally a description, and then click Next.

5. On the Connection Settings page, enter or change values as necessary, and click Next.

6. On the Review Settings page, if the settings are correct, click Submit.

   After the connection is created, you should be able to use IMPORT definitions for your applications.

7.5.1 Configuring the Java Object Cache for AXF in Distributed Oracle I/PM Managed Servers

You can use the MW_HOME/oracle_common/bin/configure-joc.py Python script, in the Middleware home, to configure the JOC on all of the Managed Servers in distributed mode. The script runs in the Oracle WebLogic Scripting Tool (WLST) online mode and expects the Administration Server to be up and running.

To enable the JOC in distributed mode with the configure-joc.py script:

1. Connect to the Administration Server with a WLST command; for example:

   MW_HOME/oracle_common/common/bin/wlst.sh
   $ connect()
   

   Enter the Oracle WebLogic Server Administration user name and password when prompted.

2. After connecting to the Administration Server with WLST, use the execfile command to start the script; for example:

   wls:/mydomain/serverConfig>execfile('MW_HOME/oracle_common/bin/configure-joc.py')
   

3. Configure JOC for all the managed servers for a given cluster.

   Enter y when the script prompts whether you want to specify a cluster name, and also specify the cluster name and discover port when prompted. This discovers all the Managed Servers for the given cluster and configures the JOC for each Managed Server. The discover port is common for the entire JOC configuration across the cluster. An example follows:

   Do you want to specify a cluster name (y/n) <y> y
   Enter Cluster Name : IPM_Cluster
   Enter Discover Port : 9988
   

   Here is a sample walkthrough for using configure-joc.py for clustered environments:

   execfile('MW_HOME/oracle_common/bin/configure-joc.py')
   .
   Enter Hostnames (eg host1,host2) : IPMHOST1, IPMHOST2
   .
   Do you want to specify a cluster name (y/n) <y> y
   .
   Enter Cluster Name : IPM_Cluster
   .
   Enter Discover Port : 9991
   .
   Enter Distribute Mode (true|false) <true> : true
   .
   Do you want to exclude any server(s) from JOC configuration (y/n) <n> n
   

For more information, see "Configuring the Distributed Java Object Cache" in Oracle Fusion Middleware High Availability Guide.

7.5.2 Verifying the AXF Installation with HelloWorld

Follow these steps to enable the HelloWorld solution:

1. As user who owns the Oracle I/PM schema, run the insertHelloCommand.sql script from the following directory:

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

   • Windows path: MW_HOME\ECM_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.

7.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/ECM_ORACLE_HOME/axf/drivers/HelloBpel

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

To enable the HelloBpel solution:

1. Run one of the following HelloBPEL SQL scripts:

   • UNIX scripts:

     MW_HOME/ECM_ORACLE_HOME/axf/drivers/HelloBpel/dbscripts /oracle/insertHelloBPELData.sql
     
     MW_HOME/ECM_ORACLE_HOME/axf/drivers/HelloBpel/dbscripts /sqlserver-db2/insertHelloBPELData.sql
     

   • Windows scripts:

     MW_HOME\ECM_ORACLE_HOME\axf\drivers\HelloBpel\dbscripts \oracle\insertHelloBPELData.sql
     
     MW_HOME\ECM_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/ECM_ORACLE_HOME/axf/drivers/HelloBpel/bpel

   • Windows path: MW_HOME\ECM_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 Oracle I/PM user; for example, weblogic

   The preceding Oracle I/PM 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.