IP Library Granted Patent US 8,898,643
Granted Patent B2
US 8,898,643 · App. 13/527,343 · Granted Nov 25, 2014

Application trace replay and simulation systems and methods

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,898,643
App. No.
13/527,343
Granted
Nov 25, 2014
Kind
B2
Abstract

Example systems and methods for trace replay and simulation are presented. The system creates a trace entry for each one of a plurality of transactions through the server interface for a client, A message type and message data are recorded into the trace entry for each one of the plurality of transactions. A collection of trace entries for an individual one of the plurality of clients is transferred to a trace player. A client identifier is replaced in the trace entry with an identifier associated with the trace player, An interaction between the server and the clients is replayed.

Claims (53)

1. A computerized method for simulating a server interface for a plurality of clients, the server interface including a plurality of interface message types, the method comprising:

creating a trace entry for each one of a plurality of transactions through the server interface for each client;

generating a dynamic identifier in the trace entries for each client and each client session;

recording in the trace entry, a message type, and message data for each one of the plurality of transactions;

transferring a collection of trace entries for an individual one of the plurality of clients to a trace player;

replacing the dynamic identifier in the trace entries with a simulation identifier associated with the trace player; and

replaying an interaction between the server interface and the individual one of the plurality of clients.

2. The method of claim 1 , comprising:

recording a user identifier in the collection of trace entries; and

replacing the user identifier at the trace player with a player identifier.

3. The method of claim 1 , further comprising:

performing a test of a client application using the collection of trace entries, the collection of trace entries comprising a sequence of interactions between the client application and a server application.

4. The method of claim 1 , comprising: storing the trace entry a log file at the server.

5. The method of claim 1 , comprising: storing the trace entry in a log file at the client.

6. The method of claim 1 , comprising: receiving, through an interactive user interface mechanism, modifications to trace entries prior to or during the replay of the interaction between the server and the client.

7. The method of claim 1 , comprising: parsing the collection of trace entries for server interface message types.

8. The method of claim 1 wherein the server is a customer relationship manager (CRM) and the client is a communication management system (CMS).

9. The method of claim 8 , wherein the server interface includes a simple object access protocol (SOAP) interface.

10. The method of claim 8 , wherein the server interface includes an integrated communication interface (ICI) compatible protocol.

11. A non.-transitory computer-readable storage medium

comprising instructions that, when executed by at least one processor of a machine having a server interface that supports a plurality of interface message types, cause the machine to perform operations comprising:

creating a trace entry for each one of a plurality of transactions through the server interface for a client;

generating a dynamic identifier in the trace entries each client and each client session;

recording in the trace entry, a message type, and message data for each one of the plurality of transactions;

transferring a collection of trace entries for an individual one of the plurality of clients to a trace player;

replacing the dynamic identifier in the trace entries with a simulation identifier associated with the trace player; and

replaying an interaction between the server and the clients.

12. The non-transitory computer-readable storage medium of claim 11 , the operations further comprising:

recording a user identifier in the collection of trace entries; and

replacing the user identifier at the trace player with a player identifier.

13. The non-transitory computer-readable storage medium of claim 11 , the operations further comprising:

receiving, through an interactive user interface mechanism, modified trace entries prior to or during the replay of the interaction between the server and the client.

14. The non-transitory computer-readable storage medium of claim 11 , the operations further comprising:

parsing the collection of trace entries for server interface message types.

15. The non-transitory computer-readable storage medium of claim 11 , wherein the server is a customer relationship manager (CRM) and the client is a communication management system (CMS), and the server interface includes a simple object access protocol (SOAP) interface.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the server interface includes an integrated communication interface (ICI) compatible protocol.

17. A system comprising:

a machine having a memory and at least one processor; and

at least one module on the machine, the at least one module being configured:

create a trace entry for each one of a plurality of transactions through the server interface for each client;

generate a dynamic identifier in the trace entries for each client and each client session;

record in the trace entry, a message type, and message data for each one of the plurality of transactions;

replace the dynamic identifier in the trace entries with a simulation identifier associated with the trace player: and

replay an interaction between the server interface and the individual one of the plurality of clients.

18. The system of claim 17 , wherein the at least one module is further configured to:

record a user identifier in the collection of trace entries; and

replace the user identifier at the trace player with a player identifier.

19. The system of claim 17 , wherein the at least one module is further configured to:

receive, through an interactive user interface mechanism, modified trace entries prior to or during the replay of the interaction between the server and the client.

20. The system of claim 17 , wherein the at least one module is further configured to:

parse the collection of trace entries for server interface message types.

21. The system of claim 17 , wherein the wherein the server is a customer relationship manager (CRM) and the client is a communication management system (CMS), and the server interface includes a simple object access protocol (SOAP) interface.

22. The system of claim 17 , wherein the server interface includes an integrated communication interface (ICI) compatible protocol.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2012
From: RODE, MATTHIAS
To: SAP AG
Reel/Frame 028404/0780 →