ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Application development Toolkit

IBM, BEA brew up Java strategy

Martin LaMonica CNET News.com

Published: 25 Nov 2003 16:30 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

IBM and BEA Systems, usually staunch rivals, are collaborating on ways to smooth out technical differences between their respective Java software lines.

The two companies on Tuesday announced that they have published specifications for three additions to their products that would make it easier for customers to run programs on their respective Java application servers. The changes are expected to be fully implemented within BEA's WebLogic and IBM's WebSphere in the next major release of their products, both due next year.

IBM and BEA will submit the specifications to the industrywide Java standardisation effort, called the Java Community Process, and will make the guidelines available to other companies without charging royalties, the companies said.

The two companies, which are in a battle for the top spot in the market for Java application servers, have already collaborated on other technical specifications in Java as well as Web services standards. IBM and BEA garnered about two-thirds of the revenue for Java application servers in 2002, according to market researcher Gartner Dataquest.

Executives from both companies said that the effort to create more common technical underpinnings for their Java server software was in response to requests from customers and independent software vendors (ISVs).

"We faced feedback, especially from ISVs, which [were less interested] in new features that are WebLogic-specific than ones that were common with WebSphere," said Scott Dietzen, chief technology officer at BEA. "This bridging strategy allows us to get common technology and certainly make it standard over time."

The Java 2 Enterprise Edition standard is designed to allow customers to run Java applications on application servers from any provider. But in practice, there are significant differences between products. ISVs, for example, generally create a version of their add-on products, such as performance-tuning tools, for both IBM's WebSphere and BEA's WebLogic.

The common tools will make it simpler for a company to write software that runs on either application server and will give ISVs an easier and quicker way to build add-ons for both products, executives said.

The three technical specifications are these: Service Data Objects, which provides a common way to pull data from multiple data sources, such as Extensible Markup Language-based file systems and relational databases; Timer for Application Servers, a mechanism for scheduling processing jobs; and Work Manager for Application Servers, for setting up processing tasks in parallel.

IBM plans to implement the specifications in the next major release of WebSphere, which is due next year, said Rod Smith, vice president of emerging technology at IBM's software group. IBM expects to release a developers kit for Service Data Objects next week.

One analyst said that the collaboration between IBM and BEA is notable for its exclusion of Sun Microsystems. Java steward Sun directs the Java standardisation process and controls the Java brand, but with only single-digit market share, Sun's Java server products lag behind BEA and IBM significantly, according to Gartner Dataquest numbers.

"You could say this announcement is the beginning of the end of Sun's leadership in the Java space, as the two market leaders are now collaborating explicitly on driving the direction of Java," said Jason Bloomberg, an analyst at research firm ZapThink.

IBM's Smith emphasized that the three specifications will be submitted as Java Specification Requests, or JSRs, which are then developed into standards through the Java Community Process. Java standardisation efforts typically take about 18 months.

"Each of these areas doesn't have a direct parallel [in the JCP]. They are very natural JSRs and in no way are we suggesting an alternative to the Java standards approach," Smith said. "Getting them into the JCP is the next step and getting the broader community to adopt them."

  • Email
  • Trackback
  • Clip Link
  • Print friendly Print with Dell

Did you find this article useful?
173 out of 258 people found this useful


Full Talkback thread

0 comments

Company/Topic Alerts

Create a new alert from the list below:






Related Jobs

Business Objects XI developer/Consultant 40-60K + bens

You will manage the Business Objects Reporting environment, design Business Objects universes, and you will also be expected to interpret and analyse ...

Market Data Project Manager / Business Analyst Tier 1 Investment Bank

Market leading Investment bank requires strong Project Manager/Business Analyst You will be working in the Market Data Projects team, which has the ...

Applications Management Team Systems Support Analyst - 00059405

To follow incident management processes in order to respond to support requests assigned by the helpdesk team - To follow change management processes ...

Discussions

AdamW AdamW

Linux, Laptops and Dual Displays

Saturday 26 July 2008, 6:34 PM

2 comments
keithmv keithmv

Password Deadlock

Saturday 26 July 2008, 12:02 PM

2 comments

Featured Talkback

The fact is: Software developers today are really designers and not coders. The reason that business anlaysts exist today to model solutions is because they understand the value of designing software before writing it. All too often developers create code that has little value because they do not understand that business classes interact with other classes within the confines of a working model or pattern.

By: 1000165269

Read full story:
Making sense of agile modelling