Create a custom launch page

You can configure an authoring portlet to use a launch page of your own design instead of the default user interface.

A custom launch page can either be a JSP or HTML file. Use remote actions to call different views and functions from with the authoring portlet's user interface. You can also use the Web content API to add other functions to your launch page. Once you have created a custom launch page, you then configure your authoring portlet to use the custom launch page instead of the default authoring portlet user interface.

Storing JSP Files

JSP files can be located:

• within the PROFILE_HOME/installedApps/cellname/PA_WCM_Authoring_UI.ear/ilwwcm-authoring.war/jsp/html directory of your server where cellname is unique to your installation.

• within any other Web application running on portal. When referencing JSP files in another Web application, use the following path: contextPath;jspPath

  For example: /wps/customapplication;/jsp/editor.jsp

A custom "create and view content" launch page

This is a simple example of a table that you can add to a JSP or HTML file to allow users to create and view content items using remote actions.

<table>
<tr><td>
<a href="?wcmAuthoringAction=new&type=com.ibm.workplace.wcm.api.WCM_Content"> Create new Content</a>
</td></tr>
<tr><td>
<a href="?wcmAuthoringAction=openmainview&view=contentbytitle"> Open content by title</a>
</td></tr>
<tr><td>
<a href="?wcmAuthoringAction=openmainview&view=contentbysitearea"> Open content by site area</a>
</td></tr>
</table>

Reloading JSP files

JSP files referenced by Web Content Management are reloaded once every 10 seconds. If you update a JSP file, you may need to wait for it to be reloaded before your changes will be displayed.

Parent topic:

Extending Web Content Management

Related concepts

Custom authoring interfaces
Use remote actions

---