Packaged JMS Application Module References In weblogic-application.xml Packaged JMS Application Module References In ejb-jar.xml
5.3.2.1 Packaged JMS Application Module References In weblogic-application.xml
When including JMS modules in an enterprise application, you must list each JMS module as a module element of type JMS in the weblogic-application.xml descriptor file packaged with the application, and a path that is relative to the root of the application. For example: module nameAppScopedEJBsname typeJMStype pathjmsappscopedejbs-jms.xmlpath module Configuring JMS Application Modules for Deployment 5-55.3.2.2 Packaged JMS Application Module References In ejb-jar.xml
If EJBs in your application use connection factories through a JMS module packaged with the application, you must list the JMS module as a res-ref element and include the res-ref-name and res-type parameters in the ejb-jar.xml descriptor file packaged with the EJB. This way, the EJB can lookup the JMS Connection Factory in the applications local context. For example: resource-ref res-ref-namejmsQueueFactoryres-ref-name res-typejavax.jms.QueueConnectionFactoryres-type resource-ref The res-ref-name element maps the resource name used by java:compenv to a module referenced by an EJB. The res-type element specifies the module type, which in this case, is javax.jms.QueueConnectionFactory. If EJBs in your application use Queues or Topics through a JMS module packaged with the application, you must list the JMS module as a resource-env-ref element and include the resource-env-ref-name and resource-env-ref-type parameters in the ejb-jar.xml descriptor file packaged with the EJB. This way, the EJB can lookup the JMS Queue or Topic in the applications the local context. For example: resource-env-ref resource-env-ref-namejmsQueueresource-env-ref-name resource-env-ref-typejavax.jms.Queueresource-env-ref-type resource-env-ref The resource-env-ref-name element maps the destination name to a module referenced by an EJB. The res-type element specifies the name of the Queue, which in this case, is javax.jms.Queue.5.3.2.3 Packaged JMS Application Module References In weblogic-ejb-jar.xml
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to This Document
» Enterprise-Grade Reliability WebLogic Server Value-Added JMS Features
» Enterprise-Level Features WebLogic Server Value-Added JMS Features
» Performance WebLogic Server Value-Added JMS Features
» Tight Integration with WebLogic Server Interoperability With Other Messaging Services
» What Is the Java Message Service? WebLogic JMS Architecture and Environment
» Related Documentation Domain Configuration
» JMS Server Behavior in WebLogic Server 9.x and Later
» JMS System Modules JMS Application Modules
» Comparing JMS System Modules and Application Modules Configurable JMS Resources in Modules
» Persistent Stores JMS Store-and-Forward SAF Path Service
» What Are JMS Configuration Resources? Methods for Configuring JMS System Resources
» JMS Server Configuration Parameters
» JMS Server Targeting JMS Server Monitoring Parameters Session Pools and Connection Consumers
» Default Targeting Advanced Subdeployment Targeting
» Using a Default Connection Factory
» Connection Factory Configuration Parameters Connection Factory Targeting
» Advantages of JMS Clustering
» Configuration Guidelines for JMS Clustering What About Failover?
» Path Service High Availability Implementing Message UOO With a Path Service
» How WebLogic JMS Accesses Foreign JMS Providers Sample Configuration for MQSeries JNDI
» Targeting Uniform Distributed Queues and Topics
» Load Balancing Options Load Balancing Messages Across a Distributed Destination
» Consumer Load Balancing Producer Load Balancing Defeating Load Balancing
» Distributed Destination Load Balancing When Server Affinity Is Enabled
» Distributed Destination Migration Distributed Destination Failover
» Configure Shared Subscriptions Oracle Fusion Middleware Online Documentation Library
» Methods for Configuring JMS Application Modules
» Sample of a Simple Standalone JMS Application Module Deploying Standalone JMS Application Modules
» How to Create JMS Servers and JMS System Module Resources
» Using AQ Destinations as Foreign Destinations Driver Support Transaction Support
» Create Users and Grant Permissions Create AQ Queue Tables
» Configure a WebLogic Data Source
» Configure AQ JMS Foreign Server Destinations
» Message Driven Beans AQ JMS Extensions
» Resource References JDBC Connection Utilization Oracle RAC Support Debugging
» Controlling Access to Destinations that are Looked Up using the JMS API
» WebLogic Messaging Bridge Advanced Topics
» Monitoring Queues Monitoring Topics Monitoring Durable Subscribers for Topics
» Monitoring Message Runtime Information Querying Messages
» Moving Messages Deleting Messages Creating New Messages
» JMS Message Management Using Java APIs Managing Transactions
» Managing Durable Topic Subscribers
» Configure JMS Servers and Persistent Stores.
» Configure a JMS Module Configure JMS Resources
» Enable Debugging Using the Command Line Enable Debugging Using the WebLogic Scripting Tool
» Changes to the config.xml File
» JMS Debugging Scopes Debugging JMS
» Messaging Kernel and Path Service Debugging Scopes Request Dyeing
» Enabling JMS Message Logging
» JMS Message Log Record Format
» Consumer Created Event Consumer Destroyed Event Message Produced Event Message Consumed Event
» Message Expired Event Retry Exceeded Event
» Pausing and Resuming Production at Boot-time Pausing and Resuming Production at Runtime
» Pausing and Resuming Insertion at Boot Time Pausing and Resuming Insertion at Runtime
» Pausing and Resuming Consumption at Boot-time Pausing and Resuming Consumption at Runtime
Show more