About Service Java rules
|
|
| New | Service | Parameters | Exceptions | History | More... |
C-1882 Using the Java Business Delegate pattern and the Java Session Facade pattern, the Java service interface makes service rules available to external, Java-based applications as if the service rules were public methods of a Java class.
To use Java service rules, Process Commander must be deployed as an enterprise application, not as a Web application. When Process Commander is deployed as an enterprise application, two EJBs (PRServiceStateless and PRServiceStateful) implement the session facade. They provide the public interface for remote and local access to Process Commander Java and EJB services.
Java services generally process service requests synchronously. That is, they immediately perform their requested processing and return a configured return value while the calling application waits. However, you can configure Java services to process service requests asynchronously, which means the service queues the request for asynchronous execution and the calling application calls back later for the results. Additionally, you can configure synchronous Java services to check for specific error conditions that you expect will be temporary — work object locks, for example — and then queue service requests that fail for those reasons for another attempt at a later time.
Use the Application Explorer or the Integration Overview landing page to see Service Java rules in your application.
Use the Rules Explorer to list all Service Java rules that are
available to you. To access the Integration Overview landing page, select 
> Integration > Overview.
Service Java rules belong to the Integration-Services category. A Service Java rule is an instance of the Rule-Service-Java rule type.
|
How to call Process
Commander through Java-based services
How to unit test a Service Java rule |
Integration-Services category
Help Home