jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject svn commit: r1718097 - in /jmeter/trunk/xdocs/usermanual: build-jms-point-to-point-test-plan.xml build-jms-topic-test-plan.xml build-monitor-test-plan.xml build-ws-test-plan.xml
Date Sat, 05 Dec 2015 15:23:04 GMT
Author: fschumacher
Date: Sat Dec  5 15:23:04 2015
New Revision: 1718097

URL: http://svn.apache.org/viewvc?rev=1718097&view=rev
Log:
* Markup changes. Usage of menuchoice and code tags.
* Correct a link to libraries for ActiveMQ and changed "active mq" to ActiveMQ.
* Remove version number (3.0) from link to ActiveMQ.

Modified:
    jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
    jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
    jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml
    jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml

Modified: jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml?rev=1718097&r1=1718096&r2=1718097&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml Sat Dec  5 15:23:04
2015
@@ -18,7 +18,6 @@
 
 <!DOCTYPE document[
 <!ENTITY sect-num '11'>
-<!ENTITY rarr     "&#x02192;" >
 ]>
 
 <document prev="build-ws-test-plan.html" next="build-jms-topic-test-plan.html" id="$Id$">
@@ -33,7 +32,7 @@
         <section name="&sect-num;. Building a JMS Point-to-Point Test Plan" anchor="building">
 
         <note>
-            Make sure the required jar files are in JMeter's lib directory. If they are not,
shutdown JMeter,
+            Make sure the required jar files are in JMeter's <code>lib</code>
directory. If they are not, shutdown JMeter,
             copy the jar files over and restart JMeter. 
             See <a href="get-started.html#libraries_activemq">Getting Started</a>
for details.
         </note>
@@ -53,8 +52,8 @@ following elements:
 and the other uses queues. Topic messages are commonly known as pub/sub messaging.
 Topic messaging is generally used in cases where a message is published by a producer and
 consumed by multiple subscribers.  A JMS sampler needs the JMS implementation jar files;
-for example, from Apache ActiveMQ.  See <a href="#libraries_activemq">here</a>
for the list
-of jars provided by ActiveMQ 3.0.</p>
+for example, from Apache ActiveMQ.  See <a href="get-started.html#libraries_activemq">here</a>
for the list
+of jars provided by ActiveMQ.</p>
 
         </section>
 
@@ -66,8 +65,11 @@ requests, and the how many requests they
             </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
-Add &rarr; ThreadGroup.</p>
+clicking your right mouse button to get the <menuchoice><guimenuitem>Add</guimenuitem></menuchoice>
menu, and then select
+<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>ThreadGroup</guimenuitem>
+</menuchoice>.</p>
 
             <p>You should now see the Thread Group element under Test Plan.  If you
do not
 see the element, then "expand" the Test Plan tree by clicking on the
@@ -82,9 +84,9 @@ below)</p>
 Figure &sect-num;.1. Thread Group with Default Values</figure>
 
             <p>Start by providing a more descriptive name for our Thread Group. In
the name
-field, enter Point-to-Point.</p>
+field, enter <code>Point-to-Point</code>.</p>
 
-            <p>Next, increase the number of users (called threads) to 5.</p>
+            <p>Next, increase the number of users (called threads) to <code>5</code>.</p>
 
             <p>In the next field, the Ramp-Up Period, leave set the value to 0
 seconds.  This property tells JMeter how long to delay between starting each
@@ -94,10 +96,10 @@ finish starting all of your users by the
 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>
 
-            <p>Clear the checkbox labeled "Forever", and enter a value of 4 in the
Loop
+            <p>Clear the checkbox labeled "<code>Forever</code>", and enter
a value of <code>4</code> in the Loop
 Count field.  This property tells JMeter how many times to repeat your test.
-If you enter a loop count value of 0, then JMeter will run your test only
-once. To have JMeter repeatedly run your Test Plan, select the Forever
+If you enter a loop count value of <code>0</code>, then JMeter will run your
test only
+once. To have JMeter repeatedly run your Test Plan, select the <code>Forever</code>
 checkbox.</p>
 
             <note>In most applications, you have to manually accept
@@ -112,7 +114,12 @@ leave the Control Panel (for example, wh
         <section name="&sect-num;.2 Adding JMS Point-to-Point Sampler" anchor="adding_point_to_point_sampler">
 
             <p>Start by adding the sampler <complink name="JMS Point-to-Point"/>
-to the Point-to-Point element (Add &rarr; Sampler &rarr; JMS Point-to-Point).
+to the Point-to-Point element 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Sampler</guimenuitem>
+  <guimenuitem>JMS Point-to-Point</guimenuitem>
+</menuchoice>).
 Then, select the JMS Point-to-Point sampler element in the tree.
  In building the example a configuration will be provided that works with ActiveMQ 3.0.
             </p>
@@ -129,18 +136,18 @@ Then, select the JMS Point-to-Point samp
                         <th colspan="3">JMS Resources</th>
                     </tr>
                     <tr>
-                        <td colspan="1">QueueuConnectionFactory</td>
-                        <td>ConnectionFactory</td>
-                        <td> This is the default JNDI entry for the connection factory
within active mq.</td>
+                        <td colspan="1">QueueConnectionFactory</td>
+                        <td><code>ConnectionFactory</code></td>
+                        <td> This is the default JNDI entry for the connection factory
within ActiveMQ.</td>
                     </tr>
                     <tr>
                         <td>JNDI Name Request Queue</td>
-                        <td>Q.REQ</td>
+                        <td><code>Q.REQ</code></td>
                         <td>This is equal to the JNDI name defined in the JNDI properties.</td>
                     </tr>
                     <tr>
                         <td>JNDI Name Reply Queue</td>
-                        <td>Q.RPL</td>
+                        <td><code>Q.RPL</code></td>
                         <td>This is equal to the JNDI name defined in the JNDI properties.</td>
                     </tr>
                     <tr>
@@ -148,48 +155,48 @@ Then, select the JMS Point-to-Point samp
                     </tr>
                     <tr>
                         <td colspan="1">Communication Style</td>
-                        <td>Request Response</td>
+                        <td><code>Request Response</code></td>
                         <td>This means that you need at least a service running outside
of JMeter and that will respond to the requests. 
                         This service must listen to the Request Queue and send messages to
the queue referenced by the <code>message.getJMSReplyTo()</code></td>
                     </tr>
                     <tr>
                         <td>Content</td>
-                        <td>test</td>
+                        <td><code>test</code></td>
                         <td>This is just the content of the message.</td>
                     </tr>
                     <tr>
                         <td>JMS Properties</td>
                         <td></td>
-                        <td>Nothing needed for active mq.</td>
+                        <td>Nothing needed for ActiveMQ.</td>
                     </tr>
                     <tr>
                          <th colspan="3">JNDI Properties</th>
                      </tr>
                      <tr>
                         <td colspan="1">InitialContextFactory</td>
-                        <td>org.apache.activemq.jndi.ActiveMQInitialContextFactory</td>
-                        <td>The standard InitialContextFactory for Active MQ</td>
+                        <td><code>org.apache.activemq.jndi.ActiveMQInitialContextFactory</code></td>
+                        <td>The standard InitialContextFactory for ActiveMQ</td>
                     </tr>
                     <tr>
                         <th colspan="3"> Properties</th>
                     </tr>
                     <tr>
-                        <td colspan="1">queue.Q.REQ</td>
-                        <td>example.A</td>
-                        <td>This defines a JNDI name Q.REQ for the request queue that
points to the queue example.A</td>
+                        <td colspan="1"><code>queue.Q.REQ</code></td>
+                        <td><code>example.A</code></td>
+                        <td>This defines a JNDI name <code>Q.REQ</code>
for the request queue that points to the queue <code>example.A</code></td>
                     </tr>
                     <tr>
-                        <td colspan="1">queue.Q.RPL</td>
-                        <td>example.B</td>
-                        <td>This defines a JNDI name Q.RPL for the reply queue that
points to the queue example.B</td>
+                        <td colspan="1"><code>queue.Q.RPL</code></td>
+                        <td><code>example.B</code></td>
+                        <td>This defines a JNDI name <code>Q.RPL</code>
for the reply queue that points to the queue <code>example.B</code></td>
                     </tr>
                     <tr>
                         <th colspan="3">Provider URL</th>
                     </tr>
                     <tr>
                         <td colspan="1">Provider URL</td>
-                        <td>tcp://localhost:61616</td>
-                        <td>This defines the URL of the active mq messaging system.</td>
+                        <td><code>tcp://localhost:61616</code></td>
+                        <td>This defines the URL of the ActiveMQ messaging system.</td>
                     </tr>
                 </table>
             </p>
