|Oracle® Fusion Middleware Managing Oracle WebCenter Capture
11g Release 1 (11.1.1)
Part Number E37898-02
|PDF · Mobi · ePub|
Getting started involves accessing the Capture Workspace Console and creating a workspace, then adding several metadata fields, a client profile, and a basic commit profile. After that, you use the Capture client and test your workspace settings. Beyond these steps, you can expand into managing workspace elements, including choice lists, database lookups, and batch processor jobs.
This chapter includes the following sections:
As described in Section 1.6, the Capture system administrator installs Oracle WebCenter Capture, starts the server, performs its initial configuration, and monitors its overall performance, including batch processor logging. This section assumes these steps are complete.
Items You Need
To get started managing a Capture workspace, you need the following from the Capture system administrator:
A user ID and password to access the Capture Workspace Console.
A user ID and password to use the Capture client.
To manage workspaces, you may also need the following from the Capture system administrator:
Data sources for connecting to an external database, needed for creating database lookups and database choice lists.
For scanning, you need access to a TWAIN-compliant scanner or multi-function device. Note that instead of scanning documents, you can import them from your file system, as described in this chapter.
For importing, you may want to have TIFF image files, PDF documents, and Microsoft Word or Excel documents available.
For scanning and recognition, you may want to have pages with bar codes and patch codes available.
Follow these steps to access the workspace console, where you create and manage workspaces. If needed, ask the Capture system administrator for sign-in information.
Open the Oracle WebCenter Console in your browser. The exact URL is determined at installation. The address uses the following format:
16400 is the default port.
At the Sign In window, enter your User ID and Password, and click Sign In.
The workspace console window displays, as shown in Figure 2-1.
Figure 2-1 Workspace Console
Follow the steps in these sections to create a workspace and add metadata fields and profiles.
If you are the first workspace manager to use the workspace console, no workspaces are present. To add a workspace:
In the Capture Workspaces pane at left, click the Add button (plus sign).
In the Create New Workspace window, enter a name for the workspace and click OK. For example, enter
The new workspace is added to the workspaces pane. For more information about adding, copying, and editing workspaces, see Section 3.2.1.
Select the new workspace, and its settings display in the right pane.
Notice that the Security tab displays your user name in the Workspace Users table, configured by the Capture system administrator during installation and initial configuration. You have workspace manager access to the workspace and can grant other managers or workspace viewers access to it.
Figure 2-2 New Workspace With Security Tab Displaying Workspace Users
Now create several metadata fields to hold metadata values for captured documents.
On the Metadata tab, click the Add button in the Metadata Fields table.
Create several metadata fields.
In the Field Name field, enter
Customer ID and select the Required field. Click Submit. The new field displays in the Metadata Fields table.
For more information about creating metadata fields, see Section 3.4.
Add another field called
Customer Name, make it required, and click Submit.
Add another field called
Correspondence Type, and click Submit.
Add another field called
Purchase Order Number, and click Submit.
Figure 2-3 Metadata Tab With New Metadata Fields Added
In this section, you create a document profile, which defines the set of metadata fields that apply to a specific type of document.
On the Classification tab, click the Add button in the Document Profiles table.
In the Name field, enter the type of document (for example,
Move all of the fields except Purchase Order Number to the Selected Metadata Fields list, and click Submit.
For more information about creating document profiles, see Section 3.10.
Figure 2-4 New Document Profile With Its Set of Metadata Fields Selected
Create another document profile called
Purchase Orders, select the following metadata fields for it, and order them as follows. Click Submit.
Purchase Order Number
In this section, you create a client profile, which defines the settings used when users select it to scan, import, and index documents in the client.
On the Capture tab, click the Add button in the Client Profiles table. Screens for selecting settings (known as train stops) display in the right pane.
Complete settings on the General Settings train stop.
In the Profile Type field, select 2 - Capture and Index. Users will use this profile to capture (scan or import) documents and then index (complete metadata values) for them.
In the Profile Name field, enter a name to display to users (example,
Import Customer Documents). For example, you might use the name to indicate how users should use the client profile.
In the Batch Prefix field, enter a naming prefix (for example,
CUST_DOC). Capture names batches as they are created by appending an incremented number to this prefix.
On the Image Settings train stop, select Import in Native Format in the Non-Image File Import Action field.
This action allows users to use this client profile to import non-image files such as PDF files or Microsoft Word documents in addition to image files. It also sets non-image files to be retained in their original format.
In the Document Profiles field on the Document Indexing Settings train stop, select the Correspondence Documents and Purchase Orders document profiles you created.
On the Security train stop, grant a Capture client user security access to the client profile.
This step requires a user or group assigned the Capture User role in the policy store. The Capture system administrator is responsible for assigning Capture User roles to groups or users.
Click the Add button in the Client Profile Users table.
In the Add Security Member window, specify whether to search groups or users assigned the Capture User role, and click Search. From the search results that display in the table, select a security member, and click Add, as shown in Figure 2-5.
Figure 2-5 Granting Client Profile Access to a Capture User
The user or group you added displays in the Client Profile Users table, as shown in Figure 2-6.
Figure 2-6 Capture User Authorized to Use the Client Profile
On the Post-Processing tab, select Commit Processor in the Batch Processor field, as shown in Figure 2-7.
After users release batches created with this client profile, the batch's documents are output by the commit processor.
Figure 2-7 Commit Processing Set as the Client Profile's Next Post Processing Step
Save the client profile by clicking Submit. For more information about client profiles, see Chapter 4.
In this section, you create a commit profile. This commit profile defines how documents are output after client users using this client profile release batches. For this example, you configure output to a local or network folder, using the Text File commit driver.
On the Commit tab, click the Add button in the Commit Profiles table.
Complete settings on the General Settings train stop.
In the Commit Profile Name field, enter a name (
Commit to Text).
In the Commit Driver field, select Text File.
In the Document Output Format field, select PDF Image-Only.
In the Restrict Commit to Document Profiles field, select the Correspondence Documents and Purchase Orders document profiles. This restricts this commit profile's processing to only those documents assigned to the selected document profiles.
Complete settings on the Commit Driver Settings train stop. Note that these settings are specific to the commit text driver you selected in step 2b.
On the Text File Folder tab, enter a location in the Commit Text File Folder field to write commit text files. A commit text file contains delimited metadata values for each document output in the batch. For the commit folder, you must either specify a folder on the Capture server or a network path accessible from the Capture server. For this example, you might specify a shared folder on your system. If the Capture server is running on Windows, you might specify a UNC path to a network share, such as
In the File Prefix field, enter
In the File Extension field, enter
On the Document Folder tab, enter a location in the Document Folder field to write the document files (in this case, PDF files). As with the text file folder, either specify a folder on the Capture server or a network path accessible from the Capture server. For this example, you might specify a shared folder on your system. If the Capture server is running on Windows, you might specify a UNC path to a network share, such as
Select the Create a folder per committed batch field.
On the Formatting tab, move Correspondence Type, Customer ID, Customer Name, and <Batch Name> to the Selected Fields list. This specifies the metadata values to be written to the text file.
On the Document File Naming tab, complete settings.
Select the Name document file based on metadata field values field, then move <Batch Name> and Customer ID to the Selected Fields list.
In the Field Delimiter field, enter an underscore (_).
Click Submit to save the commit profile.
Figure 2-8 New Commit Profile For Committing to Text File
Follow these steps to start up the Capture client application, where you test your client profile as an end user by importing several documents.
Open the Oracle WebCenter Capture client in your browser. The exact URL is determined at installation. The address uses the following format:
16400 is the default port.
If you do not know the client URL, ask your Capture system administrator.
When prompted, sign in as the user to whom you granted security access to the client profile in Section 2.3.4.
Messages display the first time you start the client, indicating that the client is checking for updates and installing client bundles. This takes a few moments the first time only. When the client has completed downloading bundles, the client applet's main user interface displays and toolbar buttons display in the batch pane at left.
Figure 2-9 Capture Client Window Upon Startup
Follow the steps in this section to test your workspace configuration in the client. For more information about using the Capture client, see Oracle Fusion Middleware Using Oracle WebCenter Capture.
The client provides a single window whose upper left pane, the batch pane, is fixed, while its other panes change, depending on the batch pane selection. For more information, see "Scanning and Importing Documents" in Oracle Fusion Middleware Using Oracle WebCenter Capture.
In the batch pane, select your profile, Import Customer Documents, in the Client Profile field.
This top left field displays client profiles available to you as a user, as you configured on the client profile's Security train stop in step 5 of Section 2.3.4. You should see profiles to which a workspace manager has granted you or a group you are a member of permission to.
Select the import source.
Select the right side (containing a triangle) of the Capture Settings/Source button, and verify that a check mark displays next to Import Source. If your system has one or more TWAIN-compliant scanners available, they are also listed here.
Click the Capture button to begin importing.
When prompted in the Import window, select the second import option (Create one document per import file), and click OK.
Select files to import.
In the Select files to import window that displays, hold down the Ctrl key and select multiple files to import. In addition to image files, you can also select non-image files such as Microsoft Word or PDF files.
A batch is created and its batch properties display in the right pane. Notice that the batch was named using the prefix you specified when creating the client profile, plus a number that increments with each new batch (CUST_DOC1). Also notice that the batch's icon indicates that it is locked to you.
In the batch pane, click the triangle to the left of your new batch to expand and view its documents.
Select each document, then review and edit it. Options for editing the selected document display in the document pane at right and are described in Oracle Fusion Middleware Using Oracle WebCenter Capture.
Figure 2-10 Capturing New Batches in the Client Window
After reviewing and editing documents, follow these steps to complete the metadata fields you configured. When a selected client profile is configured for indexing, metadata fields display in the lower left pane when a document is selected in the batch pane. For more information, see "Indexing Documents" in Oracle Fusion Middleware Using Oracle WebCenter Capture.
In the batch pane, select a document.
If needed, adjust the metadata pane by hovering the cursor between the batch and metadata panes until it changes to a two-headed arrow, then dragging to resize the panes.
In the metadata pane's Document Profile field, select a profile for the selected document.
Notice how the set of metadata fields changes when you select the other document profile you configured.
Complete metadata fields for the selected documents.
Notice that an asterisk displays next to the fields you defined as required when creating them in the workspace. A document is fully indexed when all required metadata fields contain a value. You can release a batch even if one or more of its documents is not fully indexed, but an error may occur in later commit processing.
For this example, enter any alphanumeric values you wish into the metadata fields. Using the workspace console, you can configure metadata fields in a variety of ways. For example, you can include input masks in entry fields that control what users can enter, or configure fields to display choice lists or perform a database lookup.
Note that completing metadata values for a selected page completes them for the document. To index the next document, select it in the batch or document pane, change its document profile if needed, and complete the fields.
Figure 2-11 Indexing Documents in the Client's Metadata Pane
When you are done working on a batch's documents, the next step is to release it. What happens when client users release batches depends on the client profile's post-processing setting. When configuring the client profile in Section 2.3.4, you set Commit Processor as the post-processing step, then created a commit profile to output to text file in Section 2.3.5.
In the batch pane, select the batch you created and indexed. (Hold down the Ctrl key to select multiple batches.)
Click the Release button.
A bar over the batch name moves to the right to show release progress, as shown in Figure 2-12. Releasing a batch synchronizes its documents with the Capture server and frees the batch for another user or a processor to work on.
During release, you can select other batches and documents to work on them.
Click the Refresh Batch List button.
The batch's icon may display a processing (gear) icon indicating that it is undergoing batch processing (in this case, by the Commit Processor). The batch may be removed from the batch list.
If an error occurs, the batch remains and one or more of its documents displays an error icon. For more information, see "Handling Batch Errors" in Oracle Fusion Middleware Using Oracle WebCenter Capture.
Figure 2-12 Releasing Batches in the Client's Batch Pane
After commit processing completes and one or more released batches are removed from the batch list, check for the committed batch results (commit text file and documents) in the folder you specified when creating the commit profile in Section 2.3.5.
Open the text file folder you specified in the commit profile.
You should see a text file for each batch committed.
Open the text file and view its contents.
It displays values for the metadata fields you specified (Correspondence Type, Customer ID, Customer Name, and Batch Name).
Open the document folder you specified in the commit profile.
You should see one or more PDF document files for each batch committed. Open a document file and view its contents. Note that any non-image files you imported were committed in their native format.
Figure 2-13 Text Commit Results