The bpeltests command deploys and executes a set of BPEL processes that exercise the capabilities of the engine.
The bpeltests command, a.k.a. the "spexerciser", is a client that runs a set of in-container tests intended to exercise the engine based on requirements from the BPEL specification. The spexerciser requires that the com.fs.jlo.bpel.test.BpelTestServiceProvider service provider is deployed in the target domain and bound to the URI uri:protocoladapter.bpel.unit-test. (The service provider is pre-configured in standalone server created by the pxe command.)
The spexerciser uses the BpelTestServiceProvider to follow a script of pre-fabricated requests and verify that expected responses satisfy XPath expressions. The BPEL processes, test messages, and scripts are located in the $PXE_HOME/examples/spexerciser directory in the PXE distribution. Within each subdirectory, a unit.properties file describes the group of tests.
| Option/Argument |
Effect |
| filter ... filter |
zero or more filters on the tests to run. Specifying zero filters means to run all available tests. |
| -jmxurl url |
the JMX service URL for the target domain. See the urlalias Command for more information about how to set default values and shortcuts. This defaults to the JMX service URL for the standalone server created by the pxe command. |
| -pxeurl |
the PXE connection URL for the target runtime container. This defaults to rmi://127.0.0.1:2099/MyDomain, the PXE connection URL for the standalone server created by the pxe command. |
| -q |
run quietly. This will only produce output in the event of an error. Using either -v or -vv overrides this command. |
| -v|-vv |
adjust the verbosity of logging output. See Configuring Commandline Launchers. |
| -h |
prints a synopsis to the console and exits. |
