anchor.diff:  * Apache Tomcat
   * Apache Karaf OSGI container
   
  -=== The BTM Server
  -
  -The Business Transaction Management (BTM) Server can be clustered to enable reporting and analysis of the business transaction data to be load balanced across multiple servers.
  -
  -CAUTION: The standalone server does not currently supporting a clustered configuration.
  +Instructions on how to configure the client environment can be found here: link:clientconfig.html[Client Configuration]
  +
  +=== The Server
  +
  +The Business Transaction Management (BTM) Server supports reporting and analysis of the business transaction data. These capabilities can be access through a set of REST services, more information can be found here: link:../../rest/rest-btm.html[BTM REST services]
  +
  +CAUTION: The standalone server does not currently support a clustered configuration.
  +
  +The instructions for installing the server can be found here: link:serverinstall.html[Server Installation]
  +
  +=== The User Interface
  +
  +Once the server has been installed, and started, you will be able to start up the user interface by pointing a browser to: http://localhost:<port>/hawkular/btm-ui
  +
  +_Where 'port' is the port used by the server (e.g. 8180 if port offset of 100 has been used)._
  +
  +The default username and password when first starting the server is *_jdoe_* and *_password_*.
  +
  +==== Kibana analytics dashboard
  +
  +The UI currently only provides access to the Kibana analytics dashboard, showing the response time information derived from the executing business transaction instances.
  +
  +Some tips on using Kibana:
  +
  +* The 'filters' green tab at the top of the page can be expanded to show the current filters that have been applied. Whenever you select a time region (from the top chart), or select a magnifying glass or no entry icon, this will cause the information being viewed to be further constrained by adding an additional filter. When you wish to revert back to a previous level of information, simply remove (or disable) the particular filter box.
  +
  +* In the lower table, showing the latest response time 'records', you can select the fields in the left hand column to get further statistics regarding the different values.
  +
  +Further information on using Kibana can be found here: https://www.elastic.co/guide/en/kibana/3.0/index.html
   
   
   == Business Transaction Configuration
  
positive.code: 
  |SetFault |Define a fault value. The '*_expression_*' field is the MVEL expression used to extract the fault name
  
  |SetProperty |Extract a named business property. The '*_name_*' field names the business property, and '*_expression_*' defines the MVEL expression used to extract the value
  
  |===
  
negative.code: 
  |String evaluate(String xpath, Object node) |This method applies an XPath expression to the XML document/fragment supplied in the following formats:  _String_, _javax.xml.transform.dom.DOMSource_ and _org.w3c.dom.Node_.
  
  |Node selectNode(String xpath, Object node) |This method applies an XPath expression to the XML document/fragment supplied in the following formats:  _String_, _javax.xml.transform.dom.DOMSource_ and _org.w3c.dom.Node_, to select a Node.
  
  |String serialize(Object node) |This method attempts to serialize the supplied node as a textual representation of an XML document. The supported input formats are: _String_, _javax.xml.transform.dom.DOMSource_ and _org.w3c.dom.Node_.
  
  |Node deserialize(Object node) |This method attempts to deserialize the supplied representation of an XML document. The supported input formats are: _String_, _javax.xml.transform.dom.DOMSource_ and _org.w3c.dom.Node_.
  
  |===
  
  
  == Properties
  
  The system wide properties are now defined within a single *_btm.json_* file that is included within the _standalone/data/btmconfig_ folder of the BTM server.
  
  The current properties that can be configured here are:
  
  .BTM Properties
  |===
  |Property Name | Default | Description
  
  |hawkular-btm.collector.onlynamed | false | Determine whether only business transaction fragments associated with a business transaction name should be reported.
  
  |===
  
  
  
  