Scripts and Plugins

The JEB back-end offers a rich API that can be used to develop:

While most of the discussion related to extensions development is out-of-scope for this manual, the examination and execution of extensions is not.

Capabilities

Only professional licenses offer full API access. However, all licenses allow script execution from within the RCP client:

Licenses Type RCP client Other Clients (incl. command-line)
Standard scripts no
Business scripts all extensions (Java)
Enterprise scripts all extensions (Java)

API

The JEB 2.x Application Programming Interface offers power-users ways to:

The discussion of the API is out-of-scope in this manual. Please refer to:

Scripts

Note: All versions of JEB can execute client scripts inside the RCP client.

Scripts should be dropped in your scripts/ directory (or any other directory specified in your .ScriptsFolder client option). Use the File, Script, Run Script... menu command to execute a script. The last run script can be executed again by pressing the F2 key.

You will find a large collection of sample scripts on our public Github repository.

Plugins

Plugins must be dropped in your coreplugins/ directory (or any other directory specified in your .PluginsFolder back-end option). Use the File, Engines, Execute, ... menu command to execute a plugin.

Note: technically speaking, engines plugins are JEB plugins that implement the IEnginesPlugin interface.

The full list of engines plugins loaded within your JEB instance context can be seen by running the File, Engines, Plugins command.

Double-click a plugin to execute it.

You will find a large collection of sample plugins on our public Github repository.