Configuring User Registrar

For example, change <IMG SRC='/csrc/images/ciscologo.gif'> to <IMG SRC='/csrc/images/MSO.gif'>.

If you have an existing image, you can simply replace it. Otherwise, use a standard image editor to create the image and then specify the new image by file name.

The template files contain the width and height of every image. If you replace or update an image with one of a different size, you need to update every <IMG> tag that references the modified image. The images are stored in the <csrc-root>/csrc/images directory.

Tips Make sure that you enter the correct width and height for each image. Having specified dimensions is critical to increasing the perceived performance of any Web page displayed to end users. This is particularly noticeable when using the Netscape browsers. If the template does not contain the dimensions, Netscape browsers wait to display a page until they have loaded all the images.

For example, the following two lines are messages for the known_login page:

page:known_login:missing=Username=Username, please re-enter.
page:known_login:missing=Password=Password, please re-enter.
 

System messages apply across all pages while page messages are specific to each page.

For example, to display a hint for the user's password on the login page, create an extension attribute named Hint and add it to the Subscriber object with the line <GX TYPE=cell ID=Subscriber.Hint></GX> in the login template page. Then every time the user accesses the login page, User Registrar displays the hint.

The CSRC schema also employs required and optional attributes. In this case, required means that the attribute must have a value in the database. Whereas, in the application specification file, required means the subscriber must enter the value.

Next is the most common destination that is used as the default path for the workflow. The remaining three are used as additional destinations on a per-page need. Pages defined in the specification file contain descriptions outlining the expected inputs and outputs. Using this information, you can ensure that the modifications to the workflow result in a valid application.

page choose_username
{
     Title = "Select a User Name"
     Logic = choose_username;
     Template = "choose_username.tmpl"
     Children = confirm_username;
     NextPage = confirm_username;
     CancelPage = logout;
 
    help
    {
        SeeAlso = confirm_username;
    }
 
     objects
     {
         Subscriber NewSubscriber
         {
             Required = Username, Password;
             Direction = input, output;
         }
     }
 }
 
 logic choose_username
 {
     Class = "com.cisco.csrc.ursub.choose_username"
     File = "com/cisco/csrc/ursub/choose_username.class"
     GUID = "{72AF89A6-C672-11D2-8202-0060B0FC247E}"
 }}
 

The page information section defines standard information about the page including:

• The page name and title

• The Java class to execute

• The template file to use

• The pages that can be accessed from this page

• Help settings for the page

• Required input attributes

For each page in the application, there are two entries in the application specification file (.APP):

• The description of the page and its behavior

• The actual Java logic that corresponds to the user-visible page

In each page definition, indicated by page [name] { }, the .APP file contains:

• The user visible title

• The underlying Java logic to execute

• The HTML template to use

• Navigation information

• Required input values

For each page, the corresponding logic definition, indicated by logic [name] { }, defines the Java logic to execute when processing requests for the page. There are three values that must be specified for each logic:

<!-- HEADER START -->
 
<!-- Setup the header -->
<IMG SRC='/csrc/images/CiscoLogo.gif'>&nbsp
<B>User Registrar 1.0 </B>(Subscriber)
 
<!-- If appropriate, show the help button -->
<GX type=tile id=UseHelpButton max=1>
    <FORM Method=POST
    Action="/cgi-bin/gx.cgi/GUIDGX-<GX Type=cell Id=_GUID>(guid)</GX>">
    <INPUT Type=hidden Name='_goto' Value='urhelp'>
    <INPUT type=image src=/csrc/images/nbHelp.gif
    border=0 name=helpButton></FORM>
</GX>
 
<!-- If appropriate, show the exit help button -->
<GX type=tile id="ExitHelpButton" max=1>
    <FORM Method=POST
    Action="/cgi-bin/gx.cgi/GUIDGX-<GX Type=cell Id=_GUID>(guid)</GX>">
    <INPUT Type=hidden Name='_goto' Value='urhelp'>
    <INPUT type=image src=/csrc/images/nbExitHelp.gif
    border=0 name='Exit Help' value='Exit Help'></FORM>
</GX>
 
<!-- If appropriate, show the logout button -->
<GX type=tile id="LogoutButton" max=1>
    <FORM Method=POST
    Action="/cgi-bin/gx.cgi/GUIDGX-<GX Type=cell Id=_GUID>(guid)</GX>">
    <INPUT Type=hidden Name='_logout'
    Value="<GX Type=cell Id=_PageName>(pagename)</GX>">
    <INPUT Type=image Src=/csrc/images/nbLogout.gif
    Border=0 Name=logout_button></FORM>
</GX>
 
<!-- End the header section -->
<HR>
 
<!-- HEADER END -->
<!-- BODY START -->
 
<!-- Include the current page template file -->
<GX Type=Include Id=PageTemplate></GX>
 
<!-- BODY END -->
<!-- FOOTER START -->
 
<!-- Common application footer -->
<HR>
<FONT SIZE='-2'>Copyright (C) 1999 by Cisco Systems.</FONT>
 
<!-- FOOTER END -->
 

To support any language other than English, do the following:

• Duplicate all the User Registrar Subscriber pages.

• Translate them into the new language.

• Create a new subdirectory in the language directory.

• Copy all of translated template files into the new subdirectory.

The following example shows the html directory hierarchy for a server with multilanguage support:

<csrc-root>/html/csrc-ur-sub/en
<csrc-root>/html/csrc-ur-sub/fr
<csrc-root>/html/csrc-ur-sub/sp
 

Working in conjunction with extension configurers, it is possible to augment the schema with new attributes. After an extension has been properly configured to provide a new attribute, you must update the application schema to reflect this change. Additions to the application schema require a corresponding change to either an extension callout or an additional storage attribute.