VA2 FAQ

Q1. How do I download the Rules??

Q2. What steps are necessary to install Analysis Rules?

Q3. What steps are necessary to install Statistics?

Q4. What are Error Definitons?

Q5. What interval should be choosen for Statistics or Analysis Rules?

Q6. How are log files monitored?

Q7. What are notification rules?

Q8. What is an Event?

Q9. I can see all Siebel Components but I can't see anything in the "Error Definitions for component" folder.

Q10. In "Application log File Error Definition" folder I can't see any error message when the server is down.

Q11. In server Tasks, Monitored Tasks I can't see anything.

Q12. In "Processes" folder I can see processes but I can't generate a Graph.

Q13. In "Statistic" folder, when I try to add a property and I Launch Debugger, it appears the following error message: "Run time Error '53' File not found"

Q14. In "Data Source" folder, when I execute the test with user and password the I get an error "Data Source or Login Error"

Q15. In "Notification Rules" folder, I can see Notifcation rules. However, I don't see any Reactions associated with the Notification Rules.

Q16. I've imported a Statistic for Oracle that uses SQL. It doesn't seem to be working.

Q17. I've got a dll error when I installed the MMC, and I can not use the MMC Console.



Q1. How do I download the Rules?
When you find an Analysis Rule or Statistic Collector you are interested in, right click with your mouse on the hyper link of the name. Select the "Save Target As" and you will be presented with a dialog box for saving to your local machine. Once on your hard drive, you can open you VA2 MMC Console, navigate to the Analysis Rules or Statistic folders, and choose Import.

Q2.What steps are necessary to install Analysis Rules?
To use the Analysis rule several steps must be taken:
1. Download and import the rule as seen in Q1. 2. Edit the Rule if necessary.
3. Create and associate an Error Definition to the Analysis Rule.
4. Create a Notification Rule for the expected Event(s) that could be generated by the Analysis Rule. if one does not exist.
5. Set the Interval to the desired level.


Q3.What steps are necessary to install Statistics?
To install the Statistic navigate to the Statistics folder in the VA2 MMC Console, right click and select the Import option.
1. Edit the Rule if necessary.
2. Set the Interval to the desired option


Q4.What are Error Definitons?
Error Definitions are associated with Analysis Rules. When an Analysis Rule is triggred, the Error Definiton(s) associated with the Analysis generate an event, which is then examined by defined Analysis Rules. Error Definitions are also used to define Search Strings in log files.

Q5.What interval should be choosen for Statistics or Analysis Rules?
If an Analysis rule is triggered it will send an Event. If Analysis Rules are set to a very high frequency a notification will be generated on each frequency. Generally the bigger the interval the better. For statistics, a data point will be captured with every interval, the smaller the interval the more data will be captured.

Q6.How are log files monitored?
Log files are monitored by creating an Error Definiton and setting the Search String paramater. The Search Screen option supports Perl regular expressions. Then the Error Deffintion is attached to a defined Application or Siebel Component. If defined on the Application level, the Search String will be searched for in all log files defined in the Log File paramater of the Application. If the Error Definition is attached to a Siebel Component, the search string will be examined only in log files for the particular component. When a Search String is found, an Error Event is generated that contains the search string found, and the rest of the values from the Error Definition.

Q7. What are Notification Rules?
Notification Rules examine the Events generated to determine if a particular Event is supposed to cause a notification. A Notification Rule will satisfy the condition and cause a communication to be sent through all defined channels the Notification Rule properties match the Event properties. A Notification Rule can be set to Notify All, in which case it routes all events and effectivly removes the necessity of creating custom Notification Rules. However, when the communications are routed, they will contain the text from the Notification Rule, so a generic "Notify All" rule will not be very helpfull.

Q8. What is an Event?
Events are generated as the result of an Analyis Rule returning false or a Search string defined in an Error Definition being found in a log file. When an Event is created, it is compared against Notification Rules. If a Notification Rule matches the Event, it is Routed to active Schedules. Schedules have Communication Servers associated with them, which have Administrators associated with them, and the defined Administrators(s) recieve the notification.

Q9. I can see all Siebel Components but I can't see anything in the "Error Definitions for component" folder.
The Error Definitions" for component folder is an area that you can add a "Error Definition" for a component. A Error Definition is an object defined under the Error Definition tab. It has two functions: 1. It determines what Event will be generated. 2. The Search String property is used to define what text you are looking for in a log file that constitutes and error.

For example, if you want to find a particular error strings just for the Component TxnRouter – you could add a error definition here – and that particular component log file will be searched for the error definition. You must define the error definition first, under the Error Definition tabs. Reference the documentation, look up the Error Definitions section, and the Error Definitions for Components section for more info.

