Protocol extension structure

Before organizing your extension, note the restrictions and guidelines provided in this topic.

Restrictions

The following restrictions apply to plug-ins:

For best results, minimize the amount of code that is deployed to the agent for execution.

Guidelines for naming plug-ins

Most base HCL OneTest™ Performance plug-ins follow this naming convention:

<prefix>.<component>[.subcomponent].<protocol>

where:

Using these conventions, the extension can have the following plug-ins:

Alternatively, you can divide the code into two plug-ins, one for the workbench and one for execution. This has the advantage of deploying fewer plug-ins. For an example, refer to the Siebel extension to Performance Tester.

Using this method, you would have the following two plug-ins:

Within these plug-ins, you can either arrange the components in one of two ways:

Feedback