Deploying a custom plugin or extension
Make your custom plugin or extension available by deploying it.
Procedure
- Sign in to Organize Space.
- On the top tab level, select the Settings tab.
- On the second tab level, select the XML Settings tab.
- Depending on the type of plugin or extension you are adding, select one of the following settings third-level tabs:
Type of plugin or extension Settings tab to select Background task handler Background Tasks Write plugin Write Plug-ins Metadata binding handler Extensions Search extension handler Extensions Publish compare plugin Publish Plug-ins Publish combine languages plugin Publish Plug-ins PublishPostProcesspluginPublish Plug-ins The XML of the selected setting appears on the right. - Add the configuration of your plugin or extension to the XML. You determine what to insert; it depends on your specific plugin or extension. As for where to insert it in the XML, this may depend on exactly when you want to run it. For example, you can insert the configuration for a plugin in various locations in the Publish Plug-ins XML, depending on exactly when in the publish process you want your plugin to execute. For more information, contact RWS Customer Support.
- Select Save to apply your changes.
- Access one of your Content Manager servers.
- In the Administrative Tools of your Windows Control Panel, access the Services screen.
- In this screen, stop the
BackgroundTaskservice. - In IIS Manager, in the tree on the left, expand the node representing your server and select Application Pools.
- In this screen, select and stop the IIS application pools whose names start with the string
TrisoftAppPool, for example,TrisoftAppPoolISHCM. - Copy your .NET assembly (.dll file) containing your custom plugin or extension to the following folder:
APPPATH\AppPROJECTSUFFIX\Plugins\
where:- APPPATH is the path to the Content Manager application root
- PROJECTSUFFIX is an optional unique identifier
If you left these unchanged, the path is the following: c:\InfoShare\App\Plugins\ - In IIS Manager, start the IIS application pools whose names start with the string
TrisoftAppPool, then close IIS Manager. - In the Services screen of the Control Panel, start the
BackgroundTaskservice. - Close the Services screen.
- Access another Content Manager server, and repeat steps 7-15. Repeat until you have updated all of your servers.