Always wished you could use Spring Insight but couldn’t because your applications run on Oracle WebLogic? Wish no more!
Originally introduced for tc Server and since expanded to support Tomcat and JBoss , our next release will include full support for the WebLogic container.
Combined with some specific WebLogic plugins that we have in our pipeline such as WebLogic Portal, WebLogic Tuxedo, and WebLogicMQ , Spring Insight will give WebLogic developers deep visibility into their application’s runtime performance and behavior.
WebLogic support will include:
- Versions 12.1 , 10.3 (a.k.a 11g)
- Windows and Linux
- Oracle HotSpot JDK, JRockit JDK and OpenJDK
- Instrumentation of applications packaged as WARs and as EARs. This includes all class loader configuration options such as using shared JARs from the lib folder, using the prefer-web-inf option or the prefer-application-packages (configuring filtering class loaders) option.
- Out-of-the-box installer to provide installation for the administration server of your WebLogic domain. A few simple steps will get it running on any other managed server you choose.
A word on Spring Insight support for non tc Server containers:
If you can run your application on tc Server, using the developer edition is still by far the quickest way to use Spring Insight.This gets even better if you are using STS and can therefore utilize our STS plugin that allows you to run your application from within the IDE on an Insight-enabled tc Server instance.
However, we want people who are writing Spring applications to have this valuable tool irrespective of how their applications are deployed.
The new WebLogic support, combined with the previous tc Server, Tomcat, and JBoss support make Spring Insight available for a very large percentage of Spring application developers.
Support for more types of middleware is underway (hint: not necessarily only for Java containers ;).
Ever wondered what the effort to support a new container comprises?
Here’s a very brief explanation to those out there interested in this question.
The Spring insight application uses load-time weaving (via AspectJ) to monitor your application. This instruments the code so that it gathers data on execution and time measurements.
This step has to be implemented for each container in a slightly different way, and requires intimate knowledge of the intricacies of the container’s class loaders and class loading mechanism, structure of HTTP requests and responses, and application loading logic.
WebLogic support will be available in the next major release of AppInsight and Spring Insight. If you would like to be a Beta user, drop us a note here. We look forward to hearing your feedback.