Mensaje

Resumen. Resumen. Resumen. Resumen. Resumen. Resumen.

Resumen. Resumen. Resumen. Resumen. Resumen. Resumen.

Advanced

BPMN-Specification-text. BPMN-Specification-text. BPMN-Specification-text.

BPMN-Specification-text. BPMN-Specification-text. BPMN-Specification-text.

Sección 1

Texto. texto. texto. texto. texto. texto.

Sección 2

Texto. texto. texto. texto. texto. texto.

Otros

La comunicación entre los Procesos de dos Participantes se describe con un Flujo de Mensaje. El Mensaje representa el contenido de dicha comunicación.

Opcionalmente, en el diagrama se puede colocar la representación gráfica del Mensaje: un rectángulo con líneas diagonales convergentes en su mitad superior, para dar la apariencia de un sobre. Debe estar colocado en el punto medio del Flujo de Mensaje.

Es posible distinguir entre el Mensaje que inicia una interacción (initiating Message) y el que responde (non-initiating Mesage). Este último se dibuja con un fondo sombreado claro (Figura 8.27).

Las Tareas de Servicio, Envío y Recepción, y los Eventos Mensaje (Captura y Lanzamiento) son los elementos BPMN usados para el envío y recepción de Mensajes.

Temporal

Texto.Texto.

Texto.Texto.

Texto.Texto.

Texto.Texto.

Especificación BPMN

A Message represents the content of a communication between two Participants. In BPMN 2.0.2, a Message is a graphical decorator (it was a supporting element in BPMN 1.2). An ItemDefinition is used to specify the Message structure.

When displayed in a diagram a Message is a rectangle with converging diagonal lines in the upper half of the rectangle to give the appearance of an envelope (see Figure 8.26). It MUST be drawn with a single thin line.

In addition, when used in a Choreography Diagram more than one Message MAY be used for a single Choreography Task. In this case, it is important to know the first (initiating) Message of the interaction. For return (non-initiating) Messages the symbol of the Message is shaded with a light fill (see Figure 8.27).

In a Collaboration, the communication itself is represented by a Message Flow (see “Message Flow” below for more details). The Message can be optionally depicted as a graphical decorator on a Message Flow in a Collaboration (see Figure 8.28).

A single message can be associated to many message flows. Service, send and receive task are associated to message.

Note that for Message Flow with an envelope decorator, the envelope decorator should be at the midpoint of the message flow.

BPMN nodes sending or receiving Messages: Message Events, Service, Send or Receive Tasks.

For a Send Task and a Service Task, the single input set is mapped to a WSDL message defining the input of the associated WS-BPEL activity. The inputs map to the message parts of the WSDL message. For a Receive Task and a Service Task, the single output set is mapped to a WSDL message defining the output of the associated WS-BPEL activity. The outputs map to the message parts of the WSDL message. (Page 466.)

For example, if a company is waiting for a response from a customer they will perform one set of Activities if the customer responds “Yes” and another set of Activities if the customer responds “No.” The customer’s response determines which path is taken. The identity of the Message determines which path is taken. That is, the “Yes” Message and the “No” Message are different Messages—i.e., they are not the same Message with different values within a property of the Message. The receipt of the Message can be modeled with an Intermediate Event with a Message trigger or a Receive Task. In addition to Messages, other triggers for Intermediate Events can be used, such as Timers.

solocastellano