CCM thumbnails not generated – ThumbnailServ E Exception:Unauthorized

When thumbnails for CCM files aren’t generated and the message below is logged in the SystemOut.log it probably means that the J2C authentication alias for docsAdmin doesn’t match the user mapped to the docsAdmin role of the IBMConversion app.

ThumbnailServ E   Exception:Unauthorized

For the FileViewer implementation goes ( IBMDocs 1.0.7 iFix3 ) that the J2C authentication aliases are widely used across the IBMDocs json config. files.

.\AppSrv01\config\cells\ACMECell01\IBMDocs-config\viewer-config.json
Near line 55
“j2cAlias”:”docsAdmin”,
And around line 366
“j2c_alias”: {
“ecm”: “filenetAdmin”
},

.\AppSrv01\config\cells\ACMECell01\IBMDocs-config\viewer-daemon-config.json
Line 4
“j2c_alias”: “docsAdmin”,

.\AppSrv01\config\cells\ACMECell01\IBMDocs-config\conversion-config.json
Around line 15
“j2c_alias” : “docsAdmin”,
“viewer_j2c_alias” : “viewerAdmin”,

Check her for the latest iFixes for IBMDocs 1.0.7. -> http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=Collaboration%2BSolutions&product=ibm/Lotus/IBM+Docs&release=1.0.7&platform=Windows&function=all

Wasn’t even aware yet but it seems they recently also released iFix 5.

DocsFix

 

 

 

 

 

 

 

Required fonts for IBM Docs/File Viewer 1.0.7

To meet the requirements for the sanity check of the Conversion server component of IBM Docs 1.0.7. you need to collect seven fonts and install them on each of the nodes on which you run the conversion service.

Installing means just copy and paste them under c:\windows\fonts.

This package includes all the seven fonts -> IBMDocs107fonts ( Around 10 MB in size ).

Also see this forum topic -> http://www-10.lotus.com/ldd/lcforum.nsf/d6091795dfaa5b1185256a7a0048a2d0/c9098ccd71178e0a85257e05005a2900?OpenDocument

http://connections5.acme.org/sanity/check?app=conversion&querytype=report

IBMFileViewerConversionSanityCheck

 

Connections Search index not updated anymore

When the search index of Connections isn’t updated anymore and you see no activity
in the logs of the index being ran it could be that the Search scheduled tasks are stuck in the past. You can use these steps without restarting any of the IBM Connections components.

In this example the Search tasks next start dates weren’t update anymore since November the 9th.
WrongSearchIndexStartOnDate

 

With the following wsadmin command from the searchAdmin.py library you can delete all scheduled tasks that are bound to the search application. Note, I didn’t have any customized search schedules, all were the default.

wsadmin>SearchService.deleteAllTasks()
1

Refresh the list.

wsadmin>SearchService.refreshTasks()

Show the list again and you will notice all the scheduled Search tasks are gone.

wsadmin>Scheduler.listAllTasks()

ScheduledTasksSearchEmpty

Now reset everything to default.
wsadmin>SearchService.resetAllTasks()
1
Refresh the list again
wsadmin>SearchService.refreshTasks()

Now showing the list again and you will see that the Search tasks have a next start
date that is in the future.

wsadmin>Scheduler.listAllTasks()

ScheduledTasksSearchRefreshCorrectStartDate

 

 

Run the IBM Connections Desktop Plug-in on Windows server

ICDesktopPlugin

 

When you have to work on a MS Terminal Server you will not be able to use
the IBM Connections Desktop Plug-ins for Microsoft Windows.

This as the administrator will not be able to install this plug-in on a server OS.
When you try to install it you will get a message saying that the operating system isn’t supported and that it will only run on systems like Windows 7 or Vista.

As the IBMConnectionsMSDesktop was created by making use of the MSI
packing system there are options to remove this OS check.

Please see this Blog post about how to do it.

http://sunmaiblog.wordpress.com/2010/11/04/change-launchcondition-of-an-msi-package/

The SuperOrca tool is a pretty good, and free, tool to get the job done.

http://www.pantaray.com/msi_super_orca.html

Here you download a prepackaged version of the IC Desktop Plug-in from 2014-10-07
which will install on Windows 2008 server.

IBMConnectionsMSDesktop MSI

Until now there were no issues running the IC Desktop plug-in on a MS Terminal Farm consisting of two nodes where this modified version was deployed.

Delete DB2 TaskCenter history entries in the journal

Only required from time to time but can really improve the stability of the DB2 Task Center especially if you have scheduled numerous tasks which run every day.

A lot of entries in the journal of the DB2 Task Center utility can be make it very unstable and let it crash on a regular basis with a JVM Out Of Memory error message.

You have the option to remove them manually but you can also purge them in one batch
with the following db2javit command.

db202:/opt/ibm/db2/V9.7/bin # ./db2javit -j:com.ibm.db2.tools.taskcenter.TCClearHistory -a:”DB202.INTRA.ACME.COM db2admin password Y 90″

For an explanation of the parameters please see the following IBM Technote.

http://www-01.ibm.com/support/docview.wss?uid=swg21208104

 

Hard reset for Community themes in IBM Connections

When there is the need to reset the themes for all IBM Connections Communities
to the default one you can use the following SQL commands.

Only setting the theme in the SNCOMM Communities database isn’t sufficient as
theme choices are also saved in some of the sub components of Connections.
This goes for Activities, Blogs, IdeationBlogs, Forums and Wikis.

Communities:

“UPDATE COMMUNITY SET COMMUNITY_THEME = ‘default’;”

Wikis:

“UPDATE LIBRARY SET THEME_NAME = ‘default’;”

Blogs:

“UPDATE WEBSITEASSOC SET ASSOCTHEME = ‘default’;”

Forums:

“UPDATE DF_MEMBERPROFILE SET THEMEID = ‘default’ WHERE THEMEID is not null”

Activities:

“UPDATE OA_MEMBERPROFILE  SET THEMEID = ‘default’ WHERE THEMEID is not null”

 

 

Restrict the creation of Communities

Certain customers don’t want everybody to go loose on their IBM Connections platform and let everybody freely create their own Communities.

Since IC 3.0.1 there is role which you can use to control who can create a Community.

http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Whats_new_in_this_release_ic301

You can find this role in the Communities application. By default the community-creator role is mapped to the  “Special subject” everyone. This mean every one who is logged can
create a Community.

To restrict it, map the community-creator role to the “Special subject” none and pick the users you want to give the rights to create a Community

community-creator role

community-creator role

 

 

 

 

 

 

In the UI users who don’t have the right to create a Community will miss the “Start a Community” button.