Debugging Convergence - Activating Customizations for a Convergence Deployment

Implementing Convergence customizations involves three basic steps:

1. Enabling (or confirming) customization as a service
2. Making content configuration changes
3. Confirming the changes

This information takes you through the high-level steps to enable Convergence customization. Performing the actual content changes is left to other sources.

Topics:

Requirements Specific to These Steps

Use a Firebug-enabled Firefox browser for some of the diagnostic steps.

Part 1: Customization As a Service

1. Use the iwcadmin command to verify that Convergence customizations are not enabled (the default).

   # /opt/sun/comms/iwc/sbin/iwcadmin -w password -o client.enablecustomization
   client.enablecustomization = false
   

2. Log in with Convergence client and view the user landing page.
3. Verify the iwc.log and (optionally) Firebug console output.
   • iwc.log: Check for "Client customization service is disabled for the deployment:"
     

     PROTOCOL: WARN from com.sun.comms.client.protocol.delegate.agent.ClientOptionsAgent  Thread httpSSLWorkerThread-9000-0 at 11:21:16,948 - client preferences not found for domain: sfbay.sun.com
     .
     .
     .
     PROTOCOL: INFO from com.sun.comms.client.entity.user.sun.CommsUser  Thread httpSSLWorkerThread-9000-0 at 11:04:40,021 - Client customization service is disbaled for the deployment 
     

   • Firebug console: Check for no console entries about customization when it is off. Here is the console entry that would precede the customization service entry:

     Scroll bar dimensions:  Object w=13 h=13
     

     You should not see:

     Loading Service: Customization Object enabled=true displayName=Customization name=c11n
     

4. Enable Convergence customizations by changing the client.enablecustomization setting.

   # /opt/sun/comms/iwc/sbin/iwcadmin -w password -o client.enablecustomization -v true
   client.enablecustomization updated successfully
   

5. Verify that the iwc_admin.log shows the change:

   ADMIN: INFO from com.sun.comms.client.admin.mbeans.CommonMBean  Thread RMI TCP Connection(7900)-129.145.185.117 at 11:49:40,804 - Value of config parameter client.enablecustomization modified to true 
   

   You can also display the value by using the iwcadmin again.

Part 2: Content Changes

Performing actual content changes is not part of this information. See Convergence Customization Guide or Convergence Customization Quick Start Guide for more details on how to make actual customization changes. This information focuses on basic troubleshooting of customization problems.

Part 3: Restart Application Server and Confirm Changes

Customization changes do not take effect until you stop and start Application Server. If you log in to the Convergence client before restarting Application Server, the content remains the same.

Before You Begin
Optionally, you can log out from your Convergence session.

1. Stop Application Server, for example:

   # /opt/SUNWappserver/bin/asadmin stop-domain domain1
   

2. Start Application Server, for example:

   # /opt/SUNWappserver/bin/asadmin start-domain domain1
   

3. Log in to Convergence.
4. Verify that the iwc.log entry "Client customization service is disabled..." does not appear.
   The iwc.log entry previously noted should not appear. In the entry, look soon after "ClientOptionsAgent."
5. Verify that Firebug console contains the following:

   Scroll bar dimensions:  Object w=13 h=13
   Loading Service: Customization Object enabled=true displayName=Customization name=c11n
   

Possible Problems

If the Convergence customization service does not appear to be active after making the iwcadmin command change and restarting Application Server, the most likely cause of problems is that Application server did not fully stop. View the Application Server log for errors. For example, you can use the tail command on the log file referenced by the start script's output:

# tail -f /opt/sun/comms/SUNWappserver/domains/domain1/logs/server.log
.
.
.
[#|2009-01-20T11:55:00.264-0800|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]

If this entry does not appear, Application Server has not started properly. If Application Server is still responding to web requests, the content will be the old content, and not reflect the enabled customization service.