When SharePoint® monitoring is configured, the appliance records when information is transmitted to and from the server. For example, when a user publishes content to a SharePoint server, in a form (POST parameter), the appliance monitors the URLs that contain this activity. You can define how the URLs display in the web console using several options. For example, you can display request methods (POST, GET) in URLs by setting the Show HTTP request methods in URL option using the Advanced Options on the URL page. For more information, see Advanced URL options.
By default, SharePoint encodes its URLs in a manner that makes their URLs difficult to read. In the web console, you can decide whether to display URLs as they are originally encoded or decoded in a manner that makes them more readable. For information about displaying URLs in the web console, see Encoded and decoded URLs. When SharePoint monitoring is first enabled, the appliance automatically populates a list of default variable rules. You can customize a variable rule defining how the system will transform the query segments of URLs. For more information, see Managing variable rules.
When a document is edited on a SharePoint site, its name is stored on the server and by default, the appliance displays this document name in the URL displayed in the web console. If you do not want to display this information in URLs, you can configure whether these document names are displayed by changing the variable rules. For more information, see Managing variable rules.
SharePoint and SOAP
If you are monitoring SOAP based web services you can view SOAP Operations for SharePoint®, on the All Metrics View > User Sessions. For many of the user actions performed in SharePoint, a SOAP operation call is made by the browser. Examples of user actions that result in SOAP operations are document checkout and check in. These SOAP operations are often intermixed with non-SOAP requests. The SharePoint analysis module within the appliance will combine these SOAP and non-SOAP requests to form a page. The metrics for this page display in the Page category. The display of SOAP operations names is handled differently from non-SOAP names. Regular hits display as a standard URL, and might include additional form variables appended to the URL. For example:
GET site.com/path1/index.html;param1=a?query1=b&query2=c [ form1=d&form2=e]
A SOAP operation however will show the soap action and request method.
SOAP example:
POST site.com/path1/SoapAction RequestMethod
Additionally, there are several more options for controlling how the SOAP operation name is constructed, such as including the adaptor in SOAP Operations, including server display names in SOAP Web Service and SOAP Operation names, and including the port in SOAP Web Services, SOAP Operation and SOAP Server names. To configure these options navigate to Configure > Applications > SOAP page.
Monitoring PeopleSoft applications
PeopleSoft’s applications help to improve and maintain critical relationships with customers and employees. By enabling PeopleSoft monitoring, the appliance monitors the web pages (HTTP request and responses) being passed between the client and the server. Any critical business processes delivered by PeopleSoft applications are monitored. Metrics and data from these processes are displayed in the web console.
Figure 80. PeopleSoft page
Configuring the Peoplesoft options controls which URLs are treated as Peoplesoft requests. Hits with URLs that match any regular expressions (configured on the Peoplesoft page) are processed by the appliance to
reconstruct the user's actions based on the sequence of Peoplesoft URLs and then determine the performance of these user actions. These Peoplesoft user actions display in the Page category.
For more information, see these topics: • Monitoring PeopleSoft applications • Configuring how URLs display
Monitoring PeopleSoft applications
Configuring PeopleSoft monitoring involves defining a set of regular expressions and installing a set of pre- defined configuration settings.
To configure PeopleSoft monitoring:
1 Navigate to the Configuring > Applications > PeopleSoft.
Adding regular expressions
2 Enter a Perl regular expression in the box. For example, if you know where the PeopleSoft applications are located (all components are found under quest.com/mypeoplesoft/support/), enter the
expression (in this case, quest.com/mypeoplesoft/support/.*).
Multiple regular expressions can be added.
3 Click Add and proceed to Testing regular expressions validity.
Alternatively, if you don’t know where application components are located, click the Pick a Directory link to display a window that lists the directories in use on your site.
This window allows you to easily select an existing directory to serve as the basis for a regular
expression. By selecting an item in this window, the box will be initialized with a regular expression that matches the directory you chose. This list is not obtained by an active search of your web site, but rather from the list of URLs that have been monitored and recorded by the appliance in the past.
4 From the Directory List, navigate to and select a directory.
This directory is added to the Selected Directory section (some directories contain subdirectories, directories that are nested beneath the top-level directory. For example, my.prod.quest.corp is a
subdirectory of my).
5 Click OK.
The directory is added to the regular expressions list.
Testing regular expressions validity
6 To display a list of URLs that match the regular expression, click Test.
This test is performed against the list of URLs that have been monitored and recorded by the appliance in the past.
7 Close the window when you are finished reviewing the resource list.
Configuring PeopleSoft configuration settings
8 In the PeopleSoft Configuration Settings section, click Apply to install pre-defined configuration settings. The appliance will monitor servers previously configured on the Servers page use these settings.
Configuring how URLs display
When PeopleSoft monitoring is configured, the appliance records when information is transmitted to and from the server. You can define how the URLs display in the appliance using several options. For example, you can display request methods (POST, GET) in URLs by setting the Show HTTP request methods in URL option using the Advanced Options on the URL page. For more information, see Advanced URL options.
PeopleSoft as well as other applications encode their URLs. For ease of use, you can decide whether to display URLs encoded or decoded. For information about displaying URLs in the web console, see Encoded and decoded URLs.
Figure 81. Variable Rules page
.
When you apply the pre-defined configuration settings, the system automatically populates a list of default variable rules. You can customize a variable rule defining how the system will transform the query segments of URLs. For more information, see Managing variable rules.