Remote Server Configuration Pages A
- Home
- Adding additional libraries to the CLASSPATH
- Advanced Configuration
- Basic Configuration
- Configuring the JVM, the JMeter process runs in
- FAQs
- Log levels
- modifying Properties
- Proxy Configuration
- Remote Server Configuration
- Selecting Tests to Run
- Test Results File Format
Remote Start and Stop of Servers Via <remoteConfig>
Setting the <startServersBeforeTests> option would result in a--runremote command being send to JMeter which would St Art up any remote servers you has defined in your jmeter.propertieswhen your first Test starts.
Setting the <stopServersAfterTests> option would result in a--remoteexit command being send to JMeter which would Shu t all remote servers defined in jmeter.properties after your last test have been run.
<startServersBeforeTests> and <stopServersAfterTests> can be used independantly so it's possible to use Another process to start and stop servers if required.
+---+<project> [...] <Build> <Plugins> <Plugin> <groupid>com.lazerycode.jmeter</Groupid> <artifactid>jmeter-maven-plugin</Artifactid> <version>2.0.3</Version> <Executions> <Execution> <id>jmeter-tests</id> <goals> << Span class= "pl-ent" >goal>jmeter</goal> </goals> </< Span class= "pl-ent" >execution> </executions> <configuration > <remoteconfig> <startserversbeforetests>true</< Span class= "pl-ent" >startserversbeforetests> <stopserversaftertests>true</stopserversaftertests> </remoteconfig> </ configuration> </plugin> </plugins> </ build> [...] </project>+---+
You can configure the plugin to perform a remote start and stop for each individual test by setting the <startandstopse Rversforeachtest> variable to True. If you set this along with<startserversbeforetests> and <stopServersAfterTests> the < Startserversbeforetests>and <stopServersAfterTests> settings'll be ignored.
+---+<project> [...] <Build> <Plugins> <Plugin> <groupid>com.lazerycode.jmeter</Groupid> <artifactid>jmeter-maven-plugin</Artifactid> <version>2.0.3</Version> <executions> <execution> <id> Jmeter-tests</id> <goals> <goal >jmeter</goal> </goals> </ execution> </executions> <configuration> <remoteconfig> <startandstopserversforeachtest>false</ startandstopserversforeachtest> </remoteconfig> </configuration> </plugin> </plugins> </ build> [...] </project>+---+
Instead of starting all remote servers, you can specify which ones-start by using the the<serverlist> option, this WI ll accept a comma separated list of servers for JMeter to start (these must is defined in your jmeter.properties, See the remote Testing page in the JMeter manual).
+---+<project> [...] <Build> <Plugins> <Plugin> <groupid>com.lazerycode.jmeter</Groupid> <artifactid>jmeter-maven-plugin</Artifactid> <version>2.0.3</Version> <Executions> <Execution> <id>jmeter-tests</Id> <goals> <goal>jmeter</goal> </< Span class= "pl-ent" >goals> </execution> </executions> <configuration> <remoteconfig> < Startserversbeforetests>true</startserversbeforetests> < Serverlist>server1,server2</serverlist> < Stopserversaftertests>true</stopserversaftertests> </ remoteconfig> </configuration> </plugin> </plugins> </build> [...] </PROJECT>
Jmeter-maven-plugin Advanced Application: Remote Server Configuration