You can modify the content of an existing page or create new pages to link to your custom web application. Typically, a web page has a simple JSP that specifies the template to use and another JSP to use as the content element. For example, the following code specifies that the content element uses the JSP code in <context root>\iportal\activePortal\private\newrequest\newrequestpage.jsp:

The content JSP contains the code that creates the page-specific content and functionality. This JSP contains code that places page-specific text, graphics, links, and other functionality on the page. You can use HTML code, JSP code, JSP built‑in tags, Jakarta Struts tags, Actuate servlets, Actuate custom tags, Actuate JavaBeans, CSS, and JavaScript methods to obtain data and present information on the page. For information about how to use these features, see Customizing a Java Components web application.

The default Actuate Java Components pages use HTML tables to provide formatting for each page. The tables are often nested. Individual files include other files that define elements, such as the <TABLE> declaration. As you modify the pages to suit your needs, verify that the Actuate Java Components pages for tasks, such as logging in, listing folders and files, and viewing and requesting reports appear correctly in your web browser.

When using relative hyperlinks in your HTML code, ensure that any files to which you refer are available to Actuate Java Components. Java Components resolves relative hyperlinks from the context root. For example, in the standard Java Components installation, the following code refers to an images directory at the same level as the Java Components context root directory:

All Actuate Java Components requests require action paths to have certain names. Similarly, the action paths require JSP files to have certain names and to reside in a particular directory under the context root. Do not rename the default files provided with Java Components without making the corresponding change to struts‑config.xml. If you do not change the file name consistently in all places, Java Components cannot locate your custom files.

To activate the changes you make in the Java Components configuration files, content pages, or by creating a new context root, you must restart the web server that runs Java Components.