Documentation Center

Deploying a custom plugin or extension

Make your custom plugin or extension available by deploying it.

Procedure

  1. Sign in to Organize Space.
  2. On the top tab level, select the Settings tab.
  3. On the second tab level, select the XML Settings tab.
  4. Depending on the type of plugin or extension you are adding, select one of the following settings third-level tabs:
    Type of plugin or extensionSettings tab to select
    Background task handlerBackground Tasks
    Write pluginWrite Plug-ins
    Metadata binding handlerExtensions
    Search extension handlerExtensions
    Publish compare pluginPublish Plug-ins
    Publish combine languages pluginPublish Plug-ins
    PublishPostProcess pluginPublish Plug-ins
    The XML of the selected setting appears on the right.
  5. 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.
  6. Select Save to apply your changes.
  7. Access one of your Content Manager servers.
  8. In the Administrative Tools of your Windows Control Panel, access the Services screen.
  9. In this screen, stop the BackgroundTask service.
  10. In IIS Manager, in the tree on the left, expand the node representing your server and select Application Pools.
  11. In this screen, select and stop the IIS application pools whose names start with the string TrisoftAppPool, for example, TrisoftAppPoolISHCM.
  12. 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\
  13. In IIS Manager, start the IIS application pools whose names start with the string TrisoftAppPool, then close IIS Manager.
  14. In the Services screen of the Control Panel, start the BackgroundTask service.
  15. Close the Services screen.
  16. Access another Content Manager server, and repeat steps 7-15. Repeat until you have updated all of your servers.