@@ -204,8 +211,12 @@ a visual model of the data.
             </p>
 
             <p>Select the Thread Group element and add a
-                <complink name="Graph Results"/> listener (Add &rarr; Listener
-&rarr; Graph Results).  Next, you need to specify a directory and filename of the
+                <complink name="Graph Results"/> listener 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Listener</guimenuitem>
+  <guimenuitem>Graph Results</guimenuitem>
+</menuchoice>).  Next, you need to specify a directory and filename of the
 output file.  You can either type it into the filename field, or select the
 Browse button and browse to a directory and then enter a filename.
             </p>

Modified: jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml?rev=1718097&r1=1718096&r2=1718097&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml Sat Dec  5 15:23:04 2015
@@ -18,7 +18,6 @@
 <!DOCTYPE document
 [
 <!ENTITY sect-num '12'>
-<!ENTITY rarr     "&#x02192;" >
 ]>
 <document prev="build-jms-point-to-point-test-plan.html" next="build-monitor-test-plan.html"
id="$Id$">
 
@@ -51,7 +50,7 @@ where the sender expects a response.  Me
 normal HTTP requests. In HTTP, a single user sends a request and gets a response.
 Messaging system can work in synchronous and asynchronous mode.  A JMS sampler needs 
 the JMS implementation jar files; for example, from Apache ActiveMQ.  
-See <a href="#libraries_activemq">here</a> for the list of jars provided by ActiveMQ
3.0.</p>
+See <a href="get-started.html#libraries_activemq">here</a> for the list of jars
provided by ActiveMQ.</p>
 
 </section>
 
@@ -62,8 +61,8 @@ See <a href="#libraries_activemq">here</
 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
-Add &rarr; ThreadGroup.</p>
+clicking your right mouse button to get the <menuchoice><guimenuitem>Add</guimenuitem></menuchoice>
menu, and then select
+<menuchoice><guimenuitem>Add</guimenuitem><guimenuitem>ThreadGroup</guimenuitem></menuchoice>.</p>
 
 <p>You should now see the Thread Group element under Test Plan.  If you do not
 see the element, then "expand" the Test Plan tree by clicking on the
@@ -78,11 +77,11 @@ below)</p>
 Figure &sect-num;.1. Thread Group with Default Values</figure>
 
 <p>Start by providing a more descriptive name for our Thread Group. In the name
-field, enter Subscribers.</p>
+field, enter <code>Subscribers</code>.</p>
 
-<p>Next, increase the number of users (called threads) to 5.</p>
+<p>Next, increase the number of users (called threads) to <code>5</code>.</p>
 
-<p>In the next field, the Ramp-Up Period, set the value to 0
+<p>In the next field, the Ramp-Up Period, set the value to <code>0</code>
 seconds.  This property tells JMeter how long to delay between starting each
 user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will
 finish starting all of your users by the end of the 5 seconds.  So, if we have
@@ -90,15 +89,15 @@ finish starting all of your users by the
 would be 1 second (5 users / 5 seconds = 1 user per second).  If you set the
 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
+<p>Clear the checkbox labeled "<code>Forever</code>", and enter a value
of <code>10</code> in the Loop
 Count field.  This property tells JMeter how many times to repeat your test.
-If you enter a loop count value of 0, then JMeter will run your test only
-once. To have JMeter repeatedly run your Test Plan, select the Forever
+If you enter a loop count value of <code>0</code>, then JMeter will run your
test only
+once. To have JMeter repeatedly run your Test Plan, select the <code>Forever</code>
 checkbox.</p>
 
 <p>Repeat the process and add another thread group. For the second thread
-group, enter "Publisher" in the name field, set the number of threads to 1,
-and set the iteration to 10.
+group, enter "<code>Publisher</code>" in the name field, set the number of threads
to <code>1</code>,
+and set the iteration to <code>10</code>.
 </p>
 
 <note>In most applications, you have to manually accept
@@ -112,28 +111,34 @@ leave the Control Panel (for example, wh
 
 <section name="&sect-num;.2 Adding JMS Subscriber and Publisher" anchor="adding_subscriber_publisher">
 
-<p>Make sure the required jar files are in JMeter's lib directory. If they are
+<p>Make sure the required jar files are in JMeter's <code>lib</code> directory.
If they are
 not, shutdown JMeter, copy the jar files over and restart JMeter.</p>
 
 <p>Start by adding the sampler <complink name="JMS Subscriber"/>
-to the Subscribers element (Add &rarr; Sampler &rarr; JMS Subscriber).
+to the Subscribers element
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Sampler</guimenuitem>
+  <guimenuitem>JMS Subscriber</guimenuitem>
+</menuchoice>).
 Then, select the JMS Subscriber element in the tree and edit the following properties:
 
 <ol>