If an Event is generated, for example EIM exits with error, you should look under the Events tab to see if an event is generated. If you have you Communication Servers, Schedules, and Administrators set up correctly, you will be routed an error message.



Q10. In "Application log File Error Definition" folder I can't see any error message when the server is down.

"Application Log File Error Definition" is for adding a Error Definition that operates on the application log file directory. Instead of being Component specific, it will search for a defined error string for any log file for the whole application. You should see under your Appserver, a Error Definition called "Process or Component exited with Error". This means that any Log created under the appserver with the string "Process exited with error" should generate an event. Once again, if an event is generated it will be available under the Events tab.



Q11. In server Tasks and Monitored Components folders I can't see anything.

You should see Tasks if the Siebel Server is running… if not there is a serious error.

. There are several potential causes. One is if you are working with Siebel 7. When running the setup for Siebel 7, the Siebel password that VA2 imports is encrypted. This parameter is stored in the Software Element that represents your Siebel Enterprise - in the Software Elements Option tab. Here you will see a username and password options. You must change the Password to be your Siebel password instead of the encrypted one. Unfortunately, if it is not set appropriately, no Server Tasks or Monitored Components will show up - and the log files do not list an error, but it is not able to harvest Siebel Server information. If you change the password restart the LSM and then check the Server Task and Compnent information. This step is documented in the installation steps under Siebel 7 Install notes.

You may want to check the log files for the LSM. Log files are under \VA2\LSM\log – if there is SQL errors in the vsrvrmgr(servername).log file, it means that for some reason you don’t have the most up to date executable for harvesting Task information. Stop the LSM service, replace the LSM. Make sure you have the latest executable. Check the modified date on your vsrvrmgr.exe is before 11/26/2002 at 4:30 pm, you'll need to download a new version.



Q12. In "Processes" folder I can see processes but I can't generate a Graph.
For graphs, Select the Processes Folder or the Monitored Components folder. Then right click, View > Graph XXX


In "Statistic" folder, when I try to add a property and I Launch Debugger, it appears the following error message: "Run time Error '53' File not found"
Events are generated as the result of an Analyis Rule returning false or a Search string defined in an Error Definition being found in a log file. When an Event is created, it is compared against Notification Rules. If a Notification Rule matches the Event, it is Routed to active Schedules. Schedules have Communication Servers associated with them, which have Administrators associated with them, and the defined Administrators(s) recieve the notification.

When launching the debugger, the path to the debugger.exe must be set in the VA2 console. This is not done on install. You should set it in Virtual Administrator tab > Edit > System Variables.

 

You must set the path to the folder of your debugger.exe in the install path parameter. The default path is \Program Files\Vadmin2\:. You can also do a find to find you debbuger.exe.

 

 


Q14. In "Data Source" folder, when I execute the test with user and password the I get an error "Data Source or Login Error"

When you check the datasource username and password, the result success! Is good. It means the datasource is set up correctly. It also means that the datasource exists on the same host that the MMC is installed. If you get an error, it means that the Login is incorrect, or the ODBC Datasource does not exist on the same host as the MMC. It should be created on the MMC host so that debugging can be performed. The ODBC datasource defined MUST exist on the Central Server host. A best practice is to create the same set of ODBC datasources on all the MMC hosts as the Central Service host, with the same names.



Q15. In "Notification Rules" folder, I can see Notifcation rules. However, I don't see any Reactions associated with the Notification Rules.

You must create a Reaction first if you want to associate it with a Notification Rule. I suggest that you make sure regular event routing is working first before you associate any reactions with a Notification Rule. Make sure you have carefully read the Notification Rule section of the documentation before creating Reactions for Notification Rules.

Choose from existing Reactions:


Q16. I've imported a Statistic for Oracle that uses SQL. It doesn't seem to be working.
Oracle SQL statements require you to add the table owner in fron of table names. Unless your ODBC datasource user is the Table Owner for for the monitored datasource. For example(SIEBEL is the table owner for this example): "Select COUNT(*) from SIEBEL.S_ORG_EXT"

I've got a dll error when I installed the MMC, and I can not use the MMC Console.
c. If you receive an error during install relating to not registering the snapin.dll, you will need to runt the regdlls.bat program provide with VA2 ( Start > Programs > VA2 > registerdlls.bat). The program registers the following 2 dll's : msnappr.dll, then snapin.dll. If you want to run the application by command line you can do so. CD to the \Program Files\Vadmin2 directory. Run the regsvr32 program twice, once for mssnapr.dll, then for the snapin.dll. Error message in Italian:



DOS commands to register the DLL's: regsvr32 mssnapr.dll regsvr32 snapin.dll