5 Steps to Creating an Audit and Reporting Quick Trace


5 Steps to Creating an Audit and Reporting
Quick Trace

by: John Schleicher | Sr. Technical Architect

Maintenance of a production imaging environment (like many others) can be a significant issue due to high cardinality of affected instances when the inevitable failure occurs in the system.  Trying to isolate those non-recoverable instances to initiate external recovery techniques (such as resubmission) can be a time consuming task that can lead to excessive hours of research and potential loss of those items.  TekStream recognizes this issue and its impact to IT departments and their business counterparts in AP and has included the Quick Trace capability within its Audit and Reporting package.  This article describes its usage by IT to facilitate their maintenance activities.

The Oracle Imaging Solution is based upon the WebLogic server and its workflow engine is based on BPEL components running on the SOA server.  Quick Trace captures key data points into the composite instance title for easy retrieval using the WebLogic server’s Enterprise Manager or via SQL query of the SOAINFRA data model.   These data points include items of interest such as:

  • Imaging Document ID
  • Invoice Number
  • Supplier Name
  • Expense Number

The data points also offer retrieval access from these perspectives:

  • Where is/what happened to a specific invoice instance
  • What instances have been impacted by a system event

In order to identify the location for a specific workflow instance, you will need to go through the enterprise manager.

*Note: The Enterprise Manager search does not accommodate wild cards and the complete string of the targeted search element/data point must be specified.  Quick Trace will store the data points independently to best expose them for the target search.

Quick Trace users can perform the following traversal and actions to engage traces:

Step 1: Login to Enterprise Manager:

Audit Photo 1

Step 2: Select soa-infra:

Audit Photo 2

Step 3: Go to instances:

Audit Photo 3

Step 4: Enter the invoice ID (or other desired identified search key) and hit search.  The associated instance IDs are then exposed:

Audit Photo 4

Step 5: Select that Instance ID to get the complete workflow trace:

Audit Photo 5

To locate workflow instances affected by an event the SOAINFRA.composite_instance.title field can be retrieved via sql query.  The following query identifies the imaging document IDs that were submitted today for potential resubmission:


SQL> select title from composite_instance where created_time > sysdate -1 and title is not null and title like ‘3.IPM%’;






This query represents the most simplistic example, but the availability of the key imaging fields populated by the audit and reporting package opens up recovery mechanisms not otherwise available.

Learn More about Creating an Audit and Reporting Quick Trace

Speak with a TekStream expert today!

Configuration Migration Utility Limitations – How to Migrate Oracle WebCenter Content Categorizer Rules

Configuration Migration Utility Limitations
How to Migrate Oracle WebCenter Content
Categorizer Rules


Oracle’s WebCenter Content Configuration Migration Utility (CMU) is a powerful tool for application administrators to migrate the majority of the Content Server configurations from one instance to another.  I believe Stellent developed CMU primarily to migrate the core configurations that are a part of the base Content Server, and since then the WebCenter Content product has evolved and matured.

Configuration Migration Utility Limitations:
After all the Oracle acquisitions, product restructuring, architecting, rebranding, patches and releases; it is unfortunate that more focus hasn’t been made on providing administrators and developers a cohesive tool that can be used to migrate all the configurations easily.  After some hands-on administration experience you will find there isn’t a master tool to migrate all the WebCenter Content configurations within the whole product offering.  So until then, we need to follow other migration tasks to migrate configurations not included within CMU.  Migrating custom table data such as option list values is performed using the Archiver tool.  Other WCC components can be enabled such as Content Categorizer, Framework Folders, FileStore Provider and Site Studio. Migrating the customizations associated with these components isn’t integrated with CMU and you will need to use other techniques to migrate them.  We use Archiver to migrate Framework Folders, and you use the Manage Site Replication or Backup and Restore tools (backend Archiver) to migrate Site Studio configurations.  Inbound Refinery doesn’t integrate with CMU and you will have to manually migrate the file formats and conversion options settings. But other components such as Records Management do integrate with CMU.

Migrating Content Categorizer Rules:
For a recent project I spent a couple workdays adding over 100 custom Content Categorizer rules which were tied to custom meta data fields.  After a successful QA it came time to migrate these configurations to another instance for additional QA.  The custom meta data fields migrated as expected using Content Server’s CMU.  However, I quickly discovered I could not use the CMU to migrate the Content Categorizer Rules.

The solution is to migrate an hda file that contains Content Categorizer rule field name, order, key, count and additional flags.
For WCC 11g the file is called ContentCategorizerBinder.hda and for local installs it can be found at

Or this location if using a fileshare in a cluster configuration

After migrating this file over to the destination instance you will need to restart the managed server and verify the rules are listed in the Content Categorizer applet.

Hopefully in a future release of the Oracle WebCenter product we can migrate all configurations needed using the same tool and process.

Speak to Angela About Configuration Migration Utility

Fill out the short form below, and we will have a representative contact you as soon as possible!