How does Lotus Mobile Installer ckeck for Updates?

hcl-bot · December 20, 2010, 10:27am

How does Lotus Mobile Installer ckeck for Updates? We have Installes 8.5.2 on our Servers some time ago and then told our Nokia users to manually update via the webpage.

So most of them are on “8.5.2.0 201008311819” with their devices.

Then we updatet our servers to Traveler 8.5.2.1 and I recently realized that new Nokias (or those updating manually) get a newer client release called “8.5.2.1 201011171905”.

What I am wondering now is why the Mobile Installer doesn’t push the update to those who are already on the 8.5.2.0 client. None of them got updatet, non got a message that an update is available. Tried it with a test device myself … same here.

Is there any place were I have to point to the current version (like with the smart upgrade) or what am I missing here?

Thanks

Harald

hcl-bot · December 22, 2010, 5:06am

Subject: Have the same question?

Can’t find anything in the documentation

hcl-bot · January 6, 2011, 8:57am

Subject: RE: How does Lotus Mobile Installer ckeck for Updates?

LMI should be called in one of two ways.1. Traveler in push has a flag for the softwareUpdate which will then call LMI to have LMI check for the update (and install it).

LMI can check periodically (every 9 days in 8.5.2.0 but turned off in 8.5.2.1 b/c of #1 gets done first anyway).

So, something is not working right in Nokia LMI or in the server version (VersionInfo.txt which should show the 8.5.2.1 version). You need to open a PMR so that we can get a server dump as well as a TPR from one of the devices.

LMI checks for updates by making an HTTP request to the Traveler server. You can see this in the NTSActivity and NTSServletActivity logs.

hcl-bot · January 10, 2011, 3:38am

Subject: Found the logs … but what to look for

Found the two logs but it looks like there’s just the usual user activity in there.

Any special string or keyword I can look for to identify the version check requests?

Thanks

Harald

hcl-bot · January 10, 2011, 8:04am

Subject: RE: Found the logs … but what to look for

checkForUpdate is the action to look for. If you have FINE logging enabled (or higher), you will get the requested version and the server’s response. The server response comes from VersionInfo.txt if you want to find that there too.

hcl-bot · January 14, 2011, 8:02am

Subject: Checking but nothing initiated

Seems like the server is indeed checking for updates. But noting happens then. The user in this log entry is still listed as 8.5.1.1.201001012250 in the traveler.nsf

See below (just changed the Username to First Last/OU=LW/OU=BV7/O=BGXXX and uxxyyyy as well as the server to server.domain.de to protect names).

10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX DeviceType.#297 EXITING [Generic: 100, Specific: 100]

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX TravelerServlet.doRequest#1557 NTSServletRequestSerializable appName=Lotus Installer, body=0 bytes, bodyHash=0, busySignalTimeout=-1, cmdDeviceType=DeviceType: IBM_WM_6_SYNCML_CLIENT (120), confirmed=false, contentLength=0, delay=-1, deviceId=RaNd-6401266424266365305, deviceType=DeviceType: IBM_WM_GENERIC_SYNCML_CLIENT (100), firstMessage=true, hostName=server.domain.de, hostPath=/servlet/traveler, hostPort=443, isSecure=true, logKey=0110-1712-58686, method=GET, newConnection=true, operationKey=CN=First Last/OU=LW/OU=BV7/O=BGXXXRaNd-6401266424266365305checkForUpdate, pushMsgType=0, queryString=action=checkForUpdate&appName=Lotus%20Installer&deviceType=WM6Professional&version=8.5.2.0%20201008310112, remoteAddr=2.205.125.28, requestAction=checkForUpdate, requestURI=/servlet/traveler, responseAction=checkForUpdate, syncOriginator=dm, time=1294675978670 (16ms ago at Mon Jan 10 17:12:58 CET 2011), user=uxxyyyy, userAgent=Lotus Traveler WM 8.5.2.0, userLocale=de, isLocaleDefaulted=false, userId=CN=First Last/OU=LW/OU=BV7/O=BGXXX, version=8.5.2.0 201008310112

[01/10 17:12:58.686] FINE Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX TravelerServlet.printRequest#2205 Traveler: (CN=First Last/OU=LW/OU=BV7/O=BGXXX) checkForUpdate D->S (0b, 16ms, DeviceType: IBM_WM_6_SYNCML_CLIENT (120), Lotus Installer, 8.5.2.0 201008310112)

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.doResponse#1766 Traveler: Sending request for action checkForUpdate and operation key CN=First Last/OU=LW/OU=BV7/O=BGXXXRaNd-6401266424266365305checkForUpdate

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] ConnectionHTTPSender.getSocketHolder#299 EXITING [server.domain.de] [50.125] [com.lotus.sync.servlet.ConnectionHTTPSender$SocketHolder@53b353b3]

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.doResponse#1827 Traveler: Waiting 55000ms for response for action checkForUpdate and operation key CN=First Last/OU=LW/OU=BV7/O=BGXXXRaNd-6401266424266365305checkForUpdate

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.doResponse#1922 Traveler: Response from Lotus Traveler task for action checkForUpdate and operation key CN=First Last/OU=LW/OU=BV7/O=BGXXXRaNd-6401266424266365305checkForUpdate was received

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.setNTSResponse#2656 ENTRY [200] [null]

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.setNTSResponse#2705 NTSServletResponseSerializable action=checkForUpdate, altBodySize=0, appName=Lotus Installer, body=88 bytes, busyResponse=false, contentType=text/plain, deviceId=RaNd-6401266424266365305, lastMessage=true, logKey=0110-1712-58686, operationKey=CN=First Last/OU=LW/OU=BV7/O=BGXXXRaNd-6401266424266365305checkForUpdate, pushMsgType=0, queryString=action=checkForUpdate&appName=Lotus%20Installer&deviceType=WM6Professional&version=8.5.2.0%20201008310112, requestBodyHash=0, status=200, time=1294675978670 (16ms ago at Mon Jan 10 17:12:58 CET 2011), useCompression=true, userLocale=de, userId=CN=First Last/OU=LW/OU=BV7/O=BGXXX, version=8.5.2.1 201011181900, wbxmlVersion=0

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.setNTSResponse#2706 EXITING [200] [88]

