Two WebSphere variables are applicable to customizing IBM Connections. You can view these variables from the WebSphere Application Server Integrated Solutions Console.
Enabling customization debugging
Unless you enable the customization debugging capability, new versions of customized files are loaded only when the IBM Connections applications are restarted. After you enable the debugging capability, you can usually test your changes by clearing your browser cache. Because the debugging capability is resource intensive, enable the debugging capability only while customizing IBM Connections. Also, do not enable the debugging capability on a production server. The debugging variable is CONNECTIONS_CUSTOMIZATION_DEBUG.
Turn on customization debugging capability so that you can view your changes without having to restart the IBM Connections server.
- Open the WebSphere Application Server Integrated Solutions Console.
- Click Environment>WebSphere variables and set the scope to the node where IBM Connections is installed.
- Set the variable CONNECTIONS_CUSTOMIZATION_DEBUG to true. If the variable does not exist, create it at the node level.
Customization directory path
The directory path declared in the WebSphere environment variable called CONNECTIONS_CUSTOMIZATION_PATH identifies the base location of the customization directory used by IBM Connections. This variable is set during installation of IBM Connections. Files under this path are processed by IBM Connections to override the installed files. On Microsoft Windows, if you accepted the defaults during installation, the customization path is C:\Program Files\IBM\LotusConnections\data\shared\customization.
Parent topic: 1.0 Introduction to customizing IBM Connections