Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - Installation and Administration Guide

Installing and configuring Multi-appliance clusters Configuring the appliance Specifying monitored web traffic Transforming monitored URLs Managing applications Foglight components and the appliance Using the console program Troubleshooting the appliance Appendix: Third party software Appendix: Dell PowerEdge system appliance

Modifying SOAP application definitions

You can modify a SOAP application definition by clicking its corresponding Edit link, which takes you to the SOAP > SOAP Application > Edit page.

In the SOAP Application section, you can edit the application name, set service level thresholds and choose distribution configurations.

 
* 
NOTE: If you modify an existing application definition name, this change takes up to 30 minutes to propagate throughout the metrics that are displayed in the web console.

You can also modify the regular expressions that identify the application. Select an expression’s corresponding check box, and click Delete to remove it. You can then replace it by adding regular expressions in the manner outlined in the previous section.

Deleting SOAP application definitions

When viewing the list of application components on the SOAP page, you can delete an entry by selecting its corresponding check box and then clicking Delete.

Defining a SOAP transaction

You can create a new SOAP transaction on the SOAP > Edit page.

To define a SOAP transaction:
1
From the SOAP page, in the SOAP Transactions section, select Add a SOAP Transaction.
Naming the SOAP transaction
2
In the Name box, type a unique, symbolic name you wish to associate with this SOAP transaction.
Each SOAP transaction must have a unique name, and users will use this name to locate the metrics recorded for this transaction in the web console.
Defining a service level threshold for SOAP transaction
3
In the End-to-End Time Service Level Threshold box, type the service level objective for the total time taken for all SOAP requests identified in this transaction.
For example, if you decide that most of the services should be fulfilled within 15 seconds, enter 15000 (units are in milliseconds).
4
In the Processing Time Service Level Threshold box, type the desired service level for the total processing times for all steps in the SOAP Transaction.
For example, if you decide that the processing time for most transactions should occur in under one second, enter 1000 (units are in milliseconds).
5
In the End-to-End Time Distribution Configuration box, select the distribution configuration that you would like to use for this service. Distribution configurations allow you to specify the buckets and ranges of the distribution. For more information about how this metric is calculated, see End-to-End Time Distribution in the Foglight Experience Monitor Metric Reference Guide.
6
In the Processing Time Distribution Configuration box, select the distribution configuration that you would like to use with this SOAP transaction.
For information on how this metric is calculated, see Processing Time Distribution in the Foglight Experience Monitor Metric Reference Guide.
Adding SOAP operations to the transaction
7
Click Add a SOAP Operation to begin building a sequence.
A Resource List window is displayed, listing all SOAP operations that the appliance has detected (as shown below).
8
If desired, narrow the list to a more specific set of pages by typing a search string in the Search box, and then clicking Go.
You can use an asterisk (*) as a wild card to define a segment of the string that matches any combination of characters.
•
Optionally, reduce the list further by opting to display only HTTPS secure or HTTP insecure web pages from the Protocol list, then clicking Go.
•
Show URLs with encoding or decoding.
9
Click any page to add it to the transactions sequence, after which the window closes.
10
Repeat this procedure until all SOAP operations that form the transaction have been added to the definition.
 
* 
NOTE: Every defined SOAP transaction definition must have a unique sequence of SOAP operations.
11
After all operations have been added, if required, the sequence of SOAP operations can be rearranged by using the and buttons.
12
Click OK to complete the process.
The appliance begins monitoring for activity immediately.

Managing existing SOAP transaction definitions

When viewing the list of defined SOAP transactions on the SOAP page, you can delete definitions by selecting their corresponding check box, and then clicking Delete.

Check All is used to select all entries for deletion, and Clear All is used to clear any entries that were selected for deletion.

Modify a SOAP transaction definition by clicking its corresponding Edit link. Doing so takes you to the SOAP Transactions > Edit page, which allows you to rename the SOAP transaction, add or remove SOAP operations, or reorder the operations by using the and buttons.

Mapping SOAP operations to a web service

The system attempts to correlate SOAP Operations with a corresponding SOAP Web Service when monitoring SOAP traffic. While SOAP v.1.1’s SOAPAction HTTP header tag can provide this information, web services that follow the SOAP v.1.2 standard may not be able to rely on it, since its use is no longer mandatory. As an alternative, the appliance can use a WSDL (Web Services Definition Language) file to establish these relationships.

A WSDL file provides the mapping of a SOAP Operation to a SOAP Web Service in FxM. The SOAP Web Service appears in the name of the SOAP Operation in the Resource List. For example:

AlphaStockQuoteService getStockQuote

where AlphaStockQuoteService is the SOAP Web Service name and getStockQuote is the SOAP Operation name.

If you do not have a WSDL file loaded, this SOAP Operation is displayed as:

UNKNOWN_SOAP_SERVICE getStockQuote

Therefore, by loading the WSDL file that contains the description of the AlphaStockQuoteService you instruct the system to replace UNKNOWN_SOAP_SERVICE with AlphaStockQuoteService.

You need to configure Servers and Ports for the WSDL file only if you have two SOAP Web Services using the same SOAP Operation name (in other words, only if the SOAP Operation name appears in more than one WSDL files). For example:

AlphaStockQuoteService getStockQuote
BetaStockQuoteService getStockQuote

In this case, you need to specify Servers and Ports so that the system knows which WSDL file to use. For example, AlphaStockQuoteService may run on server 192.168.1.10, while BetaStockQuoteService runs on server 192.168.1.11. You need to specify those server IPs for each WSDL file in order to get the correct SOAP Web Service name to appear for each SOAP Operation.

Uploading a WSDL file and indicating servers and ports
To upload a WSDL file and indicating server and port:
1
Click Add a WSDL file on the main SOAP page.
The SOAP > SOAP WSDL File page is displayed.
2
In the WSDL File section, click Browse, and search for the WSDL file on your network file system.
3
In the Prefix box, specify the prefix the WSDL file uses for its elements (for example, wsdl:message), to assist the appliance when parsing the file.
4
Click Upload to upload, and begin examining the WSDL file.
When this process has been completed, the Service Name and the Operations list is populated with names obtained from the WSDL file.
5
If you have two SOAP Web Services using the same SOAP Operation name:
a
In the Servers section, click Add Server to open a list of monitored servers from which SOAP services are delivered. You can select all servers, or select individual servers to build a list.
b
In the Ports section, select the check boxes that correspond with the monitored ports over which SOAP services are delivered.
6
Click OK to complete the process.
You are returned to the main SOAP page, where the newly added SOAP WSDL file and server information are displayed.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating