Modifying existing content or creating new content

Creating a custom Information Console web application : Customizing an Information Console web application : Modifying existing content or creating new content

Modifying existing content or creating new content

You can modify the content of an existing page or create new pages for linking in to your custom web application. Typically, a web page has one JSP that implements a template and another JSP to implements the content to display according to the template’s structure. For example, the following code specifies that the template’s content element on a web page uses the JSP code in <context root>\iportal\activePortal\private\newrequest\newrequestpage.jsp:

<template:put name="content" content="/iportal/activePortal/private/newrequest/newrequestpage.jsp" />

The content JSP contains the code that creates the page-specific content and functionality. The newrequestpag.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 an Information Console web application.

The default Actuate Information Console 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 Information Console 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 Information Console. Information Console resolves relative hyperlinks from the context root. For example, in the standard Information Console installation, the following code refers to an images directory at the same level as the Information Console context root directory:

<A HREF="../images/myimage.gif">

All Actuate Information Console 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 Information Console without making the corresponding change to struts-config.xml. If you do not change the file name consistently in all places, Information Console cannot locate your custom files.