and what additional options are in effect. You can also assign each software service to existing or newly created tiers and applications.
Before You Begin
It is assumed for this task that you are already familiar with the concept of software services and that you know how to create and edit software services and how to open the Rules window. For more information, see Defining or Editing User-Defined Software Services [p. 39].
After a user-defined software service is created, you need to create a group of settings that comprise the rules for the software service. It is necessary to specify, at minimum, the IP addresses and port numbers for the software service.
If you define software services for both AMD and Java/.NET Monitoring devices, when an AMD monitored software service applies to an IP address monitored by a Java/.NET Monitoring device, the software service rules are automatically transferred to Java/.NET Monitoring and need not to be configured separately on a Java/.NET Monitoring device. This rule does not apply to General Configuration Settings such as Monitoring interval which is set separately and must be kept synchronized across Data Collectors. For more information, see Configuring General Data Collector Settings [p. 31].
To configure rules for a user-defined software service: 1. Start and log in to RUM Console.
2. Select the Entire Configuration perspective.
3. Navigate to the User-Defined Software Services tab.
4. Right-click a specific software service and select Open from the context menu. It will result in opening of the Edit Software Service window.
5. In the Rules table, right-click to open the context menu and choose Add or Open. The Rule Configuration window will open.
6. On the Services tab, select or clear Enabled to activate or de-activate the service definition. 7. In Rule description, type a brief description that will later help to identify the rule.
The description you enter at this point will be shown in the Rules table, in the column Rule Name. If no text is entered here, the IP address specified later will be used as a description for this rule.
8. Right-click in the Services table and select Add or Open from the context menu. The Service Details window will pop up when adding or editing rules.
9. In the Service Details window, in the IP address(es) fields, enter the server IP address, or enter a range of IP addresses if you plan to monitor more than one server.
10. In the Port(s) fields, enter the port number of the monitored service.
You can provide a range of port numbers if such a range of ports is used in your environment. Some software services may be active on a number of predefined ports or may change ports dynamically. To allow for this, you can specify a range of ports. Note, however, that specifying more than one port for a service prevents the port number from being reported for that service. If you define more than one port for a particular service name and server IP address (by either specifying a range of ports or by creating two or more distinct rules for the same service name and server IP address but with different port numbers), the AMD will report the port number for this service as 0, causing the port number to be ignored in traffic reports.
NOTE
You can define up to 5000 definitions containing a server and a port. Each association of a server and a port counts as a single definition. Specifying a range of ports counts as providing many individual definitions.
On CAS, the number of processed server definitions is limited by the license. For more information, see Maximum Monitored Entities Licensing in the Data Center Real User Monitoring Administration Guide.
11. Optional: Select Client port(s) for reversed-direction protocols.
This option makes sense only for protocols such as X-Window whose client-server meanings are reversed. If you are uncertain, leave this option cleared.
12. Optional: Enter a virtual IP address if your network uses a pool of virtual IP addresses. For more information, see Virtual IP address [p. 87].
13. Optional: Enter the IP address of the server masking the addresses of monitored servers. If the servers you intend to monitor reside behind an appliance that masks and replaces the addresses of the target servers, you need to set NLB NAT masking IP address to the IP address of the masking server.
Without doing so, the AMD will see two unidirectional conversations instead of one bi-directional conversation between the servers and appliance:
• The conversation between the client and server is observed and recorded (IP address A talking to IP address B)
• When a response travels to the client, a different session (IP address C talking to IP address A) is recorded due to the server's IP address being replaced by the load balancer's IP address.
Unless you account for this, CAS reports will return reports with ambiguously granulated data. Using the NLB NAT masking IP address option will ensure that the AMD monitors contiguous conversations.
14. Click OK to confirm your changes and close the Service Details window. 15. Go through all available tabs and fine-tune the monitoring conditions.
The number of available configuration options depends on the analyzer. See the analyzer-specific section for more information.
16. Optional: In the Options tab, define analyzer-specific options.
The following list describes all possible options. Depending on the analyzer, some may be unavailable:
Operation load time threshold
An operation that takes more than this many seconds is considered slow. When Inherit from global setting is selected, the global setting is used. The global threshold value depends on the analyzer.
Page load time/Operation time threshold
A page load that takes more than this many seconds is considered slow. When Inherit from global setting is selected, the global setting is used. To edit the global setting, open the AMD configuration, go to Global ➤ General and set the Page load time/operation time threshold.
Server time threshold
Server time threshold relates to the server time portion of a overall page load time. Server times above the threshold limit are considered to be slow due to the poor datacenter performance. When Inherit from global setting is selected, the global setting is used. To edit the global setting, open the AMD configuration, go to Global ➤
General and set the Server time threshold. SQL query time threshold
A database query that takes more than this many seconds is considered slow. When Inherit from global setting is selected, the global setting is used. To edit the global setting, open the AMD configuration, go to Global ➤ Database Monitoring ➤
General and set the SQL query time threshold. Enable monitoring of persistent TCP sessions
When this is selected, TCP sessions not starting with SYN packets are monitored. Persistent TCP sessions, that is TCP sessions for which the start was not recorded, also referred to as non-SYN sessions, can be included in the TCP statistics, based on
configuration properties you enable in RUM Console. The inclusion of such sessions may render the statistics somewhat inaccurate and must be undertaken with care. Generate transactions and ADS data
Select this option to provide data to the report server consisting of, for example, lower-level protocol information: raw HTTP traffic data, enabling you to view the full HTTP request-response dialog.
SQL Server uses dynamic ports
This is a TDS analyzer specific option.
Select this option if the database engine you intend to monitor does not have a static port number assigned (for example, a named instance). In this case SQL Server Browser Service (SSBS) will be used to discover the actual port of the service. The AMD will use additional UDP analysis of the SSBS to discover the actual port number for the service you intend to monitor.
If you select this option make sure the connection details set in Services tab identify SQL Server Browser Service (use IP address of the server and the port number of the SSBS).
Leave this option unselected if your SQL Server uses static ports. Convert the XML content URL-encoding
This check box defines whether the XML URL-encoding content is enabled. When Inherit from global setting is selected, the global XML setting is used.
URL parameter name that contains URL encoded XML document
Provide the parameter name that contains a URL encoded XML document. If your leave the field empty, the AMD will not analyze XML documents sent in URL parameters.
17. Click OK to save the new configuration.
18. Publish the draft configuration on the monitoring device.
a. In the Entire Configuration perspective, select the Devices tab.
b. Right-click the device and select Publish Draft Configuration from the context menu.