<< December 2010 | Home | February 2011 >>

Wi-Fi, Firesheep and Lotusphere

Using the Wi-fi at Lotusphere has been a real nice experience so far this year (of course the OGS on Monday being the true test). Coverage is better and the bandwidth seems to have been upped quite a bit. I do find it a bit sad though that the network is still open and unencrypted. Even a passphrase like "Lotupshere" would make security so much better. Why you ask? Why because a place like Lotusphere which is, lets face it, a big gathering of geeks. A worse a big gathering of geeks using social software sites. And using them a lot.

Lotusphere will be a nice place for someone running Firesheep to come in a harvest 5000 accounts in a day or so. I wont let it stop me but I think people should be aware of it. If you are afraid of it I suggest using a tunneled VPN connection to access your accounts.

If you want to learn more about Firesheep see the Wikipedia article or simply search for Firesheep on Google. Also just to be fair - this is a problem, and will continue to be a problem at all conferences or gatherings with open wi-fi hotspots.

Using LotusLive for Sametime - 2 months in

I previously wrote about how we shutdown our Sametime servers and moved to LotusLive for Sametime ("Why we shutdown our Sametime servers"). About 2 months after making the switch I thought it was a good time to sum to the experience and whether it's a move we're happy with.

There's nothing to be said about performance or uptime which has been flawless. Users are happily chatting away and the worries that some had about being available for customer chat in off hours (because we are now in the same community as customers and partners) hasn't been a problem. Whether it's really not a problem or whether customers and partners haven't found us to LotusLive is unclear. Only thing I've heard from users is that it's a real pain no longer having public groups to help them maintain their buddylist. Previously many used public groups such as "Sales" or "Developers" to automatically maintain their buddylist but the concept of public, shared, groups are not available in LotusLive. That's a real shame. Same goes for LotusLive meetings which has taken over from Sametime meetings without any issues at all.

All in all I haven't heard anything from users that would make us want to go back to running our own Sametime environment.

Now from the technical side of fence I find the lack of groups really annoying. I also find the fact that file transfer isn't allowed by policy annoying and frustrating. Using Sametime as a quick way to move a file between colleagues was really nice and having to resort to drives or e-mail is so 1990's... As a LotusLive (Engage) customer

I'm also finding that lack of tools for automated user management (creation, modify, deletion) irritating and frustrating. I've heard about a LDAP sync tool or using TDI but not something I have found solid information on. The tools might be there and but they're hardly easy to find or come by from my point of view. The result is that we have to manually make sure that users update their profile with current information which is time consuming and far from ideal.

In conclusion however...

Despite all this I still find that the move was a good one and I'm hoping that some of the above can be solved in the near future. I have a list of LotusLive questions lined up for Lotusphere 2011 so if you're in the developer lab and know something about LotusLive I want to talk to you.

Lotusphere 2011: BOF accepted

The BOF titled "Let's talk plugin development!" submitted by Bob Balfe and I has been accepted for this years Lotusphere. I'm very excited about this and it's shaping up to be my busiest Lotusphere ever - two sessions and a BOF. Wow!

When the default isn't enough - creating a new Lotus Connections Files policy

As posted earlier today I had to change the default maximum library size of in Lotus Connections Files to accommodate a particular user. Of course 1 GB (double of the default) wasn't enough so I created a new policy for that particular user and assigned it. I was very easy as well. Below are the wsadmin commands.

wsadmin<FilesPolicyService.add("2GB Policy", 2097152000)
A policy was added with the new id 584f818a-106c-4343-
8f40-63ceb0ac5c5f .

wsadmin<FilesLibraryService.assignPolicy(
   "1a60c8d1-fc59-41bc-9d89-c266a9709230", 
   "584f818a-106c-4343-8f40-63ceb0ac5c5f")
The policy with the id 584f818a-106c-4343-8f40-
63ceb0ac5c5f is now assigned to the library with the id 
1a60c8d1-fc59-41bc-9d89-c266a9709230.

