Webcenter Single Sign-on

There are various way to make Webcenter Portal Single Sign-on work.

- Oracle Access Manager (OAM)

- Oracle Single Sign-on (OSSO)

-SAML-based single sign-on solution for Oracle Webcenter Portal Applications Only

- SSO Solution for Microsoft Clients, using Window Authentication based on the Simple and Protected Negotiate (SPNEGO) mechanism and the Kerberos protocol.

Oracle OAM 11G is the recommended single sigh-on solution for Oracle Webcenter Portal 11g Installations.

WebCenter PS5 : Make sure you have all lib loaded

If you running in to issue where you cant find the lib for particular webcenter services , Please check following in Jdeveloper.

Help -> About (Extensions)

When you create new application in jdeveloper you will notice three different application type.

Component Palette : Add Component to Favorite

We use many ADF Faces , HTML , JSF Component for User Interface ,So I would suggest adding most important component to favorite

 

Add to Favorite	Final Outcome

Managed vs Backing Bean

Backing Bean is Type of Managed Bean which contains one to one mapping to JSF Component.

However , Managed Bean hold data and logic for application. Managed Bean is defined in faces-config.xml , adfc-config.xml , taskflow.

ADF BC : Showing Attribute Label using Groovy

While throwing exception from BC Validator you can throw exception from Message Bundle with some custom message. However ,If you want to include some attribute label from control hint in your message then you can use following expression.

source.hints.COLUMNNAME.label

ADF Application Basic File Structure

You need to know key files in ADF that deals with configuration.

PageDefinition Parameter

Your page might be dependent on multiple id from external source which may be in different scope and It is good practice to create temporary variable in page definition file and assign it with value coming from different scope , So you can access that variable from page using only one standard #{bindings.VariableName} instead of pageflow , session or application scope access. This provided more consistency in user interface.

I created following two variable in parameters section of page definition and assigned it value with #{sessionScope.variablename} and #{pageFlowScope.variablename} , Now I don’t have to access this two different scope from my user interface , But I have to access only #{bindings.DeptId} and #{bindings.ExternalId} which provided a good standard to adopt while developing application.