Blog

Our News/Articles/Opinions/Technotes from the world of IBM Collaboration

Orphaned Devices on Traveler HA SQL

Hi all,

Had a recent issue with a customer using Traveler 9.0.1.4 on Domino 9.0.1.4 where one user had three devices listed all with the same device ID (so essentially the same device). All devices were inactive and we wanted to clear them up. So, I issued the usual console commands:

1. Tell Traveler Delete * <username>
2. Tell Traveler Security Delete * <username>

but Traveler kept saying that no devices were found for the user. Issuing Tell Traveler User <username> confirmed that there were indeed no devices associated with the user. However, in the back-end SQL database i.e. https://lotustraveler.nsf the devices were still showing !

Read Full Post

Notes 9 and SmartCloud Activities – Heuston we have a…

Bit of a moan here.

I just upgraded from Notes R8.5.3 to R9.0.1 FP1. There are a lot a features that I really like in R9.x but something is REALLY bugging me.

In R8.5.3 I was an avid user of SmartCloud Activities in the sidebar – it worked really well.

In R9.0.1 “Social Edition”, you would have expected it to be truly social. But no. SmartCloud Activities just will not work. I understand that Connections Activities do but why the regression of functionality? Why Connections but no SmartCloud – it’s bizarre.

I’ve searched technotes and nearly every page on the whole Internet to look for a solution to this without luck.

If anyone can tell me how to get this working, my gratitude will be eternal as it’s like an old friend has left me….

Thanks,

Steven.

It’s Friday ! – Undocumented Notes Table Shortcut you will love

I’ve never seen this before and a colleague came across this brilliant shortcut by accident.

Here’s how it works (in Notes 8 and 9 anyway):

1. Create a table in Notes (or use an existing table)

2. Hold the shift key and hover the mouse pointer over a row line (not the top one)

3. The cursor will change to a thick black line with a little blue diamond above it

4. Double click while still holding down shift

5. A new row appears !!!

This also works for columns as well. I think it’s great but that might be just me.

Enjoy,

Steven.

Lotus Traveler – Latest Device Updates (Feb 2012)

It’s worth noting this article published by IBM to make sure you’re on an appropriate release of Traveler for your users’ devices.  (and also for information on upcoming Traveler device support!)

http://www-01.ibm.com/support/docview.wss?uid=swg21577369&myns=swglotus&mynp=OCSSYRPW&mync=E

Steven Vaughan – Domino People Ltd

Traveler 8.5.3.1 Interim Fix Released

PREREQUISITES

Lotus Notes Traveler server version 8.5.3.1 already installed.

FIX LIST

LO65270 – MAILTO LINK DOES NOT WORK ON SOME ANDROID DEVICES.

LO65271 – UNABLE TO SYNC WITH SOME ANDROID DEVICES

LO65435 – SHORT CUT ICONS MAY DISAPEAR ON SOME ANDROID 3.X DEVICES.

LO65542 – ANDROID: LINKS IN MAIL AND CALENDAR ENTRIES ARE NOT CLICKABLE

LO65568 – IMPROVED SUPPORT FOR ANDROID 4.X PHONES

LO65759 – REPLY-TO MAIL HEADER IS NOT RESPECTED

LO65923 – CONTACT EDITOR SHOWS BLANK OR WRONG DATA

LO65948 – TRAVELER ANDROID FORCE CLOSE WHEN SD CARD STATE IS CHANGED

Please see : http://www-01.ibm.com/support/docview.wss?uid=swg24019529&wv=1 for details on installation and how to obtain the fix pack file.

Domino BES – testing handhelds are functioning

A quick and easy test to ascertain if one or more of your Blackberry Enterprise Server users is setup correctly server side or if their device is configured correctly is possible and here’s how……

From your normal Lotus Notes mail (I’m assuming you are using Notes mail !), send the user, users or group an email with the following subject line:

<$Confirm,RemoveOnDelivery,SuppressSaveInSentItems>

If the Blackberry device is able to receive and send messages, you will get an automatic  reply. If you don’t get a message back, you know something is wrong. The original message you send is removed immediately and the reply is also deleted from their sent view.

A couple of Caveats:

  1. The original message you sent and the reply mail will be in the users trash view.
  2. Obviously this will not work if the handset is turned off or doesn’t have the appropriate signal, in this case the original message you send will also not be deleted until their handset is online.

 

Yellow Status on Lotus Traveler – What to do ?

Scenario:  Every time you connect to the traveler server and issue a “tell traveler status” command from the Domino console, you get a yellow status returned or more particularly

“The response times for opening databases on mail server X are above the acceptable threshold.”

Mail users on server “X”  are perfectly happy with how quickly messages get to their devices and you want to understand how this “threshold” works and  to confirm if it is doing what you want it to do.

