« June 2006 |
Main
| August 2006 »
July 2006 Archives
Clinton Davidson's Blog
Clinton Davidson's Homepage
Clinton Davidson is the lead developer on ALIP. He has been
with Plumtree Software/BEA Systems for almost five years. During that
time, he has worked on BPM, the IDK, the JSR-168 Container and WSRP
Consumer, and Lotus Notes integration. In a previous life, he was a
graduate of the Culinary Institute of America.
Using PAPI-WS- the ALBPM Web Services API
Posted by cdavidso on July 18, 2006 at 9:03 AM | Permalink
| Comments (1)
| TrackBack (0)
PAPI-WS exposes a subset of PAPI- the ALBPM process API. Although there are only a small number of methods exposed, they are the most useful methods for calling ALBPM remotely. Among the calls are:
- Creating a process instance
- Getting a list of instances from a view
- Getting a list of instances with a filter
- Calling external methods
- Notifying a process.
I’ll cover each of these items in more detail in a later blog, but here's a brief explanation.
Creating a process instance is the same as running the Begin activity of a process programmatically. It's not the same as creating a process instance through the UI, which is a Global Activity.
Getting a list of instances from a view is analagous to going to your inbox in the Work Portal, or the ALIP Worklist portlet.
Getting a list of instances with a filter provides much of the functionality of search.
Calling external methods allows the user to run a method outside of the context of the Execution Dispatcher. This allows a user to run a method in an aspx page.
Notifying a process allows the user to notify a process through a standard wait activity or through one that allows for interruptions.
PAPI-WS Endpoint
The endpoint for PAPI-WS is http://:8585/portal/webservices/ProcessService?wsdl. Use this endpoint to generate stubs using .NET or Axis. See the .NET documentation or WSDL2Java for building stubs on the respective platforms.
If you are accessing PAPI-WS through ALIP, you will need to provide the basic authentication header. I’ll cover this in a later blog.
Additional information
See the following:
 |
