Eclipse as a CMS frontend
by Volker Weber
Wolfgang Schmidetzki, CEO and founder of Innovation Gate, gives his views on what makes or breaks the success of a CMS system. He should know, since Innovation Gate is the maker of WebGate Anywhere, a CMS that runs on top of a Java application server, with the backend provided by Domino or any SQL RDBMS. One of the difficulties is providing a user interface that can be used by the casual user as well as the power user. While most CMS utilize a browser interface that is lacking in terms of features and functions for the power user, IT organizations generally do not like to roll out client software for a CMS. WebGate originated on the Notes platform, so that was not so much of an issue before moving into the Java space. Now Wolfgang is giving us a glimpse of what he is up to:
This is a preview of things to come. Wolfgang is using Eclipse as the application framework for the content management application. Eclipse provides all the widgets he is missing in a web browser, and it is relatively easy to maintain. Of course this would be a very good fit for Workplace, and it probably could be turned into a Workplace application but then he would need an IBM server to maintain the client.
Comments
Yes, a Workplace application would need a Workplace Server to run. But he could use a lot of functionality within the product too. E.g. Instant Messaging, local secure data store, single sign on or the integration of Domino based apps to name a few.
Using thes platform functionalitie allows you to focus on the core product and make it more stable, more feature rich, less expensive or something else that helps a product on the marketplace.
Of course for some customers the Workplace Server may be a no go, but how many software solutions on the market require e.g. MS Office or Photoshop or Domino to be able to run?
As I said, you could turn this into a Workplace application. It depends on whether the benefits justify the cost.
It's the same thing as with "any SQL RDBMS". This gives an ISV greater market opportunity than saying "requires Oracle" or DB2 for that matter. If you need to roll out a middleware platform before your first user can start using your application, you may be blocking yourself. By going the open route — in both standards and open source — you can avoid a vendor lock-in. Eclipse is open, Workplace is not.
Help me do a little bit of math: Assume a two-processor server and two dozen concurrent CMS clients. How much would I have to spend to get the IBM middleware stack on that machine? DB2, Websphere Application Server, Workplace Server, Workplace clients for the CMS application. Would I have to license every person in my company, if he may at one point in time want to enter information into the CMS?
@Volker
Well this exactly is one of the cool things in the Workplace world. You pay for functionality not for the stack. You won't have to buy all the goodies which make up the technology platform (WAS, WPS, DB2, ...). They are part of the package. Contrast this with on of the competitors where you'll be buying the DB server at additional cost to be able to scale.
For most of the products you can buy per user (named user) or per processor licenses. So if it fits better, just do a per processor licensing.
@Arnd:
You don't get WAS, WPS, DB2, ... for free. Not only do you have to pay for it (also you propably don't need it) you also have to install it and keep them running 24 houres. You need administration and developer knowledge ...
We may have a workplace client for WebGate Anywhere one day - but we start with a stand alone RCP Eclipse client to make things easier - for us and our customers.
Arnd, you have the scenario. Let's see the numbers. How much does one have to pay?
Your competitor is Apache, Tomcat, Postgres.
@Wolfgang
Did I write "for free"? Of course you need to buy the Workplace product. What I said is that you will get the whole stack with one license. What would you need to buy from MS? The number of product coulsd easily reach double digits.
Now what I see of the products is that for a Workplace installation the need for deep technical knowledge of WAS, Portal, DB2 is rapidly decreasing. For a high volume installation you schould of course have the admin skills, but this is true for every solution.
@Volker
You wouldn't expect to see a number in here. I am 'only TechSales'. But you can get a Workplace for less than $ 3.000.
If Apache, Tomcat & Postgres is the best solution (meets requirements and best TCO) then go for it. But as discussed earlier, Workplace can bring in Features that may change the equation. As we all know, acquisition costs are only a part of TCO. So buying a packaged product that brings the necessary functionality may be better.
Arndt, I actually do expect to see some numbers if you want to be taken seriously. You have argued I can buy by processor or by user. The scenario looks pretty simple to me: one box, two CPUs, two dozen concurrent users from a company of say 500 people. If you are "TechSales", you should be able to cough up a number here.
I know there are different prices for everybody depending on how much they already spent, so I give you a good margin of error*. If you say 20.000, I am OK, if it's only 10.000 or if it is 40.000.
Regarding the "tech": If I could run this application easily within 1 gig of RAM on Linux with Apache, Tomcat and Postgres, how much would I need to add for Workplace?
*) This is actually a very wide margin. Anybody could cough up 20.000 for a VW Golf, if he is allowed a margin from 10.000 to 40.000. That is anybody outside of VW. An insider could probably do much better.