The first thing to explain is that Traveler will go into yellow status if it take more than 2 (yes, that’s 2) seconds to open a mailfile on a remote server.  This is fine when all mail servers are on the same LAN and in the same location.  But what about actual remote servers that are in different locations? Maybe they are on a decent connection but  you may expect the remote mailfile to take longer than 2 seconds  to open as the norm.

The good news is that you can change this threshold to make your Traveler Server “Green” again !!! and here’s how:

The next thing to note is exactly how many seconds mailfiles on server X are taking to open.

You can do this by issuing a command “tell traveler stat show” from the domino console, this will return a list of results.
(as an aside you can make more sense out of these results from this link – http://www-10.lotus.com/ldd/dominowiki.nsf/dx/System_status_results_LNT853)

Look for DCA.DB_OPEN.Time.Histogram.CN=X/O=YourOrg (where Server X is X/YourOrg)

You’ll see a list of results that look like this
DCA.DB_OPEN.Time.HistogramCN=X/O=YourOrg.000-001 = 10
DCA.DB_OPEN.Time.Histogram.CN=CN=X/O=YourOrg.001-002 = 20
DCA.DB_OPEN.Time.Histogram.CN=CN=X/O=YourOrg.002-005 = 1

In the above example it’s saying is that in the last fifteen minutes  (the default interval for status checks) 10 times it took less than one second to open a remote mailfile on Server X, 20 times it took 1 second to 2 seconds, and once it took between 2 and 5 seconds.  (you may see more results if it took longer than 5 seconds).

You may want to do this a few times over the course of a day or week to see are the times consistent.

Let’s continue the scenario and say your remote server is in another country or even continent and you wouldn’t be shocked if it took up to a minute to open the mailfile.  You’re happy to accept that this is a network restriction and you shouldn’t be constantly alerted about it i.e. you want to change the threshold to something more reasonable.

For this threshold the following “interval buckets” values apply:

1 – “000-001” seconds to open a mailfile on a remote server.
2 – “001-002” seconds to open a mailfile on a remote server.
3 – “002-005” seconds to open a mailfile on a remote server.
4 – “005-010” seconds to open a mailfile on a remote server.
5 – “010-030” seconds to open a mailfile on a remote server.
6 – “030-060” seconds to open a mailfile on a remote server.
7 – “060-120” seconds to open a mailfile on a remote server.
8 – “120-Inf” seconds to open a mailfile on a remote server.

The default for a yellow status is a value 2 (so anything above 001-002 seconds) and the default for red is 8 (so anything from 120 seconds upwards).

We’ll give an example that from looking at the “tell traveler stat show” over the course of a week, you don’t want the traveler server to go into yellow status unless it takes over a minute to open a remote mailfile.  To do this your status value will need to equal 6 (“030-060″ seconds to open a mailfile on a remote server).

In order to apply this setting you need to modify the NTSConfig.xml file (located in <domino data directory>\traveler\cfg\ on the Traveler server) to include the following line:
<PROPERTY NAME=”STATUS_DB_OPEN_INTERVAL_YELLOW” VALUE=”6″/>
and on a new line below the following line
<COMPONENT COMPONENT_TYPE=”TrueSyncServer”>

Followed by issuing a “tell traveler quit“, followed by a “load traveler” from the Domino console.

You can see if the setting has been applied correctly by doing a “tell traveler systemdump“,  go to <domino data directory>\IBM_TECHNICAL_SUPPORT\traveler\logs\dumps\ and look for the latest system dump. Open the file and search for “—– adminForTSS —–“, and then for  STATUS_DB_OPEN_INTERVAL_YELLOW” below that, the value that is applied here is the one applied to the server (ie if it hasn’t changed then this value will equal the default of 2)

Obviously the status of the server will have changed as well (assuming there are no other yellow status’).

The next step from here from IBM’s point of view would be if you could set individual thresholds for individual servers (maybe even in the server document)!!

You can apply similar changes to other thresholds in the same way, more details on the status messages is here – http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Status_command_details_LNT8521

Much kudos to Cormac McCarthy, one of our Senior Admins for taking the time for writing up his findings to share.

Domino Designer R8.5.3 – Ctrl+Shift Bug ?

We recently upgraded our clients to Notes R8.5.3 which included the Admin and Domino Designer clients.
One of our developers is a real keyboard shortcut nut and is complaining bitterly about what may be a bug or “feature” in this new release.
Previously, when pressing Ctrl+Shift, he was able to select words and upon releasing Ctrl and clicking the down arrow, select lines.

Now (when editing Script Libraries) when you press Ctrl+Shift (right-hand-side of keyboard)it changes the text from left-to-right (default) to right-to-left ! To get back to normal you have to press Ctrl+Shift of the left-hand side of the keyboard. It’s driving him mad.
To explain better, here is a script library from the mail file:

Now, I press Ctrl+Shift (the right side of the keyboard) and I get this:

You need to press Ctrl+Shift on the left side of the keyboard to get it back again.

The developer in question is blaming me personally for making him upgrade to R8.5.3 – anyone know how to make my life easy again ?