SilkPerformer license
Posted: July 18th, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: Licenses, SilkPerformer | 2 Comments »
SilkPerformer licensing mechanism is based on three mainly groups. Namely Web, Standard and Premium. The differences in each group is the type of technologies being used in the group. For example, Web encompasses the commonly used protocols while Standard focuses on additional components. This is somewhat similar to LoadRunner in terms of grouping the protocols in bundles. The following table is the full list of what the group covers in SilkPerformer 2008 (which is also available in the Release Notes).
| Web | Standard |
Premium |
| HTTP(S) (Web browser low level) HTTP(S)/HTML (Web browser high level) HTTP(S)/XML (Web services, SOAP) SAP NetWeaver WebDAV (MS Outlook Web Access) Email (SMTP/POP) FTP TCP/IP UDP i-Mode (HTTP) AMF0/AMF3/FLEX Streaming Media (MS, Real) DLL Interface |
All of Web, plus:
.Net Add-On |
All of Standard, plus:
GUI Level Testing |
As briefly mentioned in “What’s SilkPerformer?”, SilkPerfomer allows the capabilities of checking out the license with the license server, SilkMeter. This is great in a way that there are no limitation on the “Controller” and you can install it anytime. Furthermore, you can fully maximise the “controller” resource when it is not needed for an existing project.
Take note that there are still some limitations on the use of SilkPerformer on the group licenses. The groups does not cover SOA applications. If you like to test the Web Services via WSDL files, you will require the SilkPerformer SOA Edition. Similarly with LoadRunner that requires the SOA Bundle license to work for Web Service protocol.
Also, for unit-level testing tools available from SilkPerformer, namely .NET Explorer and Java Explorer, will require additional development licenses for them (the explorer tools) on top of the vuser type license. This can be thought as the same as using Quick Test Professional (QTP) scripts for LoadRunner in a load test where it requires both licenses on the QTP and LoadRunner to be functional.
Does SilkPerformer have the same stuff as L/R’s “manage services” or “add service call”? I need to import the WSDL file from local.
For the importing of WSDL file features, its available in the SOA Edition of the SilkPerformer. The following link is the data sheet for the edition:
* Borland SilkPerformer SOA Edition Data Sheet
However, I would advise to get the vendor to demonstrate its features on-site to get a better feel.