[01/10 17:12:58.686] FINE Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.printResponse#2331 Traveler: (CN=First Last/OU=LW/OU=BV7/O=BGXXX) checkForUpdate D<-S (88b, 16ms, 200rc, Lotus Installer, 8.5.2.1 201011181900)

[01/10 17:12:58.686] FINEST Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] Dispatch.destroyDispatchThreadData#252 No Dispatch Thread Data to destroy for thread Thread[Thread-52,5,main]

hcl-bot · January 14, 2011, 5:45pm

Subject: RE: Checking but nothing initiated

The issue here is on the device. I cannot tell what the issue is, but I can tell that the server is sending the right information.

The client made a request to see if Lotus Installer is up to date. The client currently has version 8.5.2.0 201008310112:

[01/10 17:12:58.686] FINE Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX TravelerServlet.printRequest#2205 Traveler: (CN=First Last/OU=LW/OU=BV7/O=BGXXX) checkForUpdate D->S (0b, 16ms, DeviceType: IBM_WM_6_SYNCML_CLIENT (120), Lotus Installer, 8.5.2.0 201008310112)

The server checks VersionInfo.txt and finds that there is an update for Lotus Installer (8.5.2.1 201011181900):

[01/10 17:12:58.686] FINE Thread-52 CN=First Last/OU=LW/OU=BV7/O=BGXXX[RaNd-6401266424266365305] TravelerServlet.printResponse#2331 Traveler: (CN=First Last/OU=LW/OU=BV7/O=BGXXX) checkForUpdate D<-S (88b, 16ms, 200rc, Lotus Installer, 8.5.2.1 201011181900)

What I cannot tell is what the device is doing with that information. It should start downloading it automatically and then asking to install OR it could ask before it downloads (depends on the device’s settting in Lotus Mobile Installer (LMI) itself).

I do know that when you got into LMI and manually do a check for updates, it will do LMI first, and then Lotus Notes Traveler (LNT) after LMI either is up to date or has been updated to be up to date. It sounds like you are in the middle of that process.

To debug the client, we’ll need the logs from the device. For that, you should create a problem report on the device and let it upload to the LNT server. The problem report will get both the Traveler and LMI logs.

hcl-bot · March 16, 2011, 3:30am

Subject: Different behaviour after upgrading to 8.5.2.2

After we upgraded to 8.5.2.2 the following happend:

One Nokia and one WinMobile device told their users that a new version is available and upgraded to 8.5.2.2

Also several of the Androids (but not all) did so.

So I assumed that their might be a problem with the old installer as on some devices the installer tells “not compatible” (although it should be) when checking for updates.

I just downloaded the installer via the traveler website on one device and immediately this one upgraded traveler. Checking for updates now this doesn’t produce an error but correctly states “no updates available”.

So I tried this on the next Nokia device and here the installer doesn’t change to the new version and remains 8.5.2.0 … still producing the error (although it said that it downloaded and installed a newer installer version).

What’s weired to is the case that we have those “not upgrading” problem on different versions (8.5.2.0 and 8.5.2.1) so I can’t imagine that a broken installer really can be the problem.

hcl-bot · March 16, 2011, 7:06am

Subject: Re: Different behaviour after upgrading to 8.5.2.2

You are going to need to open a PMR for logs and TPRs from the device to be analyzed.