-<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. For example, with ActiveMQ 5.4,
the value is "org.apache.activemq.jndi.ActiveMQInitialContextFactory"</li>
-<li>Enter the provider URL. This is the URL for the JNDI server, if there is one. For
example, with ActiveMQ 5.4 on local machine with default port, the value is "tcp://localhost:61616"</li>
+<li>Change the Name field to "<code>Sample Subscriber</code>"</li>
+<li>If the JMS provider uses the <code>jndi.properties</code> file, check
the box</li>
+<li>Enter the name of the InitialContextFactory class. For example, with ActiveMQ 5.4,
the value is "<code>org.apache.activemq.jndi.ActiveMQInitialContextFactory</code>"</li>
+<li>Enter the provider URL. This is the URL for the JNDI server, if there is one. For
example, with ActiveMQ 5.4 on local machine with default port, the value is "<code>tcp://localhost:61616</code>"</li>
 <li>Enter the name of the connection factory. Please refer to the documentation
-of the JMS provider for the information. For ActiveMQ, the default is "ConnectionFactory"</li>
-<li>Enter the name of the message topic. For ActiveMQ Dynamic Topics (create topics
dynamically), example value is "dynamicTopics/MyStaticTopic1"
-Note: Setup at startup mean that JMeter starting to listen on the Destination at beginning
of test without name change possibility. 
+of the JMS provider for the information. For ActiveMQ, the default is "<code>ConnectionFactory</code>"</li>
+<li>Enter the name of the message topic. For ActiveMQ Dynamic Topics (create topics
dynamically), example value is "<code>dynamicTopics/MyStaticTopic1</code>"
+<note>Note: Setup at startup mean that JMeter starting to listen on the Destination
at beginning of test without name change possibility. 
 Setup on Each sample mean that JMeter (re)starting to listen before run each JMS Subscriber
sample, 
-this last option permit to have Destination name with some JMeter variables</li>
-<li>If the JMS provider requires authentication, check "required" and enter the 
+this last option permit to have Destination name with some JMeter variables
+</note></li>
+<li>If the JMS provider requires authentication, check "<code>required</code>"
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
+<li>Enter <code>10</code> in "<code>Number of samples to aggregate</code>".
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>
@@ -146,25 +151,31 @@ exhibits zombie threads with one client,
 Figure &sect-num;.2. JMS Subscriber</figure>
 
 <p>Next add the sampler <complink name="JMS Publisher"/>
-to the Publisher element (Add &rarr; Sampler &rarr; JMS Subscriber).
+to the Publisher element 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Sampler</guimenuitem>
+  <guimenuitem>JMS Subscriber</guimenuitem>
+</menuchoice>).
 Then, select the JMS Publisher element in the tree and edit the following properties:
 </p>
 
 <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. For example, with ActiveMQ 5.4,
the value is "org.apache.activemq.jndi.ActiveMQInitialContextFactory"</li>
-<li>Enter the provider URL. This is the URL for the JNDI server, if there is one. For
example, with ActiveMQ 5.4 on local machine with default port, the value is "tcp://localhost:61616"</li>
+<li>Change the Name field to "<code>Sample Publisher</code>".</li>
+<li>If the JMS provider uses the <code>jndi.properties</code> file, check
the box</li>
+<li>Enter the name of the InitialContextFactory class. For example, with ActiveMQ 5.4,
the value is "<code>org.apache.activemq.jndi.ActiveMQInitialContextFactory</code>"</li>
+<li>Enter the provider URL. This is the URL for the JNDI server, if there is one. For
example, with ActiveMQ 5.4 on local machine with default port, the value is "<code>tcp://localhost:61616</code>"</li>
 <li>Enter the name of the connection factory. Please refer to the documentation
