Run the startWebLogic.sh script to start the Administration Server..

When prompted :with “Enter username to boot WebLogic server”, enter the administrative user name you have setup when you created the domain. In this case user name “admin” is shown. Then enter the password for admin user when prompted with “Enter password to boot WebLogic server”.

This will start the Administration Server. Leave this shell window running..

To start the Managed Server (dizzy1) in the domain, invoke another shell window and navigate to the bin subfolder in your domain

Execute the following command: to start the managed server.

$ ./startManagedWebLogic.sh dizzy1 http://localhost:7001

When prompted :with “Enter username to boot WebLogic server”, enter the administrative user name you have setup when you created the domain. In this case user name “admin” is shown. Then enter the password for admin user when prompted with “Enter password to boot WebLogic server”

This would start up the Managed Server. Once again, leave this window as it is..

Click New under the JMS Servers table to create a new JMS Server.

Specify the following properties and click Next:

	Name	dizzyworldJMSServer
	Persistent Store	(none)

Select dizzy1 as the target JMS server. Click Finish.

Click Activate Changes to give effect to the changes.

Click New on the JMS Modules table and specify the following properties and click Next

	Name	dizzyworldModule
	Descriptor File Name	dizzyworldModule

Select dizzy1 Managed Server as target. Click Next :

Select the checkbox for Would you like to add resources to this JMS system module and click Finish.

In the Settings for dizzyworldModule page, click the Subdeployments tab

In the Subdeployments table, click New. Enter dizzysubmodule as the Subdeployment Name and click Next

.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 Choose the type of resource you want to create, select Queue , and then click Next .

In the JMS Destination Properties, specify the following parameters and click Next

	Name	dizzyworldQueue
	JNDI Name	dizzyworldQueue
	Template	None

Select dizzysubmodule from the subdeployments list. Click Finish.

In the Settings for dizzyworldModule page, click New under the Summary of Resources table to configure a new JMS topic for the JMS module

In the Create a New JMS System Module Resource page, select Topic as the type of resource you want to create, and c lick Next. .

In the JMS Destination Properties, specify the following parameters, and click Next.

	Name	dizzyworldTopic
	JNDI Name	dizzyworldTopic
	Template	None

Select dizzyworldsubmodule from the subdeployments list. Click Finish.

Back in the Change Center, click Activatechanges

Navigate to Home. In the home page, under Environment, click Servers to get to the Summary of Servers. In the table of servers, click dizzy1.

In the Settings for dizzy1 page, click View JNDI Tree

The JNDI Tree opens in another window or tab. In that tab notice the JNDI entries dizzyworldQueue and dizzyworldTopic under the dizzy1 managed server

Scroll down in the Configuration tab of Settings for dizzyworldModule. Click dizzyworldQueue link in the Summary of Resources table.

Click Monitoring tab in the Settings for dizzyworldQueue.

Click Customize this table in the Monitoing page..

Select Messages Total from Available column and click the right arrow to move it Chosen. Then click Apply.

Notice that Messages Total appears as one of the columns in the table. .

Set WL_HOME environment variable to point to the location where you have installed WLS 10.3..

Run WL_HOME/server/bin/setWLSEnv.sh script to set up the environment variables.

Run the command java weblogic.WLST deploy_testjms.py to deploy the testds.war application.

Open a Web browser and navigate to http://localhost:7003/messaging

Using the application, post several messages to the standard queue and to the topic. Do not add messages to the distributed queue .

In the Admin console navigate to dizzyworld > Services > Messaging > JMS Modules. In the JMS Modules table, click dizzyworldModule. In the Summary of Resources table, click dizzyworldQueue . and then click the Monitoring tab. Notice that the Messages High and Messages Total column show non zero values indicating new messages have been recieved. .

Repeat these steps to view the number to messages sent to the dizzyworldTopic .

Note: On the topic (unlike the queue), Messages High value remains zero, since there are no consumers connected to the topic, posted messages are automatically deleted from the server. For a queue, messages are saved on the server until they are consumed..