Forum Discussion

FICO's avatar
FICO
Community Manager
17 years ago

Deployment Manager extended to monitor ADBs deployed in Linux

Deployment Manager extended to monitor ADBs deployed in Linux

All -

I  have been brainstorming over the past week or so for a way to extend the Deployment Manager code to not monitor a single project, but rather multiple ADBs deployed in our WAS 6.1 environment running on RHEL5. What I want to do is create a Java application that can be deployed to the same WAS environment that can monitor an ADB file for a change (timestamp) and then initiate a restart of the WebService in WAS. The existing documentation for Deployment Manager is not very helpful (from my perspective). Does anyone have any experience with an application like this or possibly Deployment Manager in general that they could assist?

Thanks!

Eric

2 Replies

  • FICO's avatar
    FICO
    Community Manager

    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.

  • FICO's avatar
    FICO
    Community Manager

    Just wondering...

    Any reason why you do not use the persistent cache capability of the Deployment Manager in Blaze Advisor 6.6 and above?

    With this feature, you can monitor your repository and let the Deployment Manager create and reuse compiled projects transparently.  You won't have to manage those ADB files and their timestamps... AND the deployment environment will benefit from the speed of compiled projects.

    There may be some other reasons for sticking to the ADB files management but I thought I would at least put it out there...

    Carole-Ann

    VP, Product Management

    http://www.twitter.com/cmatignon