Getting Started with WebSphere Application Server

118 Getting Started with WebSphere Application Server Community Edition
6. You can also see the group module full name
console.jms/myJmsResourceGroup/1.0/rar from the resulting page. You will use the
JMS Resource group in applications later.
Note:
You can also save the JMS resource deployment plan by clicking the Show Plan button in
the step 4 above. With the saved deployment plan. You can deploy the JMS resource
group within enterprise applications easily. For details, see
http://publib.boulder.ibm.com/wasce/V2.1.1/en/configuring-resources-in-the-assetscope.html#Configuringresourcesintheassetscope-ConfiguringaJMSresourcegroup
6.3.4 Stop, restart, or uninstall an installed JMS resource group.
To stop, restart or uninstall an installed JMS resource group, follow these steps:
1. In the left hand navigation pane, select Applications -> J2EE Connectors to open
the Installed J2EE Connectors page as shown in Figure 6.14.
Figure 6.14 – Installed J2EE Connectors
2. You can see the component console.jms/myJmsResourceGroup/1.0/rar you
just created.
- Click Stop to stop the JMS resource group.
- Click Restart to restart the JMS resource group.
- Click Uninstall to uninstall the JMS resource group.
6.4 Using Community Edition JMS resource
After creating the JMS resource group, you get a running JMS resource group as well as
its module name in Community Edition. To use a JMS resource group in JMS applications,
you must add a dependency to the resource group module in your deployment plan.
• If your Web application accesses a queue to send messages, you need to add a
dependency in geronimo-web.xml to the JMS resource group which the queue
belongs to.
• If you are writing an MDB, you need to add a dependency in openejb-jar.xml to
the JMS resource group which the queue belongs to.