Overview
A JMS server implements the JMS
infrastructure on a WebLogic server.
Destinations (queues or topics) are targeted to a WebLogic server when
the JMS server is targeted to the WebLogic server.
This exercise is going to have you
configure a JMS server dizzyworldJMSServer, a queue dizzyworldQueue and a topic dizzyworldTopic. You will then post messages to the queue and topic and
monitor them in the Administration Console. Right now you will not have any
consumers; you will simply be posting the messages and getting familiar with
monitoring the message statistics in the Administration Console.
Configuration JMS
Configure a JMS Server with the following specifications:
Navigate to Doamin à
Services à Messaging
à JMS Servers. Lock
the console.
Click New under the JMS Servers table and specify the following
properties:
Name: dizzyworldJMSServer
Persistent Store: (none)
Persistent Store: (none)
Click Next and target the JMS server to ms1 Managed Server. Click Finish
Save and Activate your
changes.
Configure
a JMS module and add a queue and a topic to the JMS module according to the
following specifications:
Navigate to dizzyworld à Services à Messaging à JMS Modules. Lock the
console, if necessary.
Click
New under the JMS Modules table and specify the following properties:
Name: dizzyworldModule
Descriptor File Name: dizzyworldModule
Descriptor File Name: dizzyworldModule
Click on Finish
In
the Setting for dizzyworldModule page, click the Subdeployments tab.
Under the Subdeployments table, click New to create a
subdeployment with the following specifications:
Subdeployment
Name:
dizzy1SubDeployment
In the Targets page, select the dizzyworldJMSServer as the target
under the JMS Servers table. Click Finish
Click the Configuration
tab.
In the Settings for
dizzyworldModule page under the Summary of Resources table, click New to
configure a new JMS queue for the JMS module
In the Create a New JMS System
Module Resource page under the heading of Choose the type of resource you
want to create, select Queue.
Click Next.
In
the JMS Destination Properties, specify the following parameters:
Name: dizzyworldQueue
JNDI
Name:
dizzyworldQueue
Template: None
Click Next.
Click Advanced Targeting.
Select dizzy1SubDeployment from the
subdeployments list. Click Finish
In the Settings for
dizzyworldModule page under the Summary of Resources table, click New to
configure a new JMS topic for the JMS module.
In the Settings for
dizzyworldModule page under the Summary of Resources table, click New to
configure a new JMS topic for the JMS module
In the Create a New JMS System
Module Resource page under the heading of Choose the type of resource you
want to create, select Topic.
Click Next.
In
the JMS Destination Properties, specify the following parameters:
Name: dizzyworldTopic
JNDI
Name:
dizzyworldTopic
Template: None
Click Next.
Click Advanced Targeting.
Select dizzy1SubDeployment from the
subdeployments list. Click Finish.
Activate the changes.
You should be able to see a JNDI
entry on the dizzy1 Managed Server
called dizzyworldQueue
and
dizzyworldTopic.
Deploy the Web application messaging.war
Start the application
by selecting the checkbox against the application name under the Deployments
table. Click Start and select Servicing all requests.
open http://localhost:7003/messaging.
Use
the Administration console to view the number of messages that have been posted
into each of the destinations, navigate to dizzyworld à Services à Messaging à JMS Modules. In the JMS Modules
table, click dizzyworldModule. In the Summary
of Resources page, click dizzyworldQueue, and then click
the Monitoring tab.
Customize this table to show the Messages
Total column. The Messages Total
column shows you the number of messages that have been sent to the dizzyworldQueue. Repeat these
steps to view the number to messages sent to the dizzyworldTopic.
Note: On the topic (unlike the queue), messages do not appear to be getting stored. This is because we do not have any durable subscribers registered for this topic.
Note: On the topic (unlike the queue), messages do not appear to be getting stored. This is because we do not have any durable subscribers registered for this topic.
please follow the link to get the war file
https://www.dropbox.com/sh/r7iwcihvej18quk/4pCyn9EFBA
No comments:
Post a Comment