This document contains important information about installing and configuring RulePoint and RTAM to proactively monitor PowerCenter.

Transcription

1 Informatica Corporation Proactive Monitoring for Installation & Configuration April 13, 2011 Copyright Informatica Corporation Contents Abstract... 1 Installation & Configuration... 2 Install the... 2 Install RulePoint & Custom Objects... 3 After Installing and Configuring RulePoint... 4 Identify Personas and Recipients of Alerts... 5 Tips and Tricks... 6 Notification Framework... 6 Monitor Multiple Instances of... 9 Appendix A: Rules in the Starter Kit Template Rules Advanced Rules Appendix B: Analytics and Source Services in the Starter Kit Analytics Source Services Appendix C: Templates in the Starter Kit Appendix D: Responses in the Starter Kit Contact Information Abstract This document contains important information about installing and configuring RulePoint and RTAM to proactively monitor. All references to the files in this document are relative to the root path of the starter kit zip file distributed along with this document. All such references use the blue font. Proactive Monitoring Installation and Configuration Guide

2 Installation & Configuration To install Proactive Monitoring do the following: Install the For each repository to monitor, follow these steps: Obtain the following information: Which RDBMS hosts the? (Oracle (default), SQL Server, DB2). Which user is the Owner? Which user will serve as the Readonly User (default: pcrs_readonly) and password (default: pcrs_readonly) Which Domains, Services and Integration Services are being monitored? Create readonly User and grant privileges Create read-only user and grant privileges in the same database as the repository using one of the following files depending on your repository database type oracle: ddl\powercenter\oracle\create_user_pcrs_readonly.sql sqlserver: ddl\powercenter\sqlserver\create_user_pcrs_readonly.txt db2: ddl\powercenter\db2\create_user_pc_rs_ro.sql Create Views and Synonyms Login as pcrs_readonly (or selected user) and create views and synonyms using one of the following files depending on your repository database type oracle: ddl\powercenter\oracle\pcrs_readonly.ddl.sql sqlserver: ddl\powercenter\sqlserver\pcrs_readonly.ddl.sql db2: ddl\powercenter\db2\pcrs_ro.ddl.sql Import workflow using Manager Import workflow exports\powercenter\wf_m_load_pc_alert_recipients.xml into the repository in a separate folder ("Proactive Monitoring") but don't run it at this time. We will run the workflow after installing RulePoint. Install EBF2901 Install EBF2901 (INFA for HF13, INFA for 9.0.1HF2). Download the EBF from the Informatica customer support portal and follow instructions provided therein. -2- Installation and Configuration Guide

3 Install RulePoint & Custom Objects The names $RP_HOME, $RTAM_HOME, $RP_SDK_HOME and $IDP_HOME refer to the directories where the installations are done. The choice of folder location is left to the user. However, it is recommended that RulePoint and RTAM be installed under the same parent folder. Install RulePoint 5.1SP4 to $RP_HOME Install RTAM 3.1 to $RTAM_HOME using RTAM 3.1 Admin Guide Install RulePoint SDK 2.1 to $RP_SDK_HOME Install Informatica Developer Platform (IDP) to $IDP_HOME Copy LMAPI JAR files to RulePoint Installation Copy the following JAR files to $RP_HOME\webapps\rulepoint\WEB-INF\lib : $IDP_HOME\OperationsAPI\OperationsAPI_Java\jlmapi\jlmapi.jar $IDP_HOME\OperationsAPI\OperationsAPI_Java\jlmapi\pmserversdk.jar Copy database driver JAR files to RulePoint Installation (e.g. Oracle, DB2, MS SQL Server) Install Custom Services : o Copy pcmonitor\rulepointpc.jar to $RP_HOME\WEB-INF\lib o Copy the file pcmonitor\beans.xml to $RP_HOME\WEB-INF\spring\customservices.xml Create Users and Groups (read carefully and follow instructions based on the authentication mechanism preferred: LDAP or Database). LDAP Option: Create LDAP users using the files listed below: pcuser: exports\ldap\pcuser.ldif pcmonitor: exports\ldap\pcmonitor.ldif pcadmin: exports\ldap\pcadmin.ldif : exports\ldap\.ldif dataarchitect: exports\ldap\dataarchitect.ldif itsecurity : exports\ldap\itsecurity.ldif Add the users to the LDAP groups listed below: rulepoint_users: pcuser, pcmonitor, pcadmin,, dataarchitect, itsecurity rulepoint_admins: pcuser OR Proactive Monitoring Installation and Configuration Guide

