SDK Silk Performer
SDK Silk Performer
Execution Module
The execution module is an agent-only installer. You can install the execution module using the GUI
or silent setup mode.
Silk Performer is then installed based on the settings you defined in the file
silent.sdk.properties.
SDK Interface
The SDK interface contains the header files, samples, and documentation. The interface is available
as a separate ZIP file. You must have Silk Performer Workbench or the execution module installed
before you can install the SDK interface. The SDK interface is described in detail below.
Overview
The Silk Performer (SP) Software Development Kit (SDK) allows you to create and manipulate
deployment packages, so-called project files, including compilation and execution of associated BDL
scripts.
The SDK offers a DLL interface for native integration scenarios and a Java archive for integrations
with Java based environments. Both interfaces provide equal functionality, however on different
levels. The DLL provides function-based interfaces, the Java archive provides a higher interface level
by a number of Java classes.
The SDK comprises the following interfaces:
• DLL Initialization and Cleanup
• Project Handling Interface
• Deployment Interface
• HTTP Upload Interface
• Real Time Measurements Interface
• Reporting Interface
• BDL Script Introspection Interface
• Error Handling Interface
The detailed interface (API) documentation can be found here:
• Java
• DLL (C++)
Contents
The Silk Performer SDK is a package that contains include files, documentation, and samples. The
binaries required for load test or monitoring executions are already part of the Silk Performer
Controller/Workbench installation and of the dedicated SDK installation.
This package consists of two major parts: the SDK package for Java and for C++.
To get you started quickly, a Web Browser Driven (BDLT) Silk Performer sample project and script is
attached, which runs against the public demo.borland.com server. It requires nothing more than
an Internet Explorer and an Internet connection.
The relative path to the sample Silk Performer project is hard coded in the sample .java or .cpp files.
You must adapt the path if you want to run a different Silk Performer project.
26-03-2015