Configuring and Monitoring Corillian s Voyager eg Enterprise v5.6
Restricted Rights Legend The information contained in this document is confidential and subject to change without notice. No part of this document may be reproduced or disclosed to others without the prior permission of eg Innovations, Inc. eg Innovations, Inc. makes no warranty of any kind with regard to the software and documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Trademarks Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Copyright 2012 eg Innovations, Inc. All rights reserved.
Table of Contents CONFIGURING AND MONITORING THE VOYAGER TRANSACTION PROCESSOR (TP)...1 1.1 ADMINISTERING THE TP SERVER TO WORK WITH THE EG MANAGER...1 1.2 MONITORING THE TP SERVER...3 CONFIGURING AND MONITORING THE VOYAGER FRONTEND...4 2.1 ADMINISTERING THE VOYAGER FRONTEND TO WORK WITH THE EG MANAGER...4 2.2 MONITORING THE VOYAGER FRONTEND...5 CONCLUSION...6
Table of Figures Figure 1.1: Adding a TP server...1 Figure 1.2: The list of unconfigured tests for the TP server...2 Figure 1.3: Configuring the ComFedQuery test...2 Figure 2.1: Adding a Voyager FrontEnd component...4
Configuring and Monitoring the Voyager Transaction Processor (TP) Chapter 1 Configuring and Monitoring the Voyager Transaction Processor (TP) This chapter will delineate the process of configuring and monitoring the Transaction Processor (i.e., the TP server in eg parlance) of the Voyager software. 1.1 Administering the TP Server to work with the eg Manager To achieve this, do the following: 1. Log into the eg administrative interface. 2. Add the TP server manually using the ADD/MODIFY COMPONENTS page (Infrastructutre -> Components -> Add/Modify). Remember that components manually added are managed automatically. Figure 1.1 clearly illustrates the process of adding a TP server. For more details on managing components, refer to Configuring and Monitoring Web Servers document. Figure 1.1: Adding a TP server 1
Configuring and Monitoring the Voyager Transaction Processor (TP) 3. Then, try to sign out of the eg administrative interface. Upon doing so, Figure 1.2 will appear listing the unconfigured tests for the TP server. Figure 1.2: The list of unconfigured tests for the TP server 4. Click on the ComFedQuery test in Figure 1.3 to configure it. The ComFedQuery test monitors the error statistics in the CCLogging database. Figure 1.3: Configuring the ComFedQuery test 5. When Figure 1.3 appears, provide the following information: a. TEST PERIOD - How often should the test be executed b. HOST The IP address of the host c. PORT The port at which the specified HOST listens. d. INSTANCE - Enter the name of a specific MS SQL instance that is to be monitored. The default value of this parameter is "default". To monitor an MS SQL instance named "CFS", enter this as the value of the INSTANCE parameter. e. DBHOST Enter the IP/host name of the database host f. DBPORT - Enter the port at which the database host listens g. USERNAME - Specify the user name to be used for logging into the database. This user should be authorized to connect to the CCLogging database. h. PASSWORD - Enter the password for logging into the CClogging database i. CONFIRM PASSWORD - Confirm the password by retyping it in the CONFIRM 2
Configuring and Monitoring the Voyager Transaction Processor (TP) PASSWORD text box. j. MESSAGE - In the MESSAGE text box, provide a comma-separated list of error message patterns to be monitored in the format, Displayname:messagepattern. Here, the Displayname is just a name that is used to uniquely identify the message pattern, and will be displayed in the monitor interface. The messagepattern is an expression of the form - *expr* or expr or *expr or expr* or *expr1*expr2*... or expr1*expr2, etc. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. For example, Error1:*cc_err*,Error2:*login*. k. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eg Enterprise system embeds an optional detailed diagnostic capability. With this capability, the eg agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: o The eg manager license should allow the detailed diagnosis capability o Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0. 6. Then, click the Update button in Figure 1.3 to save the configuration. 7. Then, signout. Now it will prompt to configure the Processes test. Refer to Configuring and Monitoring Web Servers document for details on configuring the Processes test and specifying the PROCESSPATTERN. 8. Now signout of the administrative interface. 1.2 Monitoring the TP Server To monitor the TP server, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. From the COMPONENT LIST page, click on the TP server being monitored. 3
Configuring and Monitoring the Voyager FrontEnd Chapter 2 Configuring and Monitoring the Voyager FrontEnd This chapter will delineate the process of configuring and monitoring the Voyager Front End (i.e., the Voyager FrontEnd in eg parlance). 2.1 Administering the Voyager FrontEnd to work with the eg Manager To achieve this, do the following: 1. Log into the eg administrative interface. 2. Add the Voyager FrontEnd component manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Figure 2.1 clearly illustrates the process of adding a Voyager FrontEnd component. For more details on managing components, refer to Configuring and Monitoring Web Servers document. Figure 2.1: Adding a Voyager FrontEnd component 4
Configuring and Monitoring the Voyager FrontEnd 3. Then, sign out of the eg administrative interface. 2.2 Monitoring the Voyager FrontEnd To monitor the Voyager FrontEnd component, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. From the COMPONENT LIST page, click on the Voyager FrontEnd component being monitored. 5
Conclusion Chapter 3 Conclusion This document has described in detail the steps for configuring and monitoring the Corillian s Voyager. For details of how to administer and use the eg Enterprise suite of products, refer to the user manuals. We will be adding new measurement capabilities into the future versions of the eg Enterprise suite. If you can identify new capabilities that you would like us to incorporate in the eg Enterprise suite of products, please contact support@eginnovations.com. We look forward to your support and cooperation. Any feedback regarding this manual or any other aspects of the eg Enterprise suite can be forwarded to feedback@eginnovations.com. 6