Navin Rajapakse, Vice President, Global Architecture and Engineering, Lehman Brothers
Lehman made the decision to adopt Jabber two years ago. We had Mindalign (Parlano), as well as several homegrown IM solutions. We had various non-communicating islands of IM.
We also wanted to be able to communicate remotely, with people working outside the building. So they opened up to AOL and Yahoo. Soon, we grew concerned about that, and wanted more control, but still needed to talk with the public networks.
The requirements led to a bake off between IBM/Lotus Sametime and Jabber. The customization of Jabber's client was significantly easier. On the server side, we evaluated the flexibility of Jabber, and adopted various open source modules.
And in the final analysis, the Jabber solution was more cost effective.
TIBCO is the company's enterprise application integration framework, and Jabber seemed relatively easy to integrate there.
We had a need to develop self-service 'bots, and Jabber offered an easy way to do that.
And we had to meet various SEC requirements on privacy, security, and auditability.
[presents tiered architecture: notes that today, Lehman is not taking advantage of server-to-server capability]
We have integrated a generalized notion of presence that can be included into other applications, and we have presence enabled our directory.
Used an early version of the Jabber web client, but the Win32 client was more critical to Lehman's use.
While the 1:1 chat was solid, there were various features needed for roll-out of group chat, which Jabber rolled out in a few months time.
Now, in use at 80%-90% of the company.
We have SEC compliant escrowing and retrieval of all IM messages as needed.
We have eliminated other IM solutions, and have integrated 20 or 30 applications taht are using Jabber as an alert mechanism.
We have integrated with LehmanLive, directory, security and reporting services.
2,000-9,500 concurrent users. All over the globe, and even during the weekend, so we need to be up 24X7.
3-3.5 M messages per week, which includes IM and chat.
Launched early part of last year: it is considered a tier 1, mission critical application, like email.
Different groups have different modes. Like the equities guys who use a chat room to swap deal information.
On the equities side, we have set up chat rooms, like foreign exchange.
We have extended the client and chat in several ways. For example, we integrated voice, so you can right click on a buddy, and it will dial.
We decided to pick a protocol, XMPP, and go with it, even though the market has not settled that protocol war.
Issues with compliance with AOL and various consortium based IM clients were problematic. We decided to go with an 80/20 rule, and use Jabber, and let the other issues fall to the side for now.
Most important, we ensured SEC compliance.
Question: How much monthly maintenance? Have you considered a hosted solution?
A: We don't have a dedicated team, we have an operations staff that handle it. Its nearly a zero maintenance, except for upgrades.
Question: How builds the applications that integrate with Jabber?
A: We built a TIBCO bridge, so our application developers are experienced in building to that.
Question: How do make sure the apps don't crush the Jabber system?
A: We have a Karma system that tracks message rates, and quickly resolve any issues.