How to use ConfigureMonitoring to deploy rulebase to specific targets

[Bruce Yip]

I try to use Hawk ConfigureMonitoring.exe to deploy rulebase to specific target BW applications only (e.g. deploy rulebase to only 1 BW application)as following procedure.

1. Upload mar file to domain using Monitoring Console at TIBCO Administrator

2. Export available targets.xml using ConfigureMonitoring -getTargets

3. Modify the targets.xml to remain only 1 BW application target

4. Run ConfigureMonitoring -deploy -monitoringAppName [Mar name] -targets [Modified-targets.xml] -domain [domain] -user [user] -pw [pwd]

However, no matter what I defined in targets.xml, the deployment will deploy the rulebase to all existing BW applications. Looks like the deployment don't read my defined targets.xml. Do anyone has experience on this

[Tristan Chou 2]

Hello, 

 

Please attach your mar file and target.xml.

 

Usually the rulebase should only be deployed for the applications in target file.

 

Thanks,

 

Tristan

[Bruce Yip]

Hello,

Attached my BWMonitor.zip with mar file BWMonitor.mar,BWMonitor-targets-org.xml andBWMonitor-targets-partial.xml.

BWMonitor.mar with 5 rulebases in there (Generic-bwengine, ActiveProcess-bwengine, test-Process_archive-1-BWmonitor-Generic-bwengine, testAlive-bwengine, checkState-bwengine). After I upload the mar file to Monitoring Cosole. Then I extract the targets to BWMonitor-targets-org.xml (with 3BW applications, i.e. testEMSConn, testbw, test)by runningConfigureMonitoring.exe -getTargets -monitoringAppName BWMonitor -domain ...... Then I modify the extracted targets.xml with my only wished BWApplication targets (i.e. testbw) to BWMonitor-targets-partial.xml. Finally runConfigureMonitoring.exe -deploy -targets BWMonitor-targets-partial.xml -monitoringAppName BWMonitor -domain ....

Thanks,

Bruce

[Tristan Chou 2]

HiBruce,

One posibility is that when you upload mar file from administrator GUI, all targets are enabled which is default option. Please consider to:

1. undeploy and delete the existing mar file from administrator, then upload mar file and choose option "Disable All" before click [Ok], then go ahead and try to deploy mar file withBWMonitor-targets-partial.xml from command line.

OR

2. you could consider to use "ConfigureMonitoring -upload" to upload mar file which will disable all targets by default, then usetry to deploy mar file withBWMonitor-targets-partial.xml from command line.

Hope this helps.

-Tristan Chou

[Bruce Yip]

Hi Tristan,

I figure out the behaviour of deploy mar file now. If I have deployed the rulebase to a target before, then the target is registered to the TIBCO Administrator. Then any future deployment of that rulebase will deploy to that target every time no matter I defined that target in the deploymenttargets.xml or not.

If I don't want to deploy the rulebase to that target. I have to remove that target through TIBCO Administrator Monitor Console first.

[Tristan Chou 2]

Hi Bruce,

 

Thank you for your sharing and glad to know your issue is resolved now. 

 

Thanks,

 

Tristan Chou