What are the four basic components of a JMS system-resource module in the config.xml in WebLogic 9.2?
-
Name, target, subdeployment, descriptor-file-name
-
Domain, jms-server, connection factory, destination
-
Config.xml, jms-module, subdeployment, descriptor-file-name
-
Name, jms-module, subdeployment, descriptor-file-name
In WebLogic 9.2, JMS system-resource modules in config.xml require four basic components: a name for identification, target(s) to specify which servers/clusters, subdeployment for organizing resources, and descriptor-file-name pointing to the JMS configuration XML. Option B incorrectly lists runtime components rather than config elements. Option C incorrectly includes config.xml itself as a component.
A JMS system module definition in WebLogic's config.xml is built from a Name identifying the module, a Target specifying which server/cluster it's deployed to, a SubDeployment grouping its resources for targeting individual JMS servers, and a descriptor-file-name pointing to the XML file holding the actual JMS resource definitions (queues, topics, connection factories). The other options either mix up unrelated top-level concepts (domain, jms-server) or reference the file itself as if it were a component.