Add support for new markup languages

By default, WebSphere Portal supports HTML markup language. You can add support for markup languages other than HTML, such as WML or cHTML. Adding support for new markup languages involves creating portlets that include resources that the markup languages require. You must also create subdirectories for the markup languages in the Web Archive (WAR) file for custom theme. After you create the portlets and subdirectories for the markup languages, run a task to add support for the markup languages. Then add the new markup languages through the Manage Markups portlet.

To add support for new markup languages, do the following:

1. Create resources to support new markup languages as appropriate.

   1. Locate the required resources.
      Find theme resources: See the Location of theme resources link below.

   2. Create subdirectories to contain resources specific to the new markup languages.
      Resources you might need to create to support new markup languages include the following:

      
      Screens

      Screens are JSPs that the portal server invokes to display various types of content. The Home screen is most often displayed because it is used for the portlet content area, another example is the Error screen. You can add new screens to the /screens directory in the WAR for custom theme.
      
      Images and style sheets
      Images, style sheets, and associated file types are often required to support new markup. You can add new images and style sheets to the /themes directory in the WAR for custom theme.
      
      Skins
      Skins are interchangeable front-ends for portlets. Skin control elements such as the minimize and maximize icons, the title bar, and the background color or pattern. You can add new skins to the /skins directory in the WAR for custom theme.

2. Open a command prompt.

3. Run the following command:
   UNIX™: ./ConfigEngine.sh action-deploy-alternate-markups-and-clients -DPortalAdminPwd=foo -DWasPassword=foo
   i: ConfigEngine.sh action-deploy-alternate-markups-and-clients -DPortalAdminPwd=foo -DWasPassword=foo
   Windows™: ConfigEngine.bat action-deploy-alternate-markups-and-clients -DPortalAdminPwd=foo -DWasPassword=foo

4. Log in to the portal as an administrator.

5. Select Administration -> Portal Settings -> Supported Markups.

6. Click Add new markup.

7. Specify the details for the new markup language in the appropriate fields and click OK.
   For more information:

   • See the portlet help topics for information about adding new markup languages.

   • For information about how the portal server searches for themes and skins, see the Search order for portal resources section in the following topic below: Aggregation.

Parent

Customize the portal
Portal style classes
Work with portal navigation
Use JSTL tags in the portal JSPs
Aggregation

Related tasks

Import a theme
Deploy the theme
Create a new skin
Enable automatic JSP reloading
Add support for new clients
Change banner text
Use the color palette in themes
Performance guidelines for themes and skins
Location of theme resources

Change the page help

 

+

Search Tips   |   Advanced Search