Methods for Configuring JMS Application Modules

5 Configuring JMS Application Modules for Deployment 5-1 5 Configuring JMS Application Modules for Deployment These sections explain how to configure JMS application modules for deployment, including JMS application modules packaged with a Java EE enterprise application and globally-available, standalone application modules. ■ Section 5.1, Methods for Configuring JMS Application Modules ■ Section 5.2, JMS Schema ■ Section 5.3, Packaging JMS Application Modules In an Enterprise Application – Section 5.3.1.2, Main Steps for Creating Packaged JMS Application Modules – Section 5.3.1, Creating Packaged JMS Application Modules – Section 5.3.2, Sample of a Packaged JMS Application Module In an EJB Application – Section 5.3.3, Packaging an Enterprise Application With a JMS Application Module – Section 5.3.4, Deploying a Packaged JMS Application Module ■ Section 5.4, Deploying Standalone JMS Application Modules ■ Section 5.5, Generating Unique Runtime JNDI Names for JMS Resources

5.1 Methods for Configuring JMS Application Modules

All JMS resources that can be configured in a JMS system module can also be configured and managed as deployable application modules, similar to standard Java EE modules. Deployed JMS application modules are owned by the developer who created and packaged the module, rather than the administrator who deploys the module; therefore, the administrator has more limited control over deployed resources. For example, administrators can only modify override certain properties of the resources specified in the module using the deployment plan JSR-88 at the time of deployment, but they cannot dynamically add or delete resources. As with other Java EE modules, configuration changes for an application module are stored in a deployment plan for the module, leaving the original module untouched. Application developers can use these tools to create and deploy target system resources 5-2 Configuring and Managing JMS for Oracle WebLogic Server ■ Create a JMS system module, as described in Section 3.5, JMS System Module Configuration and then copy the resulting XML file to another directory and rename it, using -jms.xml as the file suffix. ■ Create application modules in an enterprise-level IDE or another development tool that supports editing of XML files, then package the JMS modules with an application and pass the application to a WebLogic Administrator to deploy.

5.2 JMS Schema