Nice to Know — CMIS and WebCenter

CMIS queries is an extensive topic and I’d like to write about it in other posts, but today I want to mention some important tips regarding CMIS:

1. CMIS stands for “Content Management Interoperability Services

2. Oracle WebCenter uses OASIS CMIS

3. To work with Multivalued properties remember to use ANY <multiValuedQueryName> IN (<literal>, …).


4. To work with more than 2 ORs for the same property in a query, use this syntax:
(( (propertyA LIKE ‘value1’ OR propertyA Like ‘value2’OR (propertyA LIKE ‘value3’) ))

SELECT * FROM ora:t:IDC:GlobalProfile WHERE ora:p:dDocType LIKE ‘Demo’ AND (((ora:p:xMyBlog LIKE ‘WebCenter’ OR ora:p:xMyBlog Like ‘Portal) OR (ora:p:xMyBlog LIKE ‘Mauro’)))

5. You need to escape the characters ‘ and _ with: /

If you want more information please refer to:



Blogging on WebCenter Portal

Blogs are part of the collaboration features that WebCenter offers and they are really easy to setup.


  1. Have WebCenter Content running.
  2. Create a folder in WebCenter Content that’s going to hold your blogs.

Steps to enable blogs in WebCenter:

  1. Create a WebCenter Portal Application
  2. Create a Page for your WebCenter Portal Application
  3. Add a Content Repository Connection
Type caption for image (optional)
Type caption for image (optional)

After this setup, you have 2 options to integrate Blogs into your portal.

1. Extend Connections->Content Repository and select the Folder you want to use to store your blogs.

Type caption for image (optional)

 2. Drag and Drop the folder to your page and select Blogs

Type caption for image (optional)

This will add automatically the reference ID for the Taskflow:

Type caption for image (optional)
Type caption for image (optional)

The second option is to add the taskflow manually to your page and add the resourceId manually:

Type caption for image (optional)

Note: Remember to add “Page Customizable” if you want to manipulate the taskflow in runtime.


New Post

Change visibility of Resources – WebCenter Portal

The main idea of this post is to help you locate the  “generic-site-resources.xml” file and modify its content.

WebCenter Portal can handle resources in 2 different ways:




Creating a resource is a topic I will talk in a different post.  What I will like to share with you is how to change the visibility of  new resources in Design Time.

A good example is a Content Template, whenever you create a Content Template in Design Time, this resource by default gets a visibility to False, you can change this in runtime, but if you’re developing to test is a pain to change this property every time you lose your MDS.

Lets create a dummy content template:

2013-10-28_2121 2013-10-28_2124

By default with this settings you’re have your content template not visible. To make it visible you have 2 options:

  1. Run your Portal,
    A.-  Go to admin section then content presenter,
    B.-  Look for your template and make it visible.

    The problem with this solution is that as mentioned before you’ll lose all your changes if you are running the Portal locally and you’re erasing your MDS every time you run the Portal.


  2. Edit the generic-site-resources.xml file.
    Just look for your template, in my case “” look for the tag “<resource>”  and modify the visible property from FALSE  to TRUE.
2013-10-28_21272013-10-28_2127_001 2013-10-28_2129

WebCenter Portal – Formerly WebCenter Spaces

Before moving to something more technical I wanted to share with you another feature from the latest version of WebCenter.

As you might already know, there have been some naming convention changes for this version and one of the most important was renaming Spaces to Portal. This change didn’t come alone, now you don’t create spaces you create portals and portal templates.  Another add on is the Portal Builder.


The creation of a Portal is not really that different from creating a Space in the previous version, you can select from OOTB templates, or create your owns:

 2013-10-13_1511  2013-10-13_1511_001

In the  final step, there is a new step to create your pages from an input-text, you can include links and system pages:

To create a page hierarchy, use +.
Example: Page 1, +Page 2, +Page 3, ++Page 4 produces this hierarchy:e

  • Page 1
    • Page 2
    • Page 3
      • Page 4


But now let me show the interesting part that was added to this version. You can design the Portal for different MOBILE DEVICES:

2013-10-13_1516And preview them as well:

 2013-10-18_0347  2013-10-13_1536

There are some more interesting features, but I’ll be posting about them in different posts.

Note: This is not available from WebCenter Portal Framework.

WebCenter Content – Mobile App


With the latest  WebCenter Release  a mobile app was released, and yes this time  Android is included  as well.

Yo can get the Android app from here:  Google Store

For IOS: Apple Store

Main differences between both apps:

  • Main menu for IOS contains an extra menu (“Recently view”)
  • Default sorting for Android is based on Ascending Date
  • Default sorting for IOS is based on Descending Date
  • Extra metadata field is included in IOS detail document view (“Path”)

This is the original search from WebCenter Content:

OWCC Search

Here you have some screenshots of both apps:

Android (Tablet)
Screenshot_2013-10-16-02-27-41  photo 1
Screenshot_2013-10-15-23-09-47 photo 2
Screenshot_2013-10-15-23-10-15 photo 3
 Screenshot_2013-10-16-00-17-05 photo 4
 Screenshot_2013-10-16-02-38-31 photo

WebCenter Portal Framework PS7 small details (404)

It’s difficult to look for things that are not posted already, I’m sure I’ll start duplicating some of them, but meanwhile, I would like to start with 1 of the differences on “WebCenter Portal  Framework Application“.

Create a WebCenter Portal  Framework Application:

New Application PS7

It might look like nothing has changed, but  if you look closer to the files that were created you’ll notice a small change:

New Structure

A new file “error404.jsp” under a “jsp” folder was created. One of the “bugs” that was happening for WebCenter Applications, was related to the problem of session expiring and getting redirected to a 404, this was because the navigation URL was only valid for authenticated users or for a specific role, example:

For PS7 this is being solved from the “error404.jsp” file OTTB, this is already added to the web.xml to be taken for 404 errors:

404 Code

Similar to what we had in the Filter, the first validation is to check if the user is logged in, otherwise he will be sent to the Login screen, if the user is logged in by default you’re sent to the 404 error but you can extend this if needed.

Let’s start sharing!

After more than 5 years working with Oracle products, I finally have the opportunity to contribute something to the community. There are a lot of good blogs already out there, but I’ll do my best to contribute with interesting ideas and compile the cutting edge ones from my colleagues.

Please feel free to let me know your thoughts regarding the blog, so I can improve it.

Create a free website or blog at

Up ↑

%d bloggers like this: