![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The command-line utility, ConfigureMonitoring, provides an alternative mechanism for deploying and undeploying monitoring configurations. This utility is located in the CONFIG_FOLDER/hawk/bin directory. The log file for this utility is hawkconsole.log, and is created in the directory from which this command is invoked.See Security Considerations for the permissions required to use the ConfigureMonitoring utility.The -upload command uploads a single MAR file into TIBCO Administrator. If this is a new MAR file, a new monitoring application is created with the same name as the MAR file. If it already exists and if the contained monitoring configuration are in the Deployable state, the existing data is overwitten.It cannot update if any of the monitoring configurations in the deployed state.Example: ConfigureMonitoring.exe -upload -mar myMarFile.mar -domain myHawkDomain -user admin -pw adminpwHawk RulebaseMaps and Schedules are also similarly deployed. Only one RulebaseMap and Schedule file can be deployed per domain. The RulebaseMap file has to be named rbmap.hrm and the Schedules file has to be named schedules.hsf.Example: ConfigureMonitoring.exe -upload -mar rbmap.hrm -domain myHawkDomain -user admin -pw adminpwThe -getTargets command retrieves all potential targets for a given monitoring application in the TIBCO Administrator domain. An XML file containing the targets is created in the current directory. The name of the XML file has the format <MAR_file_name>-targets.xml, where <MAR_file_name> is the MAR file for which the targets are retrieved.Example: ConfigureMonitoring.exe -getTargets -monitoringAppName myMarFile -domain myHawkDomain -user admin -pw adminpwThis command creates the XML file myMarFile-targets.xml.
You can edit the XML file created by the -getTargets options to delete a target, effectively choosing to not deploy the monitoring configuration on that target.The -deploy command configures and deploys the monitoring configurations on the targets specified in the target file. The status of deploying each monitoring configuration on each identified target is displayed.Example: ConfigureMonitoring.exe -deploy -targets myMarFile-targets.xml -monitoringAppName myMarFile -domain myHawkDomain -user admin -pw adminpwThe -undeploy command undeploys the monitoring configurations from the targets specified in the target file. The status of undeploying each monitoring configuration from each identified target is displayed.Example: ConfigureMonitoring.exe -undeploy -targets myMarFile-targets.xml -monitoringAppName myMarFile -domain myHawkDomain -user admin -pw adminpwThe -delete command deletes the specified monitoring application from the TIBCO Administrator domain. To remove a monitoring application, none of its monitoring configurations and its targets should be in the deployed state.Example: ConfigureMonitoring.exe -delete -monitoringAppName myMarFile -domain myHawkDomain -user admin -pw adminpw
For example, -targetDomains "domain1,domain2" The password for the TIBCO Administrator user specified by the -user option. The password could be either plain text or encrypted. Passwords can be encrypted using password encryption tool. On Microsoft Windows platforms, the tool is <HAWK_ROOT>\bin\tibhawkpassword.exe and on UNIX platforms, it is <HAWK_ROOT>/bin/tibhawkpassword. Passwords can be encrypted using password encryption tool. On Microsoft Windows platforms, the tool is <HAWK_ROOT>\bin\tibhawkpassword.exe and on UNIX platforms, it is <HAWK_ROOT>/bin/tibhawkpassword.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |