Oracle WebCenter Content Configuration Migration Utility Limitations – How to migrate PDF Watermark Rules


Oracle WebCenter Content Configuration
Migration Utility Limitations

How to migrate PDF Watermark Rules

By: Angela Lindsey | WebCenter Content Senior Developer

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 PDF Watermark Rules: For a recent project we spent several hours creating the perfect PDF Watermark templates and rules for our client’s confidential documents.  After receiving business approval to push this to production we quickly discovered that Archiver only moved our custom templates as content items but not the rules we created to display them.  Shortly after that we discovered we could not use the CMU to migrate the PDF Watermark Rules either.

The solution is to migrate an hda file that contains PDF Watermark rule name, criteria, and templateID.

For WCC 11g the file is called pdfwTemplateSelectionRules.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 it is suggested to reload and verify the rule(s) are listed in the PDF Watermark Administration applet.

As noted in a previous post hopefully in a future release of the Oracle WebCenter product we can migrate all configurations needed using the same tool and process.

Speak with a TekStream expert about your Oracle WebCenter Content questions today!

Fill out the form below, and we'll contact you as soon as possible.

TekTalk Blog: Understanding the Challenges of Offshore Development


Understanding the Challenges of
Offshore Development

By: Mubeen Bolar | Director, Project Management

Today there are numerous options for US Companies to perform offshore software development known as Offshoring, or Outsourcing. Some of the countries that specialize in offshoring are India, China, Russia, Eastern Europe, Philippines, Costa Rica and Brazil. Cost is the main reason most US Companies consider outsourcing part or most of their software development. However, the lower cost often comes with significant challenges. There are several models of Outsourcing depending on the size of the US Company and their willingness to invest in offshore development.

One of the most popular models of performing offshore software development is through Offshore IT consulting companies who are vendors to US companies. These Offshore IT Companies have branches in the US and can execute projects using highly skilled employees both in the US and abroad. Sometimes the Offshore IT Consulting Company has a long term relationship with the US Company and is more like an offshore partner. Over last decade the offshore model for developing software and providing QA and IT Support Services has matured. Offshoring if done right can result in significant cost saving and increased margins. At the same time when things don’t go well, Offshoring can result in delays, poor quality, frustration and failure.

In order for offshore software development to be a success the US Company must ensure that there is a model for executing the project that encompasses a structured approach. The resources provided by the offshore company must be interviewed before being selected to join the project team. One of the major reasons for failure is having offshore resources that are low cost but do not have the right skill set and experience. It is better to pay a slightly higher offshore rate to get the right skillset and experience. Communication between the offshore team and the US Team is critical and can make or break a project. It is important for the offshore team to have good English communication skills. Misunderstanding the requirements and design of an application can result in costly mistakes and delays. There should be a Project Manager and a Technical Lead/Architect on both the offshore team and the US team. This will avoid delays associated with the offshore developers waiting for guidance from a Project Manager or a Technical Architect located in the US due to the difference in time zone.

The offshore team must have at least a 4 hour overlap with the US team, where they are available to answer questions or get clarifications. Daily team meetings will help to keep the work on track and improve communication. Development work should not be started without proper design documentation and use cases that can be followed by the offshore team. In some models, the Offshore Technical Architect comes to the US during the technical design phase and is also one of the individuals responsible for developing the Technical Design Document. Timely demos of the functionality that has been developed and frequent code reviews should be used to flush out any issues prior to integrate testing. The US Project Manager must update the tasks in the project plan with the actual hours spent on the tasks on a weekly basis. The US Project Manager must check with the offshore team if the remaining hours on the tasks each week are sufficient to complete the tasks. Scope creep can be avoided by monitoring those tasks that are taking longer than the original estimate. This may be a sign the offshore resource lacks the right skill set.

A separate QA team must write the test cases and perform system integration testing prior to User Acceptance Testing. The estimated hours for performing QA should not be lower than 20% of the development hours. The cost of QA is even lower when an Offshore QA team is used. It does not pay to cut corners. Proper testing will help to ensure the User Acceptance Testing goes smoothly. Even when an offshore software development project is a success, Time Zone Stress and the need for additional oversight can result in significant overhead especially for the US team, who has to deliver the project to business users in the US.

Speak with TekStream Solutions about your development needs!

Fill out the form below and our team will be in touch as soon as possible.

Major Automobile Shopping Site Chooses Oracle WebCenter Sites to Drive Customer Portal


Major Automobile Shopping Site
Chooses Oracle WebCenter Sites
to Drive Customer Portal

By: Karl Cepull, Engagement Director

With more than 30 million visits each month, on average, this online car shopping site is the leading destination for online car shoppers, offering credible and easy-to-understand information from consumers and experts to help buyers formulate opinions on what to buy, where to buy and how much to pay for a car.

