JBoss Open Choice, Part 1 – JBoss Enterprise Web Server

Posted on by Rich Sharples

It’s July 4th and we have an extended weekend in the US which is a good enough excuse to catch up on some blogging; at least until the Strawberry Margaritas start flowing. At Java One this year we announced an initiative called Open Choice which I blogged about previously. Fundamentally Open Choice is about broadening our footprint and giving customers what they want and moves us closer to supporting the whole applications infrastructure tier rather than just parts.

Open Choice isn’t some big, far-into-the-future vision thing it’s something we’re doing now. This year. Product-wise it consists of four offerings (where previously there was only one) and as we release them I’ll give you my perspective on why they’re important. Unfortunately I’m already a little behind – we’ve already delivered two products out of four and the third is in Alpha moving quickly towards Beta.

So let me use this post to talk about JBoss EWS 1.0 (Enterprise Web Server). EWS is basically a packaged, certified and tested bundle of Tomcat and Apache HTTP – the industry’s dominant Java web-container and Web Server respectively. We round out the bundle with mod_jk, APR and most importantly a management agent for JBoss ON. We currently support and certify on Red Hat Enterprise Linux and Solaris with Windows coming next.

Providing JBoss ON management support is pretty important – it gives customer the ability to manage the application and web stacks easily and consistently using the same toolset. If you want to learn more – there is a free Webinar on July 14th at 2pm Eastern – more here.

The rationale for supporting Tomcat is that it is absolutely the dominant Java web-container and has become an important part of the corporate IT fabric. Tomcat has been popular for years but in the last two or three  I’ve seen it evolve into a much more strategic platform for IT. Many customer I speak with have defined two distinct tiers of functionality – essentially a full Java EE stack and a lighter-weight Tomcat platform. By supporting both the dominant Java EE implementation (JBoss EAP) and Tomcat, combined with the ability to manage from a single tool – I think we can do a much better job of satisfying a much broader customer base than our competition. Here’s an (albeit unscientific) chart from a recent survey that demonstrates this well :

Most often use Java EE containers

It’s also interesting to note that from this survey JBoss’ deployment share is more than Websphere and Weblogic combined.

OK, so JBoss EWS 1.0 is out and we have customers deployed or deploying some pretty large, strategic apps. but I’m already thinking about the next version (code named Cavalier). Some initial ideas for Cavalier are :

  • increasing platform support to include AIX, HP-UX and maybe other Linux flavours;
  • alternative Connection Pool implementations for Tomcat;
  • looking at a more recent version of Apache HTTPD;
  • possibly supporting mod_cluster.
  • soft-appliances to better support virtualized hosts.

Any other thoughts are always welcome – leave a comment or get in touch directly.

JBoss + eXo = Open Source advantage

Posted on by Rich Sharples

jboss-exo

This week, we announced a partnership with eXo – creator of the Open Source eXo platform. This strategic agreement allows us to integrate and distribute each others’ technology thus providing a mutual competitive advantage. This is no doubt good for both company’s products but I think the important point is that JBoss is 1. willing to do this and; 2. able to do this.

Taking the first point – “we’re willing to do this”. I think it shows a level of maturity in our organization that stands us apart from some of our Open Source competitors. The realization that not everything needs to be invented here; that there are smart people outside JBoss as well. There’s a tendency – call it NIH Syndrome, Professional Pride – to want to own and control everything; that’s true for every engineering and product company I’ve ever worked for. When taken too far – that can be at add odds with Open Source and diminishes some of its advantage.

Taking the second point further -  “we’re able to do this”. Our business model is still pretty unique – we put less value on the bits and more on the whole experience. Control of the technology is less of a competitive advantage than some of our competitors because we have more to offer than the bits.

While proprietary software has some advantages – they’re all based on the premise that your technology is better than your competitors and keeping it hidden maintains some kind of advantage. This can only really be true half the time.

