Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Lotus Domino > Collecting support data
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Integration with XPage Embedded Experiences

XPages can be leveraged as embedded experiences in Notes and iNotes. This article outlines the considerations one should make to enable this functionality.

Gadget data flow

OpenSocial Component functionality in Notes and iNotes relies on several different pieces of data, including proxy rules, OAuth consumer information, and gadget capability information. This article outlines how this data is used and how its use can be customized.

Collecting support data

In the event that verification of the OpenSocial Component fails an administrator will need to collect support data. This article outlines how an administrator can collect support data for Notes, iNotes, and Domino.

Verification

Once the OpenSocial Component is installed and configured, administrators need to verify that their environment is working properly. This article outlines how an administrator can do such verification.

Troubleshooting

In the event that verification of the OpenSocial Component fails an administrator may need to troubleshoot his or her environment. This article outlines how an administrator can do such troubleshooting.
Community articleCollecting support data
Added by ~Vera Umponetexings | Edited by ~Vera Umponetexings on April 10, 2013 | Version 13
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
In the event that verification of the OpenSocial Component fails an administrator will need to collect support data. This article outlines how an administrator can collect support data for Notes, iNotes, and Domino.
ShowTable of Contents
HideTable of Contents
  • 1 Overview
  • 2 Collecting Support Data in Notes
  • 3 Collecting Support Data in iNotes
  • 4 Collecting Support Data on Domino
    • 4.1 Workspace log locations
      • 4.1.1 OSGi on HTTP
      • 4.1.2 OSGi on DOTS
    • 4.2 Custom logging to enable
      • 4.2.1 Widgets in iNotes
      • 4.2.2 OpenSocial Gadgets and Embedded Experiences

Cookbook Contents


Overview


OpenSocial Component functionality spans many different components and may span across the client and server. Therefore any support data that is collected may also need to span the different components and the client and server. In order to understand what support data to collect, an administrator should refer to the gadget rendering process and the Deployment Architecture. Support data should be collected from all components that are involved in the rendering scenario that is seeing the issue. For instance, if an OpenSocial gadget that uses OAuth is failing to render in the Notes client, both the Notes client logs and the Domino Server with Shindig logs would need to be considered.

The Notes client logs will report information on where the OpenSocial gadget or Embedded Experience is rendering. The OpenSocial Component location will be "localhost" when rendering locally or the hostname of the Domino Server with Shindig when rendering remotely.
Setting the container URL to http://<OpenSocial Component Location>/fiesta/notesdomino/notesdominocommoncontainer.html

Collecting Support Data in Notes


Support data for the OpenSocial Component in Notes can be collected via the normal "Collect Support Data" mechanism, also referred to as IBM Support Assistant (ISA). Custom tracing should be enabled to ensure the most detailed information is available for troubleshooting. Logs for the OpenSocial Component in Notes will primarily appear in the workspace logs, i.e., <Notes Data Directory>/workspace/logs.

1. Run the ISA tool


2. Enable customized tracing


3. Select the "Embedded Experiences" tracing


4. Pause the collector


5. Press "Pause"


6. Reproduce the issue.
7. Go back to Help -> Support -> Collect Support Data
8. "Collect" and provide the ISA

Collecting Support Data in iNotes


The iNotes client provides a console, the contents of which can be viewed and copied from the browser. For more information, see Using the iNotes console log to inspect and copy debug informationexternal link Note: While the UI in the aforementioned article is the pre-9.0 UI, the instructions are still relevant in 9.0.

In 9.0, the iNotes console provides a build number for "WCAN" (as indicated below), which is the build component ID for the OpenSocial Component on the iNotes server. If the OpenSocial Component is not installed on the iNotes server, this version number will not appear.

Collecting Support Data on Domino


Collecting support data on Domino is not as straightforward as collecting Notes or iNotes client logs. Custom logging must be enabled by hand, as outlined below. One must also consider which components are involved in the area being diagnosed. This is done by keeping in mind the gadget rendering process and the Deployment Architecture.

Workspace log locations


The OpenSocial Component on the Domino server will primarily generate logs in the OSGi workspace (similar to Notes); however, with the introduction of DOTS there are two distinct workspace folders that should be checked for logs, one for the OSGi instance that runs as part of the HTTP task and one that runs as part of the DOTS task.

OSGi on HTTP


OSGi logs from the HTTP task can be found under <Domino Data Directory>/domino/workspace/logs

To enable custom logging for the OSGi instance for the HTTP task, one can modify <Domino Data Directory>/domino/workspace/.config/rcpinstall.properties. The HTTP task must be restarted after making these changes.

OSGi on DOTS


OSGi logs from the DOTS task can be found under <Domino Data Directory>/domino/workspace-dots/logs

To enable custom logging for the OSGi instance for the DOTS task, one can modify <Domino Data Directory>/domino/workspace-dots/.config/rcpinstall.properties. The DOTS task must be restarted after making these changes.

Custom logging to enable


Widgets in iNotes


This section includes logging that should be enabled for diagnosing problems with Widgets in iNotes, including OpenSocial widget trust management.

Enable custom logging on the iNotes Mail Server
OSGi on HTTP
com.ibm.domino.servlets.widgets.level=FINEST
com.ibm.notes.toolbox.level=FINEST
com.ibm.rcp.toolbox.level=FINEST
com.ibm.inotes.widgets.level=FINEST
com.ibm.domino.common.widgets.level=FINEST


OSGi on DOTS
com.ibm.domino.osgi.widgets.level=FINEST
com.ibm.notes.toolbox.level=FINEST
com.ibm.rcp.toolbox.level=FINEST
com.ibm.inotes.widgets.level=FINEST
com.ibm.domino.common.widgets.level=FINEST

OpenSocial Gadgets and Embedded Experiences


Note: This applies not only to OpenSocial gadgets and Embedded Experiences that are rendering in iNotes, but also those rendering remotely in the Notes client.

Enable custom logging on the Domino Server with Shindig
com.ibm.fiesta.inotes.level=FINEST
com.ibm.fiesta.commons.level=FINEST
com.ibm.rcp.fiesta.level=FINEST
com.ibm.rcp.toolbox.level=FINEST
com.ibm.mm.proxy.mapping.MappingImpl.level=FINEST
com.ibm.mm.proxy.rules.PolicyImpl.level=FINEST
com.ibm.mm.proxy.connection.filter.CookieFilter.level=FINEST
com.ibm.mashups.proxy.connection.HttpURLConnectionFilter.level=FINEST
org.apache.shindig.auth.level=FINEST
org.apache.shindig.gadgets.features.level=FINEST
org.apache.shindig.gadgets.render.level=FINEST
org.apache.shindig.gadgets.servlet.level=FINEST


Cookbook Contents


  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (13)Apr 10, 2013, 10:07:48 PM~Vera Umponetexings  Adding navigation
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility