Triggers Distribution (Magic xpi 4.5)

« Go Back


Created ByKnowledge Migration User
Approval Process StatusPublished

Triggers Distribution (Magic xpi 4.5)

The start.xml file lets you define which triggers will run on each server. Whenever you build or rebuild a project that contains triggers, an example start.xml.triggers file is created under the projects/<project name> folder.


  • Because the start.xml file is not changed after it has been created, an example file is used to hold the trigger details.

  • For more information about trigger architecture, see this image.

Trigger elements hold the following details:

  • BP_ID

  • Flow_ID

  • Trigger_ID

  • Name

In the start.xml.triggers file, you will see these trigger details expressed in the following way:

<Trigger BP_ID=”1” Flow_ID=”3” Trigger_ID=”2” Name="SFDC Customers sync"/>

<Trigger BP_ID="1" Flow_ID="7" Trigger_ID="3" Name="Check Emails"/>

<Trigger BP_ID="2" Flow_ID=”5” Trigger_ID="5" Name="Sugar Contacts"/>

To determine which triggers will run on which server, you need to copy and paste the trigger details into your project’s start.xml file, as shown here.

Each Magic xpi server is responsible for loading and maintaining its own triggers. The following rules apply:

  • When you define the Triggers load element as true, and there are no child elements, all triggers will be loaded. This is the same as the previous Magic xpi functionality.

  • When you define the Triggers load element as false, no trigger will be loaded even if specific triggers are defined.

  • When you define the Triggers load element as true, and child elements exist, only those triggers defined by the child elements will be loaded by the engine.

  • You cannot load more than one instance of the same trigger on a single engine. However, the same trigger can be configured to be started by multiple engines.

  • It is not necessary to define the HTTP, Web service, and SDK external triggers in the trigger list. These triggers will function anyway.

  • If you do define HTTP and Web service triggers in the trigger list, these entries will be ignored.

  • Even if only one SAP R/3 trigger is defined in the start.xml file, all SAP R/3 triggers defined for the project will be loaded.


  1. This example shows a server running the TCP listener trigger on host

  2. This example shows how to run a single instance of a specific trigger and multi instances of other triggers.

Since version:


Related Topics