Registration, Edit My Profile and Login

 

+
Search Tips   |   Advanced Search

 

  1. Overview
  2. Registration

  3. Login

  4. Edit My Profile

 

Overview

WebSphere Portal provides Registration and Edit My Profile processes for subscriber management. Registration allows users to register for access to the portal, and information entered during Registration can be updated in Edit My Profile.

We can use portlets or JSPs to view...

  • Registration
  • Login
  • Edit My Profile

The default is portlets, which reside on special pages where the anonymous user has access rights based on the User role. The unique name...

wps.p.Login

...is assigned to the login portlet, and the unique name...

wps.p.Selfcare

...is assigned to the Registration and Edit My Profile portlets.

Using portlets will allow for themes and skins that can be turned on or off, and allows for different themes and skins for each virtual portal.

Using JSP screens allows customized JSPs that will be the same for all virtual portals.

The examples in this topic use the prefix:

portal:

...to designate JSP tags from the portal tag library in portal.tld. Our custom JSPs might use a different tag prefix.

 

Registration

During Registration, the user enters mandatory data...

The user has the option to select 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. If a language is not selected, the portal will determine which language to use from the users' browser tings.

 

Use portlets for registration

The same portlet is used for Registration and for Edit My Profile. To access, click "Sign up" on the login page.

Since the Registration and Edit My Profile portlets exist for each virtual portal, we can have different customized portlets for each virtual portal.

 

Use JSPs for Registration

In the JSP screen version, the user also has the option to select an interest, which is used by the Portal Personalization sample portlet to customize the displayed content. The following JSPs are used when a portal has been configured to use JSPs for registration:

mainMenu.jsp Enable modification of registration through JSPs.
UserProfileForm.jsp Enter or reenter user information such as personal data.
UserProfileConf.jsp 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 Displayed if an error occurs.

The Registration screen...

    was_profile_root/installedApps/cellname/wps.ear/wps.war/screens/markup_type/UserProfileForm.jsp.

To enable JSPs for registration authentication.screen.login = true in Authentication Service; as described in Setting configuration properties.

This property determines whether JSPs or portlets are being used and also determines some error processing during login.

Modify mainMenu.jsp in every theme you will be using, including the default, to enable Registration through JSPs. The default theme, IBM, is available in:

For example, to enable Registration through JSPs, uncomment the following in mainMenu.jsp in the default and every other theme you will be using, and comment out the section that generates a link to the page: Uncomment the following to allow registration via JSPs:

<%-- Enrollment aka Sign Up --%>

<%-- Comment out to enable sign up using JSPs --%>

<portal-logic:if loggedIn="no" 
                 portletSolo="no">

    <portal-internal:adminlinkinfo name="SELFCARE">

    <portal-navigation:urlGeneration contentNode="<%=wpsContentNode%>" 
                                     compositionNode='<%= wpsCompositionNode %>' 
                                     portletWindowState="Normal" 
                                     themeTemplate="">

        <portal-navigation:urlParam type="render" 
                                    name="ao" 
                                    value="thm"/>
    
        <portal-navigation:urlParam type="render" 
                                    name="OCN" 
                                    value="<%= wpsContentNodeID %>" />

            <c: var="menuTitle">
               <portal-fmt:text key="link.enrollment" 
                                bundle="nls.engine" />
            </c:>

            contents[i]="asynchDoFormSubmit('<% wpsURL.write(escapeXmlWriter); %>');";
            i = i+1;
            contents[i]='<c-rt:out value="${menuTitle}" escapeXml="true" />';
            i = i+1;
            contents[i]="";
            i = i+1;

    </portal-navigation:urlGeneration>

    </portal-internal:adminlinkinfo>

</portal-logic:if>

<%-- Uncomment to enable sign up using JSPs 

<portal-logic:if loggedIn="no" portletSolo="no">

    <c: var="menuTitle">
        <portal-fmt:text key="link.enrollment" bundle="nls.engine" />
    </c:>

    contents[i]="asynchDoFormSubmit('<portal:url command="PrepareEnrollment" home="public" reqid="no"/>');";
    i = i+1;
    contents[i]='<c-rt:out value="${menuTitle}" escapeXml="true" />';
    i = i+1;
    contents[i]="";
    i = i+1;

