IBM Connections UI's
Please refer to the Youtube video below describing how to trust SSL certificates in the WebSphere Application Server Integrated Solutions Console (ISC).
How can I troubleshoot OnTime Group Calendar Socials ability to resolve network, following, communities etc.?
Starting with OnTime Group Calendar Social v. 4.4.0 the following debug capabilities are available to debug various aspects of the application.
Resolves the currently logged in user in WebSphere Identity Manager (WIM) showing the name, uid and e-mail address is available.
Shows the e-mail addresses of the people the currently logged in user is following.
Shows the e-mail addresses of the people the currently logged in user is in network with.
When supplied with a community UUID will resolve the members of the community and show the e-mail addresses of the members. The currently logged in user must have access to the community in IBM Connection.
Opens the Test Page as described in the manual. Require the admin-role.
Same as /ontime/common/api/currentuser but requires the admin-role.
Searches for the supplied e-mail address in WebSphere Identity Manager and shows the name, uid and e-mail address of the found user. Requires the admin-role.
Searches for the supplied uid in WebSphere Identity Manager and shows the name, uid and e-mail address of the found user. Requires the admin-role.
/ontime/common/admin/wim/resolvegroup/<DN of group>
Searches for the supplied group in WebSphere Identity Manager and shows the name, uid and e-mail address of the members. Requires the admin-role.
Shows the configuration for the modules. Requires the admin-role.
Shows the OnTime Group Calendar specific configuration. Requires the admin-role.
Attempts to load the specified URL using the specified authentication mechanism. Requires the admin-role.
The short answer is "Yes!". The longer answer is that starting with IBM Connections v. 5.5 there is a new attribute which is required when configuring custom widgets such as OnTime Group Calendar - Social. The attribute needs to be added to the widgets-config.xml file and the declarations for the OnTime Group Calendar - Social widgets listed there. The attribute is called "themes" and describes the various locations that are valid for the widget meaning left column, middle column, right column and banner (new with v. 5.5).
This is mainly an issue when upgrading a previous installation as the OnTime documentation has been updated to address this.
To fix an existing installation do as follows:
- Using wsadmin checkout the widget-config.xml file
- Locate each of the OnTime Group Calendar - Social widget declarations and add the "themes" attribute as applicable for each widget:
- Profiles: themes="wpthemeThin wpthemeNarrow wpthemeBanner wpthemeWide"
- Who Is Available: themes="wpthemeThin wpthemeNarrow wpthemeBanner wpThemeWide"
- Group Calendar: themes="wpthemeBanner wpthemeWide"
- Save and close the file and check the configuration back in
- Restart your WebSphere Application Server(s)
The various "themes" actually map to locations the widget may be dropped by the user as shown below (click the image for a large version):
For more information about the "themes" attribute see the IBM technote at http://www-01.ibm.com/support/docview.wss?uid=swg21974593
There are two ways to locate the build / version number. The build version can be seen in the WebSphere ISC as follows:
- Open WebSphere Application Server Integrated Solutions Console (ISC)
- From the lefthand menu expand "Applications/Application Types" and select ”WebSphere Enterprise Applications"
- In the list click on the OnTime Group Calendar application to look into (e.g. "OnTime Group Calendar - Social - Profiles")
- Click "Display module build Ids" in the uppe right corner on the available options and note the "Build id" in the right hand column
Another way - which some find easier - is using a browser to inspect the version.json in each application e.g. <hostname>/ontime/<application>/version.json. E.g. the following links show the application versions deployed to our demo environment:
The above links shows the version output in JSON format.