Example business transaction definition
Example business transaction definition file in XML format.
The recommended method for modifying business transaction definitions is by using the web user interface. However, you can also edit them directly by using a text editor. If you create a business transaction definition that contains flows on one integration node but then move to a different integration node, you must edit the business transaction definition file directly to reflect this change.
The following example shows the type of information that might be contained in a business transaction definition:
<businessTransaction type="businessTransaction" description="Here is a BT" name="BT2" uri="/apiv1/business/businesstransactions/BT2" internal="true">
<businessEvents>
<endBusinessEvents
eventSourceAddress="jmsinput.transaction.Rollback"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.jmsinput.transaction.Rollback"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="jmsinput"
hasChildren="false"
internal="true"/>
<progressBusinessEvents
eventSourceAddress="jmsinput.transaction.Start"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.jmsinput.transaction.Start"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="jmsinput" hasChildren="false" internal="true"/>
<startBusinessEvents
eventSourceAddress="fileinput.transaction.End"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.fileinput.transaction.End"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="fileinput" hasChildren="false" internal="true"/>
<endBusinessEvents
eventSourceAddress="mqinput.transaction.Rollback"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.mqinput.transaction.Rollback"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="mqinput"
hasChildren="false"
internal="true"/>
<progressBusinessEvents
eventSourceAddress="mqinput.transaction.Start"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.mqinput.transaction.Start"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="mqinput" hasChildren="false" internal="true"/>
<startBusinessEvents
eventSourceAddress="jmsinput.transaction.End"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.jmsinput.transaction.End"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="jmsinput" hasChildren="false" internal="true"/>
<progressBusinessEvents
eventSourceAddress="fileinput.transaction.Start"
eventUri="/apiv1/monitoring/events/default.IN-OUT.INOUT.fileinput.transaction.Start"
flowUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
nodeName="fileinput" hasChildren="false" internal="true"/>
</businessEvents>
<elements description=""
elementUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/INOUT"
name="INOUT" type="http://www.ibm.com/iib/btm/element#flow"
xCoord="582" yCoord="67"
hasChildren="false" internal="true"/>
<elements description=""
elementUri="/apiv1/executiongroups/default/applications/IN-OUT/messageflows/GBHTTPFlow"
name="GBHTTPFlow" type="http://www.ibm.com/iib/btm/element#flow"
xCoord="878" yCoord="101" hasChildren="false" internal="true"/>
</businessTransaction>