4 Database option: Add users using the RulePoint Administration Menu as specified in the next step. Consult the RulePoint Admin Guide for details. Login to RulePoint as root and add pcuser, pcmonitor, pcadmin,, dataarchitect, itsecurity Make pcuser an Administrator. This user will own all imported objects Import Starter Kit into RulePoint Login to RulePoint as pcuser and import RulePoint objects using one of the export files listed below for the appropriate database being monitored. oracle: exports\rulepoint\oracle\oracle_rp-5.1_sp4_exportall-no ACLS.xml sqlserver: exports\rulepoint\sqlserver\sqlserver_rp-5.1_sp4_exportall-no ACLS.xml db2: exports\rulepoint\db2\db2_ RP-5.1_SP4_ExportAll-No ACLS.xml Create database user pc_rp to host alerts in the same database as the RulePoint repository user. Login to the RulePoint repository database and create the user and grant privileges using the file ddl\rulepoint\oracle\create_user_pc_rp.sql Seed the pc_rp schema by using the file ddl\rulepoint\oracle\pc_rp.ddl.sql After Installing and Configuring RulePoint Edit parameters for Custom Sources and Responders For each of the 3 Custom Services listed below, fill in the Domain, Integration Service, Service, Service User, Server User Password, Locale properties. Runtime Statistics Receiver Ping Service Workflow Control Responder Install Client on the RulePoint host and configure the monitored instances. A sure way to do this is to use one of the client applications to configure Domains. -4- Installation and Configuration Guide

5 Identify Personas and Recipients of Alerts Edit the XML file conf\pc_alert_recipients.xml. Fill in the RTAM ids and addresses for alert recipients for each Domain, RS combination. You can enter multiple RTAM entries separated by semi-colon. Multiple addresses can be added separated by comma <pc_alert_recipients> <pcinstance domain="domain_vm" rs = "_Service"> <persona name="itsecurity" RTAM="itsecurity;pcmonitor" ="recipient@mycompany.com"/> <persona name="pcadmin" RTAM="pcadmin;pcmonitor" ="recipient@mycompany.com"/> <persona name="" RTAM=";pcmonitor" ="recipient@mycompany.com"/> <persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" ="recipient@mycompany.com"/> </pcinstance> <pcinstance domain="domain_vm2" rs = "_Service2"> <persona name="itsecurity" RTAM="itsecurity;pcmonitor" ="recipient@mycompany.com"/> <persona name="pcadmin" RTAM="pcadmin;pcmonitor" ="recipient@mycompany.com"/> <persona name="" RTAM=";pcmonitor" ="recipient@mycompany.com"/> <persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" ="recipient@mycompany.com"/> </pcinstance> </pc_alert_recipients> Configure workflow wf_m_load_pc_alert_recipients (installed earlier ) Use Workflow Manager (Add Connections, Configure Workflow to point to the conf\pc_alert_recipients.xml path and to the pc_rp schema) Run workflow wf_m_load_pc_alert_recipients to load the XML configuration into database by executing the following: pmcmd startworkflow -f "Proactive Monitoring" -sv service -d domain -u username -p password wf_m_load_pc_alert_recipients Proactive Monitoring Installation and Configuration Guide

6 Tips and Tricks Notification Framework Configure personas The default starter kit for PC Proactive Monitoring uses four personas (i.e. alertee roles) as targets for sending alerts. The Rules sheet (in this doc) specifies the persona that has been pre-configured for each Rule. In case of template based Rules, these personas were inherited from the Templates. The framework is now limited to a single persona for a Rule. However, multiple notification destinations (RTAM ids, addresses) can be configured for each persona. The personas pre-configured in the starter kit are: pcadmin ( Administrators - typically responsible for maintaining workflows/sessions/domains/integration Services/ Services) ( Development, Subject Matter Experts - Anyone who is tasked with the logic of PC mappings/mapplets/transforms/sources/targets) dataarchitect (Anyone tasked with maintaining the data that is being integrated with ) itsecurity (Anyone tasked with dealing with IT security issues like sensitive data, malware etc.) Customers can extend the starter kit by extending/ replacing the persona list to suit your organization. Understanding how the framework works is essential to make these changes. Configure RTAM users Once the personas configuration is well understood, the association of each persona to a set of RTAM ids is specified in the conf\pc_recipients.xml file. Multiple RTAM ids can be specified for each persona. One can use an RTAM group in place of an id. The RTAM entries are separated by semi-colons (;). Configure addresses Each persona can be associated with multiple addresses. These can be individual addresses or distribution lists that are specified as a single address. The addresses are separated by commas(,). Notification Hyperlink The default starter kit includes a hyperlink with every notification that is intended to point to a Landing Page (containing information about your organizations Monitoring Project with contact information). Alternatively the hyperlink can be a -6- Installation and Configuration Guide

