You can change the appearance of the IBM Connections login page to meet your organization's needs. For example, you can replace the IBM logo that is displayed on the login page with your own company logo. Or you can include a link that enables users to have their user IDs or passwords sent to them through email.
To customize the login page, follow these steps:
Turn on the customization debugging capability. For more information, see Enabling and disabling customization debugging
2. 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 is the directory to which you installed IBM WebSphere® Application Server.
- profile_name is the profile to which you installed one of the IBM Connections applications.
- cell_name is the cell to which you installed the application.
- application_name.ear is the EAR file name for the application.
- application_name.war is the WAR file name for the application.
For a list of the web application source directories that are packaged with IBM Connections, see Application WAR files and OSGi bundles
file is the same for each application. You only need to make a copy of one instance of the file.
3. Paste the login.jsp
file into the appropriate subdirectory of the customizationDir
- To use the same login page for all of the applications, copy it into the common directory:
- To create a different login page per application, copy the file into the appropriate subdirectory for each application:
See Determining where to save your customizations
for more information about locating your base customization directory.
4. Edit the login.jsp file or files to contain the information you want.
Note: For information on how to replace the logo on the login page, refer to the steps covered in Changing the IBM Connections logo.
5. Save and close the login page.
6. To test your changes, log out of the product. Refresh the web browser, and then go to a login page.
7. Optional: If you enabled custom debugging, turn off the debugging capability when you are ready to publish your changes.
For more information, see Enabling and disabling customization debugging.
8. See Required post-customization step for details about how to apply your changes permanently.