Before you begin
files, you must set up an IBM
Connections deployment with the customization directory configured. For information about locating the customization directory, see Customizing the user interface
that is loaded for the main IBM
is loaded and cached statically.
Files in the customization directory are not updated when interim fixes are installed. If you add an override file and deploy an interim fix that also affects the file, you must copy that new change into your override file to maintain your customization.
files, complete the following steps.
used by IBM
Connections is located inside one of the web resources JAR files inside the provisioning directory (typically CONNECTIONS_HOME/data/shared/provision/webresources
), or inside the Common.ear
file that you want to override.
- Find com.ibm.lconn.core.web.resources_*.jar inside the deployed Common.ear file.
- Open the JAR file with a zip program.
- Extract the resources/SearchBar.js file to a location on your hard drive.
- Copy the source file to the customization directory or create an empty file in the correct location.
module. The name of a module is determined by its path and vice versa. You can convert the name of a module to a path by replacing all the periods in the module name with slashes.
- Using a text editor, open the SearchBar.js file from the example in step 1.
- Look for a line similar to the following one at the start of the file:
This line indicates that the name of the module is lconn.core.SearchBar.
Note: Ensure that you use the correct case in case-sensitive file systems.
- Make the required changes to the file.
customization directory on a production system. Instead, copy them in with an automated task. For example:
- Edit SearchBar.js to put an alert statement at the start of the file:
alert("This file has been customized.");
- Clear your browser's cache and refresh your IBM Connections web application.
The SearchBar.js file in the example is used by most of the applications, so when you refresh the page after clearing your browser cache, the alert added in the previous step should immediately pop up.
What to do next
customizations. For regular users who are not clearing their browser cache, your changes are only guaranteed to be active after you update the version stamp in LCC.xml
and restart each affected application, including Common.ear
. For more information, see Required post-customization step
Customizing the user interface
Required post-customization step