SALES: 1-800-867-1380

X12 Send Agreement: Batching Settings

Updated: August 1, 2014

Configure Batching in X12 agreement in Azure BizTalk Services. The Batching page on the Send Settings tab allows you to create batches to send several messages as a batch to a partner. You can also specify rules based on which a batch is triggered. These rules are based on the values of promoted properties you defined in the earlier stages. These rules are based on the values of promoted properties you defined in the earlier stages.

Add a Batch

  1. On the Batching page of the Send Settings tab, click Add Batch to launch a wizard.

  2. In the Batch details page, enter a batch name and a batch description, and then click Next.

  3. In the Batch criteria page, specify the criteria based on which a batch configuration will be triggered. The batch criterion is specified using the values of the promoted properties at runtime. You can either select the value from a grid to specify the batching condition or use a standard SQL 92 syntax to define the batching condition. To understand this better, let us assume you promoted a property (P1) whose value is set to ‘100’ at runtime. To use this property as a condition for triggering a batch, you can do either of the following:

    • Select the option for the grid, and then click the (+) icon to select the property you promoted. From the grid, select P1, specify the Operation as (==), and set the value to 100.

      OR

    • Select the Use advanced definitions option, and specify a SQL 92 expression, such as:

      P1 == 100
      
      You can use this option to provide more detailed query expressions using other operators as well. In the example used here, during the agreement processing if a property P1 is created and its value is set to 100, this batch is triggered.

    Click Next.

  4. In the Batch release criteria page, specify the criteria for batching messages together. The drop-down lets you select more than one criterion for batching, however there are four key criterion that can be used together to provide different combinations.

    • InterchangeSizeBased – For the Size(max) property, specify the number of characters to create and send a batch. The agreement accumulates batching elements until the character count in those elements exceeds the specified character count.

    • MessageCountBased – For the Count property, specify the number of messages that must be processed together as a batch.

    • ScheduleBased – For this option, specify the following properties:

      • Occurs – Specifies the unit of measurement of time in terms of minutes, hours, days, or weeks.

      • First release – Specifies which day and at what time the first batch is released.

      • Recurs every – Specifies the frequency or recurrence, after the first occurrence. For example, if you set this property to 2 and the Occurs property to Hourly, the messages are batched every 2 hours after the first release.

      noteNote
      There could be a variation of +/- 10 seconds while releasing batches based on these criteria. Also, the time period starts when the first message is received by the bridge.

    • TimeoutBased – This property specifies the timeout (in minutes) at which a batch is triggered, irrespective of whether any other criterion is met or not. This property is always used along with another property. For example, if you set the batch release criteria to MessageSizeBased, TimeoutBased and the values to 3 messages and 5 minutes respectively, the agreement will first wait to collect three messages to constitute a batch. If three messages do not arrive in 5 minutes, the agreement will go ahead and process the batch with whatever number of messages that is available. Note that the timeout value is the idle time from the last released batch. For the first batch, this timeout is the idle time from the start of the batch.

      noteNote
      There could be a variation of +/- 10 seconds while releasing batches based on these criteria. Also, the time period starts when the first message is received by the bridge.

    You can select different combinations of these key criterions to define when a batch is released.

  5. In the Summary page, verify the batch configuration and then click Save.

    Certain points to consider regarding batches:

    • When you finish these steps, a batch is created. A batch is deployed only when you deploy the agreement containing the batch.

    • You cannot edit a batch when the agreement is deployed. To edit a batch you must first stop the batch by clicking the Stop Batch link next to the batch.

    • Once you finish editing a batch, you must redeploy the agreement to ensure that the updated batch configuration is used for further batch processing.

    • If you are redeploying an agreement, you do not need to stop the batches associated with it. However, you must ensure that the changes that are made to the agreement do not affect the running batches. For example, if an agreement is updated to not process a purchase order schema (850), you must ensure that none of the running batches are processing an 850 message at that point in time. If such batches are not stopped, the messages are suspended when the batch is released.

    • Before you delete an agreement, you must stop any batches associated with the agreement.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft