Setting Up Java Message Service (JMS) Resources in WebLogic 11g

<< Previous

* Point to point queues
* Publish/subscribe topics

* Support both point-to-point and publish/subscribe
* Acknowledge based guaranteed delivery
* Transactional message delivery (JTA)
* Durable subscribers
* Distributed destinations
* Recovery from failed servers

spool c:\logs\recreate_myJmsSvr.log
 
-- Drop myJmsSvr
DROP USER "myJmsSvr" CASCADE;
 
-- USER SQL
CREATE USER myJmsSvr IDENTIFIED BY myJmsSvr
DEFAULT TABLESPACE "USERS"
TEMPORARY TABLESPACE "TEMP";
 
-- ROLES
GRANT "CONNECT" TO myJmsSvr ;
GRANT "RESOURCE" TO myJmsSvr ;
 
spool off

More screenshots: wls11gadmin_jms_create_svr

* JMS modules are application related definitions independent of domain environment
* Used to configure queues, topics, and connection factories
* Conform to weblogic-jms.xsd

* System module
– configured using Admin Console or WLST
– by adding reference in config.xml
– owned by WLS Admin
– available to all applications
* Application module
– is an independent JEE module
– can be deployed either together with EAR app or as standalone shared
– owned by developers

* Used to create connections
* Sets default client connection parameters
– priority
– TTL
– persistence
– transactional behavior
– acknowledgement policy
– flow control
* WLS default connection factories:
– located on server JNDI tree at
weblogic.jms.ConnectionFactory
weblogic.jms.XAConnectionFactory
* CF names must be unique within each JMS module
* All CF JNDI names must be unique within whole domain

* Is a light weight object stored in JNDI
* Is the target on JMS server for sending/receiving messages
* Two types of destinations
– queue (for point to point)
– topic (for publish/subscribe): client IDs are required for durable subscription

* Same as create Q, except select Topic instead of Queue:

* Support guaranteed message delivery (even if subscribers are inactive)
* Non-durable by default

* Create and configure a JMS store

* Configure CFs or destinations as persistent

* Associate JMS store with JMS server

* Used to control size and number of messages flow through JMS servers
* A threshold is a limit that triggers flow control and logging warnings
* A quota is a limit defined for JMS objects:
– max number of bytes that can be stored
– max number of messages that can be stored
* Paging
– enables automatic clearing of virtual memory especially for non-persistent messages
– enabled by default

* Manage messages in a queue

Next >>

[mv_include id=’3268′]