Kenamea Inc. this week is ramping up a new version of its Web messaging platform designed to facilitate two-way application data flows between back-office systems to remote workers' desktops, trading partners and customers.
With Kenamea Web Messaging Platform Version 2.0, the San Francisco-based company is applying more muscle to the solution's core Kenamea Message Switch, while also expanding back-end interfaces and front-end platform support, according to John Blair, corporate development officer at Kenamea.
"It's a major turn of the crank," Blair said, touting improvements to the software-based messaging hub that resides on the network to shuttle back-end application logic and components beyond the firewall to a range of external clients and other systems. Of particular note, Version 2.0 ramps up the switch's speed and availability, boosts application throughput, and provides more clustering and load-balancing support, he said.
On the back end, Kenamea has added an open standards messaging API that can tap into any enterprise system supporting HTTP, which simplifies connectivity to Web-based clients and business logic, Blair said.
Now Kenamea applications can talk to Web systems including Java servlets, Java Server Pages (JSPs), Active Server Pages (ASPs,) and Common Gateway Interface (CGI). Previously, communication of this type required the use of J2EE (Java 2 Enterprise Edition) or J2SE (Java 2 Standard Edition) interfaces, Blair said.
A new messaging system is a bit of a tough sell considering all the proprietary messaging systems, said Shawn Willett, principal analyst at Sterling, Va.-based Current Analysis Inc.
Willett pointed to such messaging systems as MQSeries, Tibco Software Inc.'s Tibco, and Microsoft Corp.'s MSMQ as well as the newer standards-based messaging systems such as JMS, and business-to-business-specific ones such as ebXML.
"[Kenamea] will have to come up with some compelling reasons to switch to their system, [and] needs to differentiate in terms of functionality, then map that to actual applications that are being built today," Willett added.
He continued that Kenamea needs to make it very easy to connect into third-party tools, adapters, and applications because JMS and MQSeries, for example, have extremely broad third-party support.