anchor.diff:  
   [source,shell]
   ----
  -bin/standalone.sh -Dkeycloak.import=standalone/configuration/hawkular-realm.json -Djboss.socket.binding.port-offset=100
  +bin/standalone.sh -Dkeycloak.import=standalone/configuration/hawkular-realm.json \
  +                             -Djboss.socket.binding.port-offset=100
   ----
   
   The _keycloak.import_ argument is only required when starting the server for the first time, and initialises Hawkular Accounts (including setting up a default user *jdoe* with password *password*).
  
positive.code:     }
  ----
  <1> Each business transaction fragment has a unique id
  <2> This interaction based correlation id will link this business transaction fragment with the web service invocation in the second fragment
  <3> Each node can provide additional details, which includes the _btm_source_ used to identify the technology that generated the node
  <4> This fragment shows one SwitchYard Service (OrderService) calling another SwitchYard Service (OrderService/InventoryService)
  
  
negative.code: <3> The SwitchYard Reference is currently recorded as a separate Service node
  <4> HTTP invocation with the matching interaction correlation id, linking this Producer node with the Consumer node in the first business transaction fragment
  
  ==== Summary
  
  These two business transaction fragments show how a business transaction instance can be traced across JMS, Apache Camel, SwitchYard and HTTP (Web Service), with the two fragments being correlated based on an ID shared between the HTTP Producer and Consumer nodes.
  
  Feel free to try out the release for yourself on your own applications. If you have any questions or comments, please contact us on link:community/join.html[these channels].
  