Selecting .NET specific operations

.NET Remoting operations

The following .NET operations are available for recording:

  • Remoting Access: Sending and receiving requests and responses for Remoting interaction. These operations are recorded both on the Client and the Server for each Remoting call.
  • Troubleshooting user applications: The Register Channel operation will fail if the channel is already registered or unavailable. The Send Request operation will fail if the Server is unavailable.
  • Remoting Calls: Calls of client to methods on remote server, and indication of this calls on server side.
    • Remoting Configuration: Setting up Remoting connections, such as:
    • Read a configuration file and configure the Remoting infrastructure.
    • Register an object type as a type that can be activated on the client or server side.
    • Create a Remoting activated entry on the client or server side.
  • Remoting Creation operations: Creating Remoting types, and proxies for Remoting servers.

.NET Database operations

You can record specific .NET Database operations as follows:

  • ADO.NET Command operations: Filling a dataset with data from database and updating information from dataset to database.
  • ADO.NET Connection operations: Connecting to and disconnecting from a database.
  • ODP.NET Operations: Filling a dataset with data from database and updating information from dataset to database with Oracle Data Provider.

Troubleshooting user applications:

  • The Open connection operation will fail if the connection string doesn't match the database definitions, or if the database is unavailable.
  • The Execute command operation will fail if the SQL query fails, usually because of syntax problems.
  • The Fill Dataset and Update Dataset operations will fail if they are relying on a wrong query.

.NET ASP operations

You can record .NET Process ASP . NET page operations by selecting them in Advanced Mode.

.NET Library operations

In Advanced Mode, you can choose to record additional Library Heap operations as follows:

.NET Library assembly operations

You may select and record Assembly Operations in the Library Operations group.

Select the required operations to record, load and compile .NET assemblies.

Application troubleshooting: The Load assembly operation will fail if the assembly is missing.

.NET Specific Configuration operations

You can select and record specific .NET configuration operations by accessing load information from 'Config' files as follows:

  • Get .NET config elements by index: Getting the key and the value at the specified index of the application's config file.
  • Get.NET Config elements by key: Getting the value of the specified key of the application's config file.
  • Get.NET Config settings: Getting elements from the config file.
  • Set .NET Config elements: Loading the application's config file, and getting the application's settings as they are defined in the config file. Also loads operations for setting or updating values in the config file.

Troubleshooting user applications:

  • The Load config file operation, and the Save config file operation will fail if the config file cannot be found or cannot be accessed.
  • The Get .NET config elements by index operation will fail if the input index is out of bounds.
  • The Get .NET config elements by key operation will fail if the input key cannot be found.

.NET Web Services operations

You can select .NET Web Services operations in normal and Advanced Mode as follows:

  • Protocols: Sending requests to the Web service and receiving responses for these requests.
  • SOAP Messages: Creating a SOAP message for transportation of data. These operations are recorded both on client side and server side.
  • Web Services Attributes: Setting attributes to Web services or Web methods, such as Web method descriptions. These operations are recorded both on client side and server side.
  • Web Services Calls: Invocation of Web methods on the client side, indicating that a Web method was called on the server side. These operations are recorded on each request a client sends to a Web service.

Troubleshooting user applications:

The Invoke operation will fail if the Server is unavailable, or unable to return a response, for example, when there is an un-handled exception on the server side.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*