Lotus Connections and extending Files Library Sizes

Funny thing at a Lotus Connections customer today. A user was complaining that he wasn't able to upload a new version of a file into his Files due to size restrictions. After poking around I found out that the user had uploaded 492 mb of data into Files. After poking some more I found out that a maximum library size is enforced based on policy. By default all users are assigned a policy that allows for 524 mb of data hence why he was unable to upload any more data.

To solve it I changed the default policy to allow for 1 gb of data per user (after asking management). This is done using the administrative service API for Lotus Connections which is quite extensive. Below are my steps with the key values in bold.

The steps are as follows:

  1. Initialize the wsadmin environment
  2. Get access to the Files administrative services
  3. Find the user id using FilesMemberService.getByEmail(email) (user id is f631a9d9-07c4-4dcc-b820-1fdaefc4895c)
  4. Find the users library id using FilesLibraryService.getPersonalByOwnerId(id) usig the just found user id (library id is 1a60c8d1-fc59-41bc-9d89-c266a9709230). This also shows the user is controlled by the default policy (policy id 00000000-0000-0000-0000-000000000000) and that he is using 93% of the allotted space)
  5. Edit the default policy using FilesPolicyService.edit(id, name, size) to set a new size of twice the original size)
  6. Refetch information about the users library using FilesLibraryService.getPersonalByOwnerId(id) to see that the new library size has been applied

D:\IBM\WAS\profiles\AppSrv01\bin>wsadmin -username wasadmin 
-password <password> -lang jython
WASX7209I: Connected to process "server1" on node SDKFU016Node01 
using SOAP connector;  The type of process is: UnManagedProcess
WASX7031I: For help, enter: "print Help.help()"

wsadmin>execfile("filesAdmin.py")
Files Administration initialized.

wsadmin>FilesMemberService.getByEmail("jdoe@example.com")
{isOprhan=false, email=jdoe@example.com, 
directoryLastUpdate=2011-01-04 17:07:57.167, 
id=f631a9d9-07c4-4dcc-b820-1fdaefc4895c, name=John Doe, 
createDate=2010-02-19 13:04:36.404, communityLastUpdate=2011-01-04 
17:12:25.084, lastVisit=2011-01-04 17:07:57.167, 
directoryGroupLastUpdate=2011-01-04 17:12:25.084}

wsadmin>FilesLibraryService.
   getPersonalByOwnerId("f631a9d9-07c4-4dcc-b820-1fdaefc4895c")
{lastUpdate=2010-02-19 13:04:36.467, externalInstanceId=null, 
id=1a60c8d1-fc59-41bc-9d89-c266a9709230, type=personal, 
ownerUserId=f631a9d9-07c4-4dcc-b820-1fdaefc4895c, title=John Doe, 
label=24924863-F97C-C455-C125-74C9004077E4, externalContainerId=null, 
policyId=00000000-0000-0000-0000-000000000000, createDate=2010-02-19 
13:04:36.467, summary=, percentUsed=0.9382985649108887, 
maximumSize=524288000, size=491938678}

wsadmin>FilesPolicyService
   .edit("00000000-0000-0000-0000-000000000000", 
   "Default Policy", 1048576000)
The policy with the id 00000000-0000-0000-0000-000000000000 was 
   updated successfully.

wsadmin>FilesLibraryService
   .getPersonalByOwnerId("f631a9d9-07c4-4dcc-b820-1fdaefc4895c")
{lastUpdate=2010-02-19 13:04:36.467, externalInstanceId=null, 
id=1a60c8d1-fc59-41bc-9d89-c266a9709230, type=personal, 
ownerUserId=f631a9d9-07c4-4dcc-b820-1fdaefc4895c, title=John Doe, 
label=24924863-F97C-C455-C125-74C9004077E4, externalContainerId=null, 
policyId=00000000-0000-0000-0000-000000000000, createDate=2010-02-19 
13:04:36.467, summary=, percentUsed=0.46914928245544435, 
maximumSize=1048576000, size=491938678}

wsadmin>