More about Service JSR94 rules
|
|
The client (calling) Java program must execute in the same JVM instance as the Process Commander server.
This interface operates as a Java process. It does not require the
Process Commander servlet container (such as Tomcat) to be running and
does not depend on the PRServlet servlet.
The Service Universal Resource Identifier (URI) of a Rule-Service-JSR94 rule is typically the name of the rule, defined by three key parts:
[package name].[customer class name].[customer method name]
If the external client application requires that the URIs of the services it calls use some other naming convention, you can register a different URI for the service by using the Alternate URI field on the Service tab of the rule.
Through changes the prlogging.xml file, you can obtain
performance statistics on the execution of services. See Performance tool
— Statistics for services. C-2432
Through changes to the prconfig.xml file, you can be
alerted to unusually long service operations. See How to detect lengthy
service operations. C-2432
In Service JSR94 interfaces created in releases before
Version 5.1, the service activity was responsible for parsing the input
list and assembling the output list. For new Service JSR94 rules, use the
Request, Response, and Exceptions tab
for data mapping. C-2436
|
Unit testing a Service JSR94
rule
How to call Process Commander through Java-based services |
|
Atlas — Standard Service JSR94 rules |