Red Hat has the knowledge and experience that allows us to collaborate, allows us to integrate and support technology that we don’t outright control. We’re also confident in ourselves, our brand and our business strategy – and that allows us to see the act of ‘enriching’ other technology (like Apache, OpenJDK, GWT, eXo, etc.) as a way to grow our footprint, capabilities and potential rather than as a competitive faux-pas.

Update :

Some more info on the agreement from eXo : About The eXo Partnership

Tab Sweep : JBoss

Posted on by Rich Sharples

From the “release early and often” files :

JBoss Messaging 2.0 beta is out. According to JBM lead, Tim Fox – New features include, performance, performance, performance, flexible clustering, seamless high-availability, large message support. See Tim’s announcement for details.

Thomas Diesler has some thoughts on how the JBoss Microcontainer could fully implement the OSGi spec. It will be interesting to see the results of this and it will be a great example of the power and flexibility of the JBoss architecture. JBossOSGi 1.0.0 Beta2 was released last week.

If you are eager to try out Eclipse 3.5 / Galileo and want to explor the upcoming features in JBoss Tools / JBDS you now can – JBoss Tools 3.1.0.M1 is available. See what’s new and noteworthy.

The recently released Seam 2.1.2 includes improved support for JAX-RS (RESTful web services) – more details here.

Finally, we have a free online seminar tomorrow (June 10th) at 9am EDT, 3pm CEST which covers Web Beans (JSR-299 / JCDI – Java Contexts and Dependency Injection). More details here.

Final thoughts on JavaOne 2009

Posted on by Rich Sharples

As expected, JavaOne was interesting. For the first time in 12 years I actually attended more than a couple of sessions; but that isn’t why it was interesting. It was interesting because we witnessed the ceremonial passing of the Java One torch from Sun to Oracle and a fairly public goodbye from Schwartz and McNealy.

By all standards it was a pretty lightly attended Java One – I expected it to be a lot lighter given the economy, the uncertainty around Java and the Bacon Fever – so I was actually pleasantly surprised. Outside of Sun itself – I think JBoss was probably the largest software vendor on the pavilion floor – that says something.

Despite the low attendance overall – we had very solid attendance at our mini-theatre sessions – I think ours was one of the few booths that drew a crowd (without having to give stuff away) – so all in all it was a good show for us.

I’d be very surprised if this wasn’t the the last Java One; and as the crews started dismantling the pavilion – I felt like I should be trying to rip down a sign or banner – some memento to remind me of the fun times I’ve had at Java One over the years.

A lot of people were questioning the future of Java at the show (as usual) but I still firmly believe it’s going to be safe enough for the next 20 or 30 years – more than long enough for most of us. I don’t think Oracle will do anything stupid; though given the size and complexity of Sun I think they’re bound to make mistakes – it’s up to us to tell them when they do and to help resolve them.

As anyone who knows Java One – it’s about the people you meet – not the content. And so it is with Java – it’s about the people / community / ecosystem – at the end of the day – no single company has really owned Java for a long time.

Update : My pictures and Marek Goldmann’s pictures on Flickr.

JBoss Open Choice

Posted on by Rich Sharples

Earlier this week we announced a couple of things. First, a change in our platform strategy, second some new products to implement that strategy. We felt we had to give that strategy a name and “Open Choice”, while unoriginal, best illustrated what we’re doing. And what we’re doing is expanding our support to include Open Source technologies  beyond what we’ve typically supported and beyond the JBoss constellation.

This is a reaction to a) customer demand; and b) the realization that not all the cool stuff is created by JBoss. What we’re also doing is reacting to market demand. Java EE, while hugely successful is not the only game in town any more.

j2ee-spring1

We want to ensure that our customers get to choose whatever frameworks, languages, development models they want without causing major disruption for the operations people who have to manage the applications for the other 90% of the application lifecyle (ie. outside development). We also want to remove the risk of deploying new developer oriented tech. by providing a stable, consistent operational footprint (JBoss) to run the resulting apps.

Note – I normally don’t use Job Trends data in isolation to make serious decisions, but it’s convenient and lazy way to find what keywords are trending.

