Informatica Proactive Monitoring for PowerCenter Operations (Version 2.0) Solutions Guide

Transcription

1 Informatica Proactive for Operations (Version 2.0) Solutions Guide

2 Informatica Proactive for Operations Solutions Guide Version 2.0 March 2012 Copyright (c) Informatica. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services,, RT, Connect, Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange, Informatica On Demand, Informatica Cloud, AddressDoctor, Agent Logic, Latency Busters, Parallel Persistence, PowerPartner, RTAM, Real Time Alert Manager, RulePoint, Siperian, Ultra Messaging, Event Detection and Response, User-Driven Complex Event Processing, "To Detect and Respond," "CEP for Humans," L2H, Low-to-High, High-to-Low, Enterprise Agent Server are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Firefox is a trademark of the Mozilla Foundation. Intel and Pentium are registered trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Active Directory, Internet Explorer, NetMeeting, PowerPoint, SQL Server, Windows 98, Windows 2000, Windows 2003, Windows NT, and WordPad are either registered trademarks or trademarks of Microsoft Corporation in the United States, other countries, or both. Sun Microsystems, Sun, AnswerBook, Java, JVM, Solaris, Solaris JumpStart, StarOffice, Sun Ray, SunForum, Ultra, and Trusted Solaris are either registered trademarks or trademarks of Sun Microsystems, Inc., in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Apache Tomcat and Tomcat are trademarks of the Apache Software Foundation in the United States, other countries, or both. BEA WebLogic is a registered trademark of BEA Systems, Inc., in the United States, other countries, or both. IBM and WebSphere are registered trademarks of International Business Machines Corporation in the United States, other countries, or both. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright Oracle. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright (c) The Regents of the University of California. All rights reserved. This product includes software developed by the Apache Software Foundation ( and other software which is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software which is licensed under the GNU Lesser General Public License Agreement, which may be found at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software licensed under the terms at openmap.bbn.com/license.html, license.html, and This product includes software licensed under the the Common Development and Distribution License ( the Common Public License ( the BSD License ( the Eclipse Public License ( the Sun Binary Code License Agreement and the MIT License ( This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422, 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: PCPM-SLG

3 Table of Contents Preface.... iii Informatica Resources.... iii Informatica Customer Portal.... iii Informatica Documentation.... iii Informatica Web Site.... iii Informatica How-To Library.... iv Informatica Knowledge Base.... iv Informatica Multimedia Knowledge Base.... iv Informatica Global Customer Support.... iv Chapter 1: Proactive for Operations Overview of Proactive for Operations Key Advantages of Proactive for Operations Overview of Solution Data Sources Monitored Solution Contents Introduction to Proactive Using Complex Event Processing... 5 Individual and Complex Event Detection How RulePoint Works Chapter 2: Installation Overview Installation Options Staging Directory Before You Install System Requirements... 9 Complete the Pre-Installation Tasks Set Up the X Window Server Proactive for Operations Installation Installing in Graphical Mode Installing in Console Mode Installing in Silent Mode After You Install Complete the Post-Installation Tasks Validating the Installation Chapter 3: Proactive for Operations Configuration Alert Recipient Tool Global Setting Tool Table of Contents i

4 Configure RulePoint Components Personas Overview Configuring Alert Recipients for Personas Configure Host Configure Notification Hyperlink Configure Default Notification Behavior Override Default Notification Behavior Configure Snooze Time to Suppress Repeat Alerts Configure Channels Appendix A: Predefined Rules Predefined Rules Overview Template Rules Advanced Rules Appendix B: Predefined Services Analytics Source Services Appendix C: Predefined Templates Appendix D: Predefined Responses Appendix E: Monitor Best Practices for Transformations, Mappings, Sessions, and Workflows Monitor Best Practices for Transformations, Mappings, Sessions, and Workflows Overview Importing Rules for Best Practices Templates for Best Practices Template Rules for Best Practices Advanced Rules for Best Practices Appendix F: Troubleshooting Troubleshooting Installation Issues Troubleshooting Configuration on Windows Troubleshooting Configuration on Linux Appendix G: Glossary Index ii Table of Contents

5 Preface The Proactive for Operations Solutions Guide describes the solution provided for proactively monitoring operations. This guide also contains how to install and configure Proactive for Operations. The target audience of this guide is the Informatica administrator, who is responsible for installing Proactive for Operations. This guide assumes that you have a working knowledge of Informatica, the application server, database server, and other system requirements to install and deploy Proactive for Operations 2.0. Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. iii

6 Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Brazil: Mexico: North America: Toll Free France: Germany: Italy: Netherlands: Portugal: Spain: Switzerland: United Kingdom: Toll Free Australia: New Zealand: Standard Rate India: Standard Rate Belgium: France: Germany: Netherlands: United Kingdom: iv Preface

7 C H A P T E R 1 Proactive for Operations This chapter includes the following topics: Overview of Proactive for Operations, 1 Key Advantages of Proactive for Operations, 2 Overview of Solution, 2 Introduction to Proactive Using Complex Event Processing, 5 Overview of Proactive for Operations Proactive for Operations protects with an automated early warning system. This solution identifies and alerts the users about processes and events that differ from the expected norm. Informatica Proactive for Operations enhances Informatica with proactive monitoring capabilities. The proactive monitoring and alert operation is performed by complex event processing products, Informatica RulePoint and Informatica Real-Time Alert Manager. This solution can identify integration processes that differ from the norm by a certain percentage or deviation. A set of pre-configured, prepackaged sources, rules, and analytics are provided with this solution. When RulePoint detects events that match the conditions specified in a rule, it sends alerts to Real-Time Alert Manager or specified IDs. For detailed information on Informatica RulePoint and Real-Time Alert Manager, see the documentation for these products. RELATED TOPICS: Overview of Solution on page 2 Solution Contents on page 3 Introduction to Proactive Using Complex Event Processing on page 5 Installation Overview on page 7 1

8 Key Advantages of Proactive for Operations administrators, developers, and users can automate monitoring tasks for large deployments using easy to create and modify rules and analytics provided by the Proactive for Operations solution. The following are some of the key advantages of using this solution for monitoring the infrastructure: Avoid failed workflows and tasks Proactive monitoring of real-time data from the Integration Service and repository can alert you to potential issues before they cause a failure. Correlate data from various processes Metrics from the repository, Integration Service, Server infrastructure, and resource usage are correlated to generate alerts on potential issues in a deployment. These alerts can be used to identify bottlenecks in your deployment and workflow design. Isolate issues accurately You can easily identify the cause of a failed workflow, such as whether the cause is a particular session, database connection, hardware resources, or processes that are taking more than the expected time or resources. Avoid manual monitoring and custom scripts You can monitor any number of sessions and workflows with the same rule, or set up different rules to monitor various aspects of the runtime. You can create or change the rule and pattern logic to suit your environment. Quick setup and deployment Pre-packaged rules, analytics, sources, and alert rules are included in the solution. These pre-packaged rules and scenarios enable you to monitor a typical deployment after installing the monitoring solution. Extensible rules and scenarios Existing rules can be further customized by using templates for specific uses. New checkpoints to monitor, rules, and patterns can be created based on your Informatica deployment. RELATED TOPICS: Solution Contents on page 3 Installation Options on page 7 Overview of Solution The Proactive for Operations solution typically runs on a separate installation along with its own repository which is optimized for real-time data and alerting. Through a Web browser, users can access and manage data sources, users, rule writing, and alert definitions. The Proactive for Operations solution is designed to work with your environment with minimum configuration requirements. 2 Chapter 1: Proactive for Operations

9 The solution architecture provides an overview of the proactive monitoring solution. Predefined RulePoint services included in the solution seamlessly integrate with data sources from. Data Sources Monitored RulePoint services are pre-configured for use with the Integration Service, the repository database, and the node on which is installed. Repository The repository provides metadata about the results of completed workflows and sessions. The Proactive for Operations solution connects to the repository to monitor completed and running workflows and sessions, transformation modifications, and workflow to session ratios. The proactive monitoring solution can derive statistics about the performance of sessions and workflows and use that data to measure against recently finished jobs and jobs currently running. Integration Service Through the Web Services Hub monitors the Domain, Data Integration Service, and Repository Service for real time information on running workflows, sessions, and the heartbeat of the integration server. This information helps to identify activities that may be running into trouble before they cause downstream processes to fail. Node Properties RulePoint listeners periodically monitor the instance's environment for CPU, memory, tablespace usage, and database status. When correlated with scheduled or in-process workflows, they help identify issues before they become larger problems. Solution Contents The following components are packaged with the monitoring solution: Pre-configured Package for Enabling The Proactive for Operations solution contains set of source services (SQL and custom), templates, advanced rules, template rules, SQL analytics, watchlists, and responses. The supported Overview of Solution 3

10 repository database types are Oracle, Microsoft SQL Server, and IBM DB2. These are defined in the ready-toimport.xml file, which is imported into RulePoint after installing the solution. For the complete list, see the Appendix in this Solutions Guide. Pre-packaged Scenarios and Alerts for Operational The Proactive for Operations includes a list of pre-packaged sources, rules, analytics, and alerts. These RulePoint artifacts cover alerting that span from operational monitoring of running workflows to identifying problems with finished workflows. The same alert are distributed to a single recipient or a group. The following is a list of the operational monitoring scenarios: Scenarios Workflow or session was successful, but zero (0) records loaded Rejected Records in a Session Disproportionate elapsed time between Workflow and Session Session or Workflow Failures Correlate session changes to workflow failures SLA Violations: Workflow, Folder, or Repository Level Significant increase in Workflow or Session Elapsed Times Significant decrease in applied row counts Workflows missing schedules Too many concurrent workflows Automatic Restart of Zombie Workflows Ping Domain, Integration Service, or Repository Service Result Stops usage of potentially erroneous reporting or operational systems. Improves accuracy of reports. Better decision making. Better productivity. Reduces failed sessions or workflows dependent on prior ones. Reduces group backlog. Improved high priority alerting to remedy issue that may impact downstream systems or processes. Identify issues that may impact downstream processes. Quickly identify root cause of a failure. Deliver on organizational and group pre-determined goals. Early identification of possible source issues or workflow problem. Reduced expense generating customized alerting scripts and maintaining them. Command Line Utilities The Alert Recipient Tool and the Global Settings Tool enable you to easily extend and modify the default settings provided by the solution. For details on using these tools, see the section on Configuration in the Solutions Guide. Database Users Scripts are provided with the installer to create two database users for the repository and the RulePoint repository. Pre-defined Personas Six roles or personas are provided by the solution to receive alerts from RulePoint. These roles cover administrators, developers, and architects. The alert recipients for each persona can be configured to suit the needs of your organization. For more details, see Configuring Personas. 4 Chapter 1: Proactive for Operations

11 RELATED TOPICS: Source Services on page 44 Predefined Services on page 43 Predefined Rules on page 35 Advanced Rules on page 41 Predefined Responses on page 52 Template Rules on page 35 Analytics on page 43 Introduction to Proactive Using Complex Event Processing RulePoint is a Complex Event Processing software platform that companies use to identify patterns in real-time event flows and batch data to proactively alert people, systems and processes. RulePoint enables easy configuration of incoming data sources. These sources are exposed to rule writers as topics. Rule writers can use a variety of modes, from simple templates to advanced rules to describe patterns that they want identified. Responses are configured as methods to distribute notice of a pattern match. These responses can be delivered to people through or dashboards and into systems. The responses can also be accompanied by supporting content. Besides out-of-the-box sources and responses, users can also customize additional ones through the SDK. Individual and Complex Event Detection Monitor or listen in near-real time to data across diverse sources, including the following sources: - Data streams - Sensors Introduction to Proactive Using Complex Event Processing 5

12 - Communications systems - Message queues - Web services - RSS feeds - Databases - Flat files Cross-reference, filter, and correlate events across disparate sources to detect complex events. Leverage third-party entity extraction, natural language processing, and categorization engines as a part of complex event detection processes. Define personalized rules and subscription criteria for Event Detection and response using wizards, advanced mode, or templates. How RulePoint Works RulePoint monitors specified data streams for predetermined events and then acts on those events with the configured rules. RulePoint uses services, which are configurable interfaces that link to another software system, to collect information from relevant streams of data flowing from different data sources. Each piece of information is referred to as an event. These events are published into RulePoint and grouped into categories familiar to and defined by users, which are referred to as topic. RulePoint then uses other services to coordinate responses to those events based on user-defined event processing rules, referred to simply as rules. A rule encapsulates the business logic of analyzing event data from multiple sources to detect specific events based on logical conditions, and then responds to the appropriate party with the proper information. RulePoint enables users to create rules themselves, ensuring that an organization s responsiveness to changing conditions is not hindered by the traditional software development cycle. When RulePoint detects events that match the conditions specified in a rule, it executes the response specified in the rule. These responses can be simple, such as sending an , instant message, or text message, or complex, such as executing updating a database, triggering a web service, initiating other processes across the enterprise, or creating new events used by other rules. 6 Chapter 1: Proactive for Operations

13 C H A P T E R 2 Installation Overview This chapter includes the following topics: Installation Options, 7 Staging Directory, 8 Before You Install, 9 Proactive for Operations Installation, 11 After You Install, 23 Installation Options The Proactive for Operations 2.0 installer supports two installation types. Complete Install Complete install allows you to install and configure all components of Proactive for Operations. Custom Install Custom install allows you to perform specific operations of the complete installation process. You can select one or more custom install options. The custom install is recommended only for advanced users. The following are the five different custom operations that can be done independently depending on the parameters provided: Configure Repository This install type captures the repository database details, updates the database properties, and validates them by connecting to the database. This install type creates tables, views, synonyms, procedures, and functions that are required to interact with the repository. Configure Proactive Repository This install type captures the proactive monitoring repository (that is, RulePoint) database options, updates the database properties, and validates them by connecting to the database. This install type creates tables, views, procedures, and functions for the proactive monitoring repository read-only user to support proactive monitoring alerts. Configure Proactive Solution XML This install type creates the ready_to_import.xml file for RulePoint by capturing all the required properties for database, proactive monitoring repository database, web services, and 7

14 node properties. This file is required to import the custom services for Proactive for Operations sources in RulePoint. The ready_to_import.xml file is saved in the $RP_Home\solutions\PCPM\bin directory after installation. You have to manually import the ready_to_import file to RulePoint after the installation. Install Proactive Libraries This install type copies the JAR files required for Proactive for Operations to the $RP_HOME\WEB-INF\lib directory. This install type also adds custom-services_em.xml and customservices_pc.xml files to the $RP_HOME\WEB-INF\spring directory. It then updates the web.xml file in the $RP_HOME \WEB-INF directory with the required information. Install Proactive Tools This install type installs the Global Setting Tool and the Alert Recipient Tool. The Global Setting Tool is a command line utility that allows you to list or update the Proactive for Operations global settings for receiving alerts. The parameters of this tool are do_not_disturb, alert_hyperlink, default_notification, and alert_history_purge_freq_days. The Alert Recipient Tool is a command line utility that allows you to list or update the Proactive for Operations alert recipients' information. RELATED TOPICS: System Requirements on page 9 Complete the Pre-Installation Tasks on page 9 Monitor Best Practices for Transformations, Mappings, Sessions, and Workflows on page 53 Staging Directory The Proactive package is installed in the staging directory before deploying to the application server. You have to enter the path to the staging directory during installation. The specified directory must be empty. The installer creates the following files in the staging directory: Installer log file (for example, Informatica Proactive 2.0_InstallLog.log) Installer properties file (for example, PCPM2.0_install.properties) Archive file of the Proactive directory The Proactive archive file is later used by the installer to deploy Proactive in the target directory of the application server. 8 Chapter 2: Installation Overview

15 Before You Install System Requirements Before you install Proactive for Operations 2.0, ensure that the minimum system requirements are met to install and run the Proactive for Operations 2.0 installer. Domain Operating Systems Supported Platforms Windows Workstation 2003 (64-bit), Windows Workstation 2008 (64-bit), Red Hat Enterprise Linux Version 5.5 (64-bit), IBM AIX Version 6.1 (64-bit), SUSE Linux Enterprise Server 11 (64-bit) Application Servers Apache Tomcat Database Servers Oracle 11.1, Oracle 11.2, Oracle 10.2, IBM DB , IBM DB2 9.7, Microsoft SQL Server 2008 R2 Hardware Requirements (Recommended) - 64-bit (Intel, AMD-compatible) Xeon equivalent or better, 1.7-Ghz minimum CPU GB RAM GB application disk space - 1 GB (preferred) Ethernet network connection Informatica RulePoint RulePoint 5.2 HotFix 3 Informatica Real-Time Alert Manager Real-Time Alert Manager 3.1 HotFix 1 Complete the Pre-Installation Tasks Before you install Proactive for Operations, ensure to meet the minimum software and hardware requirements. The installer requires information about the database, the application server, and the authentication mechanism. The following are pre-requisites that you need to complete before running the installer for each repository to monitor. 1. Install RulePoint 5.2 HotFix 3 to $RP_HOME. $RP_HOME is the path of RulePoint deployment directory in the webapps directory of the application server. 2. Install Real-Time Alert Manager 3.1 HotFix 1 to $RTAM_HOME. $RTAM_HOME is the path of Real-Time Alert Manager deployment directory in the webapps directory of the application server. 3. Ensure that a Web Services Hub is created and enabled so that RulePoint can access workflows as web services. 4. Create a database user for repository with read-only permissions. The installer contains a resources directory that has the database scripts to create the read-only user with required privileges for the databases. Before You Install 9

16 Use one of the following files to create the read-only users according to the database repository: Oracle:..\resources\dbscripts\powercenter\oracle\create_pc_user.txt Login as sys and run the script. MS-SQL:..\resources\dbscripts\powercenter\sqlserver\create_pc_user.txt Grant SELECT permission on table, sys.database_files to the read-only user for monitoring all the required databases. IBM DB2:..\resources\dbscripts\powercenter\db2\create_pc_user.txt Create a group called DB2SYSMON, and add the repository read-only user to the group. Grant SELECT permission on SYSIBMADM.TBSP_UTILIZATION to the repository read-only user. Run the following commands: db2set DB2_GRP_LOOKUP=LOCAL,TOKENLOCAL db2stop db2start 5. Create a RulePoint repository user to host alerts in the same database as the repository user. Login to the RulePoint repository database, create the user, and grant privileges using the appropriate file based on the database. The installer contains a resources directory that has the database scripts to create the RulePoint user. Use one of the following files to create the users according to the database repository: Oracle:..\resources\dbscripts\rulepoint\oracle\create_rp_user.txt MS-SQL:..\resources\dbscripts\rulepoint\sqlserver\create_rp_user.txt IBM DB2:..\resources\dbscripts\rulepoint\db2\create_rp_user.txt 6. Ensure that the instance of Apache Tomcat application server, in which RulePoint is deployed, is shut down. Set Up the X Window Server When you run the installer in graphical mode, you must use a graphics display server. On UNIX, the graphics display server is typically an X Window server. If you do not have the X Window server installed on the machine where you want to install the product, you can run the installer using an X Window server installed on another machine. Use the DISPLAY variable to redirect output of the X Window server to another UNIX machine. The following table lists the commands to set the DISPLAY environment variable: Shell Command Example C setenv DISPLAY <TCP/IP node of XWindow server>:0 setenv DISPLAY :0 Bash/Korn export DISPLAY= <TCP/IP node of XWindow server>:0 export DISPLAY= :0 Bourne DISPLAY= <TCP/IP node of XWindow server>:0 export display DISPLAY= :0 export display If you do not know the IP address of a UNIX machine where the X Window server is installed, ask your network administrator. For more information about redirecting the DISPLAY variable, see the documentation from the UNIX vendor. If the X Window server does not support the font that the installer uses, the installer can display incorrect labels on the buttons. 10 Chapter 2: Installation Overview

17 Proactive for Operations Installation You can install the Proactive for Operations 2.0 on a Windows, Linux, or AIX machine. To install Proactive for Operations, you can run the installer in graphical, console, or silent mode. Complete the pre-installation tasks to prepare for the installation. You can install Proactive for Operations from a DVD or from the root of the directory where you download the installation files. The user who runs the installer must have read, write, and execute permissions on the installer and its files directory, and write access to the /tmp directory in Linux or AIX. This section contains the following topics: Installing in Graphical Mode on page 11 Installing in Console Mode on page 15 Installing in Silent Mode on page 18 Installing in Graphical Mode The Proactive for Operations 2.0 installer allows you to define the installation preferences and install Proactive for Operations in graphical mode on Windows, Linux, or AIX. Before you begin the installation, ensure that the system meets all the memory, hardware, and software requirements to install Proactive for Operations. 1. Run the Proactive for Operations 2.0 installer based on your operating environment. To install on Windows, run Informatica_PCPM_2.0.exe from the directory that contains the extracted installation files. To install on Linux or AIX, - Use a shell command line and go to the directory that contains the extracted installation files. - Enter the Proactive for Operations executable name with the option -i gui. For example, enter Informatica_PCPM_2.0.bin -i gui. 2. In the Proactive 2.0 Setup Wizard window, click Next. 3. The Prerequisites window displays the installation requirements. Verify that all requirements are met before you continue the installation. 4. Click Next. 5. In the Installation Mode window, select the type of install, and click Next. Select Complete Install to install and configure all the components of Proactive for Operations. Select Custom Install to install and configure the required components according to the requirements. The custom install is recommended only for advanced users. The following are the options for custom install: - Configure Repository - Configure Proactive Repository - Configure Proactive Solution xml - Install Proactive Libraries - Install Proactive Tools Note: You can select one or more options in custom install mode. Proactive for Operations Installation 11

18 6. In the Choose Staging Folder window, specify the staging directory in which to configure the Proactive for Operations application. The default location for the staging directory in Windows is C:\PCPM2.0. The default location for the staging directory in Linux and AIX is /home/pcpm Click Next. 8. In the RulePoint Deployment Directory window, enter the path to $RP_HOME. For example, if RulePoint is deployed in Apache Tomcat 6 application server, enter the path $CATALINA_HOME \webapps\rulepoint. 9. Click Next. 10. In the Database Configuration window, enter the database details. The following table describes the properties that you specify for the database: Property Database Type Description Type of repository database. The supported database types are Oracle, IBM DB2, and MS-SQL. Note: This field is automatically populated based on the RulePoint database type. The information is retrieved from $RP_HOME path given in the RulePoint Deployment Directory window. read-only User read-only User Password Repository User Driver Class Connection URL read-only repository user name. Create the read-only user before starting the install process. Use the create_pc_user.txt scripts based on the repository database type to create this read-only user. For example, pcrs_readonly. For information on how to create this user, see the Preinstallation section of this guide. Password for the read-only repository user. Repository owner of the database, that is the repository schema administrator. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Repository Service you want to monitor. 4. In the Repository Service tab, the Database Username under Database Properties is the required Repository User. This user is created by the database administrator before Server is installed. JDBC driver class to establish connection to the database chosen. Information in this field is populated automatically based on the database type. The information for this field is retrieved from the JDBC properties file in $RP_HOME. JDBC connection string to connect to the database. The format for this field gets populated automatically based on the database type. You must 12 Chapter 2: Installation Overview

19 Property Description correct the string for the correct host name, port number, and the database name. 11. Click Test Connection to verify the input details. You cannot go to the next step without verifying the connection details. However, the installer provides the option to continue with the installation even if the connection is not successful. Important: We recommend you to provide the correct connection details before going to the next step. 12. Click Next. 13. In the Services Configuration window, enter the Web Services Hub WSDL URL and the required credentials. The following table describes the properties that you specify for the user parameters: Property Web Services Hub WSDL URL Domain Name Repository Service Name Repository Administrator User Name Repository Password Integration Service Name Description URL for the Web Services Hub WSDL. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Web Services Hub of the domain. 4. In the Web Services Hub tab, the Service URL is the required input for this field. Domain name of the repository. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator. The Domain Navigator panel will contain the list of domains to be monitored. Service name of repository. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Repository Service of the domain. 4. In the Repository Service tab, the Name under General Properties is the required Repository Service Name. repository service user name used to connect to the Administrator console (usually Administrator). Password for the service repository user. integration service name. The Integration Service reads workflow information from the repository. The Integration Service connects to the repository through the Repository Service to fetch metadata from the repository. Proactive for Operations Installation 13

20 Property Description To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Integration Service of the domain. 4. In the Integration Service tab, the Name under General Properties is the required Integration Service Name. Important: The installer does not validate the inputs provided for these fields. Ensure that you provide the correct information for these fields. 14. Click Next. 15. In the RulePoint Database Configuration for Proactive window, enter database authentication details, and click Test Connection. You cannot proceed to the next step without verifying the connection details. Provide details of the RulePoint repository user for receiving alerts. Create this user before running the installer. Use the create_rp_user.txt database scripts provided with the installer to create this user. Inputs for the Driver Class and Connection URL fields are automatically taken from $RP_HOME. 16. Click Next. 17. In the Configuration for Integration Service window, enter the parameters for environment monitoring. The following table describes the properties that you specify for environment monitoring: Property Node OS Type Network Domain Name Integration Service Host Name or IP Operating System User Name Operating System Password Description Choose the operating system type of the node. The supported operating system types are Windows, AIX, and Linux. Important: For Windows, ensure that the Windows Management Instrumentation service is installed and running. For Linux or AIX, enable SSHD. For Windows, enter the Network Domain Name of the machine. Host name or IP of the Integration Service machine. User name to log in to the machine for the chosen operating system. Password for the user name of the machine for the chosen operating system. Important: The installer does not validate the inputs provided for these fields. Ensure that you provide the correct information for these fields. If you see Windows or Linux configuration errors for environment monitoring, see the appendix on Troubleshooting in this guide. 14 Chapter 2: Installation Overview

21 18. Click Next. 19. Review the installation summary, and click Install. 20. Click Done to complete the installation procedure and then exit the installer. RELATED TOPICS: Complete the Post-Installation Tasks on page 23 Validating the Installation on page 24 Troubleshooting Installation Issues on page 57 Installing in Console Mode The Proactive for Operations 2.0 installer allows you to define the installation preferences and install Proactive for Operations in console mode on Windows, Linux, or AIX. Before you begin the installation, ensure that the system meets all the memory, hardware, and software requirements to install Proactive for Operations. When you run the installer in console mode, the words Quit and Back are reserved words. Do not use them as input text. 1. On the command prompt for Windows or on a shell command line for Linux and AIX, go to the directory that contains the extracted installation files. 2. Enter the Proactive for Operations executable name with the option -i console. For Windows, enter Informatica_PCPM_2.0.exe -i console. For Linux or AIX, enter Informatica_PCPM_2.0.bin -i console. 3. In the Proactive 2.0 Console Mode Installation window, press Enter to continue. 4. The Prerequisites window displays the installation requirements. Verify that all requirements are met before you continue the installation. 5. In the Installation Mode window, enter the type of install, and press Enter. Enter 1 for Complete Install to install and configure all Proactive for Operations components. Enter 2 for Custom Install to install and configure the required components according to the requirements. The custom install is recommended only for advanced users. The following are the options for custom install: - Configure Repository - Configure Proactive Repository - Configure Proactive Solution XML - Install Proactive Libraries - Install Proactive Tools Note: You can select one or more options in custom install mode. 6. In the Choose Staging Folder window, specify the staging directory in which to configure the Proactive for Operations application, and then click Next. The default location for the staging directory in Windows is C:\PCPM2.0. The default location for the staging directory in Linux and AIX is /home/pcpm In the RulePoint Deployment Directory window, enter the path to $RP_HOME and press Enter. For example, if RulePoint is deployed in Apache Tomcat 6 application server, enter the path %CATALINA_HOME%/ webapps/rulepoint. Proactive for Operations Installation 15

22 8. In the Database Configuration window, enter the database details. The following table describes the properties that you specify for the database: Property Database Type read-only User read-only User Password Repository User Driver Class Connection URL Description Type of repository database. The supported database types are Oracle, IBM DB2, and MS-SQL. Note: This field is automatically populated based on the RulePoint database type. The information is retrieved from $RP_HOME path given in the RulePoint Deployment Directory window. read-only repository user name. Use the create_pc_user.txt scripts based on the repository database type to create this read-only user. For example, pcrs_readonly. Password for the read-only repository user. Repository owner of the database, that is the repository schema administrator. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Repository Service you want to monitor. 4. In the Repository Service tab, the Database Username under Database Properties is the required Repository User. This user is created by the database administrator before Server is installed. JDBC driver class to establish connection to the database chosen. Information in this field is populated automatically based on the database type. The information for this field is retrieved from the JDBC properties file in $RP_HOME. JDBC connection string to connect to the database. The format for this field gets populated automatically based on the database type. You must correct the string for the correct host name, port number, and the database name. 9. Wait till the installer verifies the input details, and then press Enter. You cannot go to the next step without verifying the connection details. However, the installer provides the option to continue with the installation even if the connection is not successful. Important: We recommend you to provide the correct connection details before going to the next step. 10. In the Services Configuration window, enter the Web Services Hub WSDL URL and the required credentials. 16 Chapter 2: Installation Overview

23 The following table describes the properties that you specify for the user parameters: Property Web Services Hub WSDL URL Domain Name Repository Service Name Repository Administrator User Name Repository Password Integration Service Name Description URL for the Web Services Hub WSDL. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Web Services Hub of the domain. 4. In the Web Services Hub tab, the Service URL is the required input for this field. Domain name of the repository. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator. The Domain Navigator panel will contain the list of domains to be monitored. Service name of repository. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Repository Service of the domain. 4. In the Repository Service tab, the Name under General Properties is the required Repository Service Name. repository user name used to connect to the Administrator console (usually Administrator). Password for the repository user. integration service name. The Integration Service reads workflow information from the repository. The Integration Service connects to the repository through the Repository Service to fetch metadata from the repository. To provide inputs for this field, 1. Log in to Informatica Administrator console. 2. Go to Domain Navigator, and select the domain to be monitored. 3. Select the Integration Service of the domain. 4. In the Integration Service tab, the Name under General Properties is the required Integration Service Name. Important: The installer does not validate the inputs provided for these fields. Ensure that you provide the correct information for these fields. 11. In the RulePoint Database Configuration for Proactive window, enter database authentication details. Provide details of the RulePoint repository user for receiving alerts. Create this user before running the installer. Use the create_rp_user.txt database scripts provided with the installer to create this user. Proactive for Operations Installation 17