Through a separate product, Content Integration Suite. For more information, see "Java 2 Enterprise Edition Integration (J2EE)".
This section covers the following topics:
The JSP Execution functionality uses the built-in Apache Jakarta Tomcat Servlet/JSP Server to access the content and content management functions within Content Server.
The Apache Jakarta Tomcat Server is a free, open-source server of Java Servlet and Java Server Pages that is run inside of Content Server when the feature is enabled. The integration of Tomcat Server with Content Server provides the benefit of increased performance for content delivery.
Using JSP Execution functionality enables developers to access and modify Content Server content, ResultsSets, personalization and security definitions, and predefined variables and configuration settings through Java Server Pages rather than through standard component architecture. Services and Idoc Script functions can also be executed from JSP pages which reside as executable content in the Content Server.
Important:JSP pages can execute Idoc Script functions only when the JSP page is being served on the Content Server as part of the JSP Execution functionality. JSP pages served on a separate JSP server do not have this functionality. In those cases, checking a JSP page into the Content Server provides revision control but does not provide dynamic execution of IdocScript functions on the presentation tier (JSP server).
Capability for JSP to call services is provided by integrating the Tomcat 5.025 server with Content Server core functionality.
Tomcat is a free, open-source server of Java Server and Java Server Pages; version 5.025 complies with Servlet 2.4 and JSP 2.0 specifications.
The main benefit of integrating Tomcat into Content Server is the increase in performance of delivering content. The direct integration eliminates the need for a socket-based interface and enables use of all Content Server core capabilities.
Although Tomcat is embedded in content server, you can use server.xml as the configuration file to modify the internal Tomcat engine to suit your needs.
Note:This product includes software developed by the Apache Software Foundation (
With JSP support enabled, custom components can include JSP pages of type
The DomainHome/ucm/cs/weblayout/jsp/ directory is able to host JSP pages by default.
The Content Server distribution media also includes the current Java 2 SDK.
Use the following procedure to enable and configure JSP support.
In Content Server, create a new security group to be used for JSP pages (called
jsp in the subsequent steps). This security group should be restricted to developers. This step is not required but it is recommended for developer convenience. Any security groups to be enabled for JSP must be specified in step 5.
Display the User Admin screen.
Select Security, Permissions by Group.
Click Add Group.
jsp as the group name, enter a description, and click OK.
Assign Admin permission to the admin role and any developer roles.
Assign Read permission to all non-admin roles.
If you run on AIX, HP-UX, or Linux s390, the Java 2 SDK, which is required for the JSP integration, is not installed on your system automatically, nor is it provided on the distribution media. To get the internal JSP engine to run on these, a 1.5 JDK must be present on the server and the CLASSPATH in the intradoc.cfg file must be modified to include the path to the "tools.jar" file. For example, for a default 1.5 install on AIX, this file should be in /usr/java15/lib.
Select one of the following:
From the Admin Server, select the General Configuration page.
From the System Properties utility, select the Server tab.
Enable the JSP prompt:
For the Admin Server: click Enable Java Server Page (JSP)
For System Properties: click Execute Java Server Page (JSP)
Save the settings, and restart the Content Server.
Use either of the following procedures to load example pages into the Content Server:
Check in the .war file in the JSP security group. Make sure to check in other content to the JSP security group before checking in the war file.
Start the JSP Server Web App Admin from the Administration page.