This industry-leading online car shopping site provides a variety of advertising packages to automobile dealers that let them advertise their dealership and vehicle inventory to potential car buyers. To allow the dealers to enter inventory, respond to customer reviews, and access reports about the services and products they have purchased, the customer had been using a portal running on an outdated version of IBM Websphere. The portal was in need of modernization. A new platform was needed that provided built-in tools and support for managing content, including delivering that content to the right consumer at the right time. After an extensive evaluation, Oracle WebCenter Sites (OWCS) was chosen as the foundation of the new solution, and TekStream Solutions was selected as their implementation partner.

This multi-phase project will eventually include the consolidation of as many as five legacy sites into one comprehensive location for dealers, sales personnel, and internal employees to go to to obtain and manage information about the various products, purchasing options, inventory management, and reporting.

For the first phase of the project, reporting was selected as the main focus. The goal was to provide improved reporting to dealers, with ease-of-use, accuracy of information, and value of the information being the critical success factors. Tableau was selected as the underlying reporting engine, as it has the ability to deliver rich, interactive reports. Some of the updated or new reporting options include:

  • Visits by Zip Code
  • Vehicle Impressions (# of times your vehicles have been viewed)
  • Review Ratings
  • Lead Generation
  • Inventory Completeness (percentage of listings with full information, such as images and pricing)
  • Search statistics

Since only reporting was being replaced with OWCS in the first phase, all other functionality was to remain in the current IBM Websphere-driven site. Users would need to pass seamlessly between existing pages in IBM Websphere, and the new pages in OWCS. This dictated that the user interface of the new site and its pages match the legacy site, and that single sign-on be used to authenticate users between OWCS and IBM Websphere.

Starting in August of 2014, TekStream’s proven QuickStream methodology was executed over a period of 5 weeks to quickly gather detailed requirements, craft a high-level technical design, and develop a detailed project plan and budget for the remainder of the project. As part of the QuickStream, a quick proof of concept was done to test whether CAS (Central Authentication Service) would work as the single sign-on solution. (It was.) The TekStream Sites team then continued to flesh out a detailed design, followed by development and implementation of the chosen solution.

The original launch target was mid-December of 2014. However, during load testing performance bottlenecks in the underlying Tableau reporting engine were identified that would have caused a less-than-ideal user experience. The teams at both companies quickly brainstormed on alternative solutions, and the decision was made to re-architect the entire report navigation approach. This required tight coordination between the TekStream WebCenter Sites team, and the reporting and UI design teams at the client, and was accomplished in only a few short weeks.

After additional testing, the new site was successfully launched on February 24, 2015, and has been well-received. As one dealer stated:

“I am very impressed with the new reporting,  it not only matches my data but is presented in a format that allows us to analyze key areas with ease!  Whoever put this together knows their stuff and how to provide relevant information to your clients. Thanks Again!”

Below are screen shots of the newly-launched site, showing the new home page, and a sample report.






Would you like to learn more about our Oracle WebCenter Sites project?

Fill out the form below, and our team will contact you shortly!


Creating a Java Web Service to Search Oracle WebCenter Imaging


Creating a Java Web Service to Search Oracle WebCenter Imaging

By: Karla Broadrick | Senior Developer

The Oracle WebCenter Imaging APIs allow for remote manipulation of images and execution of searches.  This article details the steps to create a java web service that executes a saved search and displays the results back to the user.

Following is a summary of the high level steps involved in the process:

1)  WCI Saved Search
2)  Project Setup
3)  Basic Script code
4)  Create Web Service
5)  Apply Security Policies
6)  Testing

Step 1: Creating a WCI Saved Search

First a search must be created in WebCenter imaging.  For this example, a search is created that searches the basic fields of the Invoices application.

Creating a WCI Saved Search

Download 6 Steps

Get remaining five steps for free here.

Simply fill out the form below, and you'll be able to download the complete guide.

TekStream and Oracle WebCenter Content Provide Competitive Edge for The Wendy’s Co.


TekStream and Oracle WebCenter Content Provide Competitive Edge for The Wendy’s Co.

 By: Britton Clark | Communications and Marketing Manager

The Problem

Wendy’s wanted to stay ahead of the game with their Digital Menu Board (DMB) by relying on a single source for imaging and metadata, which in turn would expedite the delivery process involving both new and altered DMB content.

The Solution
TekStream addressed the need for an improved, centralized image management strategy by providing an Enterprise Digital Asset Management (eDAM) solution powered by Oracle WebCenter Content.

The Results
The improved Digital Menu Board was integrated at over 700 restaurant locations and allowed Wendy’s to gain a competitive advantage while lowering costs and enhancing the customer experience. WebCenter Content is Wendy’s enterprise level Content Management application that reinforces their status as an industry leader.



Want to know more? Download the datasheet below to hear the complete story!

Simply fill out the form below.