ActiveVOS Server User’s Guide
By default, the ActiveVOS server invokes an endpoint by looking up the service name in the WSDL to find the endpoint (e.g., the <soap:address>) and using the standard engine invocation framework. The PDD file can specify a different invocation method by including one of the following selections:
|
Invoke handler |
Invokes an endpoint based on: |
|---|---|
|
WSA Address |
URL in the <wsa:Address> field of the PDD file. Note that the PDD can provide a URN and then you can map the URN to a URL in the Administration Console of the ActiveVOS server. For details, see the Administration Console Online Help for URN Mappings. |
|
wsrm:Address |
Same as address above, except that the messages are sent using the WS-Reliable Messaging protocol. Select this handler if you will attach the reliable messaging policy assertion, described in WS-Reliable Messaging. |
|
WSDL Service Port |
URL in the Service's port section of the WSDL file. |
|
Java Service |
Deployed JARs, WSDL, and other resources created from a Java Interface. |
|
jms service |
For details, see Using a Java Messaging Service Invoke Handler in Designer Online Help. |
|
REST service |
For details, see Using a REST-based Service in Designer Online Help. |
|
email service |
Partner role based on the emailPLT partner link type from email.wsdl. This partner role invokes the Email Service enabled in ActiveVOS Server. |
|
identity service |
Partner role based on the identityPLT partner link type from identity.wsdl. This partner role invokes the Identity Service enabled in ActiveVOS Server. |
|
process |
BPEL process and PDD located in a workspace project and deployed to the same server as the calling process. |
|
process:subprocess |
BPEL process and PDD located in a workspace project and deployed to the same server as the calling process. The process is a subprocess; that is, it is eligible for compensation within the enclosing scope of the calling process. |
|
ejb wrapper |
Custom EJB you have written, packaged and deployed to an ActiveVOS Server server that supports EJBs. You can specify the JNDI location of the EJB as well as the query string required to invoke the endpoint. For details, see Custom Invoke Handlers. |
|
java wrapper |
Custom Java class you have written, packaged and deployed to the server. You can specify the fully qualified class name for the java class as well as the query string required to invoke the endpoint. For details, see Custom Invoke Handlers. |
Copyright (c) 2004-2008 Active Endpoints, Inc.