-of the JMS provider for the information. For ActiveMQ, the default is "ConnectionFactory"</li>
-<li>Enter the name of the message topic. For ActiveMQ Dynamic Topics (create topics
dynamically), example value is "dynamicTopics/MyStaticTopic1". 
-Note: Setup at startup mean that JMeter starting connection with the Destination at beginning
of test without name change possibility. 
+of the JMS provider for the information. For ActiveMQ, the default is "<code>ConnectionFactory</code>"</li>
+<li>Enter the name of the message topic. For ActiveMQ Dynamic Topics (create topics
dynamically), example value is "<code>dynamicTopics/MyStaticTopic1</code>". 
+<note>Note: Setup at startup mean that JMeter starting connection with the Destination
at beginning of test without name change possibility. 
 Setup on Each sample mean that JMeter (re)starting the connection before run each JMS Publisher
sample, 
-this last option permit to have Destination name with some JMeter variables</li>
-<li>If the JMS provider requires authentication, check "required" and enter the 
+this last option permit to have Destination name with some JMeter variables
+</note></li>
+<li>If the JMS provider requires authentication, check "<code>required</code>"
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
+<li>Enter <code>10</code> in "<code>Number of samples to aggregate</code>".
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
@@ -186,8 +197,12 @@ Figure &sect-num;.3. JMS Publisher</figu
 responsible for storing all of the results of your HTTP requests in a file and presenting
 a visual model of the data.</p>
 
-<p>Select the Test Plan element and add a <complink name="Graph Results"/> listener
(Add &rarr; Listener
-&rarr; Graph Results).  Next, you need to specify a directory and filename of the
+<p>Select the Test Plan element and add a <complink name="Graph Results"/> listener
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Listener</guimenuitem>
+  <guimenuitem>Graph Results</guimenuitem>
+</menuchoice>).  Next, you need to specify a directory and filename of the
 output file.  You can either type it into the filename field, or select the
 Browse button and browse to a directory and then enter a filename.</p>
 

Modified: jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml?rev=1718097&r1=1718096&r2=1718097&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml Sat Dec  5 15:23:04 2015
@@ -18,7 +18,6 @@
 <!DOCTYPE document
 [
 <!ENTITY sect-num '13'>
-<!ENTITY rarr     "&#x02192;" >
 ]>
 <document prev="build-jms-topic-test-plan.html" next="listeners.html" id="$Id$">
 
@@ -49,14 +48,17 @@ need to change the MBeanServer lookup to
 <section name="&sect-num;.1 Adding A Server" anchor="adding_server">
 <p>The first step is to add a <a href="test_plan.html#thread_group">Thread Group</a>
 element.  The Thread Group tells JMeter the number of threads you want. Always use
-1, since we are using JMeter as a monitor. This is very important for those not
+<code>1</code>, since we are using JMeter as a monitor. This is very important
for those not
 familiar with server monitors. As a general rule, using multiple threads for a
 single server is bad and can create significant stress.
 </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
-Add &rarr; ThreadGroup.</p>
+clicking your right mouse button to get the <menuchoice><guimenuitem>Add</guimenuitem></menuchoice>
menu, and then select
+<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>ThreadGroup</guimenuitem>
+</menuchoice>.</p>
 
 <p>You should now see the Thread Group element under Test Plan.  If you do not
 see the element, "expand" the Test Plan tree by clicking on the Test Plan element.</p>
@@ -70,10 +72,17 @@ Figure &sect-num;.1. Thread Group with D
 
 <section name="&sect-num;.2 HTTP Auth Manager" anchor="adding_auth">
 <p>Add the <complink name="HTTP Authorization Manager"/> to the Thread Group
element
-(Add &rarr; Config element &rarr; HTTP Authorization Manager). Enter the username
-and password for your webserver. Important note: the monitor only works with
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Config element</guimenuitem>
+  <guimenuitem>HTTP Authorization Manager</guimenuitem>
+</menuchoice>). Enter the username
+and password for your webserver. 
+<note>Important note: the monitor only works with
 Tomcat5 build 5.0.19 and newer. For instructions on how to setup Tomcat, please
-refer to tomcat 5 documentation.</p>
+refer to tomcat 5 documentation.
+</note>
+</p>
 <ol>
 <li> leave the base URL blank</li>
 <li> enter the username</li>
@@ -84,16 +93,20 @@ refer to tomcat 5 documentation.</p>
 <section name="&sect-num;.3 Adding HTTP Request" anchor="adding_request">
 
 <p>Add the <complink name="HTTP Request"/> to the Thread Group element
