Tuesday, 15 October 2013

What are Credential Vault in Portal



The credential vault is a repository where credentials are stored. Examples of credentials include certificates, private keys, user IDs, and passwords. WebSphere Portal provides a class called CredentialVaultService which portlets can use to store and retrieve credentials from the vault
A vault adapter is a plug-in module between the credential vault and CredentialVaultService

A vault segment is a partition of a vault. There are two types of segments: user-managed and administrator-managed. Portal administrators can create administrator-managed segments using the Credential Vault tab on the Security page of the Portal Administration place. This tab is called the Credential Vault portlet. WebSphere Portal provides a user-managed segment in the default vault.
A vault slot is part of a vault segment; it is represented using CredentialSlotConfig class.
There are two types of credentials: active and passive. Passive credentials allow a portlet to extract the credential's secret. Active credentials do not allow a portlet to extract the credential's secret.

The credential vault provided by WebSphere Portal defines four types of vault slots:
Portlet private slot Stores user credentials that are not shared among portlets. The Private Slot Portlet application demonstrates the private slot.
Shared slot Stores user credentials that are shared among the user's portlets. The Shared Slot Portlet application demonstrates the shared slot.
Administrative slot Allows each user to store a secret for an administrator-defined resource (for example, Lotus Notes). The Administrative Slot Portlet application demonstrates the administrative slot.
System slot Stores system credentials where the actual secret is shared among all users and portlets. The System Slot Portlet application demonstrates system slot.

Initializing CredentialVaultService

The CredentialVaultService is a portlet service that portlets can use to create vault slots for storing and retrieving credentials.

New Feature in JSR 286







  1. Inter-portlet communication (Event Event Handling )
  2. Portlet filters
  3. Public render parameters
  4. Shared session state across applications (maybe )
  5. AJAX support
  6. Java 5 annotation support in Generic portlet
  7. PortletURL generation callback listeners
  8. support for page <head> contributions and setting Cookies
  9. “private” PortletModes and setting nextPossiblePortletModes
  10. PORTLET_SCOPEd session attributes for dispatched Servlets
  11. Providing ActionRequest attributes to the RenderRequest

How to Configure WMM Attribute in IBM WebSphere Portal 6.0

step1 :- go to the following location in  your installed  portal server
/WebSphere/ibm/AppServer/profiles/Dmgr01/config/wmm
Step 2:- identify following files
wmmAttributesDescription.xml
wmmAttributes.xml
wmmDBAttributes.xml
wmmLAAttributes.xml
wmmLDAPAttributes.xml
wmmLDAPServerAttributes.xml
Step 3:- make the following chnages in  files
wmmAttributesDescription.xml

<wmmAttribute name="supervisorname">
<locale   localeName="en_US"  
  attributeName="supervisorname"
  attributeDescription="supervisorname of person." />
</wmmAttribute>
wmmAttributes.xml
<attributeMap wmmAttributeName="SupervisorName"
applicableMemberTypes="Person"
dataType="String"
valueLength="256"
multiValued="false"/>

wmmDBAttributes.xml
<attributeMap wmmAttributeName="SupervisorName"
pluginAttributeName="SupervisorName"
applicableMemberTypes="Person"
dataType="String"
valueLength="256"
multiValued="false"/>
wmmLAAttributes.xml
<attributeMap wmmAttributeName="SupervisorName"
pluginAttributeName="SupervisorName"
applicableMemberTypes="Person"
dataType="String"
valueLength="256"
multiValued="false"/>
wmmLDAPAttributes.xml
<attributeMap wmmAttributeName="SupervisorName"
pluginAttributeName="SupervisorName"
applicableMemberTypes="Person"
dataType="String"
valueLength="256"
multiValued="false"/>

wmmLDAPServerAttributes.xml

<attributeMap wmmAttributeName="SupervisorName"
pluginAttributeName="SupervisorName"
applicableMemberTypes="Person"
dataType="String"
valueLength="256"
multiValued="false"/>

Step 4 :- go to the  location
/WebSphere/ibm/AppServer/profiles/wp_profile/config/wmm

step 5:- repeate step 2 and 3
Step 6:- restart the server .

what is the personalization and customization

what is the personalization and customization 

When developing a portal application, there is lot of confusion wrt Customization vs Personalization. What the client might be calling Personalization might in fact be Customization or vice versa. So, it is very important to understand the difference between the two.

The term "customization" is used to mean the rendering of portlet content based on users preferences or manipulating the portal layout based on the users security attributes.

The term "personalization" is used to mean delivering portlet content based on a business rule or collaborative filtering.

Customization centers around what resources (portlets and pages) you show the users based on their role. This is a core capability of Portal. There are tools provided that help administrators provision these resources. Typically, portlets allow users to specify what kind of information should display. For example, a weather portlet might be customized to show
weather in the users home town.

Personalization can deliver content to a user based on a profile and/or business rule, or determine characteristics of a user based on previous purchases, or pages viewed. Personalization then selects content that is appropriate for that profile. For example, if a person has a high salary range, personalization can be configured to retrieve information about premium products, the page is assembled with the proper information and the user sees his personalized page.

Personalization includes a rules engine, a recommendation engine and a resource engine. Although a full install of Portal installs and configures personalization functions by default, there are additional databases to consider. For example, personalization uses the DB2 Content Manager Runtime Edition for storage of rules, campaigns and other objects. There is a logging framework used to record information about web site usage to a feedback database. The LikeMinds recommendation engine also requires a database to store information gathered through the logging APIs.

To use personalization, you need content to display to your users. Therefore, personalization and content management go hand in hand. You will also need to understand where content is stored and how it is managed to optimize performance.

Monday, 14 October 2013

Difference between load and get method of the Hibernate


Difference between load and get method of the  Hibernate





Get
Load
Hibernate Session class returns null if object is not found in cache as 
well as on database
load() method throws ObjectNotFoundException if object is not found on cache as well as on database but never return null.
Get method never returns a proxy, it

 either returns null or fully initialized 

Object
load() method may return proxy, which is the object with ID but without initializing other properties, which is lazily initialized.
Get method will result in slightly lower performance,
load method will result in slightly better performance,
Get method always hit database
load() method may not always hit the
database

Sunday, 13 October 2013

Java Classes That niter can be extended nor can be Initialized

Java Classes That niter  can be extended nor can be Initialized 

Ans :- 1. Array 2. Collections 
To make this type of class just make your constructor  private  .

What is Life Cycle of the Hibernate Object

What is Life Cycle of the Hibernate  Object


Very Impotent Links for Java and Portal development development

Jar Download for Spring  Maven Or Gradel Dependency for Spring