7 mailto reference to a contact address(es). The two rules ( Notification Advanced and RTAM Notification Advanced) that handle notification should be modified to point to the appropriate URL. Configure Host The responder element Responder should be edited to contain information about your organizations Host Server and authentication credentials. Configure default notification behavior In order to separate the alert logic from the physical mode of delivery; the Rules (Template Based and Advanced) have been pre-configured to use a "default" delivery mechanism. This is implemented by using the delivery property in the " Notification Response" response (delivery=default). This can be overridden at each Rule/Template level by simply editing the Advanced Rule or Template and replacing the "delivery=default" clause with one of these alternatives: delivery="rtam" (forcing notifications to go to RTAM only) delivery=" " (forcing notifications to go to only) delivery="rtam& " (forcing notifications to go to RTAM and ) The framework has been designed so that the default behavior can be easily changed by just changing one or two Rules. There are 2 Rules that ultimately govern the physical delivery of alerts. They are listed below with the portion of the WITH clause that govern the delivery behavior. RTAM Notification Advanced (delivery = "RTAM" OR delivery = "RTAM& " OR delivery = "default") Notification Advanced (delivery = " " OR delivery = "RTAM& ") With the above configuration, the default behavior for ALL rules is to send notification to RTAM only. Only rules that override this with default=" " or default="rtam& " will send alerts to . If the desired default behavior is to send only, then the above two Rules have to be modified as below: RTAM Notification Advanced (delivery = "RTAM" OR delivery = "RTAM& " ) Notification Advanced (delivery = " " OR delivery = "RTAM& " OR delivery = "default") If the desired default behavior is to send both RTAM and , then the above two Rules have to be modified as below: RTAM Notification Advanced (delivery = "RTAM" OR delivery = "RTAM& " OR delivery = "default") Proactive Monitoring Installation and Configuration Guide

8 Notification Advanced (delivery = " " OR delivery = "RTAM& " OR delivery = "default") Overriding default notification behavior Every Template/Advanced Rule in the starter kit that is responsible for sending alerts use a single response " Notification Response". Here is an example of the THEN clause of a Rule: " Notification response" with topic = "pc_workflows as pc_notifications", properties = "*", params = "body = Duplicate workflow ${folder}/${workflow_name} saved at ${workflow_last_saved}, subject = Duplicate Workflow ${folder}/${workflow_name} found!, persona =, priority = 2, channels = Design Time, rulename = ${drql_rulename}, keyval=${t0.workflow_id}, tstamp = ${t0.tstamp}, delivery = default, snooze = 0" Note that the "delivery=default" clause has been specified here. This implies that the delivery of the alert will depend on how the 2 Notification Rules (see above) are configured. To override the default behavior for a particular Advanced Rule or Template, simply replace the "delivery=default" clause in that Rule/Template with one of the other choices ("RTAM", " ", or "RTAM& ") Configure the "snooze" time for suppressing repeat alerts The starter kit has been configured to send one alert for every exception. However, there are exceptions that can be termed "Running Exceptions". Examples for Running Exceptions are "Long Running Workflows", " Domain is Down", " Integration Service is Down", "The Running Time for this workflow has exceeded the SLA". Since these exceptions are continuous (until a corrective action is taken), the triggering conditions for these alerts remain in place even after the first alert is sent out. Depending on the specification of the frequency of the sources that feed these alerts, the triggering action is repeated as long as the exception is outstanding. If repeated alerts are sent out every so often for the same running exception, it will cause inconvenience, annoyance, waste of resources etc. and may eventually result in significant alerts being ignored altogether. To address this problem, the "snooze" feature has been implemented as part of the notification framework. The snooze specification in the " Notification Response" informs the 2 notification rules on how to space out repeating alerts for the same running exception. The starter kit has used a value of 60 minutes for all Advanced Rules/Templates that deal with Running Exceptions. Singular exceptions (e.g. Workflow Failed, Mapping Saved without Comments etc.) are treated differently and the corresponding Advanced Rules/Templates have been configured with a snooze value of 0. This is to ensure that each Singular Exception is treated as an isolated occurrence and not filtered out by a snooze clause. The snooze property specifies (in minutes) the interval that should elapse between successive alerts of the same Running Exception. The definition of the uniqueness of an alert includes the combination of Domain + Service + Rulename + Key value -8- Installation and Configuration Guide

