Customize the login page in HCL
Connections™ to have the appropriate style and
content for your organization.
About this task
You can change the appearance of the Connections login page to meet your
organization's needs. For example, you might want to replace the HCL logo that is displayed on
the login page with your own company logo. Or you might want to include a link that enables users to
have their user IDs or passwords sent to them through email.
Procedure
- Optional: Turn on the customization debugging
capability. For more information, see Enabling live user interface customization editing mode.
- Copy the login.jsp file from the WAR
file of one of the applications. You 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 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.
- version is the version number of the Connections release plus the date and build
number of the JAR file.
The login.jsp file is the same for
each application. You only need to make a copy of one instance of
the file.
- Paste the login.jsp file into the
appropriate subdirectory of the customizationDir directory.
- Edit the login.jsp file or files to
contain the information you want.
- Save and close the login page.
- To test your changes, log out of the product. Refresh the
web browser, and then go to a login page.
- Optional:
Connections allows you to restrict the allowed domains that the login page redirect
url
parameter will permit as destinations (by allowing you to whitelist those
domains). See Customizing the
login page redirect parameter for details.
- Optional: If you enabled custom debugging,
turn off the debugging capability when you are ready to publish your
changes. For more information, see Enabling live user interface customization editing mode.
-
See Post-customization step for details about how to apply your changes
permanently.