Adding a JSP element to a template

You add a JSP element to an authoring template when you want the JSP element to be used by a set of items that use the same authoring template.

1. Open or create an authoring template.
2. Click Manage Elements .
3. Select JSP as the element type.
4. Enter a name. Do not use double-byte and non-ASCII characters.
5. Enter a display title to use as the title of the element displayed indexes and forms.
6. If you have created a text provider plug-in for a multi-locale site, you can also select the text provider and enter a key to look up a string from the selected text provider. The text provider displays a different display title for each language it has been configured for. The text entered in the Display Title field is only used if an appropriate display title is not available from the selected text provider, or if the text provider is not available.
7. Click OK. The JSP element is added to your form.
8. Go to the Default Content tab.
9. Go to the JSP element you added. Either specify the path to the JSP file, or do nothing if you want your content creators to enter this information.
   1. Enter the path to a JSP file if required, or leave blank if you want your content creators to specify the JSP. The path must begin with a forward slash.

      For example:

      /path/jspfilename.jsp

      Storing JSP Files:

      JSP files can be located:

      • within the was_profile_root/installedApps/node-name/wcm.ear/ilwwcm.war directory of your server.

        The JSP page is also stored in the client war directory of the local rendering portlet or of the servlet or portlet that calls the JSP, if using the Web Content Manager API. For example, to render a JSP page on a local rendering portlet, you would also need to store a copy of the JSP file under was_profile_root/installedApps/node-name/PA_WCMLocalRendering.ear/ilwwcm-localrende.war

      • 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

   2. Enter an error message to display when an incorrect JSP path is entered. A Java exception stack trace is displayed if there is syntax error.
10. Click to open the display properties of the element. This is where you define how the element is displayed on the item form.
    1. To display the element as a required field select Identify this as a required field.
    2. To hide a field on the content form from all users select Hide field. You must specify a default value if the field is a required field.
       Note: Administrators and managers can choose to display hidden fields and elements in an item by clicking Show hidden fields.
    3. Select the users or groups you want to grant edit access to a field or element by clicking Add Editors.
    4. Select the users or groups you want to grant view access to a field or element by clicking Add Viewers.
    5. Type field-specific help into Field help text. This displays with the element in the content form.

       If you have created a text provider plug-in for a multi-locale site, you can also select the text provider and enter a key to look up a string from the selected text provider. The text provider displays a different help text for each language it has been configured for. The text entered in the Field help field is only used if an appropriate help text is not available from the selected text provider, or if the text provider is not available.

11. Save the authoring template.