Urs-o-Log

IBM Connections 4.5 Metrics: Changing user profile attributes for report dimensions

By default IBM Connections Metrics reports can be displayed in three different dimensions: Geography, Department and Role. If you want to change this to other profile fields you can do that as described in this link:

http://ibm.co/1dnNgug

However you need to do some additional steps in order to populate the database with the new values and also to get rid of the old values in the report. Here are the steps I have done:

Change the definition as described in the link above, e.g. I changed two dimensions to use custom extension attributes “xxxcountry” and “xxxdepartment” which I defined in Profiles. So I changed the following lines in the metrics-config.xml:
[codesyntax lang=”xml”]

<userAttributesMappings>
<!-- <mapping metricsName="attribute1" profilesName="com.ibm.snx_profiles.base.countryCode"/> -->
<mapping metricsName="attribute1" profilesName="com.ibm.snx_profiles.ext.xxxcountry"/>
<!-- <mapping metricsName="attribute2" profilesName="com.ibm.snx_profiles.base.orgId"/> -->
<mapping metricsName="attribute2" profilesName="com.ibm.snx_profiles.ext.xxxdepartment"/>
<mapping metricsName="attribute3" profilesName="com.ibm.snx_profiles.base.title"/>
</userAttributesMappings>

</userAttributesMappings>

[/codesyntax]

Make a full synchronisation of your Connections nodes and restart the metrics application.
On the Deployment Manager, run the following wsadmin commands in order to update the data in the metrics database:wsadmin>execfile(“metricsAdmin.py”)
wsadmin>MetricsUsersService.reloadUsersAttributes()
Check the database table METRICS.F_TRX_USERS if the data for the attributes is correct. If this is not the case do the following commands:a. clear the METRICS.F_TRX_USERS.UPDATE_TS column for all users
b. run http://<server>/metrics/service/PopUserMetadata.jsp to sync the user’s data
c. check the data in f_trx_users table again
Go to your “CognosConfig” directory (the one you used to install Cognos) and run the command “cognos-configure-update.bat”
Go to the directory where you have installed Cognos Transformer (e.g. “D:\IBM\CognosTF”) ” and rebuild the cubes by running “<Cognos Transformer>\metricsmodel\build-all.bat”. This can take a long time depending on you amount of metrics data!

After doing these steps the new data was successfully displayed for the three dimensions.

IBM Connections 4.5 CR3 has been published

More information can be found here:

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

Step-by-Step directions for applying CR2 or CR3 for Connections 4.5 with Connections Content Manager:

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

Updating the IBM Connections 4.5 databases to the required schema versions for Cumulative Refresh 3 (CR3):

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

New functions included in IBM Connections 4.5 CR3:

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

IBM Connections 4.5: Blog comments not displayed in IE after migration from 4.0

After migrating IBM Connections 4.0 to 4.5 it can happen, that Blog and Ideation Blog comments for migrated Blogs are not displayed in Internet Explorer.

You will just see the small turning wheel but nothing more happens. By tracing with Fiddler you will se that only requests for the first two blogs will be made and you will also see a Javascript error message in the browser.

