BEA Systems Inc says that it was considering an OEM relationship with application server company WebLogic Inc before it decided to acquire the company last week. BEA says it went ahead with the acquisition because WebLogic was the only company among its competitors to have implemented 10 out of the 12 Java services APIs. BEA itself was working on the other two – Java-Corba mapping and the JMS Java messaging system – for its Iceberg Java enabled version of its M3 object transaction manager. WebLogic’s Tengah gives BEA access to native implementations of Enterprise Java Beans, RMI, JDBC, JNDI naming and JTS transaction services, among others. Tengah is likely to be used by BEA customers as a business logic and presentation layer to their transaction processing systems, while WebLogic customers looking to scale up their applications can now link into BEA’s full-scale Tuxedo transaction processing system. Adding end-to-end support for transaction services to Tengah is ongoing, and BEA won’t reveal the time-scales. WebLogic also gives BEA access to a new indirect sales channel. WebLogic will be run from San Francisco by Alfred Chuang, the chief technology officer at BEA as a separate division. Meanwhile, DECmessageQ 5.0, the newest version of the messaging system BEA originally acquired from Digital Equipment Corp, is due out this month or early next. It’s currently code-named Igloo.
Content from our partners
