Paul's Down-Home Page

Ordinarily I wouldn’t post this announcement here, but I’m going to break tradition and do so because I’m one of the conference co-chairs. As such, I have to help find speakers, so I want this call for papers to go out far and wide.

Windows IT Pro is now accepting session proposals for the Oct-Nov. 2005 Windows Connections conference. We’re heading to San Diego October 30 to November 2, 2005, for the premier Windows technical conference, and we’d like to hear from you!

If you’re interested in speaking on Exchange-related topics at the show, send your abstracts to paul@robichaux.net by February 18. We want proposals for regular 75-minute sessions, as well as 1/2 day and full day pre-conference and post-conference sessions.

Note that we have a limited number of speaking slots, and all participants must be able to present a minimum of three 75-minute sessions. There are three basic requirements:

• Send a minimum of 3 session proposals (4 or 5 is ideal for discussion purposes)

• Include a biographical statement with your session proposals

• Include any additional pre- or post-con session proposals, if applicable

Please adhere to the February 18 deadline as we need to make speaker and session selections right away. (We plan to have a conference brochure ready to distribute at TechEd in June.)

I had a very interesting phone call yesterday with an IBMer named Jim Colson. Jim actually is the chief architect responsible for the Workplace Client Technology platform, and he’d contacted me after seeing my earlier post complaining that WCT wasn’t generally available to tell me that it is available. Clearly there was a disconnect if it appeared that two different parts of IBM were telling me two different things, so I was eager to get the lowdown.

Jim explained that WCT is a client middleware platform, which  includes a wide range of technologies (including a managed client container, access technologies such as messaging, distributed business logic, data synchronization, and interaction technologies such as Embedded ViaVoice, and other presentation services including browser based and widget based interfaces from Eclipse).  These technologies can be used to build applications on various types of embedded, mobile, desktop, laptop, and server devices. The underlying technology has been in development for about 7 years; and  has been deployed in a wide range of solutions such as cars from Honda, Nokia mobile phones, laptops and tablets with Nissay,  and a wide range of line-of-business apps.

WCT is currently available to customers in a variety of forms. It’s already built into a number of other products, and the WCT Micro Edition SDK offers a freely downloadable set of WCT components that can be used to evaluate WCT as an app dev platform. (To be perfectly unambiguous: the SDK is for production use, but you can download it to play with.)

WCT supports building deployable assemblies of components– think of them as packaged runtimes– to support particular applications. The Enterprise Offering (more properly, the Workplace Client Technology, Micro Edition Enterprise Offering, or WCTME-EO) bundles the most commonly required components and middleware services for desktop and laptop-class devices into a single deployable bundle. So, mea culpa: WCTME-EO and the WCT SDK are both generally available and widely used, my earlier claims notwithstanding.  Thanks Jim!

Still with me? OK, back to my previous post. Among other WCT customers, Lotus is using the WCT platform to build their own client, the Workplace Client Technology, Rich Edition. This is the actual client middle platform that I’ve been trying to get, and it is not generally available– at least according to my IBM sales rep and the Lotus WCT Project Office. That’s supposed to change with the release of Lotus Workplace Messaging 2.5 and Lotus Workplace Documents 2.5.

To put this in more familiar terms, my earlier post was roughly equivalent to complaining that Microsoft wouldn’t let me have the .NET Framework (which is freely available and widely deployed, and for which beta/preview versions exist) when what I really wanted was Office. You can argue over whether Lotus is being forthright about exactly who can get  their WCT-based clients, and under what circumstances, but the bottom line is that WCT itself is available, and that’s what Jim was trying to help me understand. Now I know what specific term to use next time I complain to Ed Brill.

Since my earlier posts on Workplace, I’ve been struggling with a problem: IBM won’t sell me licenses for the Workplace Rich Client (echoes of “The Soup Nazi“…) After the earlier pricing misfire, I got another email from my sales rep, invoking the mighty power of the Workplace Client Technology Project Office:

The Workplace Client Technology Project Office has as its mission the job of implementing the Workplace Client Technology into customers environments in a controlled and measured manner and they are running pilot programs for customers. They have asked the following questions be answered in order to be considered for this piloting. We need to ensure the customer has



1. gained a thorough understanding of the technology

2. applied that understanding to real, known business pain(s) in their organization

3. high level sponsorship within their account that will consider making this technology part of their architectural strategy moving forward

Upon completion of this pre-qualification process, the Project Office can then select customers to pilot the software. Once the customer is accepted into the pilot program, we provide the customer information to download software from Passport Advantage.

We went back and forth a few times, as I sought to reassure my sales rep that I wasn’t about to start madly deploying WCT in my Fortune 100 clients without any succor from the Project Office. That didn’t help; the Project Office then wanted to know why we were an MS partner, how much Notes application development we did, and what IBM products we currently had deployed. I then sent a more detailed response that explained what we do (including an explanation of how we do capability assessments and product evaluations) and why we wanted the software. I haven’t heard back from the project office yet (or from my sales rep, for that matter), although this might be due to the holidays.

Why is IBM being so tight with this technology? Sure, it might just be a matter of risk management; they don’t want customers to have bad experiences with the product. That’s understandable, although I note that Microsoft and Oracle (among others) restrict access to beta versions of their product, not the released versions. (As a side note, I find it a little offensive that IBM expects me to audition to gain the right to buy their product, but maybe that’s just me. At least there’s no swimsuit competition).

IMHO, IBM’s overdoing it, because this approach (“we have a ‘game-changing technology‘ but we won’t let you have so you can start gaining an understanding of it”) is not exactly going to speed their product’s adoption. The WCT information page says that you need to contact your sales rep if you want to pilot or deploy the product, but it doesn’t mention the fact that the Project Office is liable to tell you to go pound sand unless you survive their evaluation process. In fairness, that result is alluded to here, but I would be happier to see a forthright acknowledgement.

So, for now the answer I’m giving my customers is simple: “WCT is not generally available to customers, although neither IBM nor press reports have made this explicit. Draw your own conclusions about what that says of its deployment readiness and maturity. I can’t comment because I haven’t been able to work with it.” I am hopeful that the strictures on WCT will loosen somewhat when 2.5 ships, but we’ll have to wait and see.