Extending JSP files with custom tags
We can extend IBM Connections by adding our own custom JSTL tags to meet the company's needs.
- Turn on the customization debugging capability. See Enable and disable customization debugging.
- Copy the .jsp file from the WAR file of one of the applications that you would like to customize. We can access the file from the following directory:
WAS_HOME/profiles/profile_name/installedApps/cell_name/ application_name.ear/application_name.war/nav/templates
where:
- WAS_HOME is the directory where IBM WebSphere Application Server is installed.
- profile_name is the profile where you installed IBM Connections.
- cell_name is the cell where you installed the application.
- application_name.ear is the name of the application EAR file. To customize interface styles that are common to all applications, use the Common.ear file.
- application_name.war is the name of the application WAR file.
For a list of the web application source directories that are packaged with Connections, see Application WAR files and OSGi bundles.
- version is the version number of the Connections release plus the date and build number of the JAR file.
- Paste the .jsp file into the appropriate subdirectory in the customization directory.
See Determining where to save the customizations for more information about locating the base customization directory.
- Copy the content of the .tag file containing the custom tags to add, then open the .jsp file and paste the content where it needs to be rendered.
- Save and close the .jsp file.
- To test the changes, refresh the web browser, and then access the page from the product.
- If we enabled custom debugging, turn off the debugging capability when we are ready to publish your changes. See Enable customization debugging.
- See Required post-customization step for information about how to apply the changes permanently.
Parent topic:
Customize the user interface
Related:
Enable live user interface customization editing mode
Determine where to save the customizations
Required post-customization step
Application WAR files and OSGi bundles