26 Integrating JavaServer Pages with Content Server

This chapter describes how to integrate Oracle WebCenter Content Server with JavaServer Pages (JSP).

This chapter includes the following sections:

26.1 About JSP Integration

You can access the Content Server core functionality from JavaServer Pages (JSP) to deliver forms and custom pages through the JSP page execution functionality using the built-in Apache Jakarta Tomcat Server.


The Content Server JSP functionality should not be enabled when you are using Site Studio for External Applications (SSXA) in conjunction with Content Server. Enabling the Content Server JSP functionality would cause parsing errors in SSXA templates.

26.1.1 JSP Execution

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 JavaServer Pages that is run inside of Content Server when the feature is enabled. The integration of Tomcat Server with WebCenter Content provides the benefit of increased performance for content delivery.

Using JSP Execution functionality enables developers to access and modify Content Server content, ResultSets, personalization and security definitions, and predefined variables and configuration settings through JavaServer 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 Content Server.


JSP pages can execute Idoc Script functions only when the JSP page is being served on Oracle WebCenter 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 in a JSP page to Oracle WebCenter Content Server provides revision control but does not provide dynamic execution of Idoc Script functions on the presentation tier (JSP server).

26.1.2 Tomcat

The capability for JSP to call services is provided by integrating the Tomcat 5.025 server with the Content Server core functionality.

  • Tomcat is a free, open-source server of Java Server and JavaServer 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 the use of all Oracle WebCenter 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.


    This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

26.1.3 Features

With JSP support enabled, custom components can include JSP pages of type jsp and jspx.

  • The DomainHome/ucm/cs/weblayout/jsp directory is able to host JSP pages by default.

  • The Oracle WebCenter Content distribution media also includes the current Java EE SDK.

26.2 Configuring JSP Support

Use the following procedure to enable and configure JSP support.

  1. 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.

    1. Display the User Admin screen.

    2. From the Security menu, choose Permissions by Group.

    3. Click Add Group.

    4. Enter jsp as the group name, enter a description, and then click OK.

    5. Assign Admin permission to the admin role and any developer roles.

    6. Assign Read permission to all non-admin roles.

    7. Click Close.

  2. 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. For the internal JSP engine to run on any of these operating systems, a 1.5 JDK must be present on the server, and the CLASSPATH value 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.

  3. Click one of the following options:

    • On the Admin Server page, click General Configuration.

    • From the System Properties utility, click the Server tab.

  4. Enable the JSP prompt:

    • For the Admin Server: click Enable Java Server Page (JSP)

    • For System Properties: click Execute Java Server Page (JSP)

  5. Enter the security groups to be enabled for JSP (including the security group you created in Step 1).

  6. Save the settings, and restart Content Server.

26.3 Loading Example Pages

Use either of the following procedures to load example pages into 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.