WebCenter Portal Automatic Logout

WebCenter Portal is usually integrated with Oracle Access Manager (OAM) to manage its authentication. This integration has several advantages such as enabling Single Sign On (SSO) across all Oracle products, but it may cause problems when timeout occurs.

In order to increase performance and maximise platform, OAM should have a reduced timeout for user sessions. So after that time, user would lose its login cookie and when he/she clicks on any link, an error page would be displayed.

To avoid that, you may use the following workaround:

Add a refresh command in the Portal template header and set the time to the OAM timeout minus 10 seconds, i.e. If OAM timeout is 15 minutes, set the refresh to 890 seconds. As the target URL, specify the OAM logout address, passing as parameter the page to be displayed after logout (end_url). For instance:

<meta http-equiv="refresh" content="890; URL=/../oam/server/logout?end_url=/myApp"/>

This tag must be included in the header of the page, before the pageTemplateDef tag.

As a result, when user inactivity is near OAM timeout, the page will refresh automatically and the application login page will be displayed.

References

Oracle Service Requests: SR 3-9350587377 : OAM11.1.2.2.0 - send error page when come over OAM inactivity timeout
Installing and Configuring OAM with WebCenter Portal
Benefits of Oracle Access Manager
HTML meta tag

WebCenter Portal disable skin version warning

If you have a look at your WebCenter Portal output log (.out), it is quite likely that you will find an annoying warning repeated constantly like the following one:

<Jan 15, 2015 10:09:27 AM COT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinFactoryImpl> <BEA-000000> <Cannot find a skin that matches family portal and version v1. We will use the skin portal.desktop.> 

This is not a big issue because it does not affect Portal operations, but it makes difficult to track logs and clients have the right to have a free of errors/warnings log.

The solution is described in this post by the A-Team. It is related to the skin version defined in your Portal application, so the recommended action is to delete the skin-version tag in the trinidad-config.xml file.

<?xml version="1.0" encoding="windows-1252"?>
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config">
  <skin-family>#{preferenceBean.defaultTrinidadSkin}</skin-family>
  <skin-version>v1</skin-version>
</trinidad-config>

After re-deploying the application the warning message should disappear.

However, apart from that issue, there is another one related to skins:

<Dec 19, 2014 8:09:41 AM COT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinCSSDocumentHandler> <BEA-000000> <Not a valid @agent CSS property rule: max-version: 9.0>
<Dec 19, 2014 8:09:41 AM COT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinCSSDocumentHandler> <BEA-000000> <Not a valid @agent CSS property rule: max-version: 16.0>

So far, these warnings have no workaround yet. According to an SR I opened with Oracle, it is a benign message and it should be fixed in 11.1.1.9 version.

References

Removing the “Cannot find a skin that matches family portal and version v1.1″ message
Oracle Support Doc ID 1965182.1
ADF BUG 14722194

How to successfully implement Oracle WebCenter

As with many other complex software products, Oracle WebCenter implementations are usually a challenge for clients. It costs a relatively important amount of money, resources must be allocated from the own company and success is not absolutely guaranteed.

There is a lack of studies regarding IT implementations, but I have found an interesting article that analyses the critical success factors of ERP implementations, focusing on the client side. Authors Finney and Corbett (2007) researched the available literature about this topic and built a list of factors; obviously, WebCenter is not an ERP system, but I found the described keys to success are almost the same in this type of projects. So I have extracted and modified the most important ones according to my own experience, and this is the result:

Strategic factors:

Factors that relate to the big picture.

• Top management commitment and support: It is one of the two most important factors. Strong and commited leadership at the high-level management has been proven as crucial for the success of implementations.
• Visioning and planning: Objectives must be defined, planning would include QA  (Quality Assurance) and Oracle WebCenter best practices.
• Build a business case: Implementation should be justified to earn commitment from the client.
• Project champion: This interesting name refers to the need of having a person in the team with not only excellent leadership skills, but also with good technical and business skills.
• Implementation strategy: A strategy must be defined with different phases and milestones.
• Vanilla WebCenter: An early analysis of the requirements should determine which out-of-the-box functionalities could be used, minimising customisations and developments, as well as the number of products to be deployed.
• Project management.
• Change management: It is usually the most important factor. Users must be trained in the new environment and be convinced of the benefits of WebCenter, having a possitive employee attitude, otherwise it will be really difficult to accomplish the goal. This task includes negotiation with different management  and opinion leaders. Sometimes it is common to find IT projects where leaders have not paid enough attention to this factor, jeopardising the whole project; based on my experience, I think you cannot succeed in an implementation if customers are not convinced of the advantages the product brings to their day-to-day work. Thus, we must be sort of Oracle evangelisers, even though I do hate that word.

Tactical factors:

Factors related to details.

• Project team: Members must be carefully selected amongst the best available IT professionals, although some training should be planned. Some business skills are desirable too.
• Communication plan: Communication must be fluent between business and IT, including low-profile employees.
• Empowered decision makers: Implementation leaders must have the authority to perform the necessary actions.
• Team morale and motivation: Project leader should care about the work environment, recognising the work, because the implementation could fail due to losing demotivated employees.
• Project cost planning and management: Client needs to know the cost of the project, however it is recommended to have an extra budget for unexpected expenses.
• IT infrastructure: Infrastructure must taken into account not just Oracle FMW Certification Matrix, also a sizing analysis would determine the hardware resources to meet the expected load of the system, depending on the number of concurrent users, page loading time, etc.
• Selection of WebCenter: Client needs to choose the products and versions of the Oracle WebCenter suite to be implemented: WebCenter Portal, Content, Sites or just plain ADF applications. Expert advise should be sought.
• Troubleshooting/crises management: Troubleshooting skills are rquired for this type of implementations, because it is usual to face new unforeseen issues.

 Once we know the critical success factors for implementations, the difficult part is how to properly manage all of them. That would depend on the unique characteristics of each client.

References

Finney, S. & Corbett, M. 2007, "ERP implementation: a compilation and analysis of critical success factors", Business Process Management Journal, vol. 13, no. 3, pp. 329-347. (Not freely available on the web).

Oracle Fusion Middleware Supported System Configurations