Subscriber management: Registration and Self-care
WebSphere Portal provides Registration and Self-care processes for subscriber management. Registration allows users to register for access to the portal, and information entered during Registration can be modified during Self-care.
Registration
During Registration, the user enters mandatory data, such as the user ID and first and last names. The user optionally selects the preferred language from a list of available languages. The portal uses this language in all interactions and makes this information available to all portlets so that they can adapt to the user preference.
The Registration process of WebSphere Portal uses portal commands to allow the user to register for access to the portal. The configuration file Puma.properties is used by the Registration process of the Registration Servlet. The key puma.UserValidator is used to specify the class that checks user information.
The following JSPs are used during the Registration process:
- UserProfileForm.jsp is used to enter or reenter user information such as personal data.
- UserProfileConf.jsp is used to review user information such as personal data. Click Continue to register the user in the portal and save the user data in LDAP and in the portal database. Click Cancel to return to the personal information form.
- Congrats.jsp confirms that the user is registered in the portal.
- RegistrationError.jsp is displayed if an error occurs.
Create new attributes for the Registration JSPs
The Registration JSPs of WebSphere Portal can be expanded for the requirements by adding new attributes to them, such as attributes for creating new information input fields. When adding an attribute to the JSPs, use a name such as wps.Name, where Name represents the name you specify. If the attribute Name already exists in the inetOrgPerson user schema in the LDAP directory, as mapped by the attributeMap.xml discussed above, the value the user enters will be written to the LDAP directory. Otherwise, the attribute name and value will be stored in the WebSphere Portal database, where the following limitations apply: the name cannot be longer than 64 characters and the value cannot be longer than 255 characters.
Self-care
The user uses the Self-care process to change mandatory and optional information entered by the user during Registration, with the exception of the user ID.
The Self-care process of WebSphere Portal uses portal commands to allow the user to edit the account information. The file Puma.properties is used by the Self-care process of the Registration Servlet. The key puma.UserValidator is used to specify the class that checks user information.
The following JSPs are used during the Self-care process:
- UserProfileForm.jsp is used to change the personal data of a valid user. It is also used to reenter personal data in the event of an error. When an authorized user requests this page, the user ID is used by the servlet to retrieve the personal data and display it in the form.
- UserProfileConf.jsp is used to review personal data. Click Continue to update the user data with the new information. Click Cancel to return to the UserProfileForm.jsp to reenter the data.
- RegistrationError.jsp is displayed if an error occurs.
Create new attributes for the Self-care JSPs
The Self-care JSPs of WebSphere Portal can be expanded for the requirements by adding new attributes to them, such as attributes for creating new information input fields. When adding an attribute to the JSPs, use a name such as wps.Name, where Name represents the name you specify. If the attribute Name already exists in the inetOrgPerson user schema in the LDAP directory, as mapped by the attributeMap.xml discussed above, the value the user enters will be written to the LDAP directory. Otherwise, the attribute name and value will be stored in the WebSphere Portal database, where the following limitations apply: the name cannot be longer than 64 characters, and the value cannot be longer than 255 characters.
See also