Before you begin
Before you can view Spring beans in an application using the Administration Console, you must follow these steps:
You only need to perform this step once for your domain.
file as a JEE library to your WebLogic Server instance, where
WL_HOMErefers to the main WebLogic Server installation directory, such as
You only need to perform this step once for your WebLogic Server instance.
weblogic-spring.jar is a JEE optional package that
creates the MBeans for your application when you deploy your
Steps include adding the
weblogic-spring.jar file as a JEE library to the
MANIFEST.MF file and adding the WeblogicSpringApplicationListener from
weblogic-spring.jar as a listener.
For details, see Spring Applications Reference
Spring beans are plain old Java objects (POJOs) that are managed by a Spring Framework container; a Spring application contains one or more Spring beans along with optional supporting Spring technologies such as transaction management and database access using JDBC, with an application context that ties everything together.
After following the instructions above, you can view the
configuration of deployed Spring beans using the Administration Console.
When the Spring application is deployed and started,
weblogic-spring.jar creates clusterable runtime MBeans
based on the Spring application context and then registers the runtime
MBeans with the runtime MBean server. For this reason, you can view the
deployed Spring beans' configuration.
Note: In this release, Spring bean management is read-only; you cannot use the Administration Console to change the configuration of a Spring bean.
The following links provide information about the Spring bean tasks you can perform using the Administration Console:
For more information about Spring support in WebLogic Server, see Spring Applications Reference in Developing Applications with WebLogic Server.
For information about creating Spring beans, see the Spring Framework documentation.