ActiveVOS Designer User’s Guide

Partner Role Invoke Handlers

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. You can select a different invocation method by making one of the following selections:

Invoke handler

Invokes an endpoint based on:

WSA Address

URL in the <wsa:Address> field of the PDD file. For details, see Selecting a Service for a Deployment Descriptor Partner Link. Note that you can provide a URN and then map the URN to a URL in the Administration Console of the ActiveVOS server. For details, see Specifying a Replaceable URN/URL for an Endpoint Reference.

WSDL Service Port

URL in the Service's port section of the WSDL file. See Selecting a Service for a Deployment Descriptor Partner Link.

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. An addressable ReplyTo endpoint is required .

Java Service

Deployed JARs, WSDL, and other resources created from a Java Interface. For details, see Creating a Java Interface.

JMS Service

For details, see Using a Java Messaging Service Invoke Handler. Note that an addressable ReplyTo endpoint is required.

REST Service

For details, see Using a REST-based Service.

Email Service

Partner role based on the emailPLT partner link type from email.wsdl, built into the Interfaces view. This partner role invokes the Email Service enabled in ActiveVOS server. For details, see Email Service.

Identity Service

Partner role based on the identityPLT partner link type from identity.wsdl, built into the Interfaces view. This partner role invokes the Identity Service enabled in ActiveVOS server. For details, see Identity Service.

Process

BPEL process and PDD located in a workspace project and deployed to the same server as the calling process. For details, see Creating a BPEL Process as a Service for Another BPEL Process.

To select a process, see Select Process Service.

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. For details, see Creating a BPEL Process as a Service for Another BPEL Process.

To select a process, see Select Process Service.

EJB Wrapper

Custom EJB you have written, packaged and deployed to an ActiveVOS 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 Handler Properties Dialog.

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 Handler Properties Dialog.