Oracle WebCenter Portal ADF Layouts – 4 Sample Code Snippets


Oracle WebCenter Portal ADF Layouts

By: Sanjay Sen | Developer | TekStream Solutions

When developing using Oracle WebCenter Portal ADF framework, designing the UI pages can get a little tricky and eventually becomes into a cumbersome process, especially if you are not sure what is going to be rendered on the client side – i.e. what is rendered into the HTML. Often times, when developing using ADF, there are several options and components one can choose (depending on what is being developed and displayed). ADF provides different layouts that, if not specified is set to DEFAULT. Different combinations of these layouts may not render into what the user expects on the HTML page, or some CSS styles that may not apply to that component’s HTML tag.

One of the most commonly used ADF component is the <af:panelGroupLayout>. The panelGroupLayout is a layout element that arranges its children in different patterns. We will describe and illustrate the different layouts that can be used to render the expected HTML tag and desired behavior. This will also allow users/developers to know exactly what they will be expecting and the right layout to be set for a specific HTML tag that is to be rendered.

ADF provides 4 layout options:

  1. DEFAULT -> The default layout allows wrapping which allows text to bidirectional layout and may not display consecutively
  2. VERTICAL -> The vertical layout provides content to be vertically stacked
  3. HORIZONTAL -> The horizontal layout provides to be strictly consecutive without wrapping
  4. SCROLL -> The scroll layout provide a vertical view with scrollbars displayed if content overflows (this is used if the panelGroupLayout is being stretched

Download the free PDF below to get sample code snippets for each ADF layout option.

ADF Code Snippets

Get All 4 Sample Code Snippets Here!

Simply fill out the form below.

Configuring Oracle Webcenter For A Cross Platform Installation



Configuring Oracle Webcenter
For A Cross Platform Installation

 By: Kevin Cocilo | IPM Integration Manager


With the introduction of Enterprise Capture (EC) for Webcenter, some customers may face the challenge of a cross platform installation. The use case surfaces when implementing EC for the iExpense solution. The solution uses the barcode recognition functionality, which of course requires that the EC Recognition Server be installed. Currently the Recognition Server is only available to run on a Windows platform. The challenge then becomes how to successfully install and run WebCenter that uses Linux for its primary processing power, while still incorporating the Windows platform for the EC Recognition Server.


As mentioned above, EC is new to Previously, the Oracle offering for Document Capture was ODC\ODDC. And although ODC is a Windows installation, it is a stand-alone client, separate and apart from Webcenter. Typically ODC would simply output .tif files and metadata to a directory location for Imaging (IPM) to ingest. The only thing required was a Samba share to facilitate the data transfer.

With, EC replaces ODC\ODDC, not as a stand-alone Windows client, but as a managed server within a Weblogic domain.  The advantages are clear. It would take advantage of the latest Oracle Fusion Middleware technical stack and leverage the infrastructure of a Weblogic domain. The integration of EC into the WebCenter should have been seamless, and probably could have been were it not for the need to have the Recognition Server on a Windows machine.


The initial architecture assessment was not straight forward simply because EC is new. There simply isn’t a lot of documentation available (either internal to Oracle, or on the normal Oracle blogs/boards).

Initial thoughts were to just extend the Linux domain. This would entail doing the initial Weblogic installation (the jdk, Weblogic, Webcenter SOA, IPM and UCM) on Linux and then simply Extend the Domain to include EC on a Windows server.  The only thing needed, so it was thought, was a Samba Share so that the Linux Domain could be accessed during the Extend process.  The only problem here is that it didn’t work. The process seemed to behave exactly as you would expect, until you reached the point to actually extend. Even though the Linux Domain was visible and seemed to have correct permissions, the command (Button) would produce an error and the domain extension would be unsuccessful. Subsequent retries and attempts produced the same results.

Successful Implementation:

What finally proved to be successful was a method of Packing\Unpacking the domain. The sample installation assumes a simple non-clustered environment.

Since we will be using 2 separate servers for the integration (Linux server for base WebCenter installation, and a Windows server for Enterprise Capture), the WebCenter installation will need to be performed twice. These are the high level steps needed:

Kevin Cocilo Blog - Download steps

Get Complete Steps to Configure Oracle Webcenter For A Cross Platform Installation For Free Today

Fill out the form below, and you will be redirected to the downloadable PDF.

[Replay] Webinar: Oracle Documents Cloud Service Video


[Replay] Webinar: Oracle Documents Cloud Service

Enterprise-Grade File Sync and Share Solution

If you missed last week’s TekTalk webinar on Oracle Documents Cloud Service, it’s now available for replay!

Click here to watch the webinar and get an exciting introduction to Oracle Documents Cloud Service, enterprise file sync and share in the Oracle Cloud. This is a next-gen cloud-based content collaboration solution and built for enterprises with robust security, application integration and mobile enablement. If you’re an Oracle customer that has been forced to use third-party platforms like Box, Dropbox, Google Docs, Microsoft or YouSendIt, you now have a native solution!

“In our first few months of using Oracle Documents Cloud Service, we’ve already cut project admin time by nearly 30%.”

Judd Robins
TekStream Executive Vice President

A Recipe for AP Invoice Automation Success – Walk Before You Run

A Recipe for AP Invoice Automation Success – Walk Before You Run

By: Carl Dion | Senior Solution Architect

Despite the progress that has been made in automating the procurement and payment process, significant human intervention is still required to process Accounts Payable (AP) invoices.  The volume of paper invoices is decreasing, but paper invoices are not being replaced by EDI (Electronic Data Exchange) and Portal mechanisms as much as they are by the submission of invoices as attachments to emails.  In any event, capturing and validating invoice information from paper invoices and invoices attached to emails and entering this information into AP systems remains a tedious, time consuming and costly process.  Invoice processing solutions that automate the extraction and validation of this information, automate the entry of valid invoice information into AP systems and provide efficient mechanisms to resolve exceptions can provide significant time and cost savings benefits.  They also facilitate improved financial controls.  Implementing such a solution that dramatically changes entrenched accounts payables processes in a stable can be a daunting task for a company.

TekStream has a proven track record of success implementing AP automation solutions utilizing the out-of-the-box Oracle Financials Imaging Implementation Accelerator as a starting point.  The Accelerator consists of a set of predefined configurations for Oracle WebCenter software that address a superset of the most common processes necessary to automate the capture, validation and uploading of invoice data into the Oracle eBusiness Suite AP module (EBS).  In TekStream’s experience the Accelerator provides a solid foundation on which to build an automated invoice processing solution for almost all customers.

Rather than starting with a clean white board and design a custom automated invoice processing solution TekStream recommends starting with the out-of-the-box Accelerator design as a baseline.  Working with the customer AP staff, TekStream then discusses customer requirements and defines customer specific configurations of the Accelerator and AP process changes that will allow the customer to utilize the Accelerator in production for a reasonable percentage of their invoices.  This allows the customer AP staff to become familiar with the Accelerator and its features and functions while using it in a production environment and integrating the Accelerator’s functionality into their production processes.  TekStream recommends customers utilize the Accelerator in this manner in production for at least two to three months before TekStream and the customer assess progress based on what has been learned during that period.  Using what they have learned about the Accelerator and how it’s functionality applies to their day-to-day invoice processing operations, the customer is now better able to assess the value proposition associated with extending and customizing the Accelerator to enhance its ability to meet the customer’s unique invoice processing automation requirements.

Introducing change to an AP operation can be challenging.  Learning to effectively utilize new technologies is part of the challenge.  Implementing the Accelerator requires that AP resources learn to use new technologies as well as adapt to new processes the Accelerator introduces.  TekStream recommends that the automation technology available with the Accelerator be implemented in two steps.  The first step is to expose the elements of the Accelerator that provide “key-from-image” functionality.  This allows the AP staff to become familiar with the WebCenter software functionality, user interface and user experience with only moderate changes to the EBS data entry processes they are familiar with.  Later, the excellent automated invoice data extraction, data validation and data uploading to EBS elements of the Accelerator can be introduced.  Having a solid foundation of familiarity with the WebCenter and Accelerator basic functionality and user experience will allow the end users to more effectively adopt and utilize these advanced invoice data extraction and validation features of the Accelerator.  This foundation will also allow AP users to adapt more quickly to the EBS processes associated with reviewing and validating invoices automatically uploaded to EBS from the Accelerator.

The Accelerator provides an effective routing process mechanism for coding and approving invoices by business users who order goods and services through a non-PO process.  The coding and approval mechanism is connected to EBS in the background to ensure valid EBS business rules are used in the coding process.  It utilizes easy to use tools that allow will non-EBS users to easily cod and approve invoices with valid account codes that are consistent with EBS business rules.  The two step implementation process suggested by TekStream allows AP users time to educate and support the business users on the new technologies and processes as they themselves learn and adapt to the same.  Once they have a solid foundation of experience with eth Accelerator and their business users have the same experience, expanding to the automated data capture, validation and upload process will go much more smoothly and efficiently.

The automated data capture and validation component of the Accelerator uses the WebCenter Forms Recognition (WFR) product.   The out-of-the-box WFR component has been pre-trained to automatically recognize, extract and validate key invoice data from scanned paper invoices and invoices imported from emails.   Many WFR customers find the pre-trained WFR component to be very effective for their invoice population.   In situations where a customer has a high volume population of vendor invoices that are unique, WFR can be trained to more effectively read these invoices.  Again, TekStream recommends that customers use WFR in production for two to three months before investing in enhanced training of the WFR solution.

In closing, there is work to do to implement an automated invoice processing solution based on the Oracle Financials Imaging Implementation Accelerator.  TekStream has the knowledge and experience to help customers navigate and execute the implementation process quickly and effectively.  TekStream’s experience and knowledge with a long list of successful Accelerator implementation reinforces our recipe for success for customers when implementing an Accelerator based solution – walk before you run.

Speak with a TekStream expert about your AP Invoicing project today.

Fill out the form below, and we'll contact you shortly!