Supporting new clients

During the operation of the portal site, you could discover that some users have upgraded their browsers, and that the new browser has certain HTML requirements. Or, you could get a request to support a new mobile phone that has special WML requirements. In either case, you can add support for the client to the portal site. If the new client requires markup that is not supported by the portal site, then first create the new markup language.

To add a new client, first create the subdirectories containing the resources that are necessary to support the new client in each of the following locations:

/Qibm/ProdData/WebAS5/PME/installedApps/ hostname/wps.ear/wps.war/screens

Screens are JSPs that are invoked by the portal server for displaying various content. The Home screen is most often displayed because it is used for the portlet content area. Other screens include the Login or Error screen. See Screens for more information.

/Qibm/ProdData/WebAS5/PME/installedApps/ hostname/wps.ear/wps.war/themes

In addition to JSPs, the themes directory might need images, style sheets, or any other file types that are required of the new markup. See Create your own theme for more information.

/Qibm/ProdData/WebAS5/PME/installedApps/ hostname/wps.ear/wps.war/skins

See Create your own skin for information about the resources in the skins directory.

For example, to add a banner page with markup that is specific to Netscape 6 browsers, you can create a Banner.jsp for each theme in the following location: 


  wp_root/app/wps.ear/wps.war/themes/html/theme_name/ns6

See Search order for portal resources for complete information about how client resources are found in the directory structure.

Use the administration portlets to add the new client to the portal site. Make sure that the client name that you add is the same as the subdirectory name that you used for the client. You can add a new client using the Portal settings page. See Supported clients help for more information.

See also