So yes, this is a reactive move; we’re reacting to customer demand and market pressure – we’re really not reacting to anything that Spring Source is doing. I’ll post another blog explaining what we’re including in our Web Framework Kit and why; but Spring Framework is included for much the same reason as struts – they’re mature technologies and both are very widely deployed :

spring-struts

It’s no secret that a big chunk of our business comes from our much larger but less nimble competitors and we have to ensure that migration is a simple and low risk proposition.

spring

As the chart shows (if you have any faith in the data) – Spring Framework usage is fairly evenly distributed across the Java container landscape. By making JBoss a better place to run Spring (among other things) – I believe that we can change this landscape dramatically.

This really isn’t about Spring Source – in fact we don’t even compete with Spring Source. Our sights are set much higher.

Tab Sweep : JBoss

Posted on by Rich Sharples

Another couple of super-busy months here at JBoss. If anything the pace of new releases and new projects is increasing. Here are some of the more prominent Community announcements I managed to bookmark :

JBoss App Server 5.1.0 CR1 – 5.1 is a pretty big milestone – it includes the new Jopr powered embedded console  – something you’ll like but also something we really need some early feedback on. Also a preview of Web Beans / JSR-299. [release notes, downloads]

Data Integration goes Open Source – I missed the launch of the Teiid Project you can find out more on the project page.

This has been brewing for a while and Manik has finally announced Infinispan – I predict that this is going to  be a pretty disruptive technology. [home page, quick guide]

JBoss Tattletale is a new tool that will analyze your code and produce detailed dependency reports – for example highlighting duplicate jars / classes, missing jars / classes, etc. [downloads, project]

The latest release of Jopr (2.2) is out – Jopr is the upstream project for JBoss Operations Network (see below). There are a shedload of UI enhancements, support for JBoss EWS and Performance improvements among other things.

Also a nice article on JBoss Cloud over on DZone.

On the JBoss Enterprise side of the house :

JBoss Operations Network 2.2 is out and JON receives a pretty decent makeover (see Greg’s post on some of the major enhancements) – product page is here.

One of the new capabilities of JON 2.2 is support for JBoss Enterprise Web Server (EWS) which was also released a few weeks ago – more on that in a future post.

If you’re currently stuck with Oracle Weblogic or IBM Websphere and need help getting off – here’s an opportunity you can’t ignore.

Sorry for the length of this post – I need to do this more frequently. The next couple of months are going to be even more hectic and you can follow the @JBossNews via Twitter. Finally, something from the happy news files – we’re still hiring.

Snoracle

Posted on by Rich Sharples

I’d like to think of myself as an informed prognosticator having worked for Sun for almost 9 years; but this is prognostication nonetheless. I missed my chance to say what I thought of an IBM acquisition but I’ll start by saying – I think I preferred it – it probably would’ve been a better outcome for the things I care about.

The things I care about are the people I know who still work for Sun, the Java ecosystem, and many of Sun’s Open Source projects that I directly or indirectly benefit from – specifically MySQL (this post will live in MySQL), OpenJDK and OpenOffice.

It still seems like a strange merger – sure, Sun and Oracle have a huge shared installed based – Sun Servers + Solaris + BEA + Oracle DBMS was the killer enterprise stack for a decade – that alone gives Oracle a vice-like grip on existing customers; but that’s about the past – not the future. I think someone did the analysis and realized it’s a marginally positive move – so I don’t think this is the big technology vision realized that Oracle are trying to promote.

I’m sure a lot of people at Sun and customers of Sun are glad the uncertainty has come to an end but unfortunately it hasn’t. I’m guessing that it will take until the end of the year before Oracle tells the world what they’re keeping and what they’re dropping. FWIW – here’s my informed guess :

Storage / Servers – the press-briefing made the merger sound like it was all about the hardware (servers and storage). I just don’t see Oracle as a hardware company and they have more to loose than gain by pissing HP off. I wouldn’t be at all surprised if some or all the hardware got sold off to HP, Fujitsu, etc. And I think Oracle could probably recover $3.5-4 bn of their $5bn outlay by doing so.

