There are two possible solutions to model the details of a web-service. The (not recommended) first version is using ARIS attributes at the Object which references the web-service.

For this first solution the attributes are maintainable at the ARIS objects Task and Event (if the task/event is triggered by an incoming sequence flow the web service is being executed, the target of the outgoing message flow is only used for the target participant of the message).

The attribute mapping for this solution is described in the following table.

The second, more advanced approach is using the ARIS objects PartnerLink, Interface and Operation (inside an assigned BPMN Allocation Diagram). Those objects are part of the standard ARIS BPEL modeling technique. This second approach enables a user to reuse already defined ARIS BPEL content (for example which operation belongs to which interface and which interfaces are available at which partner links). An ARIS connection is supported by from the BPMN Task towards the BPEL operation (which is executed by the Task) enables a process engine/BPEL export engine to determine the exact BPEL operation (and their interface/partner link).

In this second approach the operation, interface and partner-link attributes of the web service are fetched from the target of the message flow (the event which receives the message flow has connections towards the operation). This second approach is described inside chapter BPMN Web Service .

The BPEL Export implementation should define this definition in more detail.