Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
JSP elements
You use a JSP element to store a path to a JSP. When rendered within a presentation template or element design, a request to a JSP is generated and processed. A JSP element is stored in an authoring template, site, site area, content item or JSP component.
Notes:
Storing JSP pages
The JSP page must be stored within the was_profile_root/installedApps/node-name/wcm.ear/ilwwcm.war directory of your Web Content Management 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 Management 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 portal_server_root/installedApps/WCM_Local_ng_Portlet-name.ear/name.war
Syndication
Syndication will not move the JSP page referred to in a JSP element. Only the item containing the JSP element is moved. You will need to store the JSP page in the same folders of both the subscribing and syndicating servers.
Pre-rendering JSP elements
You cannot pre-render JSP elements.
Internal references
The JSP referenced within a JSP component must not include a reference, directly or indirectly, to the same JSP component. This includes references within Web Content Management tags or the API. If it does, a loop is created and your server will crash.
- Using a JSP element
When using a JSP element, you enter a path to a JSP file.