Posts Tagged ‘Content management’

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.






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

What is a Portal?

A portal is generally defined as a software platform for building websites and web applications. A portal is a web application that commonly provides personalization, single sign on, content aggregation from different sources, and hosts the presentation layer of information systems. Aggregation is the act of integrating content from different sources within a web page. Present day portals have added many features which help the editors to implement various functionalities from a single platform. The below listed various features are available in the modern day’s portals:

  • Web Content management
  • Document management
  • Digital asset management
  • Workflow management
  • Social collaboration (Communities), etc.

These features are making Portals as one of the best options to be chosen while building a web application / websites.

Portal functionality can be divided into three main parts:

  1. Portlet container: A portlet container is very similar to a servlet container. A portlet container is responsible for initializing and destroying portlets and also for passing user requests to it and collecting responses. It controls the life cycle of the portlet.
  2. Content aggregator: The main job of a portal is to aggregate content generated by various portlets.
  3. Common services:  The common services that you can find in most implementations are:
  • Single sign on: This helps us to get access to all the applications that are deployed in the Portal, once we log into the portal server
  • Personalization:This helps the user to customize his page, so that he can view the applications which he is interested.

I will introduce you how to enable the REVISION TRACKING feature in Oracle WebCenter Sites / Fatwire, through this post.

Being the content management professionals we already know about the revision tracking process, as it is one of the fundamentals of CMS. The actions that include are CHECK-IN, CHECK-OUT, CANCEL CHECKOUT, VERSIONING.

Oracle WebCenter Sites / Fatwire doesn’t enable this Revision Tracking feature by default. We will now see how to enable the mechanism in OWS / Fatwire.


1. Log in to your site’s Admin Interface.

2. Click on the Admin Tab.

3. Expand ASSET TYPES, and go down to the asset for which you would like to enable the revision tracking feature . (ex: Sample_C, Sample_A etc)

4. Expand the asset, and there you would find a link REVISION TRACKING.

5. Expand the REVISION TRACKING link as well. There you would find an option.

  • Track  (See Screen Shot below)

6. Double click on Track.

7. In the workspace, it will display the number of revisions to be stored. Enter the number of revisions to be stored, and click on the  button.  A message saying “Revision Tracking succeeded for —your asset—” will be displayed.

8. That’s it. Revision Tracking is enabled for your asset.

When you inspect your asset, you can see the CHECK-IN, CHECK-OUT, SEE VERSIONS action items along with other default action items, as follows:


If you want to disable revision tracking (In case if you have enabled revision tracking through above steps), proceed till Step-4

5. Then, expand the REVISION TRACKING link as well. There you would find two options.

  • Set Revisions
  • Untrack (See Screen Shot below)

6. Double click on UNTRACK.

7. In the workspace, it will display a confirmation message. Click on the  button.  A message saying “Untrack succeeded for —your asset—“ will be displayed.

8. That’s it. Revision Tracking is disabled.