Part I Development Tasks and Tools
1. Setting Up a Development Environment
3. Using Ant with Enterprise Server
Part II Developing Applications and Application Components
7. Using the Java Persistence API
8. Developing Web Applications
9. Using Enterprise JavaBeans Technology
10. Using Container-Managed Persistence
13. Developing Lifecycle Listeners
Part III Using Services and APIs
14. Using the JDBC API for Database Access
15. Using the Transaction Service
16. Using the Java Naming and Directory Interface
17. Using the Java Message Service
Message Queue Resource Adapter
Administration of the JMS Service
Checking Whether the JMS Provider Is Running
Creating Physical Destinations
Creating JMS Resources: Destinations and Connection Factories
Restarting the JMS Client After JMS Configuration
Transactions and Non-Persistent Messages
Using the ConfigurableTransactionSupport Interface
Authentication With ConnectionFactory
Delivering SOAP Messages Using the JMS API
To Send SOAP Messages Using the JMS API
The Sun GlassFish Message Queue software uses a default directory for storing data
such as persistent messages and its log file. This directory is called varhome. The
Enterprise Server uses domain-dir/imq as the varhome directory if the type of
relationship between the Enterprise Server and the Message Queue software is LOCAL or
EMBEDDED. If the relationship type is REMOTE, the Message Queue software determines the
varhome location. For more information about the types of relationships between the Enterprise
Server and Message Queue, see The JMS Provider.
When executing Message Queue scripts such as as-install/imq/bin/imqusermgr, use the -varhome option to point the scripts to the Message Queue data if the relationship type is LOCAL or EMBEDDED. For example:
imqusermgr -varhome $AS_INSTALL/domains/domain1/imq add -u testuser
For more information about the Message Queue software, refer to the documentation at http://docs.sun.com/coll/1343.9.