9 Channels This applies to RTAM only. Channels are used to group RTAM alerts into logical buckets. These are not physical folders but logical groups that conveniently associate a set of alerts to a common theme. Channels used in the starter kit are "Design Time" (for design time alerts), "Run Time" (for completed sessions/workflows) and "Run Time (Live)" for running workflows Monitor Multiple Instances of What is a instance? A instance essentially refers to a and the Domain that hosts it. What is included in the starter kit by default? A set of Source Services (SQL and Custom), Templates, Advanced Rules, Template Rules, SQL Analytics, Watchlists, Responders (Workflow Control, , RTAM, Alert Recorder) and Responses form the starter kit. The support PC database types are Oracle, SQL Server and DB2. The starter kit will be different for each of these 3 types. What can be monitored on Day 1 by just installing the starter kit? A single instance (Domain/RS combination) can be monitored with the installation of the starter kit What needs to be done to add another PC instance by the same RulePoint instance? Addition of a new PC instance will require the following steps: Determine a unique identifier combination for the PC instance. It is recommended that the identifier clearly indicates the Domain and the Service. (e.g. ICCDomain_ICCRS) Start with the base export XML file from RulePoint for a database type that matches the database type of the instance being added. Use the starter kit XML for the given database type if this is the first such instance for the given db type. Replace all the named Source SQL Services with a new name <Prefix>_<ExistingName> (e.g. ICCDomain_ICCRS_ Concurrent Workflows). Replace all custom Source Services ( Runtime Statistics Receiver, Workflow Control Responder, Ping Service) with a new name <Prefix>_<ExistingName> Replace the Workflow Control Response service with a new name <Prefix>_ Workflow Control Response Replace all SQL Analytics that have a as source (the following are excluded: pc_get_alert_recipients, pc_recent_alert, divide, divide_percent, divide_neg_percent) with a new name <Prefix>_<ExistingName> Replace all Topic references with a new name <Prefix>_<ExistingTopicName> Replace all Templates with a new name <Prefix>_<ExistingTemplateName> Replace all Rules with a new name <Prefix>_<ExistingRuleName> Replace all Watchlists with a new name <Prefix>_<ExistingWatchListName> Proactive Monitoring Installation and Configuration Guide

10 Import the file with the above changes into the existing RulePoint instance. Verify that all elements indicated above have been replicated Enable the new Services (Source, Analytic, Responder), Responses Can we specify a different set of recipients for different instance being monitored? Yes, you can specify a different set of recipients for each Instance (see Installation Guide/Personas and Recipients section) What is the roadmap for Multiple instance support? We will continuously evaluate feedback from customers on their experiences in this area and work towards implementing a solution that logically maps to the problem area without undue customization. We recognize that the above requirement to replicate most elements of the RulePoint instance is sub-optimal that amplifies the problems of maintenance, upgrades, version control etc. and will work towards alleviating these problems Installation and Configuration Guide

