WebCenter Sites 12c Performance with Asset Reader API and Groovy

WebCenter Sites 12c introduces a number of new APIs to use when building out your sites. The developer documentation puts an emphasis on using an MVC approach that is aided by the new groovy controllers and reader APIs including the new asset reader API. Using an MVC approach to build out a site allows for a nice and clean separation of your business logic from the display logic. You can see the official documenation on all the APIs at http://docs.oracle.com/middleware/1221/wcs/wcs-develop.htm and also at...

Fundamentals of WCS' Public Site Search Infrastructure

Webcenter Sites ships with Apache Lucene.

Apache Lucene drives:

  • Asset-oriented search within the Contributor UI. This is automatically set up by default on an standard install. Users can enable / disable it on a per asset type basis as needed.
  • Asset-oriented search through a WCS-driven website's search box (or any equivalent feature). Developers must implement website-specific search logic; WCS provides a very basic API for this purpose.

In this post, we will focus on the fundamental aspects regarding Lucene-driven asset-oriented search in WCS-...


How To Programmatically Create Vanity URLs

Since version 11gR1, WebCenter Sites has natively provided the capability to allow editors to create vanity URLs for assets out of the box.  Even before that frameworks such as the GSF extended the core product to provide that functionality.  With the SEO benefits and pleasant visitor experience, Vanity URLs have become a necessary feature without which websites’ cannot launch.

WebCenter Sites has the built-in capability to automatically generate vanity URLs upon asset creation via a set pattern.  However there are situations where content is created prior to this mechanism being...


Integrating Twitter and WCS: A Primer On Asset Event Listeners And Other Mechanisms

Welcome back!

In my previous article, I outlined the different mechanisms in WCS for plugging your own ad-hoc logic into the asset save processing flow.

Before diving into the subject at hand, here are a couple of things we are NOT going to resolve in this article:

  • The "best possible" asset model for supporting Twitter integration.
    • Asset model, like any data model, varies significantly depending on each...

On Asset Event Listeners And Other Ways of Hooking-up Ad-hoc Logic Into WCS' Asset Save Processing Flow

 

DISCLAIMER (/ SPOILER): in this blog entry, we will not explain what an asset event listener is nor how to create one; they have been around since WCS' stone age and there is extensive documentation out there explaining that in detail, including - but not limited to - WCS 11g's official documentation and Java API:


Managing AngularJS Content within Oracle WebCenter Sites

There are a multitude of reasons organizations will turn to a content management system, but the underlying goal is the same across the board: Managing your content in an organized way.  The examples that first come to mind include managing assets such as page titles, articles, images, but what happens when a more complex asset is introduced like an AngularJS widget?

A Tale of Two Cities:

With WebCenter Sites you don’t have to give up control of the contents of your organization’s widgets. Out of the box WebCenter Sites does not natively support...


Installing Eclipse Groovy Plugin

     ­­­As of WebCenter Sites 11g, Groovy is supported when used as an element type. It is suitable for when what you want to implement some business logic/computation in a familiar JAVA syntax-scripting environment (1). Groovy Language has a lot of features that are GROOVY! You need to install the Eclipse Groovy Plugin (if you are using eclipse as your IDE) for better development experience, error checking, code completion, code coloring, and etc. 

How to install Eclipse Groovy Plugin:

1-    In your Eclipse in the top...

WCS Engage: Overloading the Mailroom

WCS Engage: Don’t Overload the Mailroom

One of the most useful features in Oracle’s WebCenter Sites is a feature entitled Engage.  This feature was vastly improved from previous iterations in WCS 11.1.1.8 and provides the platform with the ability to use market segmentation. Delivering targeted content to a key demographic is the Rubix’s Cube every marketing department is furiously trying to solve. 

Although rightfully drawn to this WCS feature, what has the potential to provide a tremendous amount of benefit can often turn into the second coming of...


Stay In Touch