With plugins you can extend or restrict the functionality, for example if specific functions are not used.
In this dialog you can activate or deactivate plugins. During this process you must be aware of possible existing dependencies between plugins. It can be necessary to start a required plugin.
With the search function of the configuration manager you can search for a specific plugin also within the plugin description.
Start or stop a plugin is a two-step process.
In the first step it is necessary to activate or deactivate the checkbox for the plugin. These changes takes effect after a click on the Save button. If there are other plugins required to be started also then a message box will be displayed.
A restart of the server is necessary to start or stop the plugins. A running plugin will not be stopped and a stopped plugin will not be started until the server was restarted. The modified status of the checkbox for a plugin takes effect after a server restart.
Therefore in the second step it is necessary to restart the server. If it is running as own application, e.g. as Windows service or Linux deamon then the restart can be triggered from the configuration manager GUI itself. If the server is running within an application server, like Tomcat or if it is embedded in a custom application then it is necessary to restart it together with the application server or custom application manually.
After the plugin was activated and started it could be necessary to give the user the right to access the plugin in the dialog Permissions.
If the plugin should be removed permanently from the server and from the list in this dialog, then you can delete the corresponding zip file from the folder "plugins" and restart the server. Depending plugins will be deactivated automatically.
Note: If you delete a plugin permanently then you should know what you do because you can loose the access to the INETAPP server if you delete a plugin that is necessary, e.g. for authentication.
With plugins it is possible to activate/deactivate default features of the server. Also, it is possible to add additional functions.
For more information about the architecture, life cycle and the steps to create your own plugin please refer to the chapter "Plugins" in the Server Programming Guide. A sample for a task planner plugin and a user-group-provider including a step by step description can be found in the documentation/samples directory of the SDK.