Plugin Execution Types

A Java Plugin is a java class(es) that can be deployed as .class file or as .jar files in the Plugins directory. The plugin directory path is configured under the General Configuration Tab on the Plugin Dir parameter in the admin UI.
cis1266
Java Plugins
A Java Plugin is a java class(es) that can be deployed as .class file or as .jar files in the
Identity Portal
Plugins directory. The plugin directory path is configured under the General Configuration Tab on the Plugin Dir parameter in the admin UI.
All plugins are loaded by
Identity Portal
on startup, if you deployed a new plugin to the plugin directory when the application is already running use the
<Identity_Portal_url>/rest/admin/plugins/refresh
 URL to reload all available classes in the plugin directory.
Important:
 In cluster configuration, plugin classes should be deployed on each of the servers, and the refresh functionality (if used) should be executed on both servers. The Plugin directory path is configured for all servers, so make sure to create a path the can be created on all cluster servers and locate the files there.
The Java class plugin needs to extend the BasePlugin class and must contain a function of the plugin that will serve as the execution start point. That function
must
contain the @ExportedServerFunction annotation before it. This function can return any type of object and receive any type of arguments in correspondence to the handler call arguments passed to it.
RhinoJS Plugin
The RhinoJS Plugin is a server-side JavaScript code that is written in the plugin configuration in the admin UI. Changes in this code of the plugin will be effected immediately.
The JavaScript function must be named with the plugin name.