By configuring the availability, you can determine which attempt failures are included in the availability metric calculation.

You can configure XML and SOAP availability globally or at the software service level.

For global configuration, open the AMD configuration and go to:

  • Global ► Middleware Monitoring ► SOAP ► Availability, or
  • Global ► Middleware Monitoring ► XML ► Availability.

For the software service level, select the Availability tab in the Edit Rule window.

Failures (transport)

Incomplete responses

You can determine whether no response, that is a hit with no response from the server should be treated as failure.

HTTP errors

The AMD is able to deliver information on seven HTTP error groups (“categories”).

  • HTTP client errors (4xx)
  • HTTP server errors (5xx)
  • HTTP unauthorized errors
  • HTTP Not Found errors
  • HTTP client errors (category 3)
  • HTTP server errors (category 1)
  • HTTP server errors (category 2)

You can decide whether each of these should be taken into account when calculating (failures transport). Note that HTTP client errors (4xx), HTTP server errors (5xx), HTTP unauthorized errors, HTTP Not Found errors, and HTTP server errors (category 1) have configurable contents. For more information, see Web - Errors.

Failures (application)

You can decide whether each of five operation attributes should be reported as failures (application).