There is a fix available (an updated “Comments.js” file which needs to be placed to “<CUSTOMIZATION_DIRECTORY>/javascript/lconn/blogs/comment” for IBM Connections 4.5 CR2 which can be obtained via IBM Support.

And the fix is also included in IBM Connections 4.5 CR3 which will be published soon.

MobaXterm – The complete toolbox for remote computing

Did I ever told you about MobaXterm? A tool I never want to miss again while working with different remote computers. It includes SSH, Telnet, RDP, FTP, SFTP, VNC, XSERVER and more protocols. It has a Cygwin like Unix shell and is expandable via plugins (e.g. with OpenSSL, Perl, Python etc.).

And it is just one executable file which you can easily copy to every machine where you need it.

Just a great tool!

Probleme mit T-Mobile-Multi-SIM-Karte

Für alle, die eine Multi-SIM-Card von T-Mobile haben (also zwei SIM-Karten die auf die gleiche Rufnummer hören) und damit sowohl ihr iPhone als auch ihr iPad betreiben: Ich hatte heute das Problem, dass alle Anrufe auf meinem iPhone nach einem Mal Klingeln gleich auf die Mailbox weitergeleitet wurden.

Nachdem die kompetente T-Mobile-Hotline mir erklärt hat, dass das auch nicht gehen kann und immer nur ein Gerät gleichzeitig eingebucht sein darf (also entweder iPhone oder iPad … das ging allerdings hier schon 3 Jahre problemlos… erst seit heute ging es nicht mehr) habe ich also selbst etwas herumprobiert.

Die Lösung ist: Sobald das iPad auf “Bitte nicht stören” steht, tritt der oben beschriebene Effekt ein. Wenn “Bitte nicht stören” im iPad deaktiviert ist, funktioniert es wieder einwandfrei so wie es sein sollte (also die Anrufe kommen auf dem iPhone an, das iPad kann gleichzeitig ins Internet).

Eine wirkliche Erklärung habe ich dafür nicht und ich kann auch nicht sagen ob es nun an Apple oder an T-Mobile liegt, aber eine entsprechende kompetente Auskunft hätte ich mir halt von der Hotline gewünscht.

IBM Connections: Request to IBM HTTP Server fails with Response code 400

After migrating to IBM Connections 4.5 with SPNEGO-SSO some users were unable to connect to the Connections system. The browser showed an Error 400 message and the users were not logged in to Connections. In the Websphere log files several LTPA errors occured.

The root cause for that issue was that the size of the SSO header in the HTTP request for these users exceeded the maximum allowed value. The default value for IBM HTTP server is 8192 bytes, a SPNEGO SSO header can reach values of up to 12k.

After adding the variable

LimitRequestFieldSize 16384

to the HTTPD.CONF the issue was resolved.

IBM Connections 4.5: Search Index does not finish

We currently had the problem that the creation of the search index of IBM Connections 4.5 never came to an end. In the log file you saw the following error messages:

[codesyntax lang=”text”]

CLFRW0957W: The seedlist url https://server.acme.com/activities/seedlist/myserver?Action=GetDocuments&Range=100&Start=1&Source=com.ibm.ilel.seedlist.retriever.connections.activities.ActivitiesRetrieverFactory&Format=xml&Locale=en_US&State=MTM0NjkyMjc3NTI3MDsxMTA0NTM0MDAwMDAwOzEzODMwNDE3NjAzODY7ZmFsc2U7MDswOzA7dHJ1ZTs%3D&useLocalFS=true has been requested more than twice in the same crawl.The application will now attempt to delete the seedlist pages persisted during this crawl activities. If this warning repeats on successive crawling or indexing jobs, there is a problem with the seedlist for the activities application. In this scenario, please contact IBM support. 
CLFRW0303E: Search has encountered a problem while crawling activities. The final seedlist page could not be reached. The crawl of activities could not be completed successfully.
CLFRW0283E: Search has encountered a problem while crawling.
CLFRW0294I: Search has finished crawling the activities component.
CLFRW0962E: Some of the entries for activities were not indexed successfully.

CLFRW0957W: The seedlist url https://server.acme.com/activities/seedlist/myserver?Action=GetDocuments&Range=100&Start=1&Source=com.ibm.ilel.seedlist.retriever.connections.activities.ActivitiesRetrieverFactory&Format=xml&Locale=en_US&State=MTM0NjkyMjc3NTI3MDsxMTA0NTM0MDAwMDAwOzEzODMwNDE3NjAzODY7ZmFsc2U7MDswOzA7dHJ1ZTs%3D&useLocalFS=true has been requested more than twice in the same crawl.The application will now attempt to delete the seedlist pages persisted during this crawl activities. If this warning repeats on successive crawling or indexing jobs, there is a problem with the seedlist for the activities application. In this scenario, please contact IBM support.

CLFRW0303E: Search has encountered a problem while crawling activities. The final seedlist page could not be reached. The crawl of activities could not be completed successfully.

CLFRW0283E: Search has encountered a problem while crawling.

CLFRW0294I: Search has finished crawling the activities component.

CLFRW0962E: Some of the entries for activities were not indexed successfully.

[/codesyntax]

Because of these problems activites started to index again and again and the search index was never built correctly.

We solved the issue by changing the following line in “search-config.xml”:

OLD:

NEW:

After restarting the cluster running the search application the index was able to finish indexing activities and the search index completed successfully. You might need to recreate your search index after you made the change (however it worked here without doing that).

I have made my decision in regard to a Google Reader (R.I.P.) replacement:Backend (hosted at my provider): Fever…

Gepostet von Michael Urspringer am Donnerstag, 15. August 2013