Enterprise Portal provides four adapters:
Security proxy – key values (for example, user name, password, URL) allow users to log in to back-end applications using their ProxyAuthenticationInfo (PAI), which uses the key values as input parameters to portlets to enable single sign-on to back-end systems. This option is useful when the user wants to log in to an application through a portal that requires a user name and password different from their portal login. This adapter is available only in the Enterprise Edition.
User name/password – the keys shown for this adapter are automatically created when a user logs in to Portal Interface or Portal Studio. Users cannot create, edit, or delete keys. The key values are stored in memory and maintained only for the user’s current login session. The values are reset each time a user logs in or changes their password. The key values can be used when a user logs in to Portal Studio or Portal Interface, then wants to log in to a portlet during the same session that requires a login with the same user name and password.
Database table – uses the back-end database to store keys and user values. You can create an input field with no default values, a single default value, or a drop-down list of default values from which a user can select.
EJB – uses the Sybase Personalization Web service to store and retrieve personal key values. The EJB adapter uses only basic features of the Sybase Personalization service. The service itself has features and functionality well beyond the other personalization adapters. The EJB adapter uses a subset of those features. This adapter is available only in the Enterprise Edition.
The Sybase Personalization service is useful across
a wide range of applications—not just the portal. It is
a complete EJB application. Sybase software other than EP uses this
service to store personal information of any nature. For example,
the iAnywhere Wireless server uses this service to store user’s
mobile device characteristics (phone number, phone type, notification
schedule preferences, and so on).
