woolfel 2005/06/15 20:35:06 Modified: xdocs/usermanual build-jms-topic-test-plan.xml Log: updated the how-to for JMS topic sampler. Now I need to update the index numbers tomorrow. peter Revision Changes Path 1.3 +42 -9 jakarta-jmeter/xdocs/usermanual/build-jms-topic-test-plan.xml Index: build-jms-topic-test-plan.xml =================================================================== RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-jms-topic-test-plan.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- build-jms-topic-test-plan.xml 26 May 2005 12:30:57 -0000 1.2 +++ build-jms-topic-test-plan.xml 16 Jun 2005 03:35:06 -0000 1.3 @@ -46,10 +46,10 @@ </section> <section name="10.1 Adding Users" anchor="adding_users"> -<p>The first step you want to do with every JMeter Test Plan is to add a -<a href="test_plan.html#thread_group">Thread Group</a> element. The Thread Group tells -JMeter the number of users you want to simulate, how often the users should send -requests, and the how many requests they should send.</p> +<p>The first step is add a <a href="test_plan.html#thread_group">Thread Group</a> + element. The Thread Group tells JMeter the number of users you want to simulate, + how often the users should send requests, and the how many requests they should +send.</p> <p>Go ahead and add the ThreadGroup element by first selecting the Test Plan, clicking your right mouse button to get the Add menu, and then select @@ -78,7 +78,7 @@ finish starting all of your users by the end of the 5 seconds. So, if we have 5 users and a 5 second Ramp-Up Period, then the delay between starting users would be 1 second (5 users / 5 seconds = 1 user per second). If you set the -value to 0, then JMeter will immediately start all of your users.</p> +value to 0, JMeter will immediately start all users.</p> <p>Clear the checkbox labeled "Forever", and enter a value of 10 in the Loop Count field. This property tells JMeter how many times to repeat your test. @@ -108,15 +108,48 @@ Then, select the JMS Subscriber element in the tree and edit the following properties (see Figure 10.5): <ol> -<li>Change the Name field to .</li> +<li>Change the Name field to "sample subscriber".</li> +<li>If the JMS provider uses the jndi.properties file, check the box</li> <li>Enter the name of the InitialContextFactory class.</li> -<li>Enter the provider URL.</li> +<li>Enter the provider URL. This is the URL for the JNDI server, if there is one</li> +<li>Enter the name of the connection factory. Please refer to the documentation +of the JMS provider for the information</li> +<li>Enter the name of the message topic</li> +<li>If the JMS provider requires authentication, check "required" and enter the +username and password. For example, Orion JMS requires authentication, while ActiveMQ +and MQSeries does not</li> +<li>Enter 10 in "Number of samples to aggregate". For performance reasons, the sampler +will aggregate messages, since small messages will arrive very quickly. If the sampler +didn't aggregate the messages, JMeter wouldn't be able to keep up.</li> +<li>If you want to read the response, check the box</li> +<li>There are two client implementations for subscribers. If the JMS provider +exhibits zombie threads with one client, try the other.</li> </ol> </p> <figure image="jms/jms_sub.png"> Figure 10.3. JMS Subscriber</figure> +<ol> +<li>Change the Name field to "sample publisher".</li> +<li>If the JMS provider uses the jndi.properties file, check the box</li> +<li>Enter the name of the InitialContextFactory class.</li> +<li>Enter the provider URL. This is the URL for the JNDI server, if there is one</li> +<li>Enter the name of the connection factory. Please refer to the documentation +of the JMS provider for the information</li> +<li>Enter the name of the message topic</li> +<li>If the JMS provider requires authentication, check "required" and enter the +username and password. For example, Orion JMS requires authentication, while ActiveMQ +and MQSeries does not</li> +<li>Enter 10 in "Number of samples to aggregate". For performance reasons, the sampler +will aggregate messages, since small messages will arrive very quickly. If the sampler +didn't aggregate the messages, JMeter wouldn't be able to keep up.</li> +<li>Select the appropriate configuration for getting the message to publish. If you +want the sampler to randomly select the message, place the messages in a directory +and select the directory using browse.</li> +<li>Select the message type. If the message is in object format, make sure the +message is generated correctly.</li> +</ol> <p></p> <figure image="jms/jms_pub.png"> Figure 10.3. JMS Publisher</figure>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