</portal-logic:if>

--%>

 

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 that 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.

 

Login

WebSphere Portal v6.0 allows you the option of using JSPs or portlets to view Login. Using a screen will allow you to customize the JSP that is used for the screen, whereas a portlet will have themes and skins that can be turned on or off.

 

Use portlets for Login

The portlet option is the default option for WebSphere Portal v6.0. Access the Login portlet by clicking Login in the theme. The Login portlet can also be placed on any portal page.

Since the Login portlets exist for each virtual portal, it is possible to have different customized portlets for each virtual portal.

To set theme on the Login page

  1. Go to...

    Administration | Manage Pages

  2. Change "Search by:" to "Title contains" and search for "login".

  3. Once found set theme using Edit Page properties icon.

 

Use JSPs for Login

The Login screen is located under:

    was_profile_root/installedApps/cellname/wps.ear/wps.war/screens/markup_type/Login.jsp.

In order to enable JSPs for login authentication.screen.login = true in Authentication Service; as described in Setting configuration properties.

Modify banner_toolbar.jsp and mainMenu.jsp in every theme you will be using, including the default, to enable login through a screen. The default theme, IBM, is available in:

For example, to enable login through a screen, uncomment the following in banner_toolbar.jsp and mainMenu.jsp in the default and every other theme you will be using, and comment out the section that generates a link to the page:

  <%-- Login button --%>

  <%-- Comment out to enable screen login --%>

  <portal-logic:if loggedIn="no">

      <portal-navigation:urlGeneration contentNode="wps.Login" themeTemplate="">

          <c: var="menuTitle"><portal-fmt:text key="link.login" bundle="nls.engine" />
          </c:>
          contents[i]="asynchDoFormSubmit('<% wpsURL.write(escapeXmlWriter); %>');";
          i = i+1;
          contents[i]='<c-rt:out value="${menuTitle}" escapeXml="true" />';
          i = i+1;
          contents[i]="";
          i = i+1;

      </portal-navigation:urlGeneration>

  </portal-logic:if>

  <%-- Uncomment to allow screen login 
  <portal-logic:if loggedIn="no">
          <c: var="menuTitle"><portal-fmt:text key="link.login" bundle="nls.engine" /></c:>
          contents[i]="asynchDoFormSubmit('<portal:url home="public" screen="Login" ssl="false"/>');";
          i = i+1;
          contents[i]='<c-rt:out value="${menuTitle}" escapeXml="true" />';
          i = i+1;
          contents[i]="";
          i = i+1;

  </portal-logic:if>
  --%>
(banner_toolbar.jsp)        
  <%-- comment this to enable screen login --%> 
  <portal-logic:if loggedIn="no">
  <portal-navigation:urlGeneration contentNode="wps.Login">
          <a tabIndex="7" class="toolbarLink" href='<% wpsURL.write(escapeXmlWriter); %>'>
          <portal-fmt:text key="link.login" bundle="nls.engine"/>
          </a>
  </portal-navigation:urlGeneration>
  </portal-logic:if>
  
  <%-- Uncomment this to enable screen login  
  <portal-logic:if loggedIn="no" notScreen="Login">
      <a class="toolbarLink" 
         href='<portal-navigation:url 
         home="public" 
         screen="Login" 
         ssl="false"/>'>
             <portal-fmt:text key="link.login" bundle="nls.engine" />
      </a>
  </portal-logic:if>
  --%>    

The Login screen can be configured by enabling or disabling the ShowSignupLink and ShowResumeSession parameters. Enabling these parameters allows users the option to sign up for portal access or to resume their last session.

 

Edit My Profile

The Edit My Profile process is used to change mandatory and optional information entered by the user during Registration, with the exception of the user ID.

WebSphere Portal provides this function in two ways; either through a portlet or through JSPs. By default a portlet is used. The portlet version receives the information about mandatory attributes from the used Member Manager configuration. Optional attributes can be added using the configuration mode of the portlet. To enable the JSPs functionality, please use the instructions under section below entitled Use screens for Edit My Profile.

