By default, all backends discovered during business transaction exit calls are registered to controller in standard format (host, port) or in RFC case RFC_<connection name>. This configuration allows users to apply specific rules for backend detection, naming formulation, and allows users to add details to discovered backends.

To add a backend rule, click Add backend rule. To edit an existing backend rule, click Edit backend rule.

Backend Rule Types

The following backend rule types are supported:

Backend Rule Type

Description

HTTP Backend

Outbound call via HTTP, offers filtering for host, port, URI, query in the URL.

RFC Backend

Outbound call via RFC, offers filtering based on destination name, target host, system number.

Add Backend Rule

Define a custom RFC backend rule or HTTP backend rule.

Backend Rule Summary

A backend rule consists of several parameters.

Field

Description

Rule Type

Defines backend rule type. Based on backend rule type, users can select different filtering and naming options in rule configuration and backend naming.

Active

Activates or deactivates the rule

Name

Identifies the backend rule. If backend is being declared during business transaction, and naming rules are not configured, backend will be named same as this field.

Priority

Defines the order of backend rule evaluation, and the highest priority number is evaluated first.

Without priority, backend rules are evaluated in the order they appear in the list of backend rules.

Rule Configuration

Backend rule configuration depends on the backend rule type.

HTTP Backend Rule Configuration

  1. Match by:

    • Host: target host name.

    • Port: target port.

    • URI: URI in HTTP call.

    • Query: query string in URL (section of URL after “?”).

  2. Each input field has the following options:

    • Equals: case sensitive, has to be equal to compared value.
      Example: URI - “/sap/order/orderId={2145}” Equals - “/sap/order/orderid={2145}”

    • Starts with: case sensitive, no wildcards, URI has to start with provided value.
      Example: URI - “/sap/order/orderId={2145}” Starts with - “/sap/order”

    • Ends with: case sensitive, no wildcards, URI has to end with provided value.
      Example: URI - “/sap/order/orderId={2145}” Ends with - “{2145}”

    • Contains: case sensitive, no wildcards, has to contain part of the URI.
      Example: URI - “/sap/order/orderId={2145}” Contains - “order”

    • Matches RegEx: case sensitive, URI must match provided regular expression.
      Example: URI - “/sap/order/orderId={2145}” RegEx - “\/sap\/order\/orderId=\{[0-9]*\}”

    • Is in list: case sensitive, URI has to be in list defined with delimiter “,”.
      Example: URI - “/sap/order/orderId={2145}” Is in list - “/sap/order/orderid={2145},/sap/order/orderid={2146},/sap/order/orderid={2147}”

    • Is not empty: matches any URI if its not empty.

  3. BT Name filter - allows user to apply backend rule only to selected business transactions based on business transaction names specified in Configure Business Transaction Detection. If left empty, the rule is applied to all HTTP backends in all business transactions.

RFC Backend Rule Configuration

  1. Match by:

    • Destination: RFC destination name as per SM59

    • Host: RFC destination target host

    • System number: SAP system number

  2. Each input field has following options:

    • Equals: case sensitive, has to be equal to compared value.

    • Starts with: case sensitive, no wildcards, URI has to start with provided value.

    • Ends with: case sensitive, no wildcards, URI has to end with provided value.

    • Contains: case sensitive, no wildcards, has to contain part of the URI.

    • Matches RegEx: case sensitive, URI must match provided regular expression.

    • Is in list: case sensitive, URI has to be in list defined with delimiter “,”.

    • Is not empty: matches any URI if its not empty.

  3. BT Name filter: allows user to apply backend rule only to selected business transactions based on business transaction names specified in Configure Business Transaction Detection. If left empty, the rule is applied to all HTTP backends in all business transactions.

Backend Naming

Backend naming options also depend on the backend rule type.

HTTP Backend Naming

  1. Merge backend name: value of backend name parts will be merged using this value. For above example, backend name registered on controller for example URL vsks021.company.com/orders?customer=kenobi&order=1456 would be vsks021_company_443_/orders_order=1456.

  2. Backend name components: same as Match by options.

  3. Each component has following options:

    • As it is: the whole property value is used.

    • Use the first/last: after selecting one these options, input fields for segments and splitting will appear. Segments are determined by splitting character. Example - segments for host service.company.com if split by “.” would be service, company, com.

RFC Backend Naming

  1. Merge backend name: value of backend name parts will be merged using this value. For above example, backend name registered on controller for example RFC connection with name HK1_RFC, system number 01 and host hk1sys.company.com would be in format: HK1:hk1sys:01.

  2. Backend name components: same as Match by options.

  3. Each component has following options:

    • As it is: the whole property value is used.

    • Use the first/last: after selecting one these options, input fields for segments and splitting will appear. Segments are determined by splitting character. Example - segments for host service.company.com if split by “.” would be service, company, com.