|
| Re: Configure JMS Resources on EAR Deploy? |
 |
Mon, 12 May 2008 08:13:54 -070 |
Hi,
Is your concern that various items are not configurable in deployable modules?
WLST scripting and mbeans can be used to programmatically configure such items,
as well as for programmatically configuring non-deployable, but fully capabile,
"system" JMS modules. We sometimes use this approach for internal
testing at WebLogic as either compliment modules or as a full substitute; I've
also seen similar approaches at customers with large setups.
The core of the idea is to supply administrators a script that sets up
everything. If you want to explore this route, you can start by searching for
examples on dev2dev, and also by examining the public
weblogic.extensions.*Helper* classes (as Kats mentioned in his response).
The advantage of the WLST/mbean approach is that it works for everything and is
extremely flexible - it can even setup non-JMS items like ports, security, and
clustering. The disadvantage is that it can become fairly involved and
complex depending on how sophisticated you try to be.
|
| Post Reply
|
|
|
|
|
|
|
|
|
|