Field | Description |
DocType Name | Display only. Shows the TN document type for which you are creating the event map. |
Event Map Name | Display only. Shows the name for this event map. |
Map to Document Type | Contains a list of configured TN document types and a null value. If you select a TN document type from the list, the TN document type you are configuring will use the attribute configuration of the selected TN document type. All fields in the Select Attributes to Monitor panel will be disabled. If you do not select a TN document type from the list (that is, you select the null value), the TN document type you are configuring will use the attributes as configured in the Select Attributes to Monitor panel. For details about choosing to map TN document types to an event map, see Associating an Event Map with Multiple TN
Document Types. |
Send BAM Event After | Specifies when Trading Networks must pass TN document type events to Optimize for B2B: Service Execution Document Delivery Other (the default) Select the above options based on the following conditions: Select either Service Execution or Document Delivery only when the processing rule for the TN document type you are monitoring has both the Execute a Service and Deliver Document By processing actions associated with it. You do this to avoid sending duplicate events to Optimize for B2B. For example, if you select Service Execution, Trading Networks sends the events only after the associated service identified in the processing rule completes execution. Likewise, if you select Document Delivery, Trading Networks sends the events only after the associated document is delivered. For more information about how events are passed to the broker (deprecated), see Stages at Which Events Are Passed to the
Broker . Select Other when the processing rule for the TN document type you are monitoring has: Only one (but not both) of the Execute a Service or Deliver Document By processing actions associated with it -OR- Neither the Execute a Service nor the Deliver Document By processing actions associated with it. |
Event Map Name | Display only. Shows the name for this event map. |
Field | Description |
Post Multiple Events for Arrays | For the system attributes and the custom attributes that use a list, specifies how Trading Networks events will be passed to Optimize for B2B. If the number of values for an event can vary, and if you want to monitor multiple events, select this option. Doing so will send multiple events for the same document when there is an arraylist in custom attributes or multiple elements in system attributes. For more information, see Monitoring Multiple Events in Array
Lists. If the number of values for an event is known and is not expected to change, do not select this option. Instead, complete the Maximum Number of Items field for each list attribute. Doing so will create multiple attributes in the event map. For example: ordernumber1, ordernumber2, ordernumber3. Choose these options carefully to ensure that Trading Networks passes the events to Optimize for B2B correctly. For more information about processing rule actions, see webMethods Trading Networks Administrator’s Guide. |
Attribute Name | Lists the system attributes and custom attributes that are available for monitoring. Select the attributes that you want to monitor. Note: The system attributes Sender ID, Receiver ID, and Internal ID are always monitored. You cannot clear the selection of these attributes. |
Maximum Number of Items | For the system attributes and the custom attributes that use a list, specify the maximum number of items to send to Optimize for B2B for monitoring. Note: This field is disabled when Post Multiple Events for Arrays is selected. Note: The system attributes that use a list are Sender Profile Group and Receiver Profile Group. |