SAP NetWeaver Cloud developers can now join the rebellion against Java Redeploys
ZeroTurnaround, the creative minds behind the Jolt-and-many-other-awards winning JRebel productivity tool, have taken a very special mission – to enable Java developers to break up with the application builds and redeploys. The tedious experience of building, transporting and redeploying Java applications is under heavy pressure to shrink to essentially… zero. Starting today – this rebellion has expanded also on SAP NetWeaver Cloud territory.
Rapid Application Development
I myself am fully convinced that seeing the results of just-developed code in real time will inevitably change the way how people develop software in Java. SAP NetWeaver Cloud on its own is an illustration how software can be delivered on a bi-weekly schedule. Joining the ZT-lead redeploy rebellion nicely complements the mission it has gotten from SAP’s CTO Vishal Sikka during SAP TechEd 2012 technical keynote in Madrid:
“You [Developers] focus on your cloud application, we [SAP] will do the rest!”
Of course on our side we take those goals very seriously. Only 2 weeks have passed since Matthias Steiner published his thoughts on what would be the right direction to invest in for organization aiming at higher productivity. His message is that huge productivity boost is achieved not by making click-around tools for very narrow set of scenarios, but by providing Developers with efficiency tools, which take care about all the needlessly boring and highly repetitive time-wasting day-to-day tasks. His article became one of the most viewed pages on SCN, accumulating close to 30K visitors in the course of it’s 2 weeks of existence. This is only to confirm a suspicion we were having – that developers are actually interested in SAP NetWeaver Cloud. I believe that JRebel Hotpatching Technology at developers’ fingertips greatly supports and complements all of that.
Open Source and Open Standards – why mention that here?
Our Chief Product Owner Harald Mueller has explained during the SAP TechEd 2012 Madrid show that
“SAP NetWeaver Cloud application runtime is based on Eclipse Virgo server. In order to be successfull and evolve the technology forward, SAP is actively contributing and closely working with the Virgo community.”
For those of you who have followed JRebel releases more closely – there is a very modest, almost invisible, but at the same time – critically essential part of the JRebel 5.1.1 release notes from earlier this week. It states the following:
Added support for Virgo 3.6
No big deal, some will say… I’m sure you’ve already connected the dots, right? Although minor looking – this one single release notes line plays a central role and I believe – sits in the base of JRebel integration with SAP NetWeaver Cloud. I don’t think I need to emphasize more on how critical to the success of a our development platform is the use of well established and proven OpenSource technologies.
Skeptics kicking in right away
“But wait a minute” some would say. “Doesn’t Hotspot JVM already support hot code replacement during debugging? So why not just use that (it’s for free after all, right)?”. Well – no! Here are some details on what features are supported on both ends, leaving it up to developers to be creative and figure out what productivity gains can now be accomplished.
Another prominent group of skeptics will inevitably raise the concern about reliability – will hotpatching work in all cases? As Mathias has outlined as well – silver bullets are nice, but unfortunately – also quite rare. You can take a look at the JRebel set of supported frameworks. In case your favorite one is not included (Come on! Admit it! Did you build it yourself and never gave it to anybody or what?) – you are still free to go back to the “redeploys kingdom”.
Early adopters are more than welcome
Setting up the environment seems to be non-trivial, however once achieved – the same frame can be used to JRebel-enable any application deployed to the cloud.
What doesn’t seem to be explained too much is how to actually get the JRebel Eclipse tools in place. I believe this is due to the fact that setting up JRebel Eclipse plugins is already well described in all possible details as part of the official JRebel product documentation. Just don’t forget to read carefully the How-to: Setting up JRebel wiht SAP NetWeaver Cloud to the end. Missing some of the final steps there will cost you lots of time and confusion.
I’ll blog in the next days about my own end-to-end experience in using JRebel on SAP NetWeaver Cloud – stay tuned!
Try It Out!
At the end – I feel obliged to remind again what we’ve been telling over and over again during all the 3 TechEd events in the course of the last 2 months: For every single feature of SAP NetWeaver Cloud – we constantly urge you to try it out and share your feedback. I admire the fact that the ZeroTurnaround team behind JRebel has adopted the same practice and is seeking to actively engage and get feedback from the developers’ community.
As Toomas Römer has outlined in his blog yesterday – the current SAP NetWeaver Cloud integration is in an early stage and is still not part of any official JRebel release. Both the tools and the server-side integration are accessible via the ZeroTurnaround early-access channel.
The obvious benefit of that approach is that it allows any user to:
- get a JRebel free trial license,
- follow the setup instructions here and here,
- experience the productivity gain on a SAP NetWeaver Cloud TRIAL account
- provide feedback back to ZeroTurnaround.
We’ll of course would be extremely happy if you also share your experience on our Cloud Developer Center discussion forum
After looking closer at JRebel release schedule – SAP NetWeaver Cloud will (probably) be supported in the final JRebel 5.1.2, which will (hopefully) come right around Christmas. An amazing Christmas present for the SAP NetWeaver Cloud developers’ community. I’m looking forward to see the release notes of this one. 😉
To ZT: Keep on rocking guys! Your fan club just increased with some new members 🙂 .