Invocation Export and Import

Owned by Copy Space for Confluence
May 20, 2015

1. Overview

Invocation sequences often contain important information of an application in a structured way that allows to easily convey findings in the application to the different stakeholders. Prior to the export and import of invocation sequences, the analyst was forced to create screenshots or copy/paste invocation sequences to files. With the export and import of invocation sequences, the analyst is able to export invocation sequences to a file and sent it to the relevant stakeholders. These people can then use the user interface of inspectIT and analyze the invocation as if it where stored within a CMR. Apart from this the export/import can be used to store important findings during an analysis session to the local disc, continue with the analysis and inspect them in more detail later.

2. Integration of the storage area in the UI

The storage area is integrated as an additional element in the left hand navigation panel. This area contains invocation sequences that were saved from a running CMR to the local disc.

After the export/save of an invocation sequence, the whole information is available within the storage area node.

3. Functionality

The import and export utility allows to save/export invocation sequences from a running CMR to the local disc. This process copies all sensor information of the invocation sequence. So you can browse and analyse the sequence as if the invocation were on a CMR (without the need to actually run one).

3.1 Save an invocation sequence

Saving an invocation sequence transfers the invocation sequence from a running CMR directly to the storage area of the client. This process will not create an export file that can be shared with other people.

As a side note: It is always possible to simply archive the folder containing the saved invocation sequences within the storage area folder on the disc and copy it to the storage area of another client.

3.2 Export/Import an invocation sequence

By exporting an invocation sequence the information is saved to a user-defined file. This file can be distributed to other stakeholders. Using the import functionality of the storage area allows to import this file again to the storage area. It goes without saying that you can select multiple invocation sequences and export these as one file.

Saved invocations can also be exported later by opening the saved session, selecting the invocation sequences that should be exported and saving them to a file.

Ticket links (only internal necessary to provide for references to the ticket system):