16.10.2015 Views

Getting Started with WebSphere Application Server

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6 – Messaging 123<br />

3. Copy the deployment plan content in the edit box into an xml file. With the saved<br />

deployment plan, you can deploy a JMS resource group into Community Edition<br />

directly whenever you want, <strong>with</strong>out repeating the wizard.<br />

Part 2 - Deploy the saved JMS resource group deployment plan into Community Edition.<br />

Procedure<br />

1. Start the Community Edition server and launch the Community Edition administrative<br />

console. Login as system <strong>with</strong> password manager.<br />

2. Follow the steps in Section 6.3.4 to uninstall the existing JMS resource group to<br />

make sure there is no deployed JMS resource group which has the same ID <strong>with</strong><br />

your deployment plan.<br />

3. In the left hand navigation pane, select <strong>Application</strong>s -> Deploy New to open the<br />

Install New <strong>Application</strong>s page as shown in Figure 6.17.<br />

Figure 6.17 – Deploy JMS Resouce from existing deployment plan.<br />

4. Click Browse at the right side of Archive; select<br />

\repository\org\apache\geronimo\modules\geronimoactivemq-ra\2.1.4\geronimo-activemq-ra-2.1.4.rar<br />

5. Click Browse at the right side of Plan; select your saved JMS resource group<br />

deployment plan xml file.<br />

6. Click Install to deploy.<br />

6.7 Review questions<br />

1. What’s the major difference between HTTP and message applications?<br />

2. What are the two popular JMS application models?<br />

3. What are the steps to develop a JMS client application that produces a message?<br />

4. What do you have to do before developing JMS applications <strong>with</strong> Community<br />

Edition?<br />

5. How do you use a created JMS resource group in a Web application?

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!