11 Appendix A: Rules in the Starter Kit Template Rules Template Rules are rules that have been created from templates by specifying values for the parameters. These are just illustrations. Users are encouraged to further customize these solutions as per their requirements. Name Template Name Persona Param Values 3 errors in same workflow within 10 minutes Hardcoded Windows Pathname with C Drive Mapping modified 3 times in the last 10 minutes Mapping Naming Convention Violation Prefix m_ Scheduled Workflow did not start 3 minutes after scheduled time Scheduled Workflow missed schedule by 3 minutes due to running status Session Elapsed Time greater than recent Average Session Failed after Session Saved within 10 minutes Too many errors in same workflow within a few minutes Template dataarchitect Hardcoded Windows Pathname with Drive Template C Mapping modified too often recently Mapping Naming Convention Violation Template m_ Duration (minutes): 10 Count: 3 Times Mapping Saved: 3 Within Minutes: 10 Scheduled Workflow did not start N minutes after scheduled time pcadmin Minutes: 3 Scheduled Workflow missed schedule due to running status pcadmin Minutes: 3 Session Elapsed Time greater than recent Average Session Failed after Session Saved Template dataarchitect Count: 3 Percent Increase: 20 Duration (mins): 10 Analytics used pc_is_workflo w_running pc_getprevnse ssiontimes Proactive Monitoring Installation and Configuration Guide

12 Name Template Name Persona Param Values Session Loaded Rows 15 percent lesser than recent Average Session Modified 3 Times in the last 10 minutes Session Naming Convention Violation for Prefix s_ Skewed Session to Workflow elapsed time ratio less than 0.6 Concurren t Workflows exceeds 2 Workflow Elapsed Time greater than 15pc of recent Average of 3 runs Workflow Load Mobile records running more than 2 minutes Workflow Naming Convention Violation Workflow Running Time greater by 10 percent than recent 3 Average Session Loaded Rows lesser than recent Average Template Session Modified Too Often Recently Session Naming Convention Violation Template Skewed Session to Workflow elapsed time ratio Template dataarchitect pcadmin Percent: 15 Average Count: 3 Duration (minutes): 10 Times Modified: 3 Session Name Prefix: s_ Threshold Ratio: 0.6 Too Many Concurrent Workflows Template pcadmin Count: 2 Workflow Elapsed Time greater than recent Average Advanced Template Workflow Running Time Exceeds Workflow SLA Template Workflow Naming Convention Violation Template Workflow Running Time greater than recent Average Advanced Template Percentage increase over Average: 15 Number of Runs to compute Average: 3 SLA for elapsed time (in minutes): 2 Workflow Name: wf_m_load_mo bile_records Workflow Name Prefix: wf_ Percentage increase over Average: 10 Number of Runs to compute Average: 3 Analytics used pc_getprevnse ssionrows pc_getprevnw orkflowtimes -12- Installation and Configuration Guide

