Toolkits for Content Management

We have been impatiently waiting for the maturation of java-based CMS components and engines that could be mixed and matched in an appserver to meet specific business needs. It appears now that this approach may be seeing some daylight. Witness ex-NASA developers at Oak Grove Systems, who have built a J2EE-based workflow engine. Put this together with a versioning system and deployment engine, and you have three-fourths of a CMS back end. Best of all, you didn't "build it yourself," you merely assembled it yourself -- and that might be better than buying the whole works from a single software provider, with assembly still required anyway...
Check out Oak Grove's "Reactor 5" Workflow Engine


Our customers say...

"The analysis of the current technology vendors and products is very comprehensive and it provides an excellent guide for potential purchasers to frame their functional, architectural and usability benchmarks."


Len Asprey, Director, Practical Information Management Solutions, and, Author, <i>Integrative Document and Content Management</i>

Other ECM & Cloud File Sharing posts

ECM Standards in Perspective

In real life I don't see ECM standards proving particularly meaningful, and you should see them as a relative benefit rather than absolute must-have.