Theme JSPs and configuration files are managed as part of the main WebSphere Portal enterprise application and thus are part of the WebSphere Portal EAR file. The EAR file must be updated and redeployed when changing JSPs or configuration related files. Failure to do this could cause the modifications to be deleted when the EAR file is subsequently updated. Basic instructions on updating and redeploying the EAR file with modified files are in Deploying themes and skins in a production environment. The following JSPs are used when a portal has been configured to use JSPs for Edit My Profile:

mainMenu.jsp Enable modification of registration via JSPs.
UserProfileForm.jsp 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 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 Displayed if an error occurs.

 

Create new attributes for the Edit My Profile JSPs

The Edit My Profile 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.

 

Creating new attributes for the Edit My Profile portlets

Edit My Profile allows users to change information entered at registration. Administrators can determine what information appears in the profile by editing the list found in the configure link. LDAP or member management fields determine what fields appear as potential fields for the user profile. Some fields are disabled because they are required fields in PUMA (portal user management), and cannot be removed. You must define the attribute in the wmmAttributes.xml file and the repository specific file:

To add the attribute before enabling security, choose the Template for the appropriate LDAP server (wmmLDAPAttributes_IDS.xml for IBM Tivoli Directory Server ). To add it after enabling security, use the wmmLDAPServerAttributes.xml file.

 

Use portlets for Edit My Profile

The portlet option is the default option for WebSphere Portal v6.0.

Access the Edit My Profile portlet by clicking Edit My Profile or Sign up in the theme.

Since the Edit My Profile portlets exist for each virtual portal, it is possible to have different customized portlets for each virtual portal.

 

Use JSPs for Edit My Profile

The Edit My Profile screen is located in the expanded ear file under:

    directory/wps.expanded/wps.war/screens/markup_type/UserProfileForm.jsp.

To enable Edit My Profile through a screen: Modify mainMenu.jsp in every theme you will be using, including the default, to enable Edit My Profile through a screen. The default theme, IBM, is available in:

For example, to enable Edit My Profile through a screen, uncomment the following in mainMenu.jsp in the default and every other theme you will be using, and comment out the section that generates a link to the page:

<%-- Comment out to enable edit profile using JSPs --%>
<c-rt:if test = "${themePolicy.renderSelfCare}">

  <portal-logic:if loggedIn="yes" portletSolo="no">
      <portal-internal:adminlinkinfo name="SELFCARE">
      <portal-navigation:urlGeneration contentNode="<%=wpsContentNode%>" 
          compositionNode='<%= wpsCompositionNode %>' portletWindowState="Normal" themeTemplate="">

      <portal-navigation:urlParam type="render" 
          name="ao" 
          value="thm"/>

      <portal-navigation:urlParam type="render" 
          name="OCN" 
          value="<%= wpsContentNodeID %>" />

          <c: var="menuTitle"><portal-fmt:text key="link.selfcare" bundle="nls.engine" /></c:>
              contents[i]="asynchDoFormSubmit('<% wpsURL.write(escapeXmlWriter); %>');";
              i = i+1;
              contents[i]='<c-rt:out value="${menuTitle}" escapeXml="true" />';
              i = i+1;
              contents[i]="";
              i = i+1;

      </portal-navigation:urlGeneration>

      </portal-internal:adminlinkinfo>

  </portal-logic:if>

</c-rt:if> //end renderSelfCare

<%-- Uncomment to enable edit profile using JSPs>

<c-rt:if test = "${themePolicy.renderSelfCare}">

  <portal-logic:if loggedIn="yes" 
                   portletSolo="no" 
                   notScreen="SelfcareUserForm,SelfcareUserConf">

      <c: var="menuTitle">
         <portal-fmt:text key="link.selfcare" bundle="nls.engine" />
      </c:>
      contents[i]="asynchDoFormSubmit('<portal-navigation:url command="PrepareSelfcare" reqid="no" />');";
      i = i+1;
      contents[i]='<c-rt:out value="${menuTitle}" escapeXml="true" />';
      i = i+1;
      contents[i]="";
      i = i+1;
  </portal-logic:if>
</c-rt:if> //end renderSelfCare
      --%>

 

Related information