Posts Tagged ‘Analytics’

We are now going to discuss the Content Server Architecture of Fatwire / Oracle WebCenter Sites 11g. Content Server Arcitecture has the following levels of components. All these combinedly working, brings a high performance site, as desired by the customer.

CS Architecture

  1. Database
  2. Application Server
  3. Content Server
  4. Satellite Server
  5. CS-Direct
  6. CS-Direct Advantage
  7. Engage (Optional)
  8. Analytics (Optional)

Now, we are going to see each of these sections in detail.


Like every other architecture, in this CS-Architeture, the Database is the one which sits on the bottom of all the components.The Database can be of our own choice. This may include Oracle Database, MS SQL, DB2, etc. We can choose an Database of our choice, and perform the installation. The installation guides will have enough information for providing the right databases, and their installation, etc.

Application Server.

The application server sits above the database, and it acts as the main component for running the Content Server. The Content Server Context (CS) is deployed in this application. Hence, all the requests from the components above this level, like Engage, Analytics, etc will be passed to the CS Context through this Application Server. This application server could be of our own choice, like Apache Tomcat, JBoss. etc. But, I’ve seen Apache Tomcat with most of the installations.

Content Server:

As mentioned above, the Content Server Context will be typically deployed in the application server. But, the actually installation of Content Server Software will be done in some other directory of our choice.

The Content Server context provides access to the Java servlets that compose Content Server. What language we code : XML or JSP, we code in the Content Server context. These XML and JSP tags provide an easy-to use interface to Content Server’s Java objects, so that even web designers with no Java knowledge can create Content Server web pages.

This Content Server will have cache storage, and this cache is used to store the pages, content, blobs, etc., which are frequently requested, as well as recently requested by the end users. In this way, the need for requesting the DB for each and every query coming from end user, will be drastically reduced, and hence, improving the overall performance.

CS-Direct (or) XCELERATE :

This CS-Direct module of the Content Server sits on the top of Content Server. The concept of Basic Asset Model is introduced by the CS-Direct module of the content server. The code name for this CS-Direct is XCELERATE. You can see the name XCELERATE in many places, like naming conventions, directory names, etc.

But, the Basic Asset Model has many disadvantages, which are later revisited and solved by the Flex Asset Model.

CS-Direct Advantage (or) GATOR :

This CS-Direct Advantage module of the Content Server is an extension to the CS-Direct. It adds additional functionalities to the existing data model. It sits on the top of CS-Direct.

The concept of Basic Asset Model has some limitations. Hence, to overcome those limitations, the CS-Direct Advantage module of the content server is introduced.
The CS-Direct Advantage introduces us with the Flex Asset Model. As this data model is an extension of the existing Basic Asset Model, they might have named it as Flex Asset Model (My assumption is FLEXIBLE Asset Model).

The code name for this CS-Direct is GATOR. You can see the name GATOR in many places, like naming conventions, directory names, etc.

Fatwire Engage:

In this e-commerce world, every customer is valuable and very important. So, there is a need to keep the visitor (customer) ENGAGED to the site, so that he revisits the site frequently, and gives a good business. This will increase the overall business profits.

So, to keep them engaged to the site (business), we can use the ENGAGE software of Fatwire. This is an optional software that can be installed, so that the end user will be kept informed about the recent attractions of his interest.

It is an application that enables your marketing team to divide your site visitors into segments and then target those segments with personalized messages, or promotional, marketing, and informational messages.

Fatwire Analytics:

Again, Analytics is an optional product. It is a Content Server plug-in that monitors and analyzes website traffic. It helps you to track visitors interactions with content from the time visitors start browsing your site, up to the time they leave your site.

Satellite Server :

Satellite Server can be divided into two components. Co-Resident Satellite Server, and Remote Satellite Server. By having two such servers, the caching will be hugely improved, and thus improving the site performance, and the overall turnaround time.

The Remote Satellite Server is a caching application that speeds the performance of your delivery system by serving cached images and Content Server pages from remote servers. Remote servers over here refers to different locations, like America, Asia, Australian location servers.

Satellite Server reduces the load on the Content Server delivery system and to deliver pages more quickly.

The Remote Satellite Server is offered as a stand-alone product to help you optimize system performance according to the load on the system.

In most of the cases, the Remote Satellite Server will be installed in the same server where the web server resides.

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)