More about
Service Java rules
|
|
Java service rules provide a plain Java (POJO) interface to the PRService EJBs. External Java client applications can communicate with Process Commander either directly through the PRService beans or through a delegate proxy Java archive, generated by the service package.
The service package for a group of Java service rules generates one or more proxy Java archives. The external client application communicates with Process Commander through the proxy Java archive, which forwards the messages from the client to Process Commander and returns to the client the response.
Two Dynamic System Settings data instances identify the directories that Java services use. Review these settings and update them as appropriate:
Through changes the prlogging.xml file, you can
obtain performance statistics on the execution of services. See
Performance
tool — Statistics for services.
Through changes to the prconfig.xml file, you
can be alerted to unusually long service operations. See
How
to detect lengthy service operations.
When using Service Java rules,
do not return BigDecimal values unless the calling
system also supports this class. Return a String
value, or use a transform (identified in a Registry Java
Property Transform data instance).
|
service package |
|
About Dynamic System Settings data instances How to call Process Commander through Java-based services |