Need separate duplicate JMS modules for each server?

Question

Using WebLogic 9.2.2 on AIX 5.3.
I'm trying to set up a domain with 6 managed servers. I need to deploy several JMS queues and a foreign server to each JMSServer on each server. I looked at the JMSModule object, and I'm trying to determine whether it's possible to define a single JMSModule that I can deploy to all of my servers. So far, this doesn't appear to be possible. As a result, I have to do tons of painful cut/paste inside the console. Is this how it's supposed to work?

Answer 1

David,
Sorry, if I was not clear earlier.
A Module can be targeted to a single Cluster, one or more comma separated list of WLS servers and the servers don't have to be part of a cluster (note that certain resources such as UDD or CF that can be targeted to an entire cluster, cannot be done so, if the module is not targeted to the cluster. And to achieve the same, the user has to manually add/remove the managed servers to the list of Module's/sub-deployment's targets whenever a server is added or removed to/from the cluster/domain).
So, in your case, you can define all the JMS resources for that domain in a single Module descriptor and deploy it to a list of all the managed servers. Then you can use the sub-deployments to group and target them onto other related targets (for example, one or more queues can be grouped as a sub-deployment and targeted to a single JMSServer that is hosted by one of the WLS server instance, where the Module is currently targeted to, etc).
I believe you are creating/using a "system resource" type module via Admin console, the JMSModules wizard shall walk you through the targeting page, where you can see all the available target servers/clusters.
Here is an example of config.xml snippet for this kind of module targeting :
<jms-system-resource>
<name>SystemModule-0</name>
<target>Server-0,Server-1</target>
<sub-deployment>
<name>ConnectionFactory-0</name>
<target>Server-0,Server-1</target>
</sub-deployment>
<sub-deployment>
<name>Queues</name>
<target>JMSServer-0</target>
</sub-deployment>
<descriptor-file-name>jms/systemmodule-0-jms.xml</descriptor-file-name>
</jms-system-resource>
and the corresponding JMS module descriptor file snippet (can be found under DOMAIN_DIR/config/jms dir) as shown below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls
="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http:/
/www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<connection-factory name="ConnectionFactory-0">
<sub-deployment-name>ConnectionFactory-0</sub-deployment-name>
<jndi-name>ConnectionFactory-0</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<queue name="Queue-0">
<sub-deployment-name>Queues</sub-deployment-name>
<jndi-name>Queue-0</jndi-name>
</queue>
</weblogic-jms>
That being said, depending on, how many resources (factories, destinations etc) you are having and how you are going to group them, you may end of with too many sub-deployments within a single module, for which you need to carefully select targets/manage them.
Both approaches (one module descriptor with many sub-deployments and many module descriptors with fewer sub deployments) have positives and negatives, when its comes to manageability. The recommended best practice is to have the JMS resource configuration split into more than one module with fewer number of sub-deployments within each, to have finer control over the resource configuration/management.
Sounds like, you are trying to configure one queue on every managed server, that has duplicate(same) configuration properties. If that is the case, you can try using the UDD (Uniform Distributed Destination), that comes with automatic member (physical destination) management on all of its targets. That way, all you need is one UDD resource configuration/sub-deployment in the module and target the sub-deployment to the same targets as the module's targets (or accept the default targeting option, if available in the resource targeting page).
More information on UDDs can be found here:
http://edocs.bea.com/wls/docs100/jms/dds.html#wp1313025
Hope this helps.
Thanks
Kats