anchor.diff:  This kind of _PUT Request_ can be used to change the Business Service in general.
   The `business-service-id` used in the `url` has to match the `business-service-id` used in the body of the request.
   
  -TIP: The list of Monitored-Services including ids can be queried via the Rest-API form `opennms/rest/ifservices`
  -
  -===== Check operational-state
  +===== Check operational state of a business service
   `GET opennms/api/v2/business-services/$business-service-id/operational-status`
   This call provides the _operational-status_ of the business service.
   The result is on of the OpenNMS _severities_ in text representation.
   //TODO can Cleared or Indeterminate happen?
   (Critical, Major, Minor, Warning, Normal, Cleared, Indeterminate)
  -
  -==== Business Service based on _Monitored Services_
  -The most basic way to use a Business Service is to assign multiple Monitored-Services to it.
  -The alarm based status of the Monitored-Services is then the basis of the Business Services status.
  -The status of the Business Service then depends on the highest _severity_ of the _Alarms_.
  -
  -==== Business Service based on _Reductionkeys_
  -Add a Monitored Service
  -Remove a Monitored Service
  -
  -==== Business Service based on Business Services
  
positive.code: | `Set To`   | Uses a constant severity
  | `Ignore`   | Ignores the severity of the managed element
  |===
  ////
  
  
  ===== Operational-status changes
  If a Business Service changes its operational-status, an OpenNMS _Event_ is fired.
  The _Event_ is of the type `uei.opennms.org/bsmd/serviceOperationalStatusChanged`.
  The _Log Message_ of the _Event_ contains the name of the Business Service.
  Additionally the previous operational-status and the new operational-status are included.
  This _Event_ has no _Node_, _Interface_ or _Service_ associated.
  It also does not contain a _Reductionkey_ to cause any _Alarms_.
  
  
  ===== Reload the BusinessServiceDaemon
  //TODO What situations require a reload?
  
  A config reload is always initiated by an _uei.opennms.org/internal/reloadDaemonConfig_ event with the parameter `daemonName` set to `bsmd`.
  If the reload of the config is done an _uei.opennms.org/internal/reloadDaemonConfigSuccessful_ event is fired.
  
  .List of ways to trigger the config reload event
  - Use the `Reload` button on the `Manage Business Services` page in the admin section of the WebUI.
  - Send the  _reloadDaemonConfig_ event directly to trigger the reload
  * Use the send-event script
  
negative.code: </business-service>
  ----
  
  
  ===== List business services
  `GET opennms/api/v2/business-services`
  Provides a list of all business services as reference urls.
  
  
  ===== View business service
  `GET opennms/api/v2/business-services/$business-service-id`
  Provides the business service selected by the provided business-service-id.
  
  
  ===== Create via Rest-API
  `POST opennms/api/v2/business-services`
  Post the business service model as XML or JSON.
  This is the minimal model: `{"name": "MinimalBusinessServiceNameOnly"}`
  
  
  ===== Delete via Rest-API
  `DELETE opennms/api/v2/business-services/$business-service-id`
  Deletes the business service selected by the provided business-service-id.
  
  
  ===== Working with Ip-services
  Ip-services are used as references to monitored services.
  The Ip-service and its corresponding monitored service share the same id.
  
  TIP: The list of Monitored-Services including ids can be queried via the Rest-API form `opennms/rest/ifservices`
  
  ====== View Ip-service
  `GET opennms/api/v2/business-services/ip-services/$ip-service-id`
  Provides the Ip-service selected via the $ip-serice-id
  
  ====== Attach an Ip-service to a business service
  `POST opennms/api/v2/business-services/$business-service-id/ip-servies/$ip-service-id`
  Attaches the Ip-service selected by the $ip-service-id to the business service selected by the $business-service-id.
  
  ====== Detach an Ip-service from a business service
  `DELETE opennms/api/v2/business-services/$business-service-id/`
  Detaches the Ip-serice selected by the $ip-service-id from the business service selected by the $business-serice-id.
  
  ===== Working with contained business services
  ====== Add an business service to a business service
  `POST opennms/api/v2/business-services/$business-service-id/`
  
  ====== Remove an business service from a business service
  `POST opennms/api/v2/business-services/$business-service-id/`
  
  
  ===== Edit a business service
  `PUT opennms/api/v2/business-services/$business-service-id`
  Put the business service model as XML or JSON.
  
  .A minimal Business Service with an assigned _ip-service_
  [source:JSON]
  