Deployment Manager extended to monitor ADBs deployed in Linux

The deployment manager by default will not restart the entire application (if that is what you mean by restarting web service), but it will notify rule servers that are using that ADB file so that they get reset with its new version.

Single deployment manager can certainly monitor multiple projects (in source repository or in .adb files). You can generate a .dmanager file for your first project and then add more to it by making copies of the <SerializedRulesProjectLoaderFactory> or <RulesProjectInnovatorLoaderFactory> tag depending on where the project comes from.

Take a look at the examples\deployments\ejb\deploymentManager\ejbExamples.dmanager in Blaze installation: it shows how the the same deployment manager is used to load two projects.

If you need to do more work when rules change than just resetting the rules server, you can configure deployment manager with your own event monitor class that will be notified when project change event occurs. In response to such event you can do some extra work. For description, take a look at the "Specifying Event Monitor" in "Configuring Deployment Manager" section in Blaze documentation.