Posts Tagged ‘WEM’

No doubt, WebCenter Sites has provided a great tool called CSExplorer in JSK for exploring the Database contents. But this tool has limitations. This works only on the Windows environments. But in reality, developers work on different environments aswell like MAC, Linux, etc.

I really felt bad when I couldn’t find someway to explore the database contents. while working on MAC. Fortunately, I have gone through some other website, and came to know how to explore the HSQLDB using eclipse.

I want to explain now how to explore the underlying tables of WCS using Eclipse, more elaborately.

Step  1 :

Open your server.xml file. It can be found under the below location:

[WCS installation Dir ]/apache-tomcat-7.0.42/Sites/conf/server.xml

Get the below values:

  • Username
  • Password
  • URL

See below screen shot.


Step  2:    

Have your eclipse installed. You can get it from

Step  3:     

Download the Data tools platform from eclipse marketplace. To do this, go to the Eclipse market place window, and search for ECLIPSE DTP (DATA TOOLS PLATFORM) 1.11.1 KEPLER, and install the plugin.


 Step 4:     

Now open the Perspective ” Database Development“.

You can do this by going to the Eclipse -> Window -> Open Perspective -> Other – > Database Development

Step 5: 

In the left hand, you will see a new tree opened called DATA SOURCE EXPLORER.

Right click on DATA CONNECTIONS, and click on NEW.


 Step 6:    

You will now get the following CONNECTION PROFILE window. Select HSQLDB from the available list of options, and click on NEXT button:


 Step 7:    

Enter the DB connection details in the below window:

Enter the following values from the inputs taken in step 1.

  • Database Location  : [WCS Installation Dir ] /App_Server/apache-tomcat-7.0.42/Sites/default/data/hypersonic/csDB
  • UserName  :   sa
  • Password    : blank

Then click on the TEST CONNECTION button. It shows a PING SUCCESSFUL dialog box. Now click on FINISH button.

DB Info Screen

NOTE:  You need to add the hsqldb.jar in the above window, by clicking on the + button available against the DRIVER  drop down.

Step  8:  

That’s it. In the Data source explorer tree of left hand side, you can see a new DB connection created to your local JSK. You can explore the tables as shown in the below screenshot.




That’s it for now.





In Information Technology, no software stands and plays alone for a long time. There are number of new technologies coming these days, getting popular, well noticed by customers / clients. But after some time, a day comes where these technologies are dominated by other technologies.

Coming to the Content Management Systems, there are many niche players like EMC, Oracle, etc. And Adobe joined them by redesigning Communique 4. It has released ADOBE DAY CQ5, basing on Communiqué 4. ADOBE DAY CQ5 is a new WEB EXPERIENCE MANAGEMENT SYSTEM.

What is Adobe Experience Manager?

Adobe Experience Manager helps you organize and manage the delivery of creative assets and other content across your digital marketing channels, including web, mobile, email, communities, and video.

Similar to Oracle WebCenter Sites,  ADOBE DAY CQ5 helps us to build compelling content-centric applications that combine Web Content Management, Workflow Management, Digital Asset Management and Collaboration sites.

Prerequisites for development within CQ

For the developers,  to build WEM site using the Day CQ5, following technologies are required:

  • HTML
  • CSS
  • JavaScript
  • JSP

The documentation for Adobe Day CQ5 can be accessed from

I’m now starting with Day CQ5, and will be updating topics on Day CQ5 from now on.


In Oracle WebCenter Sites, when we create a site, few tables will be created by the Content Server.  These tables will be used by the CS to write information about the sites that are created in the system. Following are the tables that will be created.

  1. Publication Table
  2. PublicationTree Table
  3. SitePlanTree Table
Publication Table:

This table is used by the CS to store all the info related to the sites that are created in your system. This holds the information like NAME, DESCRIPTION, PUBLICATION ID of the site. Each row in this table resembles a site in your system, and its information.

publication table

PublicationTree Table:

This table is used by the CS to store the information about the asset types that are enabled for your site.  It stores the information about the different asset types that you have created  / shared from other sites in your system.

SitePlanTree Table: 

This table stores information about the hierarchical structure of a site and its page assets. This table lists sites and page assets. We can code your CSElements to extract and display information from the SitePlanTree table

There will be a top level node (Page), which will have the rest of the pages placed below it.

The SitePlan in the Admin console of WCS resembles this table in database.

SitePlanTree table

We will now discuss the new things that are introduced in Oracle WebCenter Sites.

Though functionally, the way it operates is same as that of its previous version Fatwire 7.6, there are many additions/removal of functionalities.

Speaking in depth, there are various differences between Oracle WebCenter Sites 11g and its previous version, Fatwire Content Server 7.6 / 7.5.

Following are some of the changes we can observe from the UI.

1. The name FATWIRE has been completely removed from the product, right from the user guides to the software (Of course, still some of the packages are having the name FATWIRE).

2. The UI has been completely modified. Earlier, in Fatwire 7.6, we used to have four interfaces.

  • Advanced User Interface
  • Dash User Interface
  • Insite Interface
  • WEM Interface (For selected users)

