Say we want to add (or start) managed server instances when running an application, for example, when the number of open sessions reach a certain value. For this value we have calculated that the memory consumption is beyond a level, such that the garbage collection is affected. By adding (or starting) a new server we balance the load (the number of sessions with its corresponding memory consumption) across multiple servers. By using the WebLogic Diagnostic Framework, we can collect the metrics we need and create a watch for that metric with a corresponding notification. By using this notification we can then further create the logic needed in order to add (or start) a managed server. For example, by using the notification service that come with the WebLogic Diagnostic Framework we can send a JMS message or a JMX notification. In this post we are going to use the JMS approach. Environment The WebLogic environment consists of a cluster, spanning two machines, and consisting of four managed servers. This can be easily set-up by using the scripts presented in the post Automate WebLogic 12.1.2 Deployment. The diagnostic module is configured as follows – See more at: Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.