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
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.
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.
Refresh the list.
Show the list again and you will notice all the scheduled Search tasks are gone.
Now reset everything to default.
Refresh the list again
Now showing the list again and you will see that the Search tasks have a next start
date that is in the future.
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.
The SuperOrca tool is a pretty good, and free, tool to get the job done.
Here you download a prepackaged version of the IC Desktop Plug-in from 2014-10-07
which will install on Windows 2008 server.
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.
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.
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.
“UPDATE COMMUNITY SET COMMUNITY_THEME = ‘default';”
“UPDATE LIBRARY SET THEME_NAME = ‘default';”
“UPDATE WEBSITEASSOC SET ASSOCTHEME = ‘default';”
“UPDATE DF_MEMBERPROFILE SET THEMEID = ‘default’ WHERE THEMEID is not null”
“UPDATE OA_MEMBERPROFILE SET THEMEID = ‘default’ WHERE THEMEID is not null”
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.
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
In the UI users who don’t have the right to create a Community will miss the “Start a Community” button.
Why? Because I’m an system administrator and I know what I’m doing on a server operating system.
To disable UAC on Windows 2008.
Start + R -> msconfig -> Tools
Launch the “Change UAC Settings” option.
Move the silder to “Never notify” click OK and reboot the server.
If you want to completely disable IPv6 on Windows 2008 you can use the following command.
reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 32 /f
Reboot the server and the instead of this
you should see this.
While installing IBM WebSphere Portal Express 8 on a Windows 2008 R2 server I encountered an error when I wanted to deploy the IBM Installation Manager.
Everything seemed to run smoothly but at the end the installer failed and gave me the following error.
“Error removing intermediate unpacked files at D:\IBM\Installation Manager………”
IIM installation log
First I tried a newer version of the IIM. The one packaged with WP 8 Express is 1.5.2 but
I encountered the same issue with the 1.7.0 version. I also noticed that the installation folder remained completely empty after the installation failed. Only the directory IBM and the directory InstallationManager were created.
Later on I found out that on the server ARCserve backup services were running. These services conflicted with the the installation of IIM. After stopping these services I was able to successfully complete the installation of the IBM Installation Manager.
When deploying CR2 for IBM Connections 4 and you also make use
of IBM Connections Mail plug-in take notice of the first two points in the
Update strategy document from IBM for this CR release.
When you want to use Connections Mail in combination with IC4 CR2
you need to use Connections Mail fp1.
IBM Connections Mail 1.0 FP1
And in case you made any customizations to the header.jsp for example
when adding the “Give thanks” link to navigation menu for the Kudos
add-in from ISW you need to redo these customization on a header.jsp
from the CR2 deployment.
After deploying CR2 you can find a plain header.jsp here.
Make the required edits to this file and place it in the correct path in the customization
directory of IBM Connections.
When you forget to take this last step you will notice that the mails icons itself are loaded
and that the test URL gives you a valid response response but nothing happens when
you hover over the mail or the calendar icons.
1. IBM Connections 4.0 CR2 deployment using Connections Mail need to have Connections Mail 1.0 FP1 installed. Pre-FP1 Connections Mail will not load with IBM Connections 184.108.40.206 CR2.
2. IBM Connections 4.0 CR2 deployment using Connections Mail installations that have a customized header.jsp MUST migrate the changes made in the JSP file to the new version of the header.jsp file included with CR2.