Advanced Message Start Event Properties

Properties Page

Property

Description

Implementation

Integration Server Name

Assigned Integration Server Name.

Note:

When a callable process contains both a none start event and a message start event that is configured to use an EDA event type, the message start step and the none start step of the child process must be on different Integration Servers (that is, the Integration Server Name property must be different for each of the two steps). Otherwise a validation error occurs during the build and upload procedure.

Receive Protocol

Type of receive protocol to use. Select Subscription (For Publishable Documents) or JMS (for JMS Triggered Processes) (default), or EDA (For EDA Event Triggered Processes) from the list.

Note:

Dragging and dropping an event type automatically configures the Receive Protocol to use EDA (For EDA Event Triggered Processes).

Receive Document

The document type to receive.

Click Browse... to open the Choose Document window and locate a service on an Integration Server or in CentraSite.

Click New... to open the Create a New Document Type window and create a new document on a configured Integration Server.

Click View... to open the selected document in a document editor. The View... button is available only when a document is specified in the Document field.

Note:

If you created the step by dropping an IS document or event type onto the canvas, or if you drop an IS document or event type onto an existing message start step, this field is automatically populated with the IS document name.

Note:

Selecting an e-form or CSP sourced Integration Server document as the step's Receive Document automatically selects the Enable content repository support check box and enables E-form properties.

Receive EDA Event

For the EDA protocol only. The Integration Server document type associated with the EDA event type is displayed when using EDA (For EDA Event Triggered Processes) as the Receive Protocol. This field is not editable.

Protocol Properties

Available for JMS and EDA protocols only.

Connection Alias. Accept the default PE_NONTRASACTIONAL_ALIAS for JMS or EventBus for EDA, or click Browse to select another alias (an Integration Server connection is required). For more information, see Configuring a JMS-Triggered Process and Configuring an EDA-Triggered Process.

Destination Name. Required. Defined by default as: projectName_ProcessName_ SUBQUEUE. To specify another destination name, click Browse (an Integration Server connection is required).

Subscription Filter

Available for the Subscription and JMS protocols only. The instances of a subscription document that can trigger the process. See Working with Subscription Filters.

Generate Service

Selected by default to generate a wrapper service. If cleared, no wrapper service is generated. This improves Process Engine performance.

Important:

If a wrapper service already exists, selecting this option deletes the existing service.

Generated Service Name

Name of the generated flow service used at run time

Allow Parallel Execution

Lock the step at run-time to allow it to be executed by multiple threads.

E-form

Selecting an e-form or CSP sourced Integration Server document as the step's Receive Document automatically selects the Enable content repository support check box and enables E-form properties.

For more information on working with e-forms, see Selecting an E-form Content Repository and the PDF publication Implementing E-form Support for BPM.

Important:

Incoming e-form instances must have the correct file name extension (for example, .xml for InfoPath forms, .xdp for LiveCycle forms). Otherwise, they will not trigger the receive task.

Content Repository

Select Browse... to specify a My webMethods Server content repository where e-form instances are monitored by the Process Engine listener. If you are using webMethods Content Service Platform documents, select your Content Service Platform repository.

For more information on working with My webMethods Server documents, see Selecting a webMethods Content Service Repository and the PDF publication Implementing webMethods Content Service Platform for BPM.

Template Name

Selecting an e-form or CSP sourced Integration Server document as the step's Receive Document automatically populates this field.

For more information about using e-forms, see Using E-forms in a Process and the PDF publication Implementing E-form Support for BPM.

For more information about using CSP documents, see Using webMethods Content Service Platform Documents in a Process and the PDF publication Implementing webMethods Content Service Platform for BPM.

Logged Fields

Outputs

Output fields to log. Outputs are logged after the step executes. See Log Inputs and Outputs.

Correlation

Select Not Used, Field, or Service. For more information, see Specifying Correlations.