-(Add &rarr; Sampler &rarr; HTTP Request). Then, select the HTTP Request element
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Sampler</guimenuitem>
+  <guimenuitem>HTTP Request</guimenuitem>
+</menuchoice>). Then, select the HTTP Request element
 in the tree and edit the following properties):
 <ol>
-<li>Change the Name field to "Server Status".</li>
+<li>Change the Name field to "<code>Server Status</code>".</li>
 <li>Enter the IP address or Hostname</li>
 <li>Enter the port number</li>
-<li>Set the Path field to "/manager/status" if you're using Tomcat.</li>
-<li>Add a request parameter named "XML" in uppercase. Give it a value of
-"true" in lowercase.</li>
-<li>Check "Use as Monitor" at the bottom of the sampler</li>
+<li>Set the Path field to "<code>/manager/status</code>" if you're using
Tomcat.</li>
+<li>Add a request parameter named "<code>XML</code>" in uppercase. Give
it a value of
+"<code>true</code>" in lowercase.</li>
+<li>Check "<code>Use as Monitor</code>" at the bottom of the sampler</li>
 </ol>
 </p>
 
@@ -101,8 +114,13 @@ in the tree and edit the following prope
 
 <section name="&sect-num;.4 Adding Constant Timer" anchor="adding_timer">
 
-<p>Add a timer to this thread group (Add &rarr; Timer &rarr; Constant Timer).
-Enter 5000 milliseconds in the "Thread Delay" box. In general, using intervals shorter
+<p>Add a timer to this thread group 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Timer</guimenuitem>
+  <guimenuitem>Constant Timer</guimenuitem>
+</menuchoice>).
+Enter <code>5000</code> milliseconds in the "<code>Thread Delay</code>"
box. In general, using intervals shorter
 than 5 seconds will add stress to your server. Find out what is an acceptable interval
 before you deploy the monitor in your production environment.</p>
 
@@ -115,7 +133,11 @@ before you deploy the monitor in your pr
  the raw data and statistics, make sure you use different filenames.</p>
 
 <p>Select the thread group element and add a <complink name="Simple Data Writer"/>
listener
-(Add &rarr; Listener &rarr; Simple Data Writer).  Next, you need to specify a directory
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Listener</guimenuitem>
+  <guimenuitem>Simple Data Writer</guimenuitem>
+</menuchoice>).  Next, you need to specify a directory
 and filename of the output file.  You can either type it into the filename field, or
 select the Browse button and browse to a directory and then enter a filename.</p>
 
@@ -124,16 +146,21 @@ select the Browse button and browse to a
 <section name="&sect-num;.6 Adding Monitor Results" anchor="add_monitor_listener">
 
 <p>Add the <a href="component_reference.html#listeners">Listener</a> by
selecting the
-test plan element (Add &rarr; Listener &rarr; Monitor Results). 
-<br></br>
+test plan element 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Listener</guimenuitem>
+  <guimenuitem>Monitor Results</guimenuitem>
+</menuchoice>).
+</p><p>
 By default, the Listener will select the results from the first connector in the sample response.
 The Connector prefix field can be used to select a different connector.
 If specified, the Listener will choose the first connector which matches the prefix.
 If no match is found, then the first connector is selected.
 </p>
 <p>There are two tabs in
-the monitor results listener. The first is the "Health", which displays the status of
-the last sample the monitor received. The second tab is "Performance", which shows a
+the monitor results listener. The first is the "<code>Health</code>", which displays
the status of
+the last sample the monitor received. The second tab is "<code>Performance</code>",
which shows a
 historical view of the server's performance. 
 </p>
 

Modified: jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml?rev=1718097&r1=1718096&r2=1718097&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml Sat Dec  5 15:23:04 2015
@@ -19,7 +19,6 @@
 <!DOCTYPE document[
 <!ENTITY sect-num '10'>
 <!ENTITY hellip   "&#x02026;" >
-<!ENTITY rarr     "&#x02192;" >
 ]>
 
 <document prev="build-ldapext-test-plan.html" next="build-jms-point-to-point-test-plan.html"
id="$Id$">
@@ -43,7 +42,7 @@ construct the Test Plan, you will use th
 
 <p>If the sampler appears to be getting an error from the webservice, double check
the
 SOAP message and make sure the format is correct. In particular, make sure the
-xmlns attributes are exactly the same as the WSDL. If the xml namespace is
+<code>xmlns</code> attributes are exactly the same as the WSDL. If the xml namespace
is
 different, the webservice will likely return an error.</p>
 
 </section>
