Sam Pullara

The Java Management API (JMX) has been integral to managing the WebLogic Server since WebLogic 6.0. Through this API you can search for management beans (mbeans) within the application server and query them for both configuration information and runtime monitoring information. In addition, this API can be used to actually change the configuration of the server. In fact, this API is used internally by the console and other administration tools to do their work and report their data. This API can be a powerful tool for monitoring. Let's look at an example. In this application, you... (more)

CMP 2.0, EJBGen, and Builder Make EJBs Easy!

EJBs have always been the best way to ensure that your applications were portable and would leverage all the optimizations of the J2EE server. Now they are also easy to build. With the release of WebLogic Platform 7.0, you can create EJBs in record time. At the center of this revolution is Container Managed Persistence 2.0, which allows WebLogic to build tools that remove the layers from... (more)

Integration via Web Services

WebLogic Server 7.0 contains the most advanced, performant, and standards-compliant Web service stack of any application server. With an additional download (until the JAX-RPC specification goes final - it may by the time you see this article - see http://jcp.org/jsr/detail/101.jsp) you get a Java standards-compliant Web service stack that also passes the SOAP interoperability tests. So ... (more)

Migrate Early, and Often:Maintain your flexibility to upgrade when the time comes

Working at a software company and watching products evolve over the years, "Migrate Early, and Often"is the best advice I can give someone who is trying to stay on the cutting edge of technology. Obviously, if you have an application that's in production with no problems and you aren't planning on adding any new features, then of course keep the same version of the underlying platform. H... (more)