Sven Stueven commented on Jul 30, 2008

Simple Branding

For IBM Lotus Quickr Services for WebSphere Portal there is also an article at developerworks: http://www.ibm.com/developerworks/lotus/library/quickr-themes/

dirkb commented on May 5, 2008

Simple Branding

Hi,

Whenever I demo Quickr for Portal Services to a customer, one of the first things they ask is whether they can change the Quickr logo and put their company logo in the banner.

I'm sure this is a given to a lot of you, but here's how to do it:

(note: below example assumes that you used C:\IBM\Quickr as the default installation path and that the company's logo is called mylogo.gif)

1. Save the company logo under C:\IBM\Quickr\wp_profile\installedAppsnodename\wps.ear\wps.war\themes\html\QPG\colors\default\mylogo.gif

2. open the below files:

C:\IBM\Quickr\wp_profile\installedAppsnodename\wps.ear\wps.war\themes\html\QPG\default.jsp

C:\IBM\Quickr\wp_profile\installedAppsnodename\wps.ear\wps.war\themes\html\QPG\banner.jspf

C:\IBM\Quickr\wp_profile\installedAppsnodename\wps.ear\wps.war\themes\html\QPG\banner_toolbar.jspf

To have Quickr show your logo instead of the default one, you need to make changes in the banner_toolbar.jspf file. That file is referenced in the file above it i.e. banner.jspf, and that one in its turn is referenced in the default.jsp. So once you saved your changes in banner_toolbar.jspf, you also need to resave the other two files for your changes to take effect.

1. In banner_toolbar.jspf, locate the following section:

Lotus Quickr

and change toolbar_logo.gif to mylogo.gif. Save banner_toolbar.jspf, banner.jspf and default.jsp.

1. Make sure you enabled automatic JSP reloading for your changes to take effect. Otherwise you need to restart the Quickr server (for your convenience, I've added the teh procedure below).

Enjoy! 

Dirk

Note: Enabling automatic JSP reloading (from the Infocenter)

To view changes to your theme and skins JSPs without restarting the portal server, you can force the application server to automatically check for new versions of JSPs. While this is ideal for development and testing purposes, automatic JSP reloading should be disabled in a production environment because of performance issues.

Follow these steps to enable automatic JSP reloading:

   1. Open the file was_profile_root/config/cells/cell_name/applications/wps.ear/deployments/wps/wps.war/WEB-INF/ibm-web-ext.xmi

   2. Find the following entry in this file:

     

                xmlns:webappext="webappext.xmi" xmlns:webapplication="webapplication.xmi"

                xmlns:commonext="commonext.xmi" xmlns:common="common.xmi"

                xmi:id="IBM_WPS_Ext" reloadInterval="3" reloadingEnabled="false"

                fileServingEnabled="true" directoryBrowsingEnabled="false"

                serveServletsByClassnameEnabled="false" preCompileJSPs="false">

   3. Change the value for reloadingEnabled to true.

   4. Save the file.

   5. Restart the portal server.

After completing these steps, JSPs are automatically reloaded when they are changed. However, to view changes to a JSP that is included by another (parent) JSP, you must also change the parent JSP to indicate that it must be reloaded by the server.