NetBeans – I’m not changing my mind – it’s done for. Oracle has two Java IDEs already – they don’t need a third. Oracle will pick up some great tools developers to write a migration tool but that’s about it.

OpenOffice – Oracle doesn’t like M$ but I doubt they can find a fiscally rational reason to carry the torch for Open Source and at the end of the day Oracle are doing this because it makes financial sense. I think Oracle will expect “the community” to pick up the slack.

Solaris – I think they’ll milk the legacy installed base (which is huge) but the innovation won’t continue. I think there’s an interesting opportunity for Oracle to manage the migration of the last of the Solaris holdouts to Linux. They could do this by GPLing Solaris and moving some of the Solaris features to Linux; or more likely to an Oracle proprietary OS built on Linux.

Middleware – Oracle have everything Sun has – and Oracle are by and large market leaders with large market and revenue share. Sun have one or two products that might survive and certainly some components. Oracle inherit a commitment to continue to produce the Java EE RI (and others) so Glassfish *might* survive – but Oracle have demonstrated that they don’t have appetite to maintain many products in the same market (see how quickly OC4J got killed after the BEA acquisition ?)

MySQL – I think Oracle will continue to do what Sun did somewhat accidentally – namely slowly kill it off.

Java – I’m confident that Oracle won’t fix the JCP and won’t sacrifice control for the good of the ecosystem. I also think the JCP will become a battlefield for IBM and Oracle and we’ll all be the worse for it.

OpenJDK – no-body needs two JDK’s to maintain – I think Oracle would have to move some of the monitoring / diagnostics from JRockit into a proprietary OpenJDK-based platform. JRockit has a small market share but some nice features for enterprise customers.

Cloud – not that there’s much there there but I don’t expect to see Larry eating his words.

Virtualization – I don’t really understand Oracle’s virtualization strategy other than the feeling that Larry Ellison is unlikely to entertain anything that looks like it might actually save customers money on licenses.

The best $1200 you could spend this year

Posted on by Rich Sharples

Unsurprisingly and from what I’ve seen personally – tech. conference attendance is a little light this year. But if you have some budget for attending tech. conferences – I think the combined JBoss World / Red Hat Summit (Chicago, Sept 1st-4th) could be just about the best investment you make this year.

You’ll learn about all the great tech. that Red Hat and JBoss will be shipping as well as some of the technology still in the labs. But most of all you’ll learn how Red Hat can save you and your organization money – and right now that’s got to be a smart investment.

* travel and accomodation extra

Tab Sweep : JBoss

Posted on by Rich Sharples

JBoss adding muscle to Apache CXF. We’ll be increasing our commitment to Apache CXF – in term of both resource and expertise and fully support CXF in future versions of our products. More from Alessio Saldano (JBoss WS Lead), Dan Kulp (PMC Chair for CXF) and Sacha (JBoss CTO).

Talking of Sacha – he’s just announced he’ll be leaving Red Hat. Sacha interviewed me when I joined Red Hat (just under a year ago) and I’ve enjoyed working with him – super-smart, very passionate and a genuinely nice guy – a rare combination. Good luck for the future Sacha and enjoy the break – after 8 years you deserve some R&R and time with with your family.

The JBoss Tools team delivered another major release – JBDS 2.0 and we also introduced JBDS – Portfolio Edition – which included the run-times for all the new features in JBDS 2.0.

JBoss continues to slash costs – two more customer success stories, first Covad (provider of data, voice and wireless telecommunications) who moved to JBoss from “inflexible and costly proprietary middleware software” because “That’s why we love JBoss– it allows us to do more with less,”.

IWBank (online banking and financial services) of Milan also selected JBoss because “JBoss enables us to provide more and more efficient and affordable services, which is crucial in the current economic climate”.

Finally, JBoss will be a mentoring organization in the Google Summer of Code (GSoC) – you’ll have the chance to work with some of the smartest, most exerienced Open Source developers in the business. Head over to JBoss wiki if you are interested.