Posts Tagged ‘content server’


Oracle has introduced a new feature called Vanity URL in Oracle WebCenter Sites, which provides us the ability to define and manage the VANITY URLs for any asset. In this post, we will discuss about how to enable the Vanity urls in the ContentServer, and its usage.

 1)Creation of Vanity URLs for Assets:

Vanity URLs for an asset  can be created in two way, Manually and Auto-Generated. WebCenter Sites supports two types of Vanity Urls ie Asset URLS and Blob(File) Urls. An Asset Url can be either auto-generated(pattern defined by the Administrator in Admin Interface) or created in the Contributor Interface). A Blob (File) Url is created only by the Administrator in Admin Interface using pattern, but Blob(File) url cannot be created from Contributor UI.

 i) Manually creation from the Contribute UI:

From the Contribute UI, vanity URL can be created by Content Contributors. Open the asset for which you wish to create a Vanity url. Access the asset’s edit view in the Form mode. In the form section selector, select URL. Fill the following fields.

URL :   Enter the vanity url.

Host :  Form the dropdrown, select the root url.

Template : Select the layout to render the asset on the website.

After enter click the “Add” button, then the vanity URL is displayed. The Vanity URL will not work, until the asset is “Saved”.

 ii) Auto-Generated Vanity URLs:

Vanity URLs can be generated automatically for individual assets based on the patterns configured. Once a pattern is registered, the vanity URL is generated when the asset is saved.

Login to the Admin UI and under Admin tab, expand the AssetTypes node, then expand the node for the specific asset type you are creating and auto-generated URL. Expan the URL Pattern and double click on “Add New”

Name :  Unique name for the pattern.

Site  : The pattern will be applied for the list of sites for which the asset type is enabled.

Host : The WebRoot which the vanity URL applied to.

Pattern : Enter the rule that define the vanity URL. The pattern define will be appended to the WebRoot which is mentioned in the HOST attribute, for this pattern to create Oracle provided pre-defined functions like


So, the vanity url will be something like http://localhost:8080/cs/avi/samplesubtype/sample_by_krishna.html


So, the vanity url will be something like  http://localhost:8080/cs/avi/1330543070443.html


So, the vanity url will be something like  http://localhost:8080/cs/avi/sample+by+krishna.html

(Spaces are converted into + symbols by default)

AutoGenerate for Asset:  URL pattern generation of Assets vanity url.

AutoGenerate  for Blob(File): URL pattern generation of Blob File vanity url.

The Below section “Evalutate URL Pattern” in the above images, is used to validate the auto generate url.

2) To Enable the Vanity URLs in the Content Server]

By default, these would be enabled for first site II and avi sports sites.

2.1) Configure SitePrefix : The WebCenter Sites know which URLs to treat as vanity URLs. In the Content Sever web app enter the following filter. Do the setting in the Web.xml.

If there are multiple site, need to specify comma separated SitePrefix in the param-value tag.

Location : <>/webapps/cs/WEB-INF

Add this  filter just below the   “… WEM SSO Filter … ” entry.
Add filtermapping just below  the filter-mapping of  “..WEM SSO Filter …” entry.

2.2) Create WebRoots:  Login to the Admin UI and under Admin tab, expand the WebRoots node and Add New. The WebRoots can be of Absolute , Relative or Combination.

HostName          : Enter the HostName which is unique identified for the WebRoot instance.

Root URL           : This can be Absolute or relative.

Virtual Root URL : If need to used the Virtual Url,  In futuretense.ini file for the property sites.environment specify the environment value as management/delivery.

It has two parameter the Environment and Root URL. For each environment will have one url,  enter environment name Root url and click add for

each environment.

Example : For Management environment, specify Environment = management,  Root URL =

Sites                  :  Enable WebRoot for specific sites.

3) System tool – URL Utility:   

Login to the Admin UI and under Admin tab,  can view all the vanity URLs defined in the system. This tool can be used to resolve the conflicts in the vanity urls.    Using this “URL Utility” admin can view  the conflicting urls, and can delete the vanity urls which are not required.

4) Tags to get Vanity URL: 

     The normal tags can be used to get the Vanity URL. If the vanity url is present for the given asset then below tags will return the vanity url.

i)  render:gettemplateurl

ii)  render:getpageurl

ii)  render:getbloburl

iv) satellite:link

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.

When the user enters a URL in the browser, and hits on enter, the following sequence of actions take place in order to complete the request and give the webpage as a response.

  1. The Webserver / load balancer routes the HTTP request to the Satellite Server.
  2. The Satellite server checks for the page in its cache.
  3. If the page is found in its cache, the page is returned as response.
  4. If the page is not found in its cache, the Satellite server routes the request to the Content Server.
  5. The Content Server checks for the page in its cache.
  6. If the page is found in its cache, the page is returned to satellite server.
  7. If the page is not found in the Content Server’s cache, the page is rendered by the Content Server, and it is stored in the CS Cache. Then sends the copy of the page to the Satellite Server.
  8. The Satellite server then stores the page in its cache, and returns it to the user.

In this way, the HTTP request is handled in Fatwire.


In this topic, we are going to discuss the CREATION OF USERS IN FATWIRE. To create a user in Fatwire, you need to login with ADMIN Credentials. Users can be created in Fatwire using ADVANCED UI, and the WEM UI. We are going to learn how to create the users in ADVANCED UI of FATWIRE.


1. Login to the ADVANCED  UI with Admin credentials.

2. Go to the ADMIN tab of the Advanced UI.

3. Expand “CONTENT SERVER MANAGEMENT TOOLS“. After expanding this, you will be able to see SITE, ELEMENT, ACLs, USER, etc.

4. Double click on USER. The following screen appears. In this screen, as shown below, we can MODIFY USERS, ADD USERS, DELETE USERS, MODIFY USER ATTRIBUTES.

5. Enter a name for the user in the ENTER USER NAME field. This name will be the login username for the new user.

6. Click on ADD USER radio button.

7. Click on the OK button. The following screen appears.

8. Assign the ACCESS PRIVILEGES for the user, as required.

9. Enter the PASSWORD, and re enter the same in RE-ENTER PASSWORD field.

10. Click on the ADD button.