IBM Connections – How to change Personal Notification Preferences for all Users

You may find yourself in a situation where you need to change the personal IBM Connections E-Mail Notification Settings for all Users. IBM Connections Users have the following options to choose from:

17_49_39-Email Notifications

There is a set of Default Settings which is applied to every user, as soon as the TDI-Sync runs, and the user is created in a database. So, the first thing to do, is to change these default settings. The official documentation does a pretty good job explaining the possibilities you have here, like Locking the User Notification Preferences, and the steps needed to apply the changes, so I won´t go in greater detail on those here. It is important to keep in mind, except if you are not “locking” the preferences, the preferences on Email notifications will only be set automatically for users which are created in Connections, as a result of the TDI Assembly Line, after you make those changes. In order to test the modifications made, you could use the “Restore Defaults” option on the Notification Preferences page.

But changing the default settings will not have any impact on the existing users, to change the notification options for them, you need to take a different approach.

I wanted to change the notification settings for all Users to “No Email”, but still make sure that the users can change those settings if they wish to, so simply locking those settings was not an option. I tried locking the Notification settings for all users to “No Email”, but after removing the lock, the setting would just be reverted to the setting done earlier. It turns out that there is no other possibility than to change the records in the database directly. A word of warning, you should contact the IBM Support before proceeding, because changing the records in the Connections Databases directly is not supported, I also recommend a database backup. 🙂

I am using for IBM Data Studio Software, but any other Database Software which allows you to connect to your type of database will suffice.

The Database Tables in which we need to change the records are “HOMEPAGE.EMD_RESOURCE_PREF” and “HOMEPAGE.EMD_EMAIL_PREFS” (in the HOMEPAGE database), a big thumbs up to Martin Schmidt for saving me countless hours searching for the correct table. Both of these tables have “PERSON_ID” column, so I searched in the “HOMEPAGE.PERSON” table for my test accounts in order to find out the “PERSON_ID” values of these accounts, so I could reproduce the desired state of one account and make sure that the changes made are valid and as I wanted them set. I’ve done that with the following SQL statement:

select *

from empinst.employee

where prof_display_name = ‘Milan Matejic’;

After getting the right “PERSON_ID”, I could check the Records in “HOMEPAGE.EMD_RESOURCE_PREF” and “HOMEPAGE.EMD_EMAIL_PREFS” tables.

— Email Notifications

select *

from homepage.emd_resource_pref

where person_id = ’13a96f01-37d8-4674-ae51-f6d2d19ee8e9′;


— Direct Emails

select *

from homepage.emd_email_prefs

where person_id = ’13a96f01-37d8-4674-ae51-f6d2d19ee8e9′;

The columns we need to change are “SEND_DIRECTED” in “HOMEPAGE.EMD_RESOURCE_PREF” table and “RESOURCE_TYPE” in “HOMEPAGE.EMD_EMAIL_PREFS” table. Setting “SEND_DIRECTED” to ‘0’ will result in deactivating “Receive notifications from other people by email”. For “RESOURCE_TYPE” we have the following options:

‘4’ –> Weekly

‘3’ –> Daily

‘2’ –> Individual

‘1’ –> Deactivated

In my case I wanted to set the notifications to “No Email” for all users, so I went with setting ‘1’ in all rows in the table.

Note: Before making changes for all users, you should make the change just for one test user, to make sure that there are no problems and that your statement is working properly.

I accomplished the task with the following update statements:

—– Update Statement HOMEPAGE.EMD_RESOURCE_PREF

update homepage.emd_resource_pref

set frequency_type = ‘1’

where frequency_type != ‘1’;

—– Update Statement HOMEPAGE.EMD_RESOURCE_TYPE

update homepage.emd_email_prefs

set send_directed = ‘0’

where send_directed != ‘0’;

Before and after running the update statements, you can verify the changes by looking on the number of rows with certain settings:

—- Search for Frequency Type

select *

from homepage.emd_resource_pref

where frequency_type = ‘1’;

—- Search for Send Direct

select *

from homepage.emd_email_prefs

where send_directed = ‘0’;

After running the update statements, just refresh your browser, there is no need to restart any applications or components.

As a bonus, I created an Enhancement Request, so hopefully in future we don’t need to change the database records for this, so please vote for it by accessing the IBM Connections Product Ideas Lab.

Advertisements

Sametime Community Server – LTPA Token Name

If you are planning on changing the LTPA Token on a Sametime Community Server, save yourself a lot of pain by using the existing LTPA Document and keeping the default name “LtpaToken”. You may not get any errors on the console but the SSO using LTPA just won´t work.

If you want to enable Internet Sites on the Community Server, you should read the instructions in the following article:

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

Changing Domino Transactional Logging Style

Different backup strategy/software can lead to the need for changing the Transactional Logging style on a Domino Server. There are basically two possibilities for doing this.

Possibility 1

  1. Disable Transactional Logging on a Domino Server.
  2. Shutdown Domino.
  3. Start Domino
    1. You should get a message: “Transactional logging being disabled after this restart”.
    2. “NLOGASIO” or “LOGASIO” should not start.
  4. Rename or delete the Transactional Logging directory.
  5. Restart Domino Server to confirm there are no errors.
  6. Enable Transactional Logging and set the Transactional Logging Style option you want.
  7. Restart Domino and again confirm there are no errors on the console.

This is a subtler approach, although this takes a considerate amount of time, you can make sure there are no issues before letting your server back into production. You can also keep the old transactional logs if by renaming the Transactional Logging folder.

On the downside, a consistency check will be run on every database opened, for the first time, and a new DBIID will be assigned. This can take a lot of time depending on the size of your databases.

Possibility 2

  1. Change the Transactional Logging style.
  2. Restart the Domino Server.
    1. If you are changing from “Archive” to “Circular”, you can delete or move the old Transactional Logs.

After this, no consistency check or database fixup is will be done and the databases keep their old DBIID.

Here are some useful URLs about Transactional Logging:

General Information

Best Practices

How to clean corrupt Transactional Logs

IBM Traveler 9.0.1.16 APNS Certificate Expires on 08.03.2018

As of 08.03.2018, the APNS Certificate used by Traveler 9.0.1.16 will expire and will not be valid anymore. For everybody who is running Traveler 9.0.1.16 this is a good time to update to a newer version. The current version of IBM Notes Traveler is 9.0.1.20.

You can also update the certificate files, as Detlev described in his blog post.

Why is APNS Certificate important? IBM Technical Support Video