13 Name Template Name Persona Param Values Workflow Running Time greater than Proactive Monitoring SLA 5 minutes Workflow Running Time greater than SLA 10 minutes Zombie Session Alert Rule for 5 minutes Workflow Running Time greater than Folder SLA Template Workflow Running Time greater than SLA Template Zombie Session Alert Template pcadmin Folder: Proactive Monitoring SLA for elapsed time (in minutes 5 SLA for elapsed time (in minutes) 10 Duration of time (minutes) 5 Low Watermark for rows processed in given duration: 0 Analytics used Advanced Rules Unlike Template based rules, Advanced rules do not have parameters. Users are encouraged to extend these Rules themselves once they get comfortable with the functioning of these rules. Name Persona Analytics used Check for Illegal commands Advanced Domain is Down Advanced itsecurity pcadmin Duplicate Mapping Creation Advanced pc_is_mapping_duplicate Duplicate Session Creation Advanced pc_is_session_duplicate Duplicate Workflow Creation Advanced pc_is_workflow_duplicate Notification Advanced pc_recent_alert Failed Rows in Session Advanced Failed Session Advanced dataarchitect Proactive Monitoring Installation and Configuration Guide

14 Name Persona Analytics used Integration Service is Down Advanced Invalidated Mapping Advanced Invalidated Session Advanced Invalidated Workflow Advanced Mapping Name contains spaces Advanced Service is Down Advanced pcadmin pcadmin RTAM Notification Advanced pc_recent_alert Runtime Stats Server Transformer Advanced Runtime Stats Session Transformer Advanced Runtime Stats Target Transformer Advanced Runtime Stats Workflow Transformer Advanced Session Failed Rows Advanced Transform saved with Default Name Advanced Uncommented Mapping Advanced Uncommented Session Advanced Uncommented Transform in watched folders Advanced Uncommented Workflow in watched folders Advanced Workflow succeeded but loaded Zero Rows Advanced dataarchitect -14- Installation and Configuration Guide

15 Appendix B: Analytics and Source Services in the Starter Kit Analytics These services provide data enrichment to the rules that invoke them. Name Connect To pc_get_alert_recipients pc_getprevnsessionrows pc_getprevnsessiontimes pc_getprevnthroughputs pc_getprevnworkflowtimes pc_is_mapping_duplicate pc_is_session_duplicate pc_is_workflow_running pc_recent_alert Source Services RulePoint These services fetch data from repositories and runtime instances that eventually trigger the rules in the starter kit. Frequency (seconds) Name Type Topic Connected to Alert Recorder Concurrent Workflows Event Transformer SQL Source pc_concurrent_wor kflows RulePoint (pc_rp) Starter Kit Value Recommen ded (pcrs_ro) Responder Server Mappings Modified Incremental SQL Source pc_mappings Notification Responder Event Transformer pc_notifications (pcrs_ro) (pcrs_ro) Proactive Monitoring Installation and Configuration Guide

16 Name Type Topic Connected to Pathnames SQL Source pc_pathnames Ping Service Custom Source pc_ping Runtime Statistics Receiver Custom Source pc_runtime_stats Runtime Stats Transformer Scheduler Missed Workflows Scheduler Scheduled Workflows Incremental Session Log Elapsed Time and Throughput Event Transformer SQL Source SQL Source SQL Source Frequency (seconds) Starter Kit Value Recommen ded (pcrs_ro) CLI LM API pc_runtime_server_ stats, pc_runtime_workflo w_stats, pc_runtime_session _stats, pc_runtime_target_ stats pc_missed_workflo ws pc_scheduled_work flows pc_session_log_elap sed_throughput Sessions Modified Incremental SQL Source pc_sessions Transforms Modified Incremental SQL Source pc_transforms Workflow and Session Times and Status SQL Source pc_workflow_sessio n_run_status (pcrs_ro) (pcrs_ro) 3 60 (pcrs_ro) 3 60 (pcrs_ro) (pcrs_ro) (pcrs_ro) Installation and Configuration Guide

17 Name Type Topic Connected to Workflow Control Responder Custom Responder # Workflows Incremental SQL Source pc_workflows LM API Frequency (seconds) Starter Kit Value Recommen ded (pcrs_ro) 3 60 Appendix C: Templates in the Starter Kit Name Channel Persona Parameters Hardcoded Windows Pathname with Drive Template Design Drive Letter Mapping modified too often recently Design Times Mapping Saved Mapping Naming Convention Violation Template Design Mapping Name Prefix Scheduled Workflow did not start N minutes after scheduled time Runtime pcadmin Minutes Scheduled Workflow missed schedule due to running status Runtime pcadmin Minutes Session Elapsed Time greater than recent Average Runtime dataarchitect Count Session Failed after Session Saved Template Runtime Duration (mins) Session Loaded Rows lesser than recent Average Template Runtime dataarchitect Percent Session Modified Too Often Recently Design Duration (minutes) Session Naming Convention Violation Template Design pcadmin Session Name Prefix Skewed Session to Workflow elapsed time ratio Template Runtime dataarchitect Threshold Ratio Too Many Concurrent Workflows Template Runtime pcadmin Proactive Monitoring Installation and Configuration Guide

18 Name Channel Persona Parameters Too many errors in same workflow within a few minutes Template Runtime dataarchitect Duration (minutes) Workflow Elapsed Time greater than recent Average Template Runtime Percentage increase over Average Workflow Naming Convention Violation Template Design Workflow Name Prefix Workflow Running Time Exceeds Workflow SLA Template Workflow Running Time greater than Folder SLA Template Workflow Running Time greater than recent Average Template Workflow Running Time greater than SLA Template Zombie Session Alert Template Runtime (Live) Workflow Name Runtime (Live) Folder Runtime (Live) Runtime (Live) Percentage increase over Average SLA for elapsed time (in seconds) Runtime (Live) pcadmin Duration of time (seconds) Appendix D: Responses in the Starter Kit Name Alert Recorder Response Response Notification Response Runtime Stats Transformer Response Workflow Control Response RTAM Alert Purpose For Suppress Alert feature Notifications Generic Notifier Internal Control Workflows RTAM Alerts -18- Installation and Configuration Guide

19 Contact Information Proactive Monitoring Installation and Configuration Guide