WCS 2.6 successes and woes
Category Collaboration
I've spent most of the last couple of days working with WCS2.6. As I blogged about earlier, the initial installation worked flawlessly and I was certainly impressed. However it still appears that configuring and tweaking the system are the technical challenges that they have always been. Implementing Domino LDAP worked well, but I have spent so much time working through all of the problems with the previous versions that I wonder if others would find it as easy. (While I have not had the chance to fully investigate, it does appear that this version is missing some of the out of the box integration with Domino that was present in the earlier versions. The Domino Web Access Portlet is not part of the base install, and installing the version from the portlet catalog produced an error)
The real issues began when I tried to implement the Managed Client Provisioning Server.
I've spent most of the last couple of days working with WCS2.6. As I blogged about earlier, the initial installation worked flawlessly and I was certainly impressed. However it still appears that configuring and tweaking the system are the technical challenges that they have always been. Implementing Domino LDAP worked well, but I have spent so much time working through all of the problems with the previous versions that I wonder if others would find it as easy. (While I have not had the chance to fully investigate, it does appear that this version is missing some of the out of the box integration with Domino that was present in the earlier versions. The Domino Web Access Portlet is not part of the base install, and installing the version from the portlet catalog produced an error)
The real issues began when I tried to implement the Managed Client Provisioning Server.
A prerequisite is the implementation of an external HTTP server. The most straight forward approach is using the IBM HTTP server that I have had good luck with in the past. Thankfully version 6 was included with original e-image assemblies. However, the instructions say that once this is installed, you must update the version to 6.02 and then install fixes to take to version 6.021. Of course the files for these updates are not included as part of the assembly, even though 6.02 was released last July. Instead, it's necessary to go back to the IBM site and download them. Of course when I get there I am stuck in a quandary. Version 6.021 was superseded with 6.022 etc. back in September and the now current fix pack is version 6.027. Since the electronic version of the info center has a date in February 2006 date, the question is which fixpack version should I use? You would think that since the documentation was completed long after the newer versions were released, there would be some notation one way or the other. In the end I use the 6.021 version. I migrate WCS to use the external IBM HTTP server and everything is working well. I now begin the installation of the Workplace Managed Client Provisioning Server and it consistently hangs with no error message. After experimenting and reinstalling everything several times (thank goodness for Acronis TrueImage) I have finally given up and used partnerworld to initiate a support incident. (A word or praise for this form of IBM support. I have had mixed luck over the last 25 years with IBM/Lotus support, but I have always had very good luck with the email technical support. I think it is mostly housed in various locations around the globe which sometimes creates a time lag - although for those of us that like to work on problems in the middle of the night, it's pretty convenient) Nonetheless, it works, and I am sure that within a day or two I will get a resolution.
As I wait for a resolution it unfortunately leaves me some time to reflect on the whole install process and review a couple long standing complaints.
I recognize that WCS is a enormously complex product with many moving parts as well as being a work in progress. However, my general impression is that the whole installation process does not feel very well thought out or professional. The installations that I have done in the past with previous versions have never impressed me or any customer that choose to participate. In fact several customers have remarked at how very disjointed the process appears. It is pretty clear to me that each module of the program is designed and maintained by a separate group within IBM and as a result there is little continuity to the whole process. While at least the base install is now integrated, way too much of the subsequent configuration process alternates between graphical and command line interfaces. And a great deal of the process requires looking elsewhere for instructions or installation files. I look about my desk and see that I have 8 separate piles of paper printouts along with 3 PDF files on my computer to assist me with the install. As a business partner, it will/would be very hard to convince a customer that walked in on this install that I was dealing with a mature product. (My guess is that IGS/Lab Services approach installations with instructions and implementation programs/aids that are not shared with customers or business partners)
IBM has certainly made great strides with the ease of installation for the base product. But, while the complexity of the product is orders of magnitude over Domino, I believe that as Hannover approaches, the installation, configuration, (and particularly troubleshooting and maintenance) needs great attention and improvement before the majority of customers and partners will feel comfortable with the product.
As I wait for a resolution it unfortunately leaves me some time to reflect on the whole install process and review a couple long standing complaints.
I recognize that WCS is a enormously complex product with many moving parts as well as being a work in progress. However, my general impression is that the whole installation process does not feel very well thought out or professional. The installations that I have done in the past with previous versions have never impressed me or any customer that choose to participate. In fact several customers have remarked at how very disjointed the process appears. It is pretty clear to me that each module of the program is designed and maintained by a separate group within IBM and as a result there is little continuity to the whole process. While at least the base install is now integrated, way too much of the subsequent configuration process alternates between graphical and command line interfaces. And a great deal of the process requires looking elsewhere for instructions or installation files. I look about my desk and see that I have 8 separate piles of paper printouts along with 3 PDF files on my computer to assist me with the install. As a business partner, it will/would be very hard to convince a customer that walked in on this install that I was dealing with a mature product. (My guess is that IGS/Lab Services approach installations with instructions and implementation programs/aids that are not shared with customers or business partners)
IBM has certainly made great strides with the ease of installation for the base product. But, while the complexity of the product is orders of magnitude over Domino, I believe that as Hannover approaches, the installation, configuration, (and particularly troubleshooting and maintenance) needs great attention and improvement before the majority of customers and partners will feel comfortable with the product.
Comments
I've been writing up my experiences on the OpenNTF blog (http://blog.openntf.org) as well if you want to read ahead. At some point I think we should update the wiki with FAQs about WCS install gotchas.
Posted by Anil Vartak At 09:16:59 AM On 2006/02/21 | - Website - |
However, I think it goes way beyond just implementing and configuring the product. Again, I'll probably write a post on it more fully after I get the system fully functioning, but from an administrator’s point of view there are a great many everyday tasks that I have really no clue about performing with WCS:
How do I trace a mail message to see why it was not delivered?
A user leaves the organization; how do I back up their mail and the free up space?
I decide that I want to improve performance by moving a department of several hundred users to a new server - how do I accomplish this?
How do I tune the system for peak performance?
I could go on and on.......
These are all things we struggled with in the beginning with Notes, and I am sure there are answers but the learning curve is going to be very steep. I would like to see a manual or a RedBook called "Administering WCS 2.6". I suspect that when courseware arrives for WCS there will be many, many modules and those of you in the training realm may have very bright futures.
Posted by Kit Davis At 07:41:28 AM On 2006/02/21 | - Website - |
So, I have a question for you about the best way to learn WCS. When I mention to IBM how difficult it is is install and configure WCS, they assure me that they have fixed this problem for new admins and developers by relying on virtual training. Instead of working with actual systems, they will supply reinactments of the actual code (e.g., screenshots and I think a few animations).
Do you think admins trained on virtual systems will be ready for tackling WCS installation and configuration (as it is currently in release)?
Thanks, Jack
Posted by Jack Dausman At 08:42:27 PM On 2006/02/20 | - Website - |
While the BlogSphere is a good way to hook people up that are working on similar tasks, IBM really needs to start another forum like the Business Partner Forum to facilitate collaboration. I suppose it doesn't have to be sponsored by IBM, but having the developers participate would be essential.
Posted by Kit Davis At 09:49:37 AM On 2006/02/21 | - Website - |