But now, in the latest version, i.e, Oracle WebCenter Sites 11g, we have only three interfaces.

  • Admin Interface
  • Contributor Interface
  • WEM Interface (For selected users)

3. New Tab based interface.

4. Improved Drag and Drop facility

5. Customizable DASHBOARD

6. Finally, new look and feel.



Going Deeply, we can see the following changes (according to Oracle Documentation and my observations) :

1. The Contributor Interface has been given a modern look and feel with easily accessible controls and an updated color palette. Similarly, the Advanced, or Administrative, interface has been updated to better match the Contributor Interface.

2. The page building model and process has been redesigned. The management of page content can be accomplished using drag-and-drop functionality in combination with “dock-able” search results, sidebar trees, and strategically available toolbars. Once page creation is initiated, content can be dragged to predefined slots. Slots can be constrained by asset type and role-based user permissions per slot can be assigned. Non-technical users can easily control the presentation of content with graphical layouts and predefined arguments.

3. New capabilities to operate on multiple assets efficiently, including bulk deletion, approval, and bookmarking. These operations are conveniently available from search results screens. Operations can be executed by selecting multiple assets and pressing a single button.

4. Updated capabilities to locate assets (e.g., with a keyword) from the Contributor Interface’s search bar, including a convenient, embedded control to search by asset type.

5. A dashboard is now provided out-of-the-box. Widgets to manage assignments, bookmarks, and checkouts are included. Widgets can be rearranged on the dashboard using simple drag-and-drop.

6. The new Contributor Interface for marketers and business users provides a browser-like interface to efficiently manage multiple assets simultaneously. Assets can be opened in individual tabs and out-of-the-box revision tracking prevents asset changes from being overridden by concurrent edits.

7. It is now possible to drag content from search results and sidebar trees to both asset forms and page slots. Drag and drop can also now be used to quickly order the pages of a site plan.

8. View search results as either lists or thumbnails. Search results can be docked to make them conveniently available for dragging (e.g., to a page slot).  The dock automatically appears on the active tab.

9. Assets as well as their dependencies can now be approved with a single operation

10. The integrated WEM bar is now easier to use. A single click opens the WEM bar, and it will remain open until manually closed.



 1. Dash UI and InSite UI have been removed; they are replaced with Contributor UI

2. URL attribute data type has been removed. Instead, BLOB should be used.

3. RememberMe attribute editor has been removed. Instead,  TypeAhead or PickFromTree should be used.



1.  The ability to manage new content assets of type – basic, flex, page and engage – the Admin UI (formerly called the Advanced UI). We should now access this functionality from the Contributor UI.

2.   Mirror Publishing is deprecated. Instead Real Time publish should be used.

3.   Old caching implementation, use the new inCache based implementation (this   is active upon install by default)

4.   SOAP based web services are being deprecated; Instead, the public REST API should be used.

5.   Usage of asset API from stand-alone Java applications is deprecated. Instead, REST API should be used.

6.   Support for JBoss is not available in this release.

7.   Support for Safari is not available in this release.

8.   DebugServlet is not deployed.



This release includes Oracle branded versions of the former FatWire products, which are now consolidated under one product name, Oracle WebCenter Sites, with component terminology appearing in the UIs as follows:

        • WebCenter Sites (formerly FatWire Content Server)

        • Community (formerly FatWire Community Server)

        • Targeting (formerly FatWire Engage)

        • Analytics (formerly FatWire Analytics)

        • Gadgets (formerly FatWire Gadget Server)

        • Mobility Server (formerly FatWire Mobility Server)

        • Satellite Server (formerly FatWire Satellite Server)

There are various WEM Vendors in the market. The following are some of them:

  • etc..


WEB EXPERIENCE MANAGEMENT (WEM) is one of the branches of CONTENT MANAGEMENT SYSTEMS. It is emerging as an alternative to WCM, which only concentrates on creation of online content. Whereas WEM concentrates on creation of online content along with giving the new experience to the online businesses by marketing the products to the customers of specific interests.

For example, lets consider an e-commerce site. One customer might be interested in purchasing electronic peripherals, where as some others might be interested in purchasing outfits, etc. So, according to the customers taste, the marketing needs to be done.  If a customer who is interested in electronics is sent a mail from the marketing department related to some unnecessary things he isnt interested, its of no use.

Not only marketing, when a user logins to a site, he will be presented with all the articles available with the site. But if the user is presented with the products which he is interested on the top, and the rest of the products in low priority, then the main purpose of the business might become easy. All this can be achieved with WEB EXPERIENCE MANAGEMENT.

What is difference between WCM and WEM?

While WEB CONTENT MANAGEMENT (WCM) only deals with managing the online content, WEB EXPERIENCE MANAGEMENT (WEM) deals with the management of the customers taste along with the WCM part. Hence, We can think of WEM as an extension to WCM.

How WEM helps an organization?

WEM (Web Experience Management) helps an organization in many ways providing effective  web presence by providing a dynamic and interactive portal where business users can easily login and update their content and also help the organization in a great deal providing them to do target marketing campaigns, which can convert prospects into customers.