Lexmark X792 Lexmark Document Distributor - Page 63

Using JConsole to monitor and modify a running test, Connect, MBeans, Simulation

Page 63 highlights

Testing and deploying workflow solutions 63 Prompt type Image boolean Image list Image message Integer List Message Numeric Password Scan ScanUI String Valid answer values true false Zero‑based array index [DEFAULT] only Numeric integer Zero‑based array index [DEFAULT] only Numeric integer Text string None; scan prompts are handled by the basic.scanfiles and advanced.scanfilesN settings. Answers for scan prompts should not be included in the sequence of prompt answers. [DEFAULT] only Text string Default value if no default is specified by the script true 0 N/A 0 0 N/A 0 Empty string N/A N/A Empty string Using JConsole to monitor and modify a running test You can use the Java Monitoring and Management Console (JConsole) or another JMX‑enabled application to access attributes and operations of the performance simulator process during a test. The following steps detail accessing these attributes and operations using JConsole specifically, but the listed attributes and operations are the same for other JMX‑enabled applications. 1 Run JConsole. Note: JConsole is installed with the Java SE Development Kit. The default location for JConsole is C:\Program Files\Java\jdk\bin\jconsole.exe. 2 While a performance simulator test is running, select com.lexmark.workflow.simulator.App from the list of processes on the Local tab. Note: If a test is started after the "Connect to Agent" dialog is opened, then click the empty area within the list of processes to refresh it. 3 Click Connect > MBeans tab. 4 Expand the simulator folder, and then expand the folder for the currently running test profile. 5 For e‑Task 2, expand the Advanced folder. or For e‑Task, expand the Basic folder. 6 Select Simulation.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82

Prompt type
Valid answer values
Default value if
no default is
specified by the
script
Image boolean
true
false
true
Image list
Zero
based array index
0
Image message
[DEFAULT]
only
N/A
Integer
Numeric integer
0
List
Zero
based array index
0
Message
[DEFAULT]
only
N/A
Numeric
Numeric integer
0
Password
Text string
Empty string
Scan
None; scan prompts are handled by the
basic.scanfiles
and
advanced.scanfilesN
settings. Answers for scan prompts should not be
included in the sequence of prompt answers.
N/A
ScanUI
[DEFAULT]
only
N/A
String
Text string
Empty string
Using JConsole to monitor and modify a running test
You can use the
Java Monitoring and Management Console
(JConsole) or another JMX
enabled application to access
attributes and operations of the performance simulator process during a test. The following steps detail accessing these
attributes and operations using JConsole specifically, but the listed attributes and operations are the same for other
JMX
enabled applications.
1
Run JConsole.
Note:
JConsole is installed with the Java SE Development Kit. The default location for JConsole is C:\Program
Files\Java\jdk<
current version
>\bin\jconsole.exe.
2
While a performance simulator test is running, select
com.lexmark.workflow.simulator.App
from the list of
processes on the Local tab.
Note:
If a test is started after the “Connect to Agent” dialog is opened, then click the empty area within the list
of processes to refresh it.
3
Click
Connect
>
MBeans
tab.
4
Expand the simulator folder, and then expand the folder for the currently running test profile.
5
For e
Task 2, expand the Advanced folder.
or
For e
Task, expand the Basic folder.
6
Select
Simulation
.
Testing and deploying workflow solutions
63