Using a couple of developerWorks articles (Extending the Lotus Sametime client with an LDAP directory lookup plug-in and Extending IBM Lotus Sametime Connect V7.5 with an SMS messaging plug-in) for inspiration I wrote a SMS plugin for the embedded Lotus Sametime client in Lotus Notes. The action goes in the Send menu when right-clicking a contact.
The plugin picks up the cellphone number from Domino Directory, supports sending to multiple contacts in one go and uses our exiting SMS gateway for sending the SMS'es (via e-mail). The hardest part was finding the menu path to use to stick the action where I wanted it. For others you should use com.ibm.collaboration.realtime.imhub.send/slotX where slotX is either slot1, slot2 or slot3 depending on where in the Send menu you want the action.
Once I've made it configurable which server to use for Domino Directory and how the SMS should be sent (which domain) I'll probably make it publicly available.
- Extending Sametime 7.5 - Building Plug-ins for Sametime (see page 111 and 116 for menu paths)
The wait has been long but I just got word (via Christian Henseler) that IBM yesterday released properly signed XTAF dictionaries for Notes 8.5.1. In case you're wondering "XTAF dictionaries" are the common dictionaries shared by Lotus Notes, Lotus Sametime and Lotus Symphony. Additional language dictionaries has been available for a while but the Eclipse feature wasn't signed so it was troublesome to install on client machines. The Eclipse features are now properly signed and they are easy to add to an update site and roll out using a widget catalog.
The bundle you need to grab from PartnerWorld or Passport Advantage is "IBM Lotus Notes XTAF Dictionaries 8.5.1 for Windows and Linux Multilingual (CZHE3ML)".
The last two weeks I have had the honor of installing Lotus Connections 2.5 on Windows 2008 Server 64 bit with Microsoft SQL Server 2005. Twice. And what a change from my normal Windows 2003 Server. In this blog post I'll outline some of the issues I ran into and what I had to pay special attention to.
First off Tivoli Directory Integrator 6.1.1 (the component that move data from LDAP to the Profiles SQL database) isn't supported and doesn't run on Windows 2008 Server. The TDI scripts provided with Lotus Connections 2.5 doesn't work with TDI 7 which leaves you at a dead stop. Only solution as of now is to find a Windows 2003 Server or other Windows platform to run TDI. Hopefully Lotus Connections NEXT will use TDI 7.
Next issue I had to address was that Websphere Applicaton Server (WAS) 6.1 should be at fixlevel 19 before you create any profiles on a Windows 2008 Server. This meant that the profile couldn't be created as part of the WAS installer. This wasn't too big of an issue as it's a best practice not create the profile during setup anyway. A benefit of doing it this way is that it allows you to create the profile in another location than between your WAS binary directory.
So all was well and good? Not really as the GUI tool to manage profiles isn't supported on Windows 2008 Server either. There is however a manageprofiles command to manage profiles which may be used. The command looks rather convoluted but it goes something like this (I ran it was admin):
manageprofiles.bat -create -profileName AppSrv01 -profilePath d:\WASProfiles\AppSrv01 -templatePath c:\ibm\websphere\appserver\profileTemplates\default -nodeName LotusConnectionsNode01 -cellName LotusConnectionsCell01 -hostName lc.example.com -isDefault -winserviceCheck true -winserviceAccountType specifieduser -winserviceUserName username -winservicePassword password -winserviceStartupType manualThe last few arguments create the Windows service. I have had some success doing this but most times I leave the "winservice"-arguments out and use WASService.exe to create the service instead.
wasservice -add LotusConnections -serverName server1 -profilePath d:\wasprofiles\appsrv01 -startupType automatic
When I installed Lotus Connection I had to run install.bat as admin to avoid having the SQL connection check fail.
Generally in Windows 2008 Server I found that paying special attention to drive and folder security made my life a lot easier. That goes for both WAS and IBM HTTP Server IHS). Additionally on one IHS server I had to manually install GSKit to enable SSL as it wasn't installed by the installer. I also had to put GSKit (C:\IBM\GSK7\lib) on the PATH in Windows. To symptom was that IHS couldn't access the SSL keystore.
I hope this will help someone.
Just received this picture from NLLUG2009 (the Dutch Lotus User Group 2009) of me and Kevin Cavanaugh deep in discussion. Goes to show the level of access possible at these events.
When installing and configuring Lotus Connections or any other Websphere Application Server based application you'll probably find it beneficial to speed up restarting WAS. I found that disabling auto-start of some of the Lotus Connections applications was an easy way to do this. I simply followed the steps in "Websphere Experience: Startup behavior of an application" to do it.
For the people not afraid of XML-files you might as well simply edit the deployment.xml file(s) in <profile path>\config\cells\<cell name>\applications\<application name>.ear\deployments\<application name> and set enabled="false" for the <targetMappings>-tags at the top. As always with editing files directly - proceed at your own risk... :-)
Just found an incubator project at Eclipse.org called SWTBot which is an extension to test UIs written in SWT. I will need to look into that.
While parsing my RSS feeds today I found an article on the winsupersite.com on SharePoint 2010. As always when you're involved with a technology it's good to know that the competition is doing and SharePoint is surely a technology platform to watch if you're involved with Lotus Domino and Lotus Notes.
I find it very interesting to see how Groove has been renamed to SharePoint Workspace. This will make it easier to see how Groove is connected to SharePoint and make it easier to understand for customers. Another hallmark of Microsoft (deep integration between all Office Suite members) is being extended to SharePoint and SharePoint is being extended to Office Mobile.
The launch of Office Web Applications, the ability of Office Web Applications to integrate with SkyDrive and having the opportunity of running the Office Web Applications on-premise is also quite nice. Looking at Office Web Applications it surely leaves Google Docs in the dust and looks like a much more mature and usable product. Microsoft has really hit the mark with this release and the partnership with Facebook makes it a web productivity suite to be reckoned with.
Looking at this SharePoint release I certainly have to spend some actual time getting to know the product and see how SharePoint compares to Lotus products from a collaboration point of view.
Found this nifty wiki page on Expeditor 6.2.1 Known Issues and Limitations. As always nice to know about the limitations.
I'm happy to say that I'll be speaking at the Lotus UK 'Power of Business Applications' conference on 16 June at the IBM Bedfont Lakes, UK. I'll be presenting a session called "Breathe new life into your applications with sidebar plugins and widgets" - I'll post the abstract as soon as it has been written... :-)
Received these steps from a coworker and thought I would publish for the greater good if others need it. Thanks Bjarne.
After downloading the connector to Lotus Quickr and trying to install it I found out that wasn't possible to install the Lotus Quickr connector on Vista 64-bit or Windows 7 64-bit. I searched the internet and found a solution but unfortunately it didn't work. After messing around I got it working.
- Download the Lotus Quickr connector from your Lotus Quickr site
- Execute the file - Click on OK when the error pops up and end the installer.
- Browse to the following folder Users\<username>\AppData\Local\Temp and copy the file qkrconn.msi to another location.
- Download and install Orca. This application allows you to modify MSI files. http://www.softpedia.com/progDownload/Orca-Download-79861.html
- Open the qkrconn.msi with Orca and scroll down to the "LaunchCondition" table located on the left.
- Delete the condition "(Not Intel64) And (Not VersionNT64) And (Not Msix64)" by right clicking it then selecting "Drop Row". You can delete both rows because they are not needed (I did that)
- In the table located on the left, click in the value "InstallExecuteSequence" and find the row "LaunchCondition" and delete it by right clicking it then select "Drop Row".
- In the table located on the left, click in the value "InstallUISequence" and find the row "LaunchCondition" and delete it by right clicking it then select "Drop Row".
- Save, exit and run the MSI!
Today and tomorrow I'll be at a XPages workshop with Tim Clark at IBM in Lyngby. Should be fun - probably not a lot of new stuff but it will be interesting to see how others teach XPages.
It always feels good to help out a fellow Yellowhead and especially be appreciated afterwards (by Mike Myers aka @stickfight on Twitter) :-)
"if formally declare @lekkim a god of domino java to be worshiped above all others"
Thanks Mark and happy I could help.