Download Informatica Proactive Monitoring for PowerCenter Governance 2.0

Informatica Proactive Monitoring for PowerCenter Governance
(Version 2.0)
Solutions Guide
Informatica Proactive Monitoring for PowerCenter Governance Solutions Guide
Version 2.0
June 2012
Copyright (c) 1998-2012 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 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (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, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter 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 (http://www.apache.org/), and other software which is licensed under the Apache License,
Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. 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 http://www.gnu.org/licenses/lgpl.html. 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 http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes software licensed under the terms at http://www.hpsearch.org/, http://www.antlr.org/license.html, http://displaytag.sourceforge.net/11/license.html, http://
openmap.bbn.com/license.html, http://dist.codehaus.org/janino/new_bsd_license.txt, https://github.com/jquery/jquery/blob/master/MIT-LICENSE.txt, http://www.jython.org/
license.html, http://madrobby.github.com/scriptaculous/license/, http://xdoclet.sourceforge.net/xdoclet/licenses/xdoclet-license.html, http://xstream.codehaus.org/license.html,
and http://developer.yahoo.com/yui/license.html
This product includes software licensed under the the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public
License (http://www.opensource.org/licenses/cpl1.0.php), the BSD License (http://www.opensource.org/licenses/bsd-license.php), the Eclipse Public License (http://
www.eclipse.org/org/documents/epl-v10.php), the Sun Binary Code License Agreement and the MIT License (http://www.opensource.org/licenses/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: PMPG-SLG-20000-0001
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Chapter 1: Introduction to Proactive Monitoring for PowerCenter Governance. . . . . . . 1
Proactive Monitoring for PowerCenter Governance Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . 1
Solution Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2: Solution Technical Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction to Complex Event Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
RulePoint Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Solution Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
PowerCenter Components Monitored. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Solution Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 3: Introduction to Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installation and Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 4: First Time Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
First Time Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Overview of Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Verify System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Install RulePoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Install Real-Time Alert Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Install PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Create RulePoint and PowerCenter Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Set Up the X Window Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installing in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
After You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table of Contents
i
Restart RulePoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Create Users and Groups in RulePoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configure Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Grant Permissions to PowerCenter Read-Only User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Start Services and Enable Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Validate the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring RulePoint Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring Default Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Troubleshooting RulePoint Service Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Troubleshooting Real-Time Alert Manager to Receive Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 5: Custom Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Custom Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installing in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
After You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Import the XML Files for the Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Troubleshooting Custom Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Troubleshooting PowerCenter Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Troubleshooting PowerCenter Services Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Troubleshooting RulePoint Source Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Troubleshooting Errors While Importing the XML Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Restore Deleted Tools to the Staging Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Chapter 6: Overlay Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Overlay Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installing in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Installing in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
After You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Appendix A: Alert Recipient Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Appendix B: Global Setting Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Global Settings Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Cleanup Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Appendix C: Predefined Alert Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix D: Predefined Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Predefined Rules Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Template Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
ii
Table of Contents
Advanced Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Appendix E: Predefined Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Appendix F: Predefined Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Source Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Responder Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Appendix G: Predefined Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Appendix H: Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table of Contents
iii
Preface
The Proactive Monitoring for PowerCenter Governance Solutions Guide describes the solution provided for
proactively monitoring PowerCenter development environment. This guide also contains how to install and
configure Proactive Monitoring for PowerCenter Governance.
The target audience of this guide is the Informatica PowerCenter administrator, who is responsible for installing
Proactive Monitoring for PowerCenter Governance. This guide assumes that you have a working knowledge of
Informatica PowerCenter, the application server, database server, and other system requirements to install and
deploy Proactive Monitoring for PowerCenter Governance.
Informatica Resources
Informatica Customer Portal
As an Informatica customer, you can access the Informatica Customer Portal site at
http://mysupport.informatica.com. 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
email at [email protected]. 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 http://mysupport.informatica.com.
Informatica Web Site
You can access the Informatica corporate web site at http://www.informatica.com. 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.
iv
Informatica How-To Library
As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com.
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 http://mysupport.informatica.com.
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 email at [email protected].
Informatica Multimedia Knowledge Base
As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at
http://mysupport.informatica.com. 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 email at [email protected].
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 http://mysupport.informatica.com.
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America
Europe / Middle East / Africa
Asia / Australia
Toll Free
Toll Free
Toll Free
Brazil: 0800 891 0202
France: 0805 804632
Australia: 1 800 151 830
Mexico: 001 888 209 8853
Germany: 0800 5891281
New Zealand: 09 9 128 901
North America: +1 877 463 2435
Italy: 800 915 985
Netherlands: 0800 2300001
Portugal: 800 208 360
Standard Rate
Spain: 900 813 166
India: +91 80 4112 5738
Switzerland: 0800 463 200
United Kingdom: 0800 023 4632
Standard Rate
Belgium: +31 30 6022 797
France: +33 1 4138 9226
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511445
Preface
v
vi
CHAPTER 1
Introduction to Proactive Monitoring
for PowerCenter Governance
This chapter includes the following topics:
¨ Proactive Monitoring for PowerCenter Governance Solution Overview, 1
¨ Solution Capabilities, 2
Proactive Monitoring for PowerCenter Governance
Solution Overview
Informatica Proactive Monitoring for PowerCenter Governance is an automated early warning system for the
PowerCenter development environment. This solution identifies and alerts the PowerCenter developer of
exceptions in transformation, mappings, sessions, and workflows.
The proactive monitoring solution can identify inadvertent coding violations by PowerCenter developers while
designing mappings, sessions, and workflows. A set of pre-configured, prepackaged sources, rules, analytics, and
alert rules 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 email IDs.
For example, the monitoring solution can check for naming convention violations, use of illegal commands in
command tasks, required attributes not enabled for sessions, and sessions and workflows without comments. The
alert messages identify the session, workflow, or task in which the violation occurred.
The proactive monitoring and alert operation is performed by the complex event processing products, Informatica
RulePoint and Informatica Real-Time Alert Manager.
For more information about Informatica RulePoint and Real-Time Alert Manager, see the documentation for these
products.
1
Solution Capabilities
PowerCenter developers can automate monitoring tasks for large PowerCenter deployments with predefined rules
and analytics provided by the proactive monitoring solution.
Proactive monitoring of PowerCenter developer tasks ensures that best practices are followed when implementing
sessions and workflows. The pre-packaged rules and analytics can monitor the PowerCenter repository for
violation of design guidelines.
The proactive monitoring solution offers the following advantages for a PowerCenter development environment:
Troubleshoot effectively
You can enforce best practices for the design and implementation of PowerCenter transformations, workflows,
tasks, sessions and mappings. Alerts are sent to the specified recipients when a transformation, workflow, or
session is created and saved that violates the best practices specified in the rules.
This helps the troubleshooting process since the alert contains the attribute name and value which violates
the best practices. For example, the monitoring solution can detect session and workflow names that violate
the naming convention, mapping names without descriptions, naming conflicts, and whether a session is
modified often within the specified duration.
Prevent data loss
You can prevent data loss during the execution of a session or workflow by monitoring some of the properties
during the design of the session or workflow. For example, the monitoring solution can detect if certain
options such as, the truncate target table option or rollback transactions on error value is set.
Detect potential production issues
You can monitor session and workflow properties in the development environment to prevent issues in the
production environment. For example, the monitoring solution sends an alert if hardcoded values are used for
source connection parameters, illegal command tasks, hard-coded Microsoft Windows drive, and hard-coded
UNIX path names.
Prevent undesirable changes
You can monitor the session or workflow properties for any undesirable changes that affect the execution of
the workflow or task. For example, the monitoring solution will send an alert when sessions are disabled or
when a session is modified three times within the last 60 minutes.
Improve log management
Detailed alerts in Real-Time Alert Manager help to monitor the level of traceability of PowerCenter objects
during execution. This helps in better log management. For example, the monitoring solution sends an alert if
a transformation has Tracing Level set higher than terse.
Enforce session and workflow configuration
You can enforce the selection of the workflow and session properties as defined by development best
practices because the solution monitors session properties that affect the execution of workflows. For
example, the monitoring solution sends an alert if the session has both Fail parent if the task fails and Fail
parent if this task does not run options not set.
Customize templates and rules
You can define new template rules using the existing templates based on your monitoring requirements. The
monitoring solution contains pre-built rules for self-service editing and tuning, along with the tools for creating
new-rules, which helps organizations scale and manage rules consistently.
2
Chapter 1: Introduction to Proactive Monitoring for PowerCenter Governance
CHAPTER 2
Solution Technical Overview
This chapter includes the following topics:
¨ Introduction to Complex Event Processing , 3
¨ Solution Architecture, 5
Introduction to Complex Event Processing
Proactive monitoring for PowerCenter leverages complex event processing product, Informatica RulePoint, to
process and analyze PowerCenter events. RulePoint can monitor or listen in near-real time to data across diverse
sources.
RulePoint is a complex event processing software platform that you can use to identify patterns in real-time event
flows and batch data to proactively alert people, systems and processes.
You can integrate multiple types of data sources seamlessly with RulePoint. Data sources are exposed to rule
writers as topics. RulePoint users can use multiple modes, from simple templates to advanced rules that describe
patterns that they want identified.
When events match the specified patterns, RulePoint sends alerts based on the configured responses. Responses
are delivered to recipients through email or dashboards and into systems. The responses contain details of the
error or event. You can customize additional sources and responses through the SDK.
RulePoint Architecture
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
3
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. 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.
Users can create and modify 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 email, instant message, or text message, or
complex, such as updating a database, triggering a web service, initiating other processes across the enterprise,
or creating new events used by other rules.
4
Chapter 2: Solution Technical Overview
Solution Architecture
The proactive monitoring solution works with your PowerCenter environment with minimum configuration
requirements. Predefined RulePoint services integrate with PowerCenter data sources.
The proactive monitoring solution is a RulePoint application which runs on a Java application server. The
application server and RulePoint are installed on a machine, separate from the PowerCenter installation. Through
a web browser, you can access and manage data sources, users, rule writing, and alert definitions.
The following illustration shows the solution architecture:
The proactive monitoring solution runs on a RulePoint instance and connects to the PowerCenter components to
collect data. Incremental changes to sessions, workflows, mappings, and transformations are gathered from the
PowerCenter repository.
You can see the alert information in the Real-Time Alert Manager dashboard.
PowerCenter Components Monitored
The proactive monitoring installation program collects data about the PowerCenter environment and configures
RulePoint to obtain data for rule processing.
The proactive monitoring solution is pre-configured to connect RulePoint source services with the PowerCenter
repository. During runtime, RulePoint connects to the PowerCenter repository. The PowerCenter repository
contains metadata for mappings, sessions, and workflows. The proactive monitoring solution connects to the
repository to retrieve information on modified transformations, mappings, sessions, and workflows to use in rule
processing.
Solution Contents
The proactive monitoring solution contains RulePoint artifacts, database scripts, command line utilities, and
personas to quickly configure and monitor the PowerCenter installation.
The installation program installs the required components on the specified RulePoint instance and configures all
RulePoint artifacts, such as pre-defined source services, templates, advanced rules, template rules, SQL
Solution Architecture
5
analytics, watch lists, and responses. To enable RulePoint to obtain and process data from PowerCenter, the
installer creates database tables for the following two database users:
¨ Read-only user in the PowerCenter repository.
¨ User with read and write privileges on the proactive monitoring repository in the RulePoint database.
Command line utilities and personas are installed to configure and control alert recipients and the mode of
delivery. The following command line utilities and personas extend and modify the default settings provided by the
solution:
Command Line Utilities
The Alert Recipient Tool
Use the Alert Recipient Tool to change or list the alert recipients.
Global Settings Tool
Use the global setting tool to change the overall settings for receiving alerts and notifications.
The command line tools are available for both Microsoft Windows and UNIX platforms.
Pre-defined Personas
Alert recipients are logically grouped by function into different personas, such as administrators, developers, and
architects. You can configure multiple notification destinations, such as Real-Time Alert Manager IDs and email
addresses for each persona based on the needs of your organization.
The rules sheet specifies the persona that is configured for each rule. In the case of template based rules, these
personas are inherited from the templates. You can specify the default list of alert recipients for each PowerCenter
folder and workflow.
The following personas are configured by default with the proactive monitoring solution:
pcadmin
PowerCenter administrators. The pcadmin admin persona is responsible for maintaining PowerCenter
workflows, sessions, domains, integration services, and repository services.
apparchitect
PowerCenter developers or subject matter experts. The apparchitect persona is responsible for the logic of
PowerCenter mappings, mapplets, transforms, sources, and targets.
dataarchitect
Any user who maintains the data that is integrated with PowerCenter.
itsecurity
Any user responsible for dealing with IT security issues, such as sensitive data and malware.
pcuser
Any PowerCenter user who sets up workflows, mapping, and transformations.
pcmonitor
Anyone who tracks PowerCenter performance. By default, all alerts are sent to the pcmonitor persona.
6
Chapter 2: Solution Technical Overview
CHAPTER 3
Introduction to Installation and
Configuration
This chapter includes the following topics:
¨ Installation and Configuration Overview, 7
¨ Installation Options, 7
Installation and Configuration Overview
You can install Proactive Monitoring for PowerCenter Governance 2.0 on a Windows, Linux, or AIX machine. To
install Proactive Monitoring for PowerCenter Governance, you can run the installer in graphical or console mode.
Complete the pre-installation tasks to prepare for the installation.
You can install Proactive Monitoring for PowerCenter Governance from a DVD or from the root of the directory
where you download the installation files.
When you run the installer, you provide a path to a staging directory. The installer creates the directory and
extracts the Proactive Monitoring for PowerCenter Governance package to the folder before deploying it to the
target directory of the application server.
Proactive Monitoring for PowerCenter Governance supports homogenous database environments for an instance
of RulePoint, Real-Time Alert Manager, and PowerCenter. Therefore, use the same database type for both
PowerCenter and RulePoint for an instance. For example, if you install PowerCenter on Oracle, you must install
RulePoint on Oracle. On the other hand, difference in the operating system does not affect the functioning of
Proactive Monitoring for PowerCenter Governance.
Installation Options
When you run the Proactive Monitoring for PowerCenter Governance installer, you can choose from the following
installation options:
¨ First time install. Install and configure all components of Proactive Monitoring for PowerCenter Governance.
¨ Custom install. Install a specific component of Proactive Monitoring for PowerCenter Governance.
You see the custom installation option when you install Proactive Monitoring for PowerCenter Governance 2.0
on an instance of Proactive Monitoring for PowerCenter Governance 2.0.
7
Choose the custom install option to correct the errors of the previous instance of proactive monitoring install.
For example, if you created an incorrect pcrs_readonly user, you must correct the user name and password,
and regenerate the solution XML files.
¨ Overlay install. Install Proactive Monitoring for PowerCenter Governance 2.0 on Proactive Monitoring for
PowerCenter Operations 2.0, 2.0 HotFix 1, or 2.1. You cannot install Proactive Monitoring for PowerCenter
Governance 2.0 on any other versions of Proactive Monitoring for PowerCenter Operations earlier than 2.0.
When you run the installer for overlay install, provide the correct location for $RP_HOME.
8
Chapter 3: Introduction to Installation and Configuration
CHAPTER 4
First Time Installation
This chapter includes the following topics:
¨ First Time Installation Overview, 9
¨ Before You Install, 9
¨ Installing in Graphical Mode, 13
¨ Installing in Console Mode, 15
¨ After You Install, 17
¨ Configuring RulePoint Components, 20
¨ Configuring Default Notification, 21
¨ Troubleshooting RulePoint Service Errors, 22
¨ Troubleshooting Real-Time Alert Manager to Receive Alerts, 22
First Time Installation Overview
You can install Proactive Monitoring for PowerCenter Governance in graphical or console mode on Windows,
Linux, or AIX. Complete the pre-installation tasks to prepare for the first time installation.
You can install Proactive Monitoring for PowerCenter Governance from a DVD or from the root of the directory
where you download the installation files.
Before You Install
Before you install Proactive Monitoring for PowerCenter Governance, complete the following tasks for each
repository to monitor:
¨ Verify the system requirements.
¨ Install RulePoint.
¨ Install Real-Time Alert Manager.
¨ Install PowerCenter.
¨ Create RulePoint and PowerCenter Users.
¨ Set up the X Window server.
¨ Shut down the instance of Apache Tomcat application server where RulePoint is deployed.
9
Overview of Pre-Installation Tasks
Before you install Proactive Monitoring for PowerCenter Governance, set up the machine to meet the
requirements to install and run Proactive Monitoring for PowerCenter Operations. The installer requires
information about the database, the application server, and the authentication mechanism.
On Linux or AIX, 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. The /tmp directory must have sufficient space for the
installer to perform the upgrade.
Verify System Requirements
Before you install Proactive Monitoring for PowerCenter Governance, ensure to meet the minimum system
requirements to install and run the Proactive Monitoring for PowerCenter Governance installer.
The following table lists the platforms supported by Proactive Monitoring for PowerCenter Governance:
Domain
Supported Platforms
Operating Systems
- Windows
- Linux
- AIX
Application Servers
Apache Tomcat
Database Servers
- Oracle
- IBM DB2
- Microsoft SQL Server
Recommended Hardware Requirements
- 64-bit Intel or AMD-compatible, Xeon equivalent or better,
1.7 Ghz minimum CPU
- 12-16 GB RAM
- 5-10 GB application disk space
- 1 GB Ethernet network connection
Informatica RulePoint
RulePoint 5.2 HotFix 3
Informatica Real-Time Alert Manager
Real-Time Alert Manager 3.1 HotFix 1
Informatica PowerCenter
- Informatica PowerCenter 8.6.1
- Informatica PowerCenter 9.0.1
- Informatica PowerCenter 9.1.0
For more information about Proactive Monitoring for PowerCenter Operations support, see the Product Availability
Matrix at https://communities.informatica.com/community/my-support/tools/product-availability-matrices.
Install RulePoint
Install RulePoint 5.2 HotFix 3 in $RP_HOME.
$RP_HOME is the path of RulePoint deployment directory in the webapps directory of Apache Tomcat application
server. For example, $CATALINA_HOME\webapps\rulepoint.
Install Real-Time Alert Manager
Install Real-Time Alert Manager 3.1 HotFix 1 in $RTAM_HOME.
10
Chapter 4: First Time Installation
$RTAM_HOME is the path of Real-Time Alert Manager deployment directory in the webapps directory of Apache
Tomcat application server. For example, $CATALINA_HOME\webapps\rtam
Install PowerCenter
Install and configure PowerCenter Repository Service.
The PowerCenter repository service must run on Windows, Linux, or AIX.
Create RulePoint and PowerCenter Users
Before you install Proactive Monitoring for PowerCenter Governance, create the database users for RulePoint and
PowerCenter repository.
Complete the following prerequisites before you install Proactive Monitoring for PowerCenter Governance:
1.
Create a database user, pc_rp, to host alerts in the RulePoint database.
Log in to the RulePoint database, create the user, and grant privileges using the correct file based on the
database type.
The Proactive Monitoring for PowerCenter Governance installer contains a resources directory that has the
text files with the database scripts and instructions to create the RulePoint database user. You can find the
database scripts in the following path of the installer:
¨ Oracle. ..\resources\dbscripts\rulepoint\oracle\create_rp_user.txt
Run the SQL commands in the create_rp_user.txt file to create the RulePoint database user.
¨ Microsoft SQL Server. ..\resources\dbscripts\rulepoint\sqlserver\create_rp_user.txt
Follow the steps in the create_rp_user.txt file to set up the Microsoft SQL server and create the RulePoint
database user.
¨ IBM DB2. ..\resources\dbscripts\rulepoint\db2\create_rp_user.txt
Follow the steps in the create_pc_user.txt file to set up the IBM DB2 server and create the RulePoint
database user.
2.
Create a database user, pcrs_readonly, with read-only permissions to access PowerCenter repository.
The Proactive Monitoring for PowerCenter Governance installer contains a resources directory that has the
text files with the database scripts and instructions to create the PowerCenter read-only user with required
privileges for the databases.
You can find the database scripts in the following path of the installer:
¨ Oracle. ..\resources\dbscripts\powercenter\oracle\create_pc_user.txt
Log in as sys. Run the SQL commands in the create_pc_user.txt file to create the PowerCenter repository
read-only user.
¨ Microsoft SQL Server. ..\resources\dbscripts\powercenter\sqlserver\create_pc_user.txt
Follow the steps in the create_pc_user.txt file to set up the Microsoft SQL Server and create the
PowerCenter repository read-only user.
Grant SELECT permission on table, sys.database_files to pcrs_readonly for monitoring all the required
databases.
¨ IBM DB2. ..\resources\dbscripts\powercenter\db2\create_pc_user.txt
Before You Install
11
Follow the steps in the create_pc_user.txt file to set up the IBM DB2 server and create the PowerCenter
repository read-only user. Refer the following steps to grant permissions:
¨Create a group called DB2SYSMON, and add pcrs_readonly to the group.
¨Grant SELECT permission on SYSIBMADM.TBSP_UTILIZATION to pcrs_readonly.
¨Run the following commands:
db2set DB2_GRP_LOOKUP=LOCAL,TOKENLOCAL
db2stop
db2start
3.
If the users created for Microsoft SQL Server use Windows authentication, then the connection URL must
have the useNTLMv2 and domain properties set. If the useNTLMv2 and domain properties are not set, you
cannot install Proactive Monitoring for PowerCenter Governance as the Test Connection fails.
Change the db.url_base value in jdbc.properties file of RulePoint and in the PowerCenter Database
Configuration window of the installer.
For example, db.url_base=jdbc:jtds:sqlserver://
invr28cep1:1433;DatabaseName=rulepoint_cep44;useNTLMv2=true;domain=INVR28CEP1.
Note: The Alert Recipient Tool and the Global Setting Tool does not work with Microsoft SQL Server when
you configure the user using Windows authentication. The Alert Recipient Tool and the Global Setting Tool
parses only the db.url_base property in the jdbc.properties file. Hence the db.url_base must contain the
correct value as db.url={db.url_base}.{databasename}.
Set Up the X Window Server
When you run the installer in graphical mode on UNIX or Linux, 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 with 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 10.1.50.23:0
Bash/Korn
export DISPLAY=”<TCP/IP node of XWindow server>:0”
export DISPLAY=”10.1.50.23:0”
Bourne
DISPLAY=”<TCP/IP node of XWindow server>:0”
DISPLAY=”10.1.50.23:0”
export display
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.
12
Chapter 4: First Time Installation
Installing in Graphical Mode
You can install Proactive Monitoring for PowerCenter Governance in graphical mode on Windows, Linux, or AIX.
1.
Run the Proactive Monitoring for PowerCenter Governance installer based on the operating system.
¨ To install on Windows, run Informatica_PMPC_Governance_2.0.exe from the root directory.
¨ To install on Linux or AIX, use a shell command line to run Informatica_PMPC_Governance_2.0.bin from the
root directory with -i gui option for graphical mode installation. For example, enter
Informatica_PMPC_Governance_2.0.bin -i gui
2.
In the Introduction window, click Next.
The Choose Staging Folder window appears.
3.
Specify the staging directory in which to configure the Proactive Monitoring for PowerCenter Governance
solution.
The following table shows the default location of the staging folder:
4.
Operating System
File Path
Windows
C:\PMPC_Governance_2.0
Linux and AIX
/home/PMPC_Governance_2.0
Click Next.
The RulePoint Deployment Directory window appears.
5.
Enter the path to $RP_HOME.
For example, enter the following path of the RulePoint deployment directory in webapps directory of Apache
Tomcat 6 application server:
$CATALINA_HOME\webapps\rulepoint
6.
Click Next.
The Installation Type window appears.
7.
Verify the installation type.
8.
Click Next.
The Prerequisites window appears.
9.
Verify the installation requirements, and click Next.
The RulePoint Database Configuration for Proactive Monitoring window appears.
10.
Enter the RulePoint database user name and database password, and click Test Connection.
To proceed to the next step, you must verify the connection details.
Inputs for the fields Driver Class and Connection URL are taken from $RP_HOME.
Note: If you continue the installation after the connection fails, the installer does not create objects that are
required for monitoring.
11.
Click Next.
The PowerCenter Database Configuration window appears.
12.
Enter the PowerCenter database details.
Installing in Graphical Mode
13
The following table lists the properties that you specify for the PowerCenter database:
Property
Description
Database Type
Type of PowerCenter repository database.
Note: You cannot choose the database type. The default
database is the RulePoint database type. The database
types for the RulePoint repository and the PowerCenter
repository must be same.
PowerCenter read-only User
PowerCenter repository read-only user name.
PowerCenter read-only User Password
Password for the PowerCenter read-only repository user.
PowerCenter Repository User
Account for the PowerCenter repository database.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
Driver Class
JDBC driver class to establish connection to the
PowerCenter repository database. Information in this field
is populated based on the database type.
The information for this field is retrieved from the JDBC
properties file in $RP_HOME.
Connection URL
13.
JDBC connection string to connect to the PowerCenter
repository database. The format for this field gets
populated based on the database type. You must correct
the string for the correct host name, port number, and the
database name.
Click Next.
The PowerCenter Services Configuration window appears.
14.
Enter the required credentials.
The following table lists the properties that you specify for the PowerCenter user parameters:
Property
Description
PowerCenter Domain Name
Domain name of the PowerCenter repository.
You can get the information in the Domain Navigator panel
of Informatica Administrator.
PowerCenter Repository Service Name
Service name of PowerCenter repository.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
15.
Click Next.
16.
Review the pre-installation summary, and click Install.
After the installation is complete, the Install Complete window appears.
17.
14
Click Done to complete the installation procedure and then exit the installer.
Chapter 4: First Time Installation
Installing in Console Mode
You can install Proactive Monitoring for PowerCenter Governance in console mode on Windows, Linux, or AIX.
Note: When you run the installer in console mode, the words Quit and Back are reserved words. You cannot use
the reserved words as input text during installation.
1.
At the command prompt for Windows or on a shell command line for Linux and AIX, run the Proactive
Monitoring for PowerCenter Governance installer located in the root directory.
2.
Enter the Proactive Monitoring for PowerCenter Governance executable name with the option -i console.
¨ For Windows, enter Informatica_PMPC_Governance_2.0.exe -i console.
¨ For Linux or AIX, enter Informatica_PMPC_Governance_2.0.bin -i console.
3.
In the Introduction window, press Enter.
The Choose Staging Folder window appears.
4.
Specify the staging directory in which to configure the Proactive Monitoring for PowerCenter Governance
solution.
The following table shows the default location of the staging folder:
5.
Operating System
File Path
Windows
C:\PMPC_Governance_2.0
Linux and AIX
/home/PMPC_Governance_2.0
Enter Y to confirm the staging directory path.
The RulePoint Deployment Directory window appears.
6.
Enter the path to $RP_HOME.
For example, enter the following path of the RulePoint deployment directory in webapps directory of Apache
Tomcat 6 application server:
$CATALINA_HOME\webapps\rulepoint
The Installation Type window appears.
7.
Verify the installation type.
8.
Press Enter.
The Prerequisites window appears.
9.
Verify the installation requirements, and press Enter.
The RulePoint Database Configuration for Proactive Monitoring window appears.
10.
Enter the RulePoint database user name and database password.
Inputs for the fields Driver Class and Connection URL are taken from $RP_HOME. Wait till the installer
verifies the input details.
Note: If you continue the installation after the connection fails, the installer does not create objects that are
required for monitoring.
11.
Press Enter.
The PowerCenter Database Configuration window appears.
12.
Enter the PowerCenter database details.
Installing in Console Mode
15
The following table lists the properties that you specify for the PowerCenter database:
Property
Description
Database Type
Type of PowerCenter repository database.
Note: You cannot choose the database type. The default
database is the RulePoint database type. The database
types for the RulePoint repository and the PowerCenter
repository must be same.
PowerCenter read-only User
PowerCenter repository read-only user name.
PowerCenter read-only User Password
Password for the PowerCenter read-only repository user.
PowerCenter Repository User
Account for the PowerCenter repository database.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
Driver Class
JDBC driver class to establish connection to the
PowerCenter repository database. Information in this field
is populated based on the database type.
The information for this field is retrieved from the JDBC
properties file in $RP_HOME.
Connection URL
13.
JDBC connection string to connect to the PowerCenter
repository database. The format for this field gets
populated based on the database type. You must correct
the string for the correct host name, port number, and the
database name.
Press Enter.
The PowerCenter Services Configuration window appears.
14.
Enter the required credentials.
The following table lists the properties that you specify for the PowerCenter user parameters:
Property
Description
PowerCenter Domain Name
Domain name of the PowerCenter repository.
You can get the information in the Domain Navigator panel
of Informatica Administrator.
PowerCenter Repository Service Name
Service name of PowerCenter repository.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
15.
Press Enter.
16.
Review the installation summary, and then press Enter.
After the installation is complete, the Install Complete window appears.
17.
16
Press Enter to complete the installation and exit the installer.
Chapter 4: First Time Installation
After You Install
After installation, configure the environment for the new installation. Perform the post-installation tasks to ensure
that the services for Proactive Monitoring for PowerCenter Governance run properly.
Complete the following tasks:
¨ Restart RulePoint.
¨ Create users and groups in RulePoint.
¨ Configure alerts.
¨ Start services and enable schedules.
¨ Validate the installation.
Restart RulePoint
Restart Apache Tomcat application server instance where RulePoint and Real-Time Alert Manager are deployed.
Restarting the Tomcat application server instance restarts RulePoint and Real-Time Alert Manager.
1.
After you restart the Tomcat application server, log in to RulePoint to ensure that the solution is correctly
installed.
Launch a web browser and enter the following URL:
http://HostName:port_number/rulepoint
HostName is the host name or IP address of the server where RulePoint is installed. The port_number is the
HTTP port number of the Tomcat server. The default port number is 8080.
The default user name and password is admin/admin.
2.
Log in to Real-Time Alert Manager to ensure that the solution is correctly installed.
Launch a web browser and enter the following URL:
http://HostName:port_number/rtam
HostName is the host name or IP address of the server where Real-Time Alert Manager is installed. The
port_number is the HTTP port number of the Tomcat server. The default port number is 8080.
The default user name and password is admin/admin.
Create Users and Groups in RulePoint
Create users and groups in RulePoint based on the authentication mechanism.
You can create either LDAP or database users using the scripts provided in the release package. Run the scripts
to create the users, pcuser, pcmonitor, pcadmin, apparchitect, dataarchitect, and itsecurity.
1.
Create the users and add them to the LDAP groups, rulepoint_users and rulepoint_admins.
a.
Create the LDAP users.
The installation package contains the sample ldif scripts. Refer to the sample scripts to create the LDAP
user authentication for proactive monitoring based on the organizational structure. An ldif file contains
all the attributes for an user. Run the ldif file from the LDAP server machine.
Refer the following ldif scripts when you create the users or personas:
¨ pcuser. exports\ldap\pcuser.ldif
After You Install
17
¨ pcmonitor. exports\ldap\pcmonitor.ldif
¨ pcadmin. exports\ldap\pcadmin.ldif
¨ apparchitect. exports\ldap\apparchitect.ldif
¨ dataarchitect. exports\ldap\dataarchitect.ldif
¨ itsecurity. exports\ldap\itsecurity.ldif
b.
Add the users to the following LDAP groups:
¨ rulepoint_users. pcuser, pcmonitor, pcadmin, apparchitect, dataarchitect, and itsecurity
¨ rulepoint_admins. pcuser
2.
Create database users.
a.
To create database users, add users from the RulePoint administration menu.
b.
Login to RulePoint as admin.
c.
Add users pcuser, pcmonitor, pcadmin, apparchitect, dataarchitect, and itsecurity.
Role is ROLE_USER for each database user.
d.
3.
Make pcuser an administrator. The administrator owns all imported objects in RulePoint.
For Microsoft SQL Server, grant execute permission to the RulePoint user.
Grant execute permission to the RulePoint user, pc_rp, for the following functions and procedure:
¨ pc_get_email
¨ pc_get_rtam
¨ pc_alert_recorder
Detailed instructions on how to grant permissions to pc_rp are available in the create_rp_user.txt file in the
following directory of the installer:
..\resources\dbscripts\rulepoint\sqlserver
Configure Alerts
Configure the users or personas to receive alerts through email, Real-Time Alert Manager, or both.
1.
Configure Real-Time Alert Manager to receive alerts for the users.
After creating the users, either LDAP or database option, log in to Real-Time Alert Manager with each of the
six user IDs. You log in with the IDs to configure Real-Time Alert Manager to receive alerts for each of the
users. By default, the Real-Time Alert Manager IDs receives the alerts.
2.
Configure the alert recipients for personas.
a.
Use the alert recipient tool, art.bat in Windows or art.sh in Linux or AIX to configure delivery of alerts to
personas.
You can configure to deliver the alerts through email or RTAM IDs.
b.
Use the following command to add or change the alert recipients:
art.bat -u <db_username> -p <db_password> -a -d "Domain_name" -r "Repository_Service" -pe
"persona" -m "rtam_list" -e "email_list"
Here, db_username and db_password refers to the RulePoint database user and database password.
18
Chapter 4: First Time Installation
Grant Permissions to PowerCenter Read-Only User
For Microsoft SQL Server, grant execute permissions on the functions, TO_DATE_MMDDYYYYHHMI and
TO_DATE_MMDDYYYYHHMISS to the PowerCenter read-only user, pcrs_readonly.
Detailed instructions on how to grant permissions to pcrs_readonly are available in the create_pc_user.txt file in
the following directory of the installer:
..\resources\dbscripts\powercenter\sqlserver
Start Services and Enable Schedules
Start all the interval based SQL source services, and enable the schedules for all the other services.
1.
Log in to RulePoint.
2.
Start all the interval based source services for Proactive Monitoring for PowerCenter Governance.
a.
Go to Services > Show Services.
b.
Click the particular interval based source services.
c.
Go to View Service.
d.
Click Start to start the service.
For example, PowerCenter Sessions Modified Incremental is an interval based SQL source service. This
service connects to the PowerCenter repository and the status is active by default. The recommended
schedule frequency for this service is 21600 seconds.
3.
Enable the schedules for all other source services.
a.
Go to Services > Show Services.
b.
Click the particular SQL source services.
c.
Go to schedules for PowerCenter Daily Alert History Purge Requestor > Status.
d.
Change the Status to active.
Validate the Installation
After you complete installation, verify the installation to ensure that the installation is successful.
1.
Log in to RulePoint.
2.
Start all the interval based source services for Proactive Monitoring for PowerCenter Governance.
3.
Enable the schedules for all other source services.
4.
Review the global setting parameters.
Run the following command in the gst.bat or gst.sh to list the attribute settings:
gst.bat -u <db_username> -p <db_password> -l
db_username and db_password refers to the RulePoint repository database user and repository password.
5.
Check the frequency of the schedules.
The frequency of the schedules must not be too high or not too low. Schedules with too high or too low
frequency impact the alerting system.
6.
After you enable and configure the services, you can see that the events are generated. This verifies that the
installation is successful.
After You Install
19
Configuring RulePoint Components
After installation, configure the RulePoint components to work with the rules and services of Proactive Monitoring
for PowerCenter Governance.
1.
Determine the frequency of source services, and update the service schedulers accordingly.
The alerting frequency of the sources must not be too high nor too low. Each service can have different
schedule based on the requirements.
Note: By default, schedules of all source services are disabled. Activate the schedules of all the source
services manually to start monitoring the PowerCenter instances.
You can use the Interval Based SQL source service to connect to a database and run SQL queries or
commands to create RulePoint events. This service waits for a configured period after the previous task has
completed before running again. You can configure the time interval to wait between the executions.
2.
Edit Watchlists.
a.
Go to Watchlists > Show Watchlists.
b.
Click the watchlist you want to edit.
c.
In View Watchlist: <watchlist name> tab, click Edit.
d.
Enter the change content and same the changes.
Watchlists contain items that you store as a single object with a unique name that you define. You can
reference this name in a rule so that it can use the data stored in the object. Watchlist of the monitored folders
are case sensitive. Watchlists are useful because you can change the items within the watchlist at any time,
and any rule referencing that watchlist automatically uses those new items. Start modifying a small watchlist,
and progressively add to it after you have a good understanding of the solution and the various configuration
options.
For example, for the PowerCenter Monitored Folders watchlist, you can replace the entries with the list of
folders in the repository that you want to monitor.
3.
Configure email host.
In Rulepoint, edit the PowerCenter Email Responder service to add information about the email host server
and its authentication credentials of the organization.
4.
a.
Go to Services > Show Services.
b.
In the Services tab, select Class as Responders and Type as Email.
c.
Click PowerCenter Email Responder service.
d.
In View Service: PowerCenter Email Responder tab, click Edit.
e.
Enter the required details for the email service and save the changes.
Configure Real-Time Alert Manager responder service.
a.
Go to Services > Show Services.
b.
In the Services tab, select Class as Responders and Type as RTAM.
c.
Click RTAM service.
d.
In View Service: RTAM tab, click Edit.
e.
Edit the Connection URL field, tcp://localhost:[port] with the port number configured for Real-Time
Alert Manager.
This value is available in $CATALINA_HOME\webapps\RTAM\WEB-INF\classes\activemq.xml file. Information in
the amq:transportConnector tag is the input for this field.
f.
20
Enter the required details for the responder service and save the changes.
Chapter 4: First Time Installation
Configuring Default Notification
Every template and advanced rule in proactive monitoring solution that is responsible for sending alerts uses a
single response, PowerCenter Notification Response. The predefined response uses Real-Time Alert Manager
alerts as the default delivery mechanism.
1.
Use the Global setting Tool, gst.bat in Windows or gst.sh in Linux or AIX, to change the default response
delivery method.
During installation, the notification settings are set to the following default values:
¨ do_not_disturb. 'N'
¨ default_notification. 'RTAM'
¨ alert_history_purge_freq_days. '60'
¨ alert_hyperlink. 'https://community.informatica.com/solutions/1514'
Use the following command to add or change the attribute settings:
gst.bat -u <db_username> -p <db_password> -a do_not_disturb=N, default_notification=Email
Here, db_username and db_password refers to the RulePoint database user and database password.
2.
Configure the default response delivery method for each rule or template by editing the delivery=default
clause with one of the following alternatives:
¨ delivery="RTAM". Forces notifications to go to Real-Time Alert Manager.
¨ delivery="Email". Forces notifications to go to email.
¨ delivery="RTAM&Email". Forces notifications to go to Real-Time Alert Manager and email.
The proactive monitoring solution has two predefined rules that govern the delivery of alerts. The WITH
clause in the following rules govern the delivery behavior:
¨ PowerCenter RTAM Notification Advanced (delivery = "RTAM" OR delivery = "RTAM&Email" OR delivery =
"default")
¨ PowerCenter Email Notification Advanced (delivery = "Email" OR delivery = "RTAM&Email")
With the preceding configuration, the default behavior for ALL rules is to send notification to Real-Time Alert
Manager. Rules that override the default behavior with default="Email" or default="RTAM&Email" send alerts
to email.
To change the default behavior to send email, you can change the above two rules as follows:
¨ PowerCenter RTAM Notification Advanced (delivery = "RTAM" OR delivery = "RTAM&Email" )
¨ PowerCenter Email Notification Advanced (delivery = "Email" OR delivery = "RTAM&Email" OR delivery =
"default")
To change the default behavior to send Real-Time Alert Manager and email, you can change the above two
rules as follows:
¨ PowerCenter RTAM Notification Advanced (delivery = "RTAM" OR delivery = "RTAM&Email" OR delivery =
"default")
¨ PowerCenter Email Notification Advanced (delivery = "Email" OR delivery = "RTAM&Email" OR delivery =
"default")
3.
To override the default behavior for a particular advanced rule or template, use the global setting tool to
replace the delivery=default clause in that rule or template with one of the other choices, RTAM, Email, or
RTAM&Email.
4.
Configure notification hyperlink.
Use the global setting tool to change the default settings of the hyperlink. The alert hyperlink set by default is
https://community.informatica.com/solutions/1514.
Configuring Default Notification
21
5.
Configure snooze time to suppress repeat alerts.
The snooze property specifies the interval, in minutes, that must elapse between successive alerts of the
same running exception. The proactive monitoring solution is configured to send one alert for every exception.
Based on the specification of the frequency of the sources that feed these alerts, the triggering action repeats
if the exception is outstanding.
To space out the alerts from the same exception, configure the snooze property in the PowerCenter
Notification Response service. The default value is 60 minutes.
Troubleshooting RulePoint Service Errors
After installation, RulePoint services are disabled due to errors in the database connection parameters, or due to permissions
and privileges that are not valid for the database user.
1.
Launch RulePoint.
2.
Navigate to the Services List.
3.
Filter by Disabled Services.
4.
Navigate to the service details and verify that the database connection parameters are correct.
5.
Click Run Once and ensure the service runs without errors.
To view errors, check the Last Errors tab.
Troubleshooting Real-Time Alert Manager to Receive
Alerts
Alerts do not show up in the Real-Time Alert Manager dashboard even when you start all the services after installation.
22
1.
Ensure that you created the personas or users required by Proactive Monitoring for PowerCenter
Governance, such as pcuser, pcmonitor, dataarchitect, pcadmin, apparchitect, and itsecurity.
2.
Log in to Real-Time Alert Manager with these user IDs.
3.
Check the contents of the ALERT_RECIPIENTS_TABLE for the correct details of PowerCenter domain,
PowerCenter repository service, personas, email, and Real-Time Alert Manager users.
4.
Check the Global_settings table for pc_rp. Ensure that the default entries for Real-Time Alert Manager
are available.
5.
Activate the rules correctly.
6.
Ensure that all responders are active. System errors disables the rules and responders.
7.
Check the pc_notification events created under the Events tab in RulePoint.
8.
Ensure that all the services are running.
9.
For SQL Sources, ensure that the schedules are active.
10.
Review the rulepoint.log file and resolve any exceptions.
Chapter 4: First Time Installation
CHAPTER 5
Custom Installation
This chapter includes the following topics:
¨ Custom Installation Overview, 23
¨ Before You Install, 23
¨ Installing in Graphical Mode, 24
¨ Installing in Console Mode, 26
¨ After You Install, 28
¨ Troubleshooting Custom Installation, 29
Custom Installation Overview
You can use the custom install option to repair a previous install of Proactive Monitoring for PowerCenter
Governance.
Choose the custom install option to correct the errors occurred during the previous install of proactive monitoring.
For example, if you created an incorrect pcrs_readonly user, you must correct the user name and the password,
and regenerate the solution XML files. After you complete the custom install, run the importcli utility to import the
generated XML files to RulePoint.
You can select one or more custom installation options.
Before You Install
Before you install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring
for PowerCenter Governance 2.0, shut down the instance of Apache Tomcat application server where RulePoint is
deployed.
23
Installing in Graphical Mode
You can use the custom install option to repair an existing install of Proactive Monitoring for PowerCenter
Governance. You can run the installer in graphical mode on Windows, Linux, or AIX.
1.
Run the Proactive Monitoring for PowerCenter Governance installer based on the operating system.
¨ To install on Windows, run Informatica_PMPC_Governance_2.0.exe from the root directory.
¨ To install on Linux or AIX, use a shell command line to run Informatica_PMPC_Governance_2.0.bin from the
root directory with -i gui option for graphical mode installation. For example, enter
Informatica_PMPC_Governance_2.0.bin -i gui
2.
In the Introduction window, click Next.
The Choose Staging Folder window appears.
3.
Specify the staging directory in which to configure the Proactive Monitoring for PowerCenter Governance
solution.
The following table shows the default location of the staging folder:
4.
Operating System
File Path
Windows
C:\PMPC_Governance_2.0
Linux and AIX
/home/PMPC_Governance_2.0
Click Next.
The RulePoint Deployment Directory window appears.
5.
Enter the path to $RP_HOME.
For example, enter the following path of the RulePoint deployment directory in webapps directory of Apache
Tomcat 6 application server:
$CATALINA_HOME\webapps\rulepoint
6.
Click Next.
The Installation Type window appears.
7.
Select the custom installation option to install and configure the required components.
The following table shows the custom installation options:
24
Option
Description
Configure PowerCenter
repository
Choose this option when you want to get the PowerCenter repository details, update
the PowerCenter database properties, and validate them by connecting to the
database.
Configure Proactive Monitoring
Repository
Choose this option when you want to get the RulePoint database details, update the
database properties, and validate them by connecting to the database.
Configure Proactive Monitoring
Solution XML
Choose this option when you want to create the XML files for RulePoint. The XML
files are common.xml, govCommon.xml, and governance.xml.
Install Proactive Monitoring Tools
Choose this option when you want to install the command line utilities, Global Setting
Tool and Alert Recipient Tool.
Chapter 5: Custom Installation
Note: You can select one or more custom installation options.
8.
Verify the installation requirements, and click Next.
The RulePoint Database Configuration for Proactive Monitoring window appears.
9.
Enter the RulePoint database user name and database password, and click Test Connection.
To proceed to the next step, you must verify the connection details.
Inputs for the fields Driver Class and Connection URL are taken from $RP_HOME.
Note: If you continue the installation after the connection fails, the installer does not create objects that are
required for monitoring.
10.
Click Next.
The PowerCenter Database Configuration window appears.
11.
Enter the PowerCenter database details.
The following table lists the properties that you specify for the PowerCenter database:
Property
Description
Database Type
Type of PowerCenter repository database.
Note: You cannot choose the database type. The default
database is the RulePoint database type. The database
types for the RulePoint repository and the PowerCenter
repository must be same.
PowerCenter read-only User
PowerCenter repository read-only user name.
PowerCenter read-only User Password
Password for the PowerCenter read-only repository user.
PowerCenter Repository User
Account for the PowerCenter repository database.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
Driver Class
JDBC driver class to establish connection to the
PowerCenter repository database. Information in this field
is populated based on the database type.
The information for this field is retrieved from the JDBC
properties file in $RP_HOME.
Connection URL
12.
JDBC connection string to connect to the PowerCenter
repository database. The format for this field gets
populated based on the database type. You must correct
the string for the correct host name, port number, and the
database name.
Click Next.
The PowerCenter Services Configuration window appears.
13.
Enter the required credentials.
The following table lists the properties that you specify for the PowerCenter user parameters:
Property
Description
PowerCenter Domain Name
Domain name of the PowerCenter repository.
Installing in Graphical Mode
25
Property
Description
You can get the information in the Domain Navigator panel
of Informatica Administrator.
PowerCenter Repository Service Name
Service name of PowerCenter repository.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
14.
Click Next.
15.
Review the pre-installation summary, and click Install.
After the installation is complete, the Install Complete window appears.
16.
Click Done to complete the installation procedure and then exit the installer.
Installing in Console Mode
You can use the custom install option to repair an existing install of Proactive Monitoring for PowerCenter
Operations. You can run the installer in console mode on Windows, Linux, or AIX.
Note: When you run the installer in console mode, the words Quit and Back are reserved words. You cannot use
the reserved words as input text during installation.
1.
At the command prompt for Windows or on a shell command line for Linux and AIX, run the Proactive
Monitoring for PowerCenter Governance installer located in the root directory.
2.
Enter the Proactive Monitoring for PowerCenter Governance executable name with the option -i console.
¨ For Windows, enter Informatica_PMPC_Governance_2.0.exe -i console.
¨ For Linux or AIX, enter Informatica_PMPC_Governance_2.0.bin -i console.
3.
In the Introduction window, press Enter.
The Choose Staging Folder window appears.
4.
Specify the staging directory in which to configure the Proactive Monitoring for PowerCenter Governance
solution.
The following table shows the default location of the staging folder:
5.
Operating System
File Path
Windows
C:\PMPC_Governance_2.0
Linux and AIX
/home/PMPC_Governance_2.0
Enter Y to confirm the staging directory path.
The RulePoint Deployment Directory window appears.
6.
Enter the path to $RP_HOME.
For example, enter the following path of the RulePoint deployment directory in webapps directory of Apache
Tomcat 6 application server:
$CATALINA_HOME\webapps\rulepoint
26
Chapter 5: Custom Installation
The Installation Type window appears.
7.
Select a custom installation option to install and configure the required components.
The following table shows the custom installation options:
Option
Description
1 - Configure Proactive Monitoring
Repository
Choose this option when you want to get the RulePoint database details, update
the database properties, and validate them by connecting to the database.
2 - Configure PowerCenter repository
Choose this option when you want to get the PowerCenter repository details,
update the PowerCenter database properties, and validate them by connecting to
the database.
3 - Configure Proactive Monitoring
Solution XML
Choose this option when you want to create the XML files for RulePoint. The
XML files are common.xml, govCommon.xml, and governance.xml.
4 - Install Proactive Monitoring Tools
Choose this option when you want to install the command line utilities, Global
Setting Tool and Alert Recipient Tool.
Note: You can select one or more custom installation options.
8.
Verify the installation requirements, and press Enter.
The RulePoint Database Configuration for Proactive Monitoring window appears.
9.
Enter the RulePoint database user name and database password.
Inputs for the fields Driver Class and Connection URL are taken from $RP_HOME. Wait till the installer
verifies the input details.
Note: If you continue the installation after the connection fails, the installer does not create objects that are
required for monitoring.
10.
Press Enter.
The PowerCenter Database Configuration window appears.
11.
Enter the PowerCenter database details.
The following table lists the properties that you specify for the PowerCenter database:
Property
Description
Database Type
Type of PowerCenter repository database.
Note: You cannot choose the database type. The default
database is the RulePoint database type. The database
types for the RulePoint repository and the PowerCenter
repository must be same.
PowerCenter read-only User
PowerCenter repository read-only user name.
PowerCenter read-only User Password
Password for the PowerCenter read-only repository user.
PowerCenter Repository User
Account for the PowerCenter repository database.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
Driver Class
JDBC driver class to establish connection to the
PowerCenter repository database. Information in this field
is populated based on the database type.
Installing in Console Mode
27
Property
Description
The information for this field is retrieved from the JDBC
properties file in $RP_HOME.
Connection URL
12.
JDBC connection string to connect to the PowerCenter
repository database. The format for this field gets
populated based on the database type. You must correct
the string for the correct host name, port number, and the
database name.
Press Enter.
The PowerCenter Services Configuration window appears.
13.
Enter the required credentials.
The following table lists the properties that you specify for the PowerCenter user parameters:
Property
Description
PowerCenter Domain Name
Domain name of the PowerCenter repository.
You can get the information in the Domain Navigator panel
of Informatica Administrator.
PowerCenter Repository Service Name
Service name of PowerCenter repository.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
14.
Press Enter.
15.
Review the pre-installation summary, and then press Enter.
After the installation is complete, the Install Complete window appears.
16.
Press Enter to complete the installation and exit the installer.
After You Install
After you install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring for
PowerCenter Governance 2.0, configure the environment for the new installation. Perform the post-installation
tasks to ensure that the services for Proactive Monitoring for PowerCenter Governance run properly.
1.
Restart the Apache Tomcat instance where RulePoint is deployed.
Restarting Apache Tomcat starts RulePoint and Real-Time Alert Manager.
2.
Import the XML files for the solution.
3.
Start all RulePoint services, and enable the schedules for SQL source services.
Import the XML Files for the Solution
You get the custom installation options when you install Proactive Monitoring for PowerCenter Governance 2.0 on
an instance of Proactive Monitoring for PowerCenter Governance 2.0. If you performed the custom install to
28
Chapter 5: Custom Installation
Configure Proactive Monitoring Solution XML, import the XML files to RulePoint. You need the XML files to import
the custom services of Proactive Monitoring for PowerCenter Governance sources to RulePoint.
The XML files are common.xml, govCommon.xml, and governance.xml. You can find the XML files in the $RP_HOME
\Solutions\PCPM\bin\Governance_2.0 directory after installation.
Run the importcli utility to import the XML files to RulePoint.
You can also manually import the XML files to RulePoint. Manual import of the XML files affect the topic tree
structure. When you install Proactive Monitoring for PowerCenter Governance, the topics are organized into
directories. Manual import of the XML files flatten the topic tree structure, that is, all the topics are grouped under
the main topic. The required directory structure is not maintained.
Import XML Files Using importcli Utility
Use the importcli.bat or importcli.sh utility to import the XML files to RulePoint. You can find the importcli utility
in the $RP_HOME\Solutions\PCPM\tools\importcli directory after installation.
1.
At the command prompt for Windows or on a shell command line for Linux and AIX, run the following
command before you run the importcli utility:
Cd $RP_HOME\Solutions\PCPM\tools\importcli
2.
Run the importcli utility.
importcli ..\..\bin\Governance_2.0\common.xml,..\..\bin\Governance_2.0\govCommon.xml,..\..
\Governance_2.0\governance.xml
The sequence to enter the file names is common.xml, govCommon.xml, governance.xml.
Import the XML Files Manually
You can manually import the XML files into RulePoint.
1.
Log in to RulePoint using the administrator credentials.
2.
Click Administration > Import > Upload File.
3.
Browse to the location of the XML files.
4.
Enter the name of the XML files separated by comma.
The sequence to enter the file names is common.xml, govCommon.xml, governance.xml.
5.
Click Upload.
6.
Select the uploaded files.
7.
Click Start Import.
8.
Select overwrite option if there is a collision, and click Import.
9.
After importing the XML files, restart RulePoint.
Note: You can see the import status of the file in the Import History window.
Troubleshooting Custom Installation
Common installation errors and their solution is described here. Use the custom install option to fix errors that
might have occurred during the previous install process using the complete install option. You do not have to
perform a complete install again.
Troubleshooting Custom Installation
29
Troubleshooting PowerCenter Connection
During complete installation, if you ignore the test connection failure in the PowerCenter Database Configuration window, the
synonyms required to connect to the PowerCenter objects are not created. After installation, connection to PowerCenter fails
though the proactive monitoring objects such as rules, services, and other objects are successfully created. You can see
privilege errors during run time, for example, while activating the rules.
Use the following procedure to correct the error:
1.
Run the installer.
2.
When asked for a staging folder, enter a new folder name.
3.
In the Installation Type window, select the options, Configure PowerCenter Repository and Configure
Proactive Monitoring Solution XML.
4.
In the PowerCenter Database Configuration window, enter correct information for the PowerCenter
database.
5.
Ensure that the Test Connection operation is successful.
6.
Ensure that the PowerCenter repository user is same as the PowerCenter read-only user name.
The required privileges and synonyms to connect to the PowerCenter database are created.
7.
Complete the install.
The updated XML files, common.xml, govCommon.xml, and governance.xml with the correct
pcrs_readonly user is created in the directory, $RP_HOME\Solutions\PCPM\bin\Governance_2.0.
8.
Run the importcli utility to import the XML files to RulePoint with the right sequence of the XML files. The
correct sequence to enter the XML files is, common.xml, govCommon.xml, and governance.xml.
Importing the correct XML files corrects the objects that used incorrect user name and incorrect
password from the first install.
Troubleshooting PowerCenter Services Configuration
The Proactive Monitoring for PowerCenter Governance installer does not validate the PowerCenter services configuration details
provided during installation. After the install, the rules and services fail because they point to invalid PowerCenter domain or
PowerCenter repository service, though proactive monitoring objects are created successfully. In addition, the alert recipients
are populated with the default values for PowerCenter, such as the domain, repository service.
Use the following procedure to recover from the error:
30
1.
Run the installer.
2.
When asked for a staging folder, enter a new folder name.
3.
In the Installation Type window, select Configure Proactive Monitoring Solution XML.
4.
In the PowerCenter Services Configuration window, enter correct information for the PowerCenter
services.
5.
Ensure to provide correct information for pcrs_readonly and the pc_rp user configuration.
6.
Complete the install.
The updated XML files, common.xml, govCommon.xml, and governance.xml with the correct
pcrs_readonly user is created in the directory, $RP_HOME\Solutions\PCPM\bin\Governance_2.0.
7.
Run the importcli utility to import the XML files to RulePoint with the right sequence of the XML files. The
correct sequence to enter the XML files is, common.xml, govCommon.xml, and governance.xml.
Importing the correct XML files corrects the objects that used incorrect user name and incorrect
password from the first install.
8.
Use the ART tool and update the PowerCenter details.
Chapter 5: Custom Installation
Troubleshooting RulePoint Source Connection
During complete installation, if you ignore the test connection failure in the RulePoint Database Configuration for Proactive
Monitoring window, the objects required for monitoring are not created in RulePoint. After installation, the alerts and global
setting related objects are not created though the proactive monitoring objects, such as rules, services, and other objects are
created successfully. You do not receive alerts although the rules are activated at run time.
Use the following procedure to correct the error:
1.
Run the installer
2.
When asked for a staging folder, enter a new folder name.
3.
In the Installation Type window, select the options, Configure Proactive Monitoring Repository and
Configure Proactive Monitoring Solution XML.
4.
In the RulePoint Database Configuration for Proactive Monitoring window, enter correct information
for the RulePoint user.
This creates the objects required for monitoring.
5.
Ensure that the Test Connection operation is successful.
6.
Complete the install.
The updated XML files, common.xml, govCommon.xml, and governance.xml with the correct
pcrs_readonly user is created in the directory, $RP_HOME\Solutions\PCPM\bin\Governance_2.0.
7.
Run the importcli utility to import the XML files to RulePoint with the right sequence of the XML files. The
correct sequence to enter the XML files is, common.xml, govCommon.xml, and governance.xml.
Importing the correct XML files corrects the objects that used incorrect user name and incorrect
password from the first install.
Troubleshooting Errors While Importing the XML Files
You will see errors if the XML files, common.xml, govCommon.xml, and governance.xml, are imported twice. This is due to a
limitation in RulePoint. The XML files are validated on the second import.
The error occurs if the connection parameters for SQL Services are not valid.
1.
Run the installer.
2.
When asked for a staging folder, enter a new folder name.
3.
In the Installation Type window, select the options, Configure PowerCenter Repository and Configure
Proactive Monitoring Solution XML.
4.
Enter correct values for all the fields.
5.
Complete the install.
The updated XML files, common.xml, govCommon.xml, and governance.xml with the correct
pcrs_readonly user is created in the directory, $RP_HOME\Solutions\PCPM\bin\Governance_2.0.
6.
Run the importcli utility to import the XML files to RulePoint with the right sequence of the XML files. The
correct sequence to enter the XML files is, common.xml, govCommon.xml, and governance.xml.
Importing the correct XML files corrects the objects that used incorrect user name and incorrect
password from the first install.
7.
After the import, go to the Services List.
8.
Enter valid connection parameters for the required services.
9.
Save the services.
Troubleshooting Custom Installation
31
Restore Deleted Tools to the Staging Folder
Restore deleted tools to the staging folder
32
1.
Run the installer.
2.
When asked for a staging folder, enter a new folder name.
3.
In the Installation Type window, select Install Proactive Monitoring Tools.
4.
Complete the install.
Chapter 5: Custom Installation
CHAPTER 6
Overlay Installation
This chapter includes the following topics:
¨ Overlay Installation Overview, 33
¨ Before You Install, 33
¨ Installing in Graphical Mode, 34
¨ Installing in Console Mode, 35
¨ After You Install, 36
Overlay Installation Overview
You can install Proactive Monitoring for PowerCenter Governance 2.0 on Proactive Monitoring for PowerCenter
Operations 2.0, 2.0 HotFix 1, or 2.1. You can run the installer in graphical or console mode on Windows, Linux, or
AIX. Complete the pre-installation tasks to prepare for the overlay installation.
You can perform the overlay installation of Proactive Monitoring for PowerCenter Governance 2.0 from a DVD or
from the root of the directory where you download the installation files. On Linux, 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. The /tmp directory must have sufficient space for the installer to perform the overlay installation.
When you install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring for
PowerCenter Operations 2.0, 2.0 HotFix 1, or 2.1, you might see some of the old best practices rules and
templates in RulePoint. Use the cleanup utility of the Global Setting Tool to remove the old rules and templates.
Before You Install
Before you install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring
for PowerCenter Operations 2.0, 2.0 HotFix 1, or 2.1, shut down the instance of Apache Tomcat application server
where RulePoint is deployed.
33
Installing in Graphical Mode
You can install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring for
PowerCenter Operations 2.0, 2.0 HotFix 1, or 2.1 in graphical mode on Windows, Linux, or AIX.
1.
Run the Proactive Monitoring for PowerCenter Governance installer based on the operating system.
¨ To install on Windows, run Informatica_PMPC_Governance_2.0.exe from the root directory.
¨ To install on Linux or AIX, use a shell command line to run Informatica_PMPC_Governance_2.0.bin from the
root directory with -i gui option for graphical mode installation. For example, enter
Informatica_PMPC_Governance_2.0.bin -i gui
2.
In the Introduction window, click Next.
The Choose Staging Folder window appears.
3.
Specify the staging directory in which to configure the Proactive Monitoring for PowerCenter Governance
solution.
The following table shows the default location of the staging folder:
4.
Operating System
File Path
Windows
C:\PMPC_Governance_2.0
Linux and AIX
/home/PMPC_Governance_2.0
Click Next.
The RulePoint Deployment Directory window appears.
5.
Enter the path to $RP_HOME.
For example, enter the following path of the RulePoint deployment directory in webapps directory of Apache
Tomcat 6 application server:
$CATALINA_HOME\webapps\rulepoint
6.
Click Next.
The Installation Type window appears.
7.
Verify the installation requirements, and click Next.
The RulePoint Database Configuration for Proactive Monitoring window appears.
8.
Enter the RulePoint database user name and database password, and click Test Connection.
To proceed to the next step, you must verify the connection details.
Inputs for the fields Driver Class and Connection URL are taken from $RP_HOME.
Note: If you continue the installation after the connection fails, the installer does not create objects that are
required for monitoring.
9.
Click Next.
The PowerCenter Database Configuration window appears.
10.
Enter the password for the PowerCenter read-only user, and click Test Connection.
To proceed to the next step, you must verify the connection details.
11.
Click Next.
The PowerCenter Services Configuration window appears.
34
Chapter 6: Overlay Installation
12.
Enter the required credentials.
The following table lists the properties that you specify for the PowerCenter user parameters:
Property
Description
PowerCenter Domain Name
Domain name of the PowerCenter repository.
You can get the information in the Domain Navigator panel
of Informatica Administrator.
PowerCenter Repository Service Name
Service name of PowerCenter repository.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
13.
Click Next.
14.
Review the pre-installation summary, and click Install.
After the installation is complete, the Install Complete window appears.
15.
Click Done to complete the installation procedure and then exit the installer.
Installing in Console Mode
You can install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring for
PowerCenter Operations 2.0, 2.0 HotFix 1, or 2.1 in console mode on Windows, Linux, or AIX.
Note: When you run the installer in console mode, the words Quit and Back are reserved words. You cannot use
the reserved words as input text during installation.
1.
At the command prompt for Windows or on a shell command line for Linux and AIX, run the Proactive
Monitoring for PowerCenter Governance installer located in the root directory.
2.
Enter the Proactive Monitoring for PowerCenter Governance executable name with the option -i console.
¨ For Windows, enter Informatica_PMPC_Governance_2.0.exe -i console.
¨ For Linux or AIX, enter Informatica_PMPC_Governance_2.0.bin -i console.
3.
In the Introduction window, press Enter.
The Choose Staging Folder window appears.
4.
Specify the staging directory in which to configure the Proactive Monitoring for PowerCenter Governance
solution.
The following table shows the default location of the staging folder:
5.
Operating System
File Path
Windows
C:\PMPC_Governance_2.0
Linux and AIX
/home/PMPC_Governance_2.0
Enter Y to confirm the staging directory path.
The RulePoint Deployment Directory window appears.
Installing in Console Mode
35
6.
Enter the path to $RP_HOME.
For example, enter the following path of the RulePoint deployment directory in webapps directory of Apache
Tomcat 6 application server:
$CATALINA_HOME\webapps\rulepoint
The Installation Type window appears.
7.
Verify the installation requirements, and press Enter.
The RulePoint Database Configuration for Proactive Monitoring window appears.
8.
Enter the RulePoint database user name and database password.
Inputs for the fields Driver Class and Connection URL are taken from $RP_HOME. Wait till the installer
verifies the input details.
Note: If you continue the installation after the connection fails, the installer does not create objects that are
required for monitoring.
9.
Press Enter.
The PowerCenter Database Configuration window appears.
10.
Enter the password for the PowerCenter read-only repository user, and wait till the installer verifies the input
details.
11.
Press Enter.
The PowerCenter Services Configuration window appears.
12.
Enter the required credentials.
The following table lists the properties that you specify for the PowerCenter user parameters:
Property
Description
PowerCenter Domain Name
Domain name of the PowerCenter repository.
You can get the information in the Domain Navigator panel
of Informatica Administrator.
PowerCenter Repository Service Name
Service name of PowerCenter repository.
You can get the information in the PowerCenter Repository
Service properties of Informatica Administrator.
13.
Press Enter.
14.
Review the installation summary, and then press Enter.
After the installation is complete, the Install Complete window appears.
15.
Press Enter to complete the installation and exit the installer.
After You Install
After you install Proactive Monitoring for PowerCenter Governance 2.0 on an instance of Proactive Monitoring for
PowerCenter Operations 2.0, 2.0 HotFix 1, or 2.1, configure the environment for the new installation. Perform the
36
Chapter 6: Overlay Installation
post-installation tasks to ensure that the services for Proactive Monitoring for PowerCenter Governance run
properly.
1.
Restart the Apache Tomcat instance where RulePoint is deployed.
Restarting Apache Tomcat starts RulePoint and Real-Time Alert Manager.
2.
Start all RulePoint services, and enable the schedules for SQL source services.
After You Install
37
APPENDIX A
Alert Recipient Tool
Use the Alert Recipient Tool, art.bat in Windows or art.sh in Linux or AIX to change or list the alert recipients. You
can change the values based on the requirements and the persona that need to receive alerts.
On successful installation of Proactive Monitoring for PowerCenter Governance, the art.bat and art.sh files are
available in $RP_HOME\Solutions\PCPM\tools\bin directory.
Before you run the alert recipient tool, run the following command:
cd $RP_HOME\Solutions\PCPM\tools\bin
Run the following command to add or change the alert recipients:
art.bat -u <db_username> -p <db_password> -a -d "Domain_name" -r "Repository_Service" -pe "persona" -m
"rtam_list" -e "email_list"
The following table lists the attributes of the alert recipient tool:
Attribute
Description
Mandatory
-d, -domain
Domain name of the PowerCenter
repository
Yes
-r, -rs
PowerCenter repository service name
Yes
-f, -folder
Directory name
No
-w, -wf_name
Workflow name
No
-pe, -persona
Persona
Yes
-m, -rtam
Real-Time Alert Manager IDs list,
separated by semicolon
Yes
-e, -email
Email IDs list, separated by comma
Yes
Use the following command to list all the contents of the alert recipient tables:
art.bat -u <db_username> -p <db_password> -l
Example
Consider the following properties:
pcinstance domain="Domain_captured from Installer UI" rs = "Repository_Service captured from Installer
UI"
persona name="itsecurity" RTAM="itsecurity;pcmonitor" Email="[email protected]"
persona name="pcadmin" RTAM="pcadmin;pcmonitor" Email="[email protected]"
persona name="apparchitect" RTAM="apparchitect;pcmonitor" Email="[email protected]"
persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" Email="[email protected]"
38
pcinstance domain="Domain_captured from Installer UI" rs = "Repository_Service captured from Installer
UI"
folder= "Proactive Monitoring"
persona name="itsecurity" RTAM="itsecurity;pcmonitor" Email="[email protected]"
persona name="pcadmin" RTAM="pcadmin;pcmonitor" Email="[email protected]"
persona name="apparchitect" RTAM="apparchitect;pcmonitor" Email=" [email protected]"
persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" Email="[email protected]"
pcinstance domain="Domain_captured from Installer UI" rs = "Repository_Service captured from Installer
UI"
folder="Proactive Monitoring" wf_name="wf_m_load_pc_alert_recipients"
persona name="itsecurity" RTAM="itsecurity;pcmonitor" Email="[email protected]"
persona name="pcadmin" RTAM="pcadmin;pcmonitor" Email="[email protected]"
persona name="apparchitect" RTAM="apparchitect;pcmonitor" Email="[email protected]"
persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" Email= "[email protected]"
You can use the alert recipient tool to change the values of the preceding example.
cd $RP_HOME\Solutions\PCPM\tools\bin
art.bat -u <db_username> -p <db_password> -a -d "Domain_VM" -r "Repository_Service" -pe "apparchitect" m "dataarchitect;pcmonitor" -e "[email protected]"
The alert recipient tool performs the following changes to the preceding example:
pcinstance domain="Domain_captured from Installer UI" rs = "Repository_Service captured from Installer
UI"
persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" Email= "[email protected]"
If you specify a directory or a workflow name, you can use the following command to make the required changes:
art.bat -u <db_username> -p <db_password> -a -d "Domain_VM" -r "Repository_Service" -pe "apparchitect" –
w "wf_m_load_pc_alert_recipients" –f "Proactive Monitoring" -m "dataarchitect;pcmonitor" -e
"[email protected]"
The alert recipient tool performs the following changes to the preceding example:
pcinstance domain="Domain_captured from Installer UI" rs = "Repository_Service captured from Installer
UI" folder="Proactive Monitoring"
wf_name="wf_m_load_pc_alert_recipients
persona name="dataarchitect" RTAM="dataarchitect;pcmonitor" Email= "[email protected]"
Note: The Alert Recipient Tool does not work with Microsoft SQL Server when you configure the user using
Windows authentication.
39
APPENDIX B
Global Setting Tool
Use the global setting tool, gst.bat in Windows or gst.sh in Linux or AIX to change the global settings for receiving
alerts and notifications, and to remove RulePoint rules and templates of an older installation. On successful
installation of Proactive Monitoring for PowerCenter Governance, the gst.bat and gst.sh files are available in
$RP_HOME\Solutions\PCPM\tools\bin directory.
Run the following command before you run the global settings tool:
cd $RP_HOME\Solutions\PCPM\tools\bin
When you run the global settings tool, you get the following options:
¨ settings. List or update global settings of Proactive Monitoring for PowerCenter Governance.
¨ cleanup. Remove the RulePoint rules and templates that are obsolete.
Note: The Global Setting Tool does not work with Microsoft SQL Server when you configure the user using
Windows authentication.
Global Settings Tool
Use the settings tool option to list or update global settings of Proactive Monitoring for PowerCenter Governance.
Usage
Use the following command to add or change the attribute settings:
gst.bat settings -u <db_username> -p <db_password> -a do_not_disturb=N, default_notification=Email
Use the following command to list the attribute settings:
gst.bat settings -u <db_username> -p <db_password> -l
Here, db_username and db_password refers to the RulePoint database user and database password.
You can use both add and list options together.
gst.bat settings -a … -l
The following table lists the parameters of the global settings tool:
40
Parameters
Description
Mandatory
-u, -username
Database user name.
Yes
-p, -password
Database password.
Yes
Parameters
Description
Mandatory
-l, -list
List contents of pcpm_settings table.
No
-a, -add
List of name value pairs to add to the
pcpm_settings table, separated by
comma.
No
The following table lists the attributes that you can add or change using the Global Setting Tool option:
Attribute
Default Value
Description
default_notification
RTAM
Default notification method. You can set
it to RTAM, or Email, RTAM&Email, or
RTAM+Email.
By default, all predefined rules have a
setting of default for the delivery
mechanism. This attribute determines
the alerting mode when the delivery
setting is default. If overridden at the
rule level, this setting has no impact.
do_not_disturb
N
Do not disturb settings to temporarily
stop alerts.
For example, set this value to Y if the
monitored PowerCenter instance is
down for maintenance. This prevents
sending out any alert during the
maintenance period. After the
maintenance is over, you can reset it to
N.
alert_hyperlink
https://community.informatica.com/
solutions/1514
Alert hyperlink URL included in every
Real-Time Alert Manager or email alert
sent by Proactive Monitoring for
PowerCenter Governance. You can set
this URL to an intranet web page, email
ID, or a distribution list.
Proactive Monitoring for PowerCenter
Governance includes a default hyperlink
with every notification that points to a
landing page. This landing page
contains information about the
PowerCenter Monitoring project of the
organization with contact information.
You can also specify the hyperlink as a
mail to reference to one or many
contact email addresses. Modify the two
rules that handle notifications,
PowerCenter Email Notification
Advanced and PowerCenter RTAM
Notification Advanced, to point to the
appropriate URL of the landing page.
alert_history_purge_freq_days
60 days
Alert history purge duration specifies
the time to retain alert history.
Global Settings Tool
41
Attribute
Default Value
Description
Proactive Monitoring for PowerCenter
Governance includes tables in the
pc_rp schema that contains the alert
history. These tables grow with time,
and it is a good practice to archive and
purge these tables. This attribute
specifies the time, in days, to retain the
history. All alerts older than this time
are archived and purged.
num_of_workflows_and_sessions_recs
_persisted
5
Use this parameter to set the number of
records to persist in the shadow table.
The actual number of records persisted
is twice the number of the value entered
for this attribute.
For example, if
num_of_workflows_and_sessions_recs
_persisted = 5, then the last 10 records
are retained in the shadow tables of
pc_completed_workfows and
pc_completed_sessions. The remaining
records are copied into the
LP_PC_COMPLETED_SESSIONS and
LP_PC_COMPLETED_WORKFLOWS
tables.
Cleanup Tool
Use the cleanup tool option to remove the RulePoint rules and templates of an old installation of Proactive
Monitoring for PowerCenter Governance. You can use the tool to clean up the best practice rules configured when
you installed Proactive Monitoring for PowerCenter Operations 2.0. You can also use the tool also to clean up the
Proactive Monitoring for PowerCenter Operations 2.0 rules configured after you upgrade to Proactive Monitoring
for PowerCenter Operations 2.1.
In Proactive Monitoring for PowerCenter Governance 2.0, the topics are organized for better differentiation
between the topics of Proactive Monitoring for PowerCenter Operations and Proactive Monitoring for PowerCenter
Governance. The naming convention of all the rules and templates follow a standard naming guideline.
Upgrading Proactive Monitoring for PowerCenter Operations 2.0 to 2.1 creates the rules and templates with the
new names. On the other hand, the rules and templates configured for Proactive Monitoring for PowerCenter
Operations 2.0 install are also available. You can use the cleanup utility to remove the rule and templates with the
old names.
The cleanup utility deletes all the advanced rules, templates, and the associated template rules configured for
Proactive Monitoring for PowerCenter Operations 2.0. The tool, however, does not delete any template rules and
the associated templates that you created for Proactive Monitoring for PowerCenter Operations 2.0.
Important: Ensure to back up the XML files for the full export before you run the cleanup utility. You have to redo
the customizations that you have done for any advanced rule, template, or template rules. Do not change the
standard rules. You can create a new rule or new template rule.
You can get the input XML files for the cleanup utility in the $RP_HOME\Solutions\PCPM\tools\bin directory, one each
for the supported databases. Use the correct XML file based on the database type.
42
Appendix B: Global Setting Tool
After you install Proactive Monitoring for PowerCenter Governance 2.0, use the input_2.0_best_practices.xml to
remove the old best practice rules configured for Proactive Monitoring for PowerCenter Operations 2.0.
Usage
gst.bat cleanup -c <URL> -u admin -p admin -i <file_path> -o <output.xml> -z -dbuser <user_name> dbpass <password>
¨ The –z option deletes the rules and templates. If you do not specify –z, the delete does not occur, but you can
review the output.xml to see if the correct set of rules are selected for delete. Use the –z option to finalize the
delete.
¨ The –o option logs in to the specified output.xml.
The following table lists the parameters of the cleanup tool:
Parameters
Description
Mandatory
-c <url>, -connect <url>
RulePoint connection URL
Yes
-u <username>, -uname <username>
RulePoint user name
Yes
-p <password>, -password <password>
RulePoint password
Yes
-du <username>, -dbuser <username>
RulePoint database user name
Yes
-dp <password>, -dbpass <password>
RulePoint database Password
Yes
-i <input file path>, -input <input file
path>
Path of the input XML file
Yes
-o <output file path>, -output <output
file path>
Path of the output XML file
No
-z, -finalize
Finalize the modifications
Yes
Cleanup Tool
43
APPENDIX C
Predefined Alert Channels
Proactive Monitoring for PowerCenter Governance solution provides the following predefined channels:
¨ Alert History Archives.
¨ Governance
44
APPENDIX D
Predefined Rules
This appendix includes the following topics:
¨ Predefined Rules Overview, 45
¨ Template Rules, 45
¨ Advanced Rules, 48
Predefined Rules Overview
Proactive Monitoring for PowerCenter Governance provides a set of predefined rules that are available by default
upon installation. You can use these rules or create rules using the templates provided for the rules.
Template Rules
You can create rules from the template rules by specifying values based on the requirement.
The following table lists the predefined template rules that are available by default upon installing Proactive
Monitoring for PowerCenter Governance:
Rule Name
Description
Properties
PC_GM5 Mapping name should begin
with m_
Notify if the mapping name does not
begin with m_.
- Topic: pc_mappings
- Analytics: - Source: PowerCenter Mappings
Modified Incremental
- Notification: PowerCenter Notification
Response
PC_GM6 Check if a mapping is
modified 3 times within the last 60
minutes
Notify if a mapping is modified three
times within the last 60 minutes.
- Topic: pc_mappings
- Analytic: - Source: PowerCenter Mappings
Modified Incremental
- Response: PowerCenter Notification
Response
45
46
Rule Name
Description
Properties
PC_GS3 Session name should begin
with s_
Notify if the session name does not
begin with s_.
- Topic: pc_sessions
- Analytics: - Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS8 Check whether rollback of
transaction on error is not set
Notify if a Rollback Transactions on
Error is not set for a session.
- Topic: pc_sessions
- Analytic: pc_get_session_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS9 Check if session is modified 3
times within the last 60 minutes
Notify if the session is modified three
times within the last 60 minutes.
- Topic: pc_sessions
- Analytic: - Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS12 Check whether save session
log for these runs uses the global
variable PMSessionLogCount
Notify if Save session log for these runs
attribute does not use the global
variable $PMSessionLogCount.
- Topic: pc_sessions
- Analytics: pc_get_session_attrib
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS13 Check whether stop on
errors uses the global variable
PMSessionErrorThreshold
Notify if Stop on errors attribute does
not use the global variable
$PMSessionErrorThreshold.
- Topic: pc_workflows
- Analytics: pc_get_session_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS14 Check whether write
backward compatible session log file is
set
Notify whether a session does not have
Write Backward Compatible Session
Log File set.
- Topic: pc_sessions
- Analytics: pc_get_session_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS16 Check for session where
commit interval exceeds 1000 seconds
Notify if Commit Interval greater than
equal to 1000 seconds for a session.
- Topic: pc_sessions
- Analytics:
pc_get_task_parent_failure_options
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GT3 Check for transformations with
lookup SQL override
Notify if the Lookup SQL Override for a
transformation is not NULL.
- Topic: pc_transforms
- Analytics: - Source: PowerCenter Transforms
Modified Incremental
- Response: PowerCenter Notification
Response
Appendix D: Predefined Rules
Rule Name
Description
Properties
PC_GT4 Check for transformations with
source SQL override
Notify if SQL Query for a transformation
is not NULL.
- Topic: pc_transforms
- Analytics: - Source: PowerCenter Transforms
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GT5 Check for transformations with
tracing level higher than terse
Notify if a transformation has Tracing
Level higher than terse.
- Topic: pc_transforms
- Analytics: pc_get_transform_attribute
- Source: PowerCenter Transforms
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GT7 Check if sequence generator
reset option is set
Notify if the sequence generator Reset
option is set.
- Topic: pc_transforms
- Analytics: pc_get_transform_attribute
- Source: PowerCenter Transforms
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GW3 Workflow name should begin
with wf_
Notify if a workflow name does not
begin with wf_.
- Topic: pc_workflows
- Analytics: - Source: PowerCenter Workflows
Incremental
- Notification: PowerCenter Notification
Response
PC_GW6 Check whether save workflow
log for these runs used the global
variable PMWorkflowLogCount
Notify if Save workflow log for these
runs attribute does not use the global
variable $PMWorkflowLogCount.
- Topic: pc_workflows
- Analytics: pc_get_workflow_attribute
- Source: PowerCenter Workflows
Incremental
- Response: PowerCenter Notification
Response
PC_GW8 Check whether backward
write compatible workflow log option is
set
Notify whether a workflow does not
have Write Backward Compatible
Workflow Log File set.
- Topic: pc_workflows
- Analytics: pc_get_workflow_attribute
- Source: PowerCenter Workflows
Incremental
- Response: PowerCenter Notification
Response
PC_GW9 Check if Windows path name
is hardcoded with drive letter C
Notify if the command task contains a
hardcoded Microsoft Windows drive
letter C:\.
- Topic: pc_command_tasks
- Analytics: - Source: PowerCenter Command
Tasks
- Response: PowerCenter Notification
Response
Template Rules
47
Advanced Rules
Advanced rules do not have parameters. You can extend these rules once you are comfortable with the
functioning of these rules.
The following table lists the predefined advanced rules that are available by default upon installing Proactive
Monitoring for PowerCenter Governance:
48
Rule Name
Description
Properties
PC_GM1 Check for mappings without
description
Notify if the description for a mapping
is NULL.
- Topic: pc_mappings
- Analytics: - Source: PowerCenter Mappings
Modified Incremental
- Notification: PowerCenter Notification
Response
PC_GM2 Check for duplicate mappings
Notify if the name of the mapping is
duplicated.
- Topic: pc_mappings
- Analytics: pc_is_mapping_duplicate
- Source: PowerCenter Mappings
Modified Incremental
- Notification: PowerCenter Notification
Response
PC_GM3 Check for mappings that are
not valid
Notify if a mapping is not valid.
- Topic: pc_mappings
- Analytics: - Source: PowerCenter Mappings
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GM4 Check for mapping names
with spaces
Notify if the mapping name has spaces.
- Topic: pc_mappings
- Analytics: - Source: PowerCenter Mappings
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS1 Check for sessions that are
not valid
Notify if the session is not valid.
- Topic: pc_sessions
- Analytics: - Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS2 Check for sessions without
description
Notify if the description for a session is
NULL.
- Topic: pc_sessions
- Analytics: - Source: PowerCenter Sessions
Modified Incremental
- Notification: PowerCenter Sessions
Modified Incremental
PC_GS4 Check for duplicate sessions
Notify if a session name is repeated.
- Topic: pc_sessions
- Analytics: pc_is_session_duplicate
- Source: PowerCenter Sessions
Incremental
- Notification: PowerCenter Sessions
Modified Incremental
Appendix D: Predefined Rules
Rule Name
Description
Properties
PC_GS5 Check whether a sessions is
not reusable
Notify if a session is not reusable.
- Topic: pc_sessions
- Analytics: - Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS6 Check if session log file name
is not derived from the session name
Notify if the session log file name does
not contain the session name.
- Topic: pc_sessions
- Analytics: pc_get_session_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS7 Check whether the truncate
table option is set
Notify if a truncate target table is set.
- Topic: pc_sessions
- Analytic:
pc_get_session_mapping_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS10 Check for disabled sessions
Notify if a session is disabled.
- Topic: pc_sessions
- Analytic: - Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS11 Check for hardcoded source
connection parameters in a session
Notify if the source connection value of
a session does not begin with $.
- Topic: pc_sessions
- Analytic: pc_get_session_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS15 Check whether both the
parent fail options are not set
Notify if a session has both Fail parent
if the task fails and Fail parent if this
task does not run options not set.
-
PC_GS17 Check whether the option fail
parent if this task does not run is not set
Notify if a session has the option "ail
parent if this task does not run not set.
- Topic: pc_sessions
- Analytics:
pc_get_task_parent_failure_options
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GS18 Check whether target
connection value is empty
Notify if a Target connection value is
empty for a session.
- Topic: pc_sessions
- Analytic: pc_get_session_attribute
- Source: PowerCenter Sessions
Modified Incremental
- Response: PowerCenter Notification
Response
Topic: pc_sessions
Analytics: task_parent_failure_options
Source: Sessions Modified Incremental
Response: Notification Response
Advanced Rules
49
50
Rule Name
Description
Properties
PC_GT1 Check for transformations
without description
Notify if the description for a
tranformation is NULL.
- Topic: pc_transforms
- Analytics: - Source: PowerCenter Transforms
Modified Incremental
- Notification: PowerCenter Notification
Response
PC_GT2 Check for transformations with
default names
Notify if the transformation are saved
with default names.
- Topic: pc_transforms
- Analytics: - Source: PowerCenter Transforms
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GT6 Check whether connection
information option is set
Notify if the Connection Information
option is not set.
- Topic: pc_transforms
- Analytics: pc_get_transform_attribute
- Source: PowerCenter Transforms
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GW1 Check for workflows without
description
Notify if the description for a workflow
is NULL.
- Topic: pc_workflows
- Analytics: - Source: PowerCenter Mappings
Modified Incremental
- Notification: PowerCenter Sessions
Modified Incremental
PC_GW2 Check for duplicate workflows
Notify if a workflow name is repeated.
- Topic: pc_workflows
- Analytics: pc_is_workflow_duplicate
- Source: PowerCenter Workflows
Incremental
- Notification: PowerCenter Sessions
Modified Incremental
PC_GW4 Check for workflows that are
not valid
Notify if the workflow is not valid.
- Topic: pc_workflows
- Analytics: - Source: PowerCenter Workflows
Incremental
- Response: PowerCenter Notification
Response
PC_GW5 Check if the workflow is a
web service
Notify if the workflow is a web service.
- Topic: pc_workflows
- Analytic: - Source: PowerCenter Mappings
Modified Incremental
- Response: PowerCenter Notification
Response
PC_GW7 Check if workflow log file
name is not derived from workflow name
Notify if the Workflow Log File name
does not contain the workflow name.
- Topic: pc_workflows
- Analytics: pc_get_workflow_attribute
- Source: PowerCenter Workflows
Incremental
- Response: PowerCenter Notification
Response
Appendix D: Predefined Rules
Rule Name
Description
Properties
PC_GW10 Check for hardcoded UNIX
path
Notify if the command tasks contain
hard coded UNIX path names.
-
Topic: pc_command_tasks
Analytics: Source: PowerCenter Command Tasks
Response: PowerCenter Notification
Response
PC_GW11 Check for illegal command
tasks
Notify if the workflow contains illegal
command tasks listed in the
PowerCenter CLI command watchlist.
-
Topic: pc_command_tasks
Analytics: Source: PowerCenter Command Tasks
Response: PowerCenter Notification
Response
PC_S13 Load Global Settings from
Database
Generate Real-Time Alert Manager
alert when global settings are loaded
from the database.
- Topic: pc_pmpc_global_settings
- Analytics: pc_get_rtam
- Source: PowerCenter Load PMPC
Global Settings from Database
- Response: PowerCenter Real-Time
Alert Manager Alert
PC_S14 RTAM Notification
Generate Real-Time Alert Manager
notification.
Internal
PC_S15 Email Notification
Generate email notification.
Internal
PC_S16 Daily alert history report
Send a daily report of the alert history.
- Topic: pc_alert_history_purge_request
- Analytics: pc_get_alert_history_csv,
pc_get_purge_cutoff_date
- Source: PowerCenter Daily Alert
History Purge Requestor
- Response: PowerCenter Real-Time
Alert Manager Alert
PC_S17 Zero records purged from alert
history
Send a daily report when zero records
are purged.
- Topic: pc_alert_history_purge_request
- Analytics:
pc_get_alert_history_purge_count,
pc_get_purge_cutoff_date
- Source: PowerCenter Daily Alert
History Purge Requestor
- Response: PowerCenter Real-Time
Alert Manager Alert
PC_S18 Purge alert history
Notify when alert history is purged.
- Topic: pc_alert_history_purge_request
- Analytics:
pc_get_alert_history_purge_count,
pc_get_purge_cutoff_date
- Source: PowerCenter Daily Alert
History Purge Requestor
- Response: PowerCenter Real-Time
Alert Manager Alert
Advanced Rules
51
APPENDIX E
Predefined Templates
The following table lists the predefined templates that are available by default upon installing Proactive
Monitoring for PowerCenter Governance:
52
Template Name
Description
Properties
PC_GMT1 Violation of
mapping naming
convention
Notify if the convention for naming
a mapping is violated.
-
Topic: pc_mappings
Analytics: Source: PowerCenter Mappings Modified Incremental
Response: PowerCenter Notification Response
PC_GMT2 Mapping
modified often within a
specified duration
Notify if a mapping is modified for
a specified number of times within
the stipulated duration.
-
Topic: pc_mappings
Analytics: Source: PowerCenter Mappings Modified Incremental
Notification: PowerCenter Notification Response
PC_GST1 Compare
session attributes
Notify if the session attribute
contains a specified value.
-
Topic: pc_sessions
Analytics: pc_get_session_attribute
Source: PowerCenter Sessions Modified Incremental
Response: PowerCenter Notification Response
PC_GST2 Violation of
session naming
convention
Notify if the session naming
convention is violated.
-
Topic: pc_sessions
Analytics: Source: PowerCenter Sessions Modified Incremental
Notification: PowerCenter Notification Response
PC_GST3 Session
modified often within a
specified duration
Notify if the session is modified for
a specified number of times within
the stipulated duration.
-
Topic: pc_sessions
Analytics: Source: PowerCenter Sessions Modified Incremental
Notification: PowerCenter Notification Response
PC_GTT1 Compare
transformation attributes
Notify if the transformation
attribute contains a specified
value.
-
Topic: pc_transforms
Analytics: pc_get_transform_attribute
Source: PowerCenter Transforms Modified Incremental
Response: PowerCenter Notification Response
PC_GWT1 Violation of
workflow naming
convention
Notify if the workflow naming
convention is violated.
-
Topic: pc_workflows
Analytics: Source: PowerCenter Workflows Modified Incremental
Response: PowerCenter Notification Response
Template Name
Description
Properties
PC_GWT2 Compare
workflow attributes
Notify if the workflow attribute
contains a specified value.
-
Topic: pc_workflows
Analytics: pc_get_workflow_attribute
Source: PowerCenter Workflows Modified Incremental
Response: PowerCenter Notification Response
PC_GWT3 Windows
pathname is hardcoded
with a drive letter
Notify if the command tasks
contains the specified drive letter.
For example, "C:\"
-
Topic: pc_command_tasks
Analytics: Source: PowerCenter Command Tasks
Response: PowerCenter Notification Response
53
APPENDIX F
Predefined Services
This appendix includes the following topics:
¨ Analytics, 54
¨ Source Services, 56
¨ Responder Services, 57
Analytics
RulePoint analytics implement a data processing function, and it can be referenced in rules to determine whether
to activate a rule.
Analytics provide simple functions such as math, text, date functions, or more advanced functions such as,
connecting to a remote server and process data before returning results. Analytics provide data enrichment to the
rules that run them.
The following table lists the predefined analytics that are available by default after installing Proactive
Monitoring for PowerCenter Governance:
54
Name
Connects to...
Description
pc_get_email
RulePoint Repository
Obtain the email address for a specified
recipient of an alert.
pc_get_rtam
RulePoint Repository
Obtain the Real-Time Alert Manager target for a
specified recipient of an alert.
pc_get_global_setting
RulePoint Repository
Obtain value from the global settings framework
for a specified attribute name.
pc_get_purge_cutoff_date
RulePoint Repository
Obtain the text string for the cutoff date. The
cutoff date will be specified in the alerts.
pc_recent_alert
Rulepoint Repository
Check if a recent alert has been sent for a
specific rule name, key-value combination, and
a snooze interval. The snooze parameter
determines the most recent alert.
pc_get_alert_history_purge_count
RulePoint Repository
Obtain the count of alert history records to be
purged.
Name
Connects to...
Description
pc_get_session_count_for_workflow
PowerCenter Repository
Retrieve the number of sessions in a
PowerCenter workflow.
pc_is_mapping_duplicate
PowerCenter Repository
Obtain the duplicates of a specified mapping in
all other folders.
pc_is_session_duplicate
PowerCenter Repository
Obtain the duplicates of a specified session in
all other folders.
pc_is_workflow_running
PowerCenter Repository
Obtain the current running status of
PowerCenter workflow in a folder.
pc_is_workflow_duplicate
PowerCenter Repository
Obtain the duplicates of a specified workflow in
all other folders.
pc_get_session_details_for_mapping
PowerCenter Repository
Obtain PowerCenter session details
corresponding to the specified mapping.
pc_get_all_sessions_attribute_all_values
PowerCenter Repository
Obtain all sessions with a specified attribute
irrespective of its value.
pc_get_all_workflows_with_attribute_all_v
alues
PowerCenter Repository
Obtain all workflows with a specified attribute
irrespective of its value.
pc_get_all_transforms_with_attribute_all_
values
PowerCenter Repository
Obtain all transformations with a specified
attribute irrespective of its value.
pc_get_transform_attribute_count
PowerCenter Repository
Obtain the number of transformations for a
specified attribute value.
pc_get_all_sessions_with_attribute
PowerCenter Repository
Obtain all the sessions for a specified attribute
with a specified value.
pc_get_workflow_attribute_count
PowerCenter Repository
Obtain the number of workflows for a specified
attribute value.
pc_is_session_on_test_load
PowerCenter Repository
Check if a session has the Enable Test Load
attribute set.
pc_get_session_attribute_count_all_value
s
PowerCenter Repository
Obtain the count for a session attribute for all
values.
pc_get_transform_attribute
PowerCenter Repository
Obtain the value for a specified transformation
attribute.
pc_get_transform_attribute_count_all_val
ues
PowerCenter Repository
Obtain the number of transformations for a
specified attribute irrespective of its value.
pc_get_workflow_attribute
PowerCenter Repository
Obtain the workflow attribute for a specified
workflow.
pc_get_all_transforms_with_attribute
PowerCenter Repository
Retrieve all transformations with an attribute
matching specified value.
pc_get_task_parent_failure_options
PowerCenter Repository
Obtain the value of failed parent task option for
a specified session.
Analytics
55
Name
Connects to...
Description
pc_get_session_mapping_attribute
PowerCenter Repository
Obtain the mapping attributes for a specified
session.
pc_get_session_attribute_count
PowerCenter Repository
Obtain count for a specified session attribute
name and value.
pc_get_session_attribute
PowerCenter Repository
Obtain the value for a specified session attribute
name.
pc_get_workflow_attribute_count_all_valu
es
PowerCenter Repository
Obtain the number of workflows for a specified
attribute irrespective of its value.
pc_get_all_workflows_with_attribute
PowerCenter Repository
Obtain all the workflows for a specified attribute
with a specified value.
Source Services
The source services fetch data from PowerCenter repositories and runtime instances that eventually trigger the
rules in the starter kit.
The following table lists the predefined source services that are available by default after installing Proactive
Monitoring for PowerCenter Governance:
56
Source Service Name
Description
Properties
PowerCenter Command Tasks
Retrieve the details of
"Command" task type
used in PowerCenter
workflows.
- Type: Interval Based SQL Source
- Topic: pc_command_tasks
- Connected to: PowerCenter Repository
(pcrs_readonly)
- Default: 600 seconds
PowerCenter Daily Alert History Purge
Requestor
Retrieve alert history
purge frequency from the
global settings
framework.
-
Appendix F: Predefined Services
Type: SQL Source
Topic: pc_alert_history_purge_request
Connected to: Rulepoint Repository (pc_rp)
Default: Daily
Responder Services
With a responder service, you can define the interface parameters for a particular type of response, that is the
action to be taken when a rule activates. From a single responder service, you can create multiple specific
responses.
The following table lists the predefined responder services that are available by default after installing
Proactive Monitoring for PowerCenter Governance:
Responder Service Name
Description
Properties
PowerCenter Alert History Purge Responder
Responds to events by
purging alert history older
than the specified number
of days.
-
Type: SQL Responder
Topic: Connected to: Rulepoint Repository (pc_rp)
Default: -
PowerCenter Alert Recorder
The alert recorder stores
details of alerts in the
RulePoint database.
-
Type: SQL Responder
Topic: Connected to: Rulepoint Repository (pc_rp)
Default: -
PowerCenter Email Responder
Responds to events by
sending email alerts.
-
Type: Email
Topic: Connected to: Email server
Default: -
PowerCenter Notification Responder
Responds to events by
transforming them as
notification events.
-
Type: Event Transformer
Topic: pc_notifications
Connected to: Default: -
RTAM
Sends notifications to the
Real-Time Alert Manager.
-
Type: RTAM Responder
Topic: Connected to: Default: -
Responder Services
57
APPENDIX G
Predefined Responses
You can configure to send responses to a single user or groups of users through email or Real-Time Alert
Manager user interface.
The following table lists the predefined responses that are available by default upon installing Proactive
Monitoring for PowerCenter Governance:
58
Name
Purpose
PowerCenter Alert Recorder Response
Sends response for suppressing repeat alerts.
PowerCenter Email Response
Sends email notifications.
PowerCenter Notification Response
Generic notifier.
PowerCenter RTAM Alert
Sends alerts through Real-Time Alert Manager.
PowerCenter Alert History Purge Response
Purges all data present in tables that records all proactive
monitoring alerts.
APPENDIX H
Frequently Asked Questions
What is the required database size to create the database user, pc_rp, to host alerts in the RulePoint database? Do I have to
create the pc_rp user in the same database as the PowerCenter repository user?
The RulePoint or Real-Time Alert Manager repository do not need to be on the same database as the
PowerCenter repository. It can be on a different instance or on a different machine. It is a good practice to
host RulePoint and Real-Time Alert Manager on a different database. Alerts created in the RulePoint or RealTime Alert Manager database can grow up to a few gigabytes over a period of 60 days based on the number
of activations.
On the other hand, both the database type must be same. If PowerCenter repository is on an Oracle
database, the RulePoint or Real-Time Alert Manager databases must be on an Oracle database.
Can a single instance of the Proactive Monitoring solution monitor multiple PowerCenter repositories?
You cannot monitor multiple PowerCenter repositories through a single instance of Proactive Monitoring. You
can configure the rules to monitor a single PowerCenter repository.
Can the Proactive Monitoring solution monitor multiple nodes with grid?
You cannot monitor multiple nodes with grid. You can configure the rules to monitor a single PowerCenter
node.
What are the views or synonyms to be created while creating the database user, pcrs_readonly, with read-only permissions to
access PowerCenter repository?
The scripts to create the pcrs_readonly user grants the required privileges for environment monitoring and for
reading the PowerCenter repository. The installer creates the required views and synonyms.
Is a GUI available to use Global Setting Tool and Alert Recipient Tool?
No, you must use the Global Setting Tool and Alert Recipient Tool through command line.
How does RulePoint communicate with PowerCenter or database servers to collect information?
RulePoint communicates with PowerCenter or database servers through the pc_rp user. RulePoint connects
to the PowerCenter repository using JDBC. RulePoint connects to PowerCenter runtime using Web Services
Hub.
59
INDEX
A
Alert Recipient Tool 38
alert_history_purge_freq_days 40
alert_hyperlink 40
art.bat 38
art.sh 38
C
Channels 44
Cleanup Tool 40
graphical mode
installation requirements 12
gst.bat 40
gst.sh 40
I
installation requirements
X Window Server 12
P
Predefined Channels 44
D
default_notification 40
do_not_disturb 40
E
environment variables
DISPLAY 12
G
Global Setting Tool 40
60
S
settings tool 40
X
X Window Server
installation requirements 12