Supporting new markup languages
WebSphere Portal supports HTML markup language. You can define other markup languages to be supported, such as WML or cHTML. Before define another markup language to be supported, ensure that you have portlets that provide markup for that language. In addition, create a subdirectory for the markup in each of the locations listed in the following:
- For 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. Create the following directory location(s):
- Windows and UNIX:
- PROFILE_HOME/installedApps/cellname/wps.ear/wps.war/screens
- i5/OS:
- AppServer_root_usr/installedApps/cellname/wps.ear/wps.war/screens
- For 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.
Create the following directory location(s):
- Windows and UNIX:
- PROFILE_HOME/installedApps/cellname/wps.ear/wps.war/themes
- i5/OS:
- AppServer_root_usr/installedApps/cellname/wps.ear/wps.war/themes
For more information refer to the topic about Creating a new theme.
- For skins
- Create the following directory location(s):
- Windows and UNIX:
- PROFILE_HOME/installedApps/cellname/wps.ear/wps.war/skins
- i5/OS:
- AppServer_root_usr/installedApps/cellname/wps.ear/wps.war/skins
For more information about the resources in the skins directory refer to the Creating a new skin.
To add WML and cHTML as supported markup...
- Run the following command:
- UNIX: ./ConfigEngine.sh action-deploy-alternate-markups-and-clients -DPortalAdminPwd=password -DWasPassword=password
- i5/OS: ConfigEngine.sh action-deploy-alternate-markups-and-clients -DPortalAdminPwd=password -DWasPassword=password
- Windows: ConfigEngine.bat action-deploy-alternate-markups-and-clients -DPortalAdminPwd=password -DWasPassword=password
Observe the following hints:
- Use -DPortalAdminPwd=password -DWasPassword=password to specify the portal and WAS passwords.
- For complete information about how client resources are found in the directory structure refer to the topic about the Search order for portal resources. The JSPs in each of these locations must provide the markup that is required by the new markup language.
- Use the Manage Markups administration portlets to add the new markup to the portal site. Verify the markup name that you add is the same as the subdirectory name that you used for the markup. You can add a new markup using the Manage Markups administration portlets in the Portal settings-Supported Markups page.
Parent topic:
Customize the portal
Related concepts
Portal style classes
Work with portal navigation
Use JSTL tags in the portal JSPs
User and group management
Related tasks
Creating a new theme
Import a theme
Deploy the theme
Creating a new skin
Enable automatic JSP reloading
Supporting new clients
Changing banner text
Related reference
Use the color palette in themes
Performance guidelines for themes and skins
Related information
Changing the page help