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.

 

 

 

 

 

 

Error removing intermediate unpacked files while installing IIM

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

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.

arcserve services

arcserve services

 

Note for deploying IC4 CR2 with Connections Mail

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

What’s New in IBM Connections Mail 1.0 Fix Pack 1

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.

<WAS_home>/profiles/<profile_name>/installedApps/<cell_name>/Homepage.ear/homepage.war/nav/templates

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.

http://yourserver/connections/resources/discovery/DiscoveryServlet?email=test-user-email

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

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 4.0.0.0 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.

 

Configure Windows NFS client with write permissions

Under Windows you can choose to install a NFS client to access NFS files
shares as available on Linux systems.

 

Install Windows NFS client

Install the NFS client on Windows 8.

With the default options you will only have read options to these NFS shares.

By changing the default anonymous Uid and Gid on your Windows desktop and
match these to the ones set on the Linux NFS shares you also get write
permissions for these shares.

These two values can be created and set in the registry under.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default

- Select “New DWORD (32-bit) Value”
- Change the Base setting to Decimal.
- Enter the UID found on the Linux directory as shared by the NFS system.

Reg Keys

Then restart you Windows client.

You can use the “Map network drive” function in the Explorer interface to map your
NFS share or use the mount command line tool.

You can use the same syntax as when mapping a Windows Samba file share.

With the mount command check if the values set for Uid and Gid options are
now being used.

mount command

Mount screenshot

permissions nfs shares

Permissions NFS share

 

 

 

 

 

Investigate and resolve error code CLFRT0066E

When you mention that the search results of one of the IC components
aren’t up to date anymore it could be that there is corrupt data
inside one of the components.

You will notice this when you try to search recent articles and they don’t
show up in the search results even if the “Search index was last updated”
status mentions that is was updated very recently ( /search component ).

You will find the CLFRT0066E error message if you try to retreive the
seedlist of the IC component that has no recent search results.

In the few cases I heard about the CLFRT0066E error it was caused
by corrupt data in the Blogs component. So I in this example i will go with Blogs as well.

https://server.connections.net/blogs/seedlist/myserver

<ErrorResponse version=”1.0″>
 <MessageCode>
    error.internal.backend
 </MessageCode>
 <MessageText>
     CLFRT0066E: A backend internal error occurred – Java Exception Message : java.lang.NullPointerException
 </MessageText>
</ErrorResponse>

The next challenge is to find the corrupt data in the Blogs database. When
searching inside the scope of the Blogs component you should roughly be
able to find out since when the search results weren’t updated anymore.

I didn’t try it but deciding to remove the index and start rebuilding it all
will not likely help to fix the issue as the corrupt data inside the component
will continue to cause the retrieval of the seedlist to fail.

If you have some good log rotation in place for WebSphere you should
also be able to pinpoint since when the indexing process for Blogs started
to fail from the SystemOut.log of the JVM where search is running on.

To find out the specific time when the corrupt data was occured
you can use the start and range seedlist arguments.

https://server.connections.net/blogs/seedlist/myserver?Start=????&Action=GetDocuments&Format=xml&SeedlistId=SeedlistId&Range=???

Just begin with start=0 and range=1000 then try to get as close to the point
when you receive the CLFRT0066E error. The content of the seedlist is
chronological starting with start=0 will probaby give you as the first result
the creation of the first Blog.

When you have a good idea around what time the corrupt data started to
occur you will have to try to find the corrupt data inside the Blogs database.

My best guess is that it is about a corrupt Blog, a Blog entry or a comment.

BLOGS.WEBSITE
BLOGS.WEBLOGENTRY
BLOGS.ROLLER_COMMENT

For Oracle you will have to use the to_timestamp function to search in the
columns with the type of timestamp.

select * from BLOGS.WEBSITE
where
LASTMODIFIED >= totimestamp(’14-05-2012 21:24:00′, ‘dd-mm-yyyy hh24:mi:ss’)
and
LASTMODIFIED <= to
timestamp
('14-05-2012 21:25:33', 'dd-mm-yyyy hh24:mi:ss')

//LASTMODIFIED or DBMODTIME just play around with both.

The next steps are bit depending on where you find the corrupt data and if
you are able to remove it in the Connections interface itself.
If you cannot do it anymore in the interface what will be very likely you will
have to try and clean it up in with SQL queries in the database itself.

Cleaning this up with SQL will require some db expertise as you will bump
into table relationships, foreigns keys etc.

After you got rid of the corrupt data and you no longer get the CLFRT0066E
error when retrieving the seedlist the next step is rebuilding the complete index.
( Not entirely sure about this step but I had to do it to fix the index of the Blogs component  ).

When running in a multi node setup you can use the startBackgroundIndex to recreate
the index without taking Connections offline.

Start the background indexing process for one of the nodes.

SearchService.startBackgroundIndex(“/opt/IBM/LotusConnections/backgroundIndex”, “activities, blogs, communities, dogear, files, forums, profiles, wikis”)

When this is finished stop the JVM which hosts the Search application on that node.
Rename the old index directory as specified in the SEARCHINDEXDIR
WebSphere environment variable and replace it with the new created directory and
start up the JVM again. Repeat this step for all your nodes.

As file content indexing is done per node and stuff like recommendations, content
in the Do-You-Know widget are all retreived from the search index it will take
some time before all this information is rebuild again.

Thanks to Sjaak Ursinus who pointed me in the right direction.

http://www-10.lotus.com/ldd/lcforum.nsf/DateAllFlatWeb/3830298936fefcfb852579c100496ddb?OpenDocument