@@ -60,27 +59,29 @@ get a better idea of the differences.</p
 
 <note>JMeter sends requests in the order that they appear in the tree.</note>
 
-<p>Start by using menu File &gt; "Templates&hellip;" and select template "Building
a SOAP Webservice Test Plan".
-Then, click "Create" button.
+<p>Start by using menu
+  <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>Templates&hellip;</guimenuitem></menuchoice>
+  and select template "<code>Building a SOAP Webservice Test Plan</code>".
+Then, click "<code>Create</code>" button.
 
 <figure image="ws_template.png" width="1050" height="684">
 Figure &sect-num;.1.0. Webservice Template</figure>
 Change the following:
 <ol>
-<li>In "HTTP Request Defaults" change "Server Name of IP"</li>
-<li>In "Soap Request", change "Path:"
+<li>In "<code>HTTP Request Defaults</code>" change "<code>Server
Name of IP</code>"</li>
+<li>In "<code>Soap Request</code>", change "<code>Path:</code>"
 <figure width="998" height="734" image="ws_http_request.png">Figure &sect-num;.1.1
Webservice Path</figure>
 </li>
 </ol>
 </p>
 
-<p>Next, select "HTTP Header Manager" and update "SOAPAction" header to match your
webservice.
+<p>Next, select "<code>HTTP Header Manager</code>" and update "<code>SOAPAction</code>"
header to match your webservice.
 Some webservices may not use SOAPAction in this case remove it.<br/>
 Currently, only .NET uses SOAPAction, so it is normal to have a blank SOAPAction for all
other webservices. The list includes JWSDP, Weblogic, Axis, The Mind Electric Glue, and gSoap.
 </p>
 <figure image="ws_header.png" width="1327" height="348">Figure &sect-num;.1.2 Webservice
Headers</figure>
 
-<p>The last step is to paste the SOAP message in the "Body Data"
+<p>The last step is to paste the SOAP message in the "<code>Body Data</code>"
 text area.</p>
 <figure width="998" height="734" image="ws_http_request.png">Figure &sect-num;.1.3
Webservice Body</figure>
 
@@ -113,10 +114,10 @@ finish starting all of your users by the
 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>
 
-<p>Finally, clear the checkbox labeled "Forever", and enter a value of 2 in
+<p>Finally, clear the checkbox labeled "<code>Forever</code>", and enter
a value of <code>2</code> in
 the Loop Count field.  This property tells JMeter how many times to repeat your
-test. If you enter a loop count value of 0, then JMeter will run your test only
-once. To have JMeter repeatedly run your Test Plan, select the Forever
+test. If you enter a loop count value of <code>0</code>, then JMeter will run
your test only
+once. To have JMeter repeatedly run your Test Plan, select the <code>Forever</code>
 checkbox.</p>
 
 <note>In most applications, you have to manually accept
@@ -137,8 +138,12 @@ Figure &sect-num;.3. JMeter Users Thread
 responsible for storing all of the results of your HTTP requests in a file and presenting
 a visual model of the data.</p>
 
-<p>Select the JMeter Users element and add a <complink name="Aggregate Graph"/>
listener (Add &rarr; Listener
-&rarr; Aggregate Graph).  Next, you need to specify a directory and filename of the
+<p>Select the JMeter Users element and add a <complink name="Aggregate Graph"/>
listener 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Listener</guimenuitem>
+  <guimenuitem>Aggregate Graph</guimenuitem>
+</menuchoice>).  Next, you need to specify a directory and filename of the
 output file.  You can either type it into the filename field, or select the
 Browse button and browse to a directory and then enter a filename.</p>
 
@@ -150,10 +155,10 @@ Figure &sect-num;.4. Graph Results Liste
 <section name="&sect-num;.4 Rest Webservice" anchor="rest_webservice">
 <p>Testing a REST Webservice is very similar as you only need to modify in HTTP Request
 <ul>
-<li>Method: to select the one you want to test</li>
-<li>Body Data: which can be JSON, XML or any custom text</li>
+<li><code>Method</code>: to select the one you want to test</li>
+<li><code>Body Data</code>: which can be JSON, XML or any custom text</li>
 </ul>
-You may also need to modify "HTTP Header Manager" to select the correct "Content-Type"
+You may also need to modify "<code>HTTP Header Manager</code>" to select the
correct "<code>Content-Type</code>"
 </p>
 </section>
 </body>



Mime
View raw message