gpoul's Out Of Memory Blog

The WebSphere Application Server V8.0 Beta is now available.

Update 7/9: Andrew posted that the download is now fixed and he also included some helpful links to get started with trying the beta.

You learn something new every day. Looks like Lombardi uses GWT for Blueprint and the web portions (i.e. everything that’s not Eclipse-based) of Teamworks. There is a video on the GoogleDevelopers channel where Alex Moffat showcases Blueprint and describes why they chose GWT.

In addition they’ve also been demoing their solution as part of the Google I/O 2010 Sandbox this week.

btw: Lombardi is an IBM company.

A few recent WebSphere announcements we presented last week at Impact 2010:

• WebSphere DataPower XC10 caching appliance – also known as the eXtreme Scale with SSD in a purple box
• WebSphere CloudBurst Appliance 2.0 – now featuring WebSphere Process Server support, multi-image pattern support, dynamic system management to add/remove capacity, intelligence for the runtime / WebSphere Virtual Enterprise features packaged as WebSphere Application Server Hypervisor Edition Intelligent Management Pack for use with CloudBurst and Hypervisor Edition, and last but not least we now also support Red Hat Enterprise Linux in addition to SuSE Linux Enterprise Server
• CICS Transaction Server and WebSphere Application Server Feature Packs for Dynamic Scripting – Running WebSphere sMash with WebSphere Application Server V6.1/V7.0 or CICS Transaction Server for zOS V4.1.

Of course by reading it on this blog you’re at least a week late and you missed all the labs and presentations in Las Vegas, but there’s still enough time to prepare for Impact 2011 :-)

PM12112: CHANGE HOW PLUG-IN FINDS ANOTHER SERVER IF THE AFFINITY SERVER WAS ALREADY MARKED DOWN WHEN THE REQUEST ARRIVES:

When an affinity server is offline, the pending connections will be directed to the next server in the primaryserver list instead of distributed among the available servers. This can cause an overloading of the “next server” which can lead to a cascading failure situation.

Have you already migrated to V7.0 and want something new to play with? Want to port your application to something new and exciting?

Whatever your motivation, you can now participate in the WebSphere Application Server V8.0 Alpha program. If you choose to participate, please take the time to provide your feedback to help us improve the product! [via WebSphere Community Blog]

Update 7/5: The WebSphere Application Server V8.0 Beta is now available.

Due to the enthusiastic attendance of our IBM Software Experience last year we also planned some great workshops for you in 2010!

We start in Q1 with a workshop about Rational Application Framework for WebSphere and WebSphere CloudBurst Appliance and a separate workshop a week later about WebSphere MQ File Transfer Edition.

We hope you’ll enjoy them as much as the ones we had last year! – If you have suggestions for workshops in 2H10, please let us know!

We published our first two results for a new benchmark called SPECjEnterprise2010 a few weeks ago. This new benchmark covers Java EE 5, which makes it much more applicable to today’s applications than the old SPECjAppServer2004.

We’re the first vendor to publish results, which demonstrates our commitment and leadership. – Of course these results will only make sense in context compared to benchmark results submitted by other vendors.

Update 1/19: A press release covering this is also available in the IBM press room.

I was recently discussing with a colleague on how to do caching inside of WebSphere Process Server (WPS). A few days later I stumble upon a blog post linking to a developerWorks tutorial on this exact topic. Good timing, Andrew! :-) [via SOA Tips 'n' Tricks blog]

Update 4/3/2010: In addition to caching the data you might also want to use DRS for replicating the cache in a cluster.

What do you think about hosting a public WebSphere IdeaJam similar to the Lotus IdeaJam? Vote now!

When a request is retried, all servers might not be attempted before failure reported to client.

If you’re running clusters with only two cluster members you might want to apply APAR PK99869 or upgrade to the fix pack as soon as it’s available.