I n s t a l l a t i o n G u i d e - Informatica · PowerMart, Metadata Manager, Informatica Data...

Informatica® Proactive Monitoring for PowerCenter3.0 HotFix 1

Installation Guide

Informatica Proactive Monitoring for PowerCenter Installation Guide3.0 HotFix 1

© Copyright Informatica LLC 2016, 2019

This software and documentation contain proprietary information of Informatica LLC 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 LLC. 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©(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 Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging, Informatica Master Data Management, and Live Data Map are trademarks or registered trademarks of Informatica LLC 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.

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 © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights reserved. Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright © University of Toronto. All rights reserved. Copyright © Daniel Veillard. All rights reserved. Copyright © Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright © PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved. Copyright © Red Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC Corporation. All rights reserved. Copyright © Flexera Software. All rights reserved. Copyright © Jinfonet Software. All rights reserved. Copyright © Apple Inc. All rights reserved. Copyright © Telerik Inc. All rights reserved. Copyright © BEA Systems. All rights reserved. Copyright © PDFlib GmbH. All rights reserved. Copyright © Orientation in Objects GmbH. All rights reserved. Copyright © Tanuki Software, Ltd. All rights reserved. Copyright © Ricebridge. All rights reserved. Copyright © Sencha, Inc. All rights reserved. Copyright © Scalable Systems, Inc. All rights reserved. Copyright © jQWidgets. All rights reserved. Copyright © Tableau Software, Inc. All rights reserved. Copyright© MaxMind, Inc. All Rights Reserved. Copyright © TMate Software s.r.o. All rights reserved. Copyright © MapR Technologies Inc. All rights reserved. Copyright © Amazon Corporate LLC. All rights reserved. Copyright © Highsoft. All rights reserved. Copyright © Python Software Foundation. All rights reserved. Copyright © BeOpen.com. All rights reserved. Copyright © CNRI. All rights reserved.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of 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.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.

This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://www.dom4j.org/ license.html.

The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://dojotoolkit.org/license.

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 copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http:// www.gnu.org/software/ kawa/Software-License.html.

This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.

This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.

This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http:// www.pcre.org/license.txt.

This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.

This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5-current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/master/LICENSE; https://github.com/hjiang/jsonxx/blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/LICENSE; http://one-jar.sourceforge.net/index.php?page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-lang.org/license.html; https://github.com/tinkerpop/blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html; https://aws.amazon.com/asl/; https://github.com/twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), 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 Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/.

This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license.

See patents at https://www.informatica.com/legal/patents.html.

DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC 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.

Publication Date: 2019-04-01

https://www.informatica.com/legal/patents.html

Table of Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Part I: Pre-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1: Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Proactive Monitoring for PowerCenter Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

The Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Proactive Monitoring for PowerCenter Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Proactive Monitoring Solution Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2: Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Verify System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Verify Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Prepare the Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

PowerCenter Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Proactive Monitoring Repository Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Plan the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Download and Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Verify the License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configure the Command Line Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Install Microsoft Visual Studio on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Copy Domain Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Create a PowerCenter Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configure the Control File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Encrypt Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Create a System User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Record Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

License and Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Proactive Monitoring Repository Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 Table of Contents

Informatica Domain and Application Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

PowerCenter Repository Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

RulePoint Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Part II: Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3: Proactive Monitoring Governance Installation on Windows. . . . . . . 29Installing the Governance Edition for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Installing the Governance Edition on an Operations Edition for Windows. . . . . . . . . . . . . . . . . . 34

Chapter 4: Proactive Monitoring Governance Installation on UNIX. . . . . . . . . . 35Installing the Governance Edition for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing the Governance Edition on an Operations Edition for UNIX. . . . . . . . . . . . . . . . . . . . . 39

Chapter 5: Proactive Monitoring Operations Installation on Windows. . . . . . . 41Installing the Operations Edition for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing the Operations Edition on a Governance Edition for Windows. . . . . . . . . . . . . . . . . . . 46

Chapter 6: Proactive Monitoring Operations Installation on UNIX. . . . . . . . . . 47Installing the Operations Edition for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Installing the Operations Edition on a Governance Edition for UNIX. . . . . . . . . . . . . . . . . . . . . . 51

Part III: Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 7: Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Post-Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configure Repository Database Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Grant Permissions on Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Revoke User Permissions on Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Verify the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configure the Email Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configure LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Create Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Create Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Add Users to Real-Time Alert Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Enable Dashboard Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Import the Keystore File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configure the Node Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Read the Release Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Read the Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Table of Contents 5

Part IV: Apply the HotFix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 8: Apply the Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61HotFix Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Before You Apply the Hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Read the Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Verify Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Stop the Proactive Monitoring Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Download and Extract the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Apply the HotFix on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Apply the HotFix on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

After You Apply the HotFix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Start the Proactive Monitoring Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Import the RulePoint Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Read the Release Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Appendix A: Starting and Stopping Proactive Monitoring Components. . . . . . . 69Starting and Stopping the Proactive Monitoring Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Starting and Stopping the Node Agent (Operations only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Appendix B: Logging In to Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Logging In to the RulePoint Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Logging In to the Proactive Monitoring Management Console. . . . . . . . . . . . . . . . . . . . . . . . . 71

Logging In to the Real-Time Alert Manager Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Logging In to the PowerCenter Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Appendix C: Configure Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Prepare the Reports Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Step 1. Create Connection Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Step 2. Create a Folder in the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Step 3. Edit the Import File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Step 4. Import the File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Step 5. Schedule the Reporting Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Appendix D: Installation and Configuration Checklist. . . . . . . . . . . . . . . . . . . . . . . . 77Installation and Configuration Checklist Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Proactive Monitoring for PowerCenter Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

After You Install Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6 Table of Contents

PrefaceThe Proactive Monitoring for PowerCenter Installation Guide is written for the system administrator who is responsible for installing Proactive Monitoring for PowerCenter This guide assumes you have knowledge of operating systems, relational database concepts, and the database engines, flat files, or mainframe systems in your environment. This guide also assumes you are familiar with the interface requirements for the supporting applications.

Informatica Resources

Informatica NetworkInformatica Network hosts Informatica Global Customer Support, the Informatica Knowledge Base, and other product resources. To access Informatica Network, visit https://network.informatica.com.

As a member, you can:

• Access all of your Informatica resources in one place.

• Search the Knowledge Base for product resources, including documentation, FAQs, and best practices.

• View product availability information.

• Review your support cases.

• Find your local Informatica User Group Network and collaborate with your peers.

Informatica Knowledge BaseUse the Informatica Knowledge Base to search Informatica Network for product resources such as documentation, how-to articles, best practices, and PAMs.

To access the Knowledge Base, visit https://kb.informatica.com. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at [email protected].

Informatica DocumentationTo get the latest documentation for your product, browse the Informatica Knowledge Base at https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx.

If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected].

Informatica Product Availability MatrixesProduct Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types of data sources and targets that a product release supports. If you are an Informatica Network member, you can access PAMs at https://network.informatica.com/community/informatica-network/product-availability-matrices.

7

HTTPS://NETWORK.INFORMATICA.COM/

http://kb.informatica.com

mailto:[email protected]

https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx


https://network.informatica.com/community/informatica-network/product-availability-matrices

Informatica VelocityInformatica Velocity is a collection of tips and best practices developed by Informatica Professional Services. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions.

If you are an Informatica Network member, you can access Informatica Velocity resources at http://velocity.informatica.com.

If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].

Informatica MarketplaceThe Informatica Marketplace is a forum where you can find solutions that augment, extend, or enhance your Informatica implementations. By leveraging any of the hundreds of solutions from Informatica developers and partners, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at https://marketplace.informatica.com.

Informatica Global Customer SupportYou can contact a Global Support Center by telephone or through Online Support on Informatica Network.

To find your local Informatica Global Customer Support telephone number, visit the Informatica website at the following link: http://www.informatica.com/us/services-and-training/support-services/global-support-centers.

If you are an Informatica Network member, you can use Online Support at http://network.informatica.com.

8 Chapter 1: Preface

http://velocity.informatica.com


https://marketplace.informatica.com

http://www.informatica.com/us/services-and-training/support-services/global-support-centers/

http://network.informatica.com

Part I: Pre-InstallationThis part contains the following chapters:

• Installation Overview, 10

• Before You Install, 15

9

C h a p t e r 1

Installation OverviewThis chapter includes the following topics:

• Proactive Monitoring for PowerCenter Installation, 10

• The Installation Process, 10

• Proactive Monitoring for PowerCenter Architecture, 11

Proactive Monitoring for PowerCenter InstallationThe installer bundles the Proactive Monitoring, RulePoint, and Real-Time Alert Manager components for the Proactive Monitoring for PowerCenter solution. You must install the Informatica platform and configure PowerCenter services before you run the Proactive Monitoring installer. The installer starts the RulePoint, Real-Time Alert Manager, and Proactive Monitoring instances during installation.

Important: To ensure optimal monitoring results, install Proactive Monitoring for PowerCenter on a machine outside of the Informatica domain.

You can perform the following types of installation for Proactive Monitoring for PowerCenter:

• Install or apply the 3.0 HotFix 1 Governance or Operations Edition.

• Install or apply the 3.0 HotFix 1 Governance Edition on the Operations Edition.

• Install or apply the 3.0 HotFix 1 Operations Edition on the Governance Edition.

If you are currently running a version prior to 3.0, you must first upgrade to 3.0, and then you can apply version 3.0 HotFix 1.

The Installation ProcessThe installation process consists of the following high-level phases:

1. Pre-installation tasks. Before you run the installer, perform the following tasks to plan and prepare for the installation:

• Verify the system requirements.

• Prepare the PowerCenter and Proactive Monitoring databases.

• Install the command line utilities.

10

• Record installation information required by the installer.

2. Installation. Install Proactive Monitoring in graphical mode on Windows or in console mode on UNIX. The installer completes the following tasks:

• Creates Proactive Monitoring services.

• Creates schemas in the Proactive Monitoring repository.

• Validates the domain.

• Configures and deploys web applications for configuring and monitoring the PowerCenter environment.

• Starts the services.

3. Post-installation tasks. After you run the installer, you perform the following post-install tasks:

• Verify the installation.

• Configure the node agent if you perform operations monitoring.

• Enable dashboard alerts.

• Import keystore file.

Refer to the instructions in this guide for detailed information. You can also use the installation checklist as a guideline when you install Proactive Monitoring.

Proactive Monitoring for PowerCenter ArchitectureThe Proactive Monitoring for PowerCenter solution is a complex event monitoring solution that you can use to monitor PowerCenter governance and operations. It bridges the RulePoint and Real-Time Alert Manager products to PowerCenter through a set of proactive monitoring rules and services.

When you monitor PowerCenter governance, you can monitor consistency in PowerCenter development practices. When you monitor PowerCenter operations, you can monitor development and production errors and down time.

Proactive Monitoring for PowerCenter Architecture 11

The following image shows the high-level components of the Proactive Monitoring for PowerCenter solution:

Proactive Monitoring Solution ComponentsWhen you install Proactive Monitoring for PowerCenter, the installer creates a topology with services and design components. It also creates schemas in the Proactive Monitoring repository database.

RulePoint TopologyThe RulePoint topology is a group of application services, system services, nodes, and hosts that constitute the run-time environment in RulePoint. A topology service runs the topology.

The following RulePoint components are installed with the Proactive Monitoring for PowerCenter solution:

System services

Physical processes that run on the host machine. The RulePoint topology contains the following system services:

• Grid manager. Controls the application services in the topology. It also deploys objects into the application services and handles all interactions between the design environment and the services.

• UM store. Enables guaranteed delivery for data exchange across all services within RulePoint.

• UM lbmrd. Provides address resolver capability across the application services in RulePoint.

If you add multiple hosts or nodes to a topology to facilitate high availability, you can configure the UM store and UM lbmrd system services to enable guaranteed delivery through messaging.

12 Chapter 1: Installation Overview

Host agent

Manages the communication between the grid manager and the nodes. A Host Agent Service manages the host agent. The node contains application services that receive monitoring data, process it, and send responses.

The following RulePoint application services run within the node:

• Source controller. Receives source data from the PowerCenter environment, pre-processes events and forwards them to an event processor.

• Event processor. Consumes events and runs rules. The event processor activates a rule when it meets the rule conditions. Then, the event processor forwards responses to the responder controller. The event processor is also known as the rules engine.

• Responder controller. Consumes event activations and delivers responses to a configured external response target. The responder controller can deliver alerts to Real-Time Alert Manager and to email recipients.

• Activity manager. Records and stores the activity of the RulePoint application services. It displays data on the dashboard.

Design ComponentsThe design components with the Proactive Monitoring solution are web-based applications that you use to perform configuration, deployment, and monitoring tasks. A Design Service manages the design components.

RulePoint Console

A web-based application where you manage monitoring objects and administer RulePoint. You can create and deploy applications, manage users and the topology, and view topology activity on a dashboard.

Real-time Alert Manager

A web-based application where you can view alerts about the monitored environment on the RTAM dashboard. Each alert has a priority, subject, and body.

Proactive Monitoring Management Console

A web-based application where you can configure monitoring details and alert deliveries. Configure details about the domain, objects, and events that you want to monitor. Configure alert recipients and the method of delivery. If you monitor operations, you can also view monitoring reports.

Proactive Monitoring RepositoryThe Proactive Monitoring for PowerCenter installation creates schemas in the repository database to store the solution metadata and configuration data, domain and topology information, and a history of responses for Real-Time Alert Manager.

Informatica DomainThe Informatica domain is a collection of nodes and services that support the administration of the distributed services.

You must install the Informatica platform and create the application services before you install Proactive Monitoring for PowerCenter.

Proactive Monitoring for PowerCenter uses the following domain components to monitor PowerCenter governance and operations:

Proactive Monitoring for PowerCenter Architecture 13

PowerCenter Integration Service

The Informatica application service that runs sessions and workflows that you monitor. It runs the following types of workflows that collect monitoring information:

• Operations web service workflows that monitor the domain and the application services on a node.

• Operations workflows that collect historical run-time statistics about PowerCenter sessions and workflows.

PowerCenter Repository Service

The Informatica application service that manages the PowerCenter repository. The PowerCenter Integration Service reads from and writes to the PowerCenter repository through the PowerCenter Repository Service.

Web Services Hub Service

The Informatica application service that runs the web service workflow in conjunction with the PowerCenter Integration Service to monitor the domain and application services on a node.

Node agent

An operations monitoring service that runs on the Informatica domain node and collects resource usage information from the host machine. After you install Proactive Monitoring for PowerCenter, you copy the node agent files from the Proactive Monitoring machine to the node, and register it.

PowerCenter repository

Stores design-time and run-time metadata related to mappings, sessions, and workflows. Proactive monitoring collects the following type of information from the PowerCenter repository:

• Governance metadata related to development standards

• Operations metadata related to active and historical run-time statistics

PowerCenter Client

The client tool that you use to create mappings and workflows that you run in the monitored environment. You also schedule proactive monitoring workflows through the PowerCenter Client.

14 Chapter 1: Installation Overview

C h a p t e r 2

Before You InstallThis chapter includes the following topics:

• Read the Release Notes, 15

• Verify System Requirements, 15

• Prepare the Databases, 16

• Plan the Installation, 18

• Download and Extract the Installer Files, 19

• Verify the License Key, 20

• Configure the Command Line Utilities, 20

• Create a System User Account, 23

• Record Installation Information, 23

Read the Release NotesRead the Release Notes for updates to the installation and upgrade process. You can also find information about known and fixed limitations for the release.

Verify System RequirementsVerify that your environment meets minimum system requirements for the installation process, temporary disk space, port availability, databases, and hardware.

Domain Requirement

Operating System - Windows- Linux

Database Server - Oracle- Microsoft SQL Server

15

Domain Requirement

Hardware - 64-bit Intel or AMD compatible- Xenon equivalent or greater- 4 CPU at 1.7 GHz- 16 GB RAM- 1 Gbps Network Interface Card- 2.6x kernel with glibc 2.5X+ (Linux)

PowerCenter - Install a supported PowerCenter version: 8.6.1 HotFix 13 through 10.1.- Create a PowerCenter Integration Service, a PowerCenter Repository Service, and a Web

Services Hub Service.

For more information about product requirements and supported platforms, see the Product Availability Matrix on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices/overview

Verify Disk Space RequirementsVerify that your machine meets temporary and installation disk space requirements.

Consider the following space requirements for Proactive Monitoring:Temporary space requirements

The installer writes temporary files to the hard disk. Verify that you have enough available disk space on the machine to support the installation. When the installation completes, the installer deletes the temporary files and releases the disk space.

The installer requires 200 MB of temporary disk space.

Installation space requirements

The Proactive Monitoring installation requires 40 GB of free disk space.

Database space requirements

Allocate disk space for the Proactive Monitoring repository based one on the number of expected incoming events and generated responses. Consider allocating from 35 to 50 GB of space for a high volume of activity.

Contact Informatica Global Customer Support for specific database size requirements for your use case.

Prepare the DatabasesBefore you install Proactive Monitoring, you need to prepare the database repositories. Create a database for the Proactive Monitoring repository, and create Proactive Monitoring users in the PowerCenter repository database.

PowerCenter Repository Database RequirementsCreate a user with read-only permissions on the PowerCenter repository database. You will need to provide the user name and password when you install Proactive Monitoring.

16 Chapter 2: Before You Install

https://network.informatica.com/community/informatica-network/product-availability-matrices/overview

Create a Read-only User in Microsoft SQL ServerLog in to Microsoft SQL Server Management Studio using as the database administrator and run the following commands to create a user and assign permissions:

USE masterCREATE LOGIN <pcrs_readonly> WITH PASSWORD=<'pcrs_readonly'>, DEFAULT_DATABASE=<repository database name>, CHECK_EXPIRATION=OFF, CHECK_POLICY=OFFUSE <<repository database name>>CREATE USER <pcrs_readonly> FOR LOGIN 'pcrs_readonly'ALTER USER pcrs_readonly WITH DEFAULT_SCHEMA=db_datareaderEXEC sp_addrolemember N'db_datareader', N'pcrs_readonly'EXEC sp_addrolemember N'db_ddladmin', N'pcrs_readonly'GRANT CREATE TABLE TO pcrs_readonlyGRANT DELETE,INSERT TO pcrs_readonlyGRANT SELECT ON sys.database_files TO pcrs_readonly

Note: Do not associate any server roles to the login other than the default public server role.

Create a Read-only User in OracleLog in to the PowerCenter repository database as the database owner and perform the following tasks:

• Create a read-only user, for example pcrs_readonly.

• Grant the following privileges to the user:

ALTER TABLE

CREATE INDEX

CREATE SESSION

CREATE SYNONYM

CREATE TABLE

CREATE VIEW

INSERT INTO TABLE

If you are going to monitor the Informatica environment for operations, perform the following task:

• Log in as "sys as sysdba" and run the following commands:

grant select on sys.dba_free_space to <read only user name>;grand select on sys.dba.data_files to <read only user name>

Proactive Monitoring Repository RequirementsSet up a database for the Proactive Monitoring repository.

The Proactive Monitoring repository supports the following database types:

• Microsoft SQL Server

• Oracle

Allocate disk space for the Proactive Monitoring repository based one on the number of expected incoming events and generated responses. Consider allocating from 35 to 50 GB of space for a high volume of activity.

Note: You must use the same database type as the PowerCenter repository database.

Prepare the Databases 17

Microsoft SQL Server Database RequirementsCreate a database user account with permission to perform the following actions:

• Create, alter, drop, and select tables, views, and schemas.

• Create and drop procedures.

• Create and drop indexes.

Note: Ensure that the default schema is not empty.

Oracle Database RequirementsUse the following guidelines when you set up the database repository on Oracle:

• Create a database user account with permission to perform the following actions:

- Create, alter, drop, and select tables, views, and schemas

- Create and drop procedures

- Create and drop indexes

• Set parameters on the database.The following table lists the configuration parameters that you must set:

Parameter Value

SESSIONS 800

PROCESSES 500

TRANSACTIONS 600

Plan the InstallationThe Proactive Monitoring for PowerCenter installation contains dependencies between the installer tasks and the pre- and post-installation tasks. Before you run the installer, you need to decide on some tasks that you want the installer to perform and the tasks that you will perform.

Some tasks that the installer can perform require the Informatica command line utilities. If you want the installer to perform the tasks, you must install and configure the command line utilities on the machine where you plan to install Proactive Monitoring for PowerCenter. The configuration tasks include copying domain files and setting environment variables.

The installer can perform the following tasks:Validate the domain.

The installer validates the domain and service information that you specify in the install wizard.

Important: If you do not install the command line utilities, and you enter domain or service information during installation that is not valid, the installer completes without errors, but the Proactive Monitoring instance will not be valid. You must then manually remove the installation and run the installer again.

Import the workflow and enable reporting.

The installer imports the workflow that generates reports from results written to the Proactive Monitoring repository.


If you do not install the command line utilities and enable reporting in the install wizard, you must manually configure reporting. To configure reporting after installation, you must edit the import .xml file and then import it into the PowerCenter repository.

Download and Extract the Installer FilesThe installer files are compressed and distributed as a .zip file for Windows and a .tar file for UNIX. You need to download installers for Proactive Monitoring for PowerCenter (Proactive Monitoring) and the Informatica command line utilities.

Note: Make sure that you download the file to a local directory or a shared network drive that is mapped on your machine. You can then extract the installer files. However, you cannot run the installer from a mapped file. Copy the extracted files to a local drive and then run the installer.

Step 1. Download the installers

Download the following installers:Proactive Monitoring for PowerCenter

You can download the Proactive Monitoring installer in the following ways:

• Installation DVD. Download the compressed file from the installation DVD to a directory on your machine and then extract the installer files, or extract the installer files directly from the DVD to a directory on your machine. If you download the compressed file to a directory on your machine, verify the length of the entire installation directory path, including the compressed file name, is 60 characters or less.

• HTTP. Download the compressed file from the Informatica Electronic Software Download site to a directory on your machine and then extract the installer files.

Command line utilities

If you want the installer to validate the domain and create PowerCenter metadata, you must download and extract the command line utilities. You can download the command line utilities through FTP. Download the compressed file from the Informatica Electronic Software Download site to a directory on your machine and then extract the installer files. Verify that you download the version of the utilities associated with the version of PowerCenter that you plan to monitor.

Step 2. Extract the installer files

On Windows, use a zip utility to extract the installer files to a directory on your machine. Verify the zip utility version is compatible with the Windows operating system version. When you unzip the file, verify that the zip utility also extracts empty folders.

On UNIX, use a native tar or GNU tar utility to extract the installer files to a directory on your machine. The user that runs the installer must have read and write permissions on the installer files directory and execute permissions on install.sh.

Download and Extract the Installer Files 19

Verify the License KeyBefore you install the software, verify that you have the license key available.

You can get the license key in the following ways:

• Installation DVD. If you receive the installation files in a DVD, the license key file is included in the Informatica License Key CD.

• HTTP download. If you download the installation files from the Informatica Electronic Software Download (ESD) site, the license key is in an email message from Informatica. Copy the license key file to a directory accessible to the user account that installs the product.

Configure the Command Line UtilitiesConfigure the command line utilities so that the Proactive Monitoring for PowerCenter installer can perform domain tasks during the installation process.

The Proactive Monitoring installer uses the command line utilities to perform the following tasks:

• Validates the domain information and the application service names.

• Creates a connection object in the PowerCenter repository to connect to the Proactive Monitoring database.

• Imports a workflow into the PowerCenter repository that generates reports.

Install Microsoft Visual Studio on WindowsThe command line utilities on Windows require the Microsoft Visual Studio redistributable package.

The redistributable package is included with the command line utility files that you extracted. The version of Microsoft Visual Studio depends on the version of the utilities that you extracted. The version will be 2008 or 2013.

Run the file located in the following directory:

<utilities installation directory>/PowerCenter/server/<Microsoft Visual Studio version>

Copy Domain FilesCopy files from the domain that the installer requires to run commands through the command line program.

Copy the following files from the Informatica domain to the machine where you installed the command line utilities:

• krb5.conf. If the domain uses Kerberos authentication, copy the Kerberos configuration file from the Informatica domain.

• truststore files. If the domain uses a custom Transport Layer Security (TLS) protocol, copy infa_truststore.jks and infa_truststore.pem from the Informatica domain.


Set Environment VariablesSet environment variables that the installer requires to run commands through the command line program.

PATH

On UNIX, set PATH to the PowerCenter\server\bin directory of the command line utilities installation, such as <Utilities installation directory>\PowerCenter\server\bin.

Library path

On UNIX, set the library path environment variable to the PowerCenter\server\bin directory of the command line utilities.

INFA_TRUSTSTORE

If the domain is enabled for secure communication, set the INFA_TRUSTSTORE environment variable with the directory that contains the truststore files for the SSL certificates. The directory must contain truststore files named infa_truststore.jks and infa_truststore.pem. You must set the INFA_TRUSTSTORE variable whether you use the default SSL certificate from Informatica or you specify an SSL certificate.

INFA_TRUSTSTORE_PASSWORD

If you specify the SSL certificate to enable secure communication in the domain, set the INFA_TRUSTSTORE_PASSWORD environment variable with the encrypted password for the infa_truststore.jks that contains the SSL certificate. You do not need to set this variable if you use the default SSL certificate from Informatica.

KRB5_CONFIG

If the domain uses Kerberos authentication, set KRB5_CONFIG to the path and file name of the Kerberos configuration file. The name of the Kerberos configuration file is krb5.conf.

Create a PowerCenter FolderThe installer imports the reporting workflow into the PowerCenter repository. You need to create a PowerCenter folder to store the Proactive Monitoring workflow and associated objects.

Use the pmrep command line utility to create a folder in the PowerCenter repository. Use a folder name such as "pmpc_workflow."

From the command line, enter the following command:

pmrep connect -r <repository name>createfolder-n <folder name>-d <folder description>-a <owner security domain>

When you run the command, consider the following rules and guidelines:

• To avoid errors at run time, do not put a period (.) in the folder name.

• The owner security domain is required only if the domain uses LDAP authentication.

You will need the folder name when you configure the pmrep control file that the installer uses to import the workflow.

Configure the Command Line Utilities 21

Configure the Control FileThe installer uses pmrep to import the reporting workflow into the PowerCenter repository. You must configure the control file that pmrep uses to perform the import.

The extracted installer files contain a control file with the parameters required to import the workflow. You need to update the parameter values based on your repository. Find the control file associated with the PowerCenter repository database type.

The control file is in the following location: <Installer download directory>\bin\packs\controlFile\<database type>\

The following example shows the control file text that you need to edit:

<?xml version="1.0" encoding="UTF-8"?>

<IMPORTPARAMS > <FOLDERMAP SOURCEFOLDERNAME="pmpc_reporting_<database>" SOURCEREPOSITORYNAME="RS_1" TARGETFOLDERNAME="" TARGETREPOSITORYNAME=""/> <RESOLVECONFLICT> <TYPEOBJECT OBJECTTYPENAME="All" RESOLUTION="REUSE"/> </RESOLVECONFLICT></IMPORTPARAMS>

The following table describes the parameters that you need to update in the control file:

Parameter Value

TARGETFOLDERNAME The name of the target folder where you want to store the reporting workflow.

TARGETREPOSITORYNAME The name of the PowerCenter repository.

When you run the installer, you must provide a path to the control file.

Encrypt PasswordIf you specify the SSL certificate to enable secure communication in the domain, you must encrypt the password for the infa_truststore.jks that contains the SSL certificate.

Use the pmpasswd command line utility encrypt the password, and then you set the INFA_TRUSTSTORE_PASSWORD environment variable with the encrypted password.

From the command line enter the following command:

pmpasswd <password>pmpasswd returns the encrypted password.

Use the encrypted password when you set the environment variable INFA_TRUSTSTORE_PASSWORD.

Create a System User AccountCreate a system user account to perform the installation.

Windows

To access a repository on Microsoft SQL Server that uses a Windows trusted connection, create a domain account.

The user account requires the following permissions:

• Logged in user account. The user account must be a member of the Administrators group and have the Log on as a service permission. Log in with this user account before you install Proactive Monitoring.

• Another user account. The user account must be a member of the Administrators group and have Log on as a service and Act as operating system permissions. Log in with this user account before you install Proactive Monitoring.

• Execute permission on the command line utility files

UNIX

Verify that the user account that you use to install Proactive Monitoring has the following permissions:

• Read, write, and execute permission on the installation directory

• Write permission on the /tmp directory

• Execute permission on the command line utility files

Record Installation InformationWhen you install Proactive Monitoring, you need to know information about the Informatica domain, the databases, and other install requirements.

Use the tables in this section to record the information that you need.

License and Installation DirectoryUse the following table to record License and installation directory information that you need when you run the installer:

Installer Property Value

Installation directory

License file path and name

Create a System User Account 23

Proactive Monitoring Repository DatabaseUse the following table to record Proactive Monitority Repository Database information that you need when you run the installer:

Installer Property Description Value

Database type Database type for the Proactive Monitoring database.

Database user name User name of the Proactive Monitoring database.

Database password Password for the Proactive Monitoring user.

Database host The name of the machine hosting the database.

Database port The port number of the database.

SID/Service name The service name or database name. If the database is on Oracle, indicate whether to use the SID or service name in the JDBC connection string. For Oracle RAC databases, select from Oracle SID or Oracle service name. For other Oracle databases, select Oracle SID.

JDBC parameters Optional parameters to include in the database connection string. Use the parameters to optimize database operations for the database. Verify that the parameter string is valid.

Custom JDBC connection string Custom JDBC string for the DataDirect drivers.

Informatica Domain and Application DetailsUse the following table to record Informatica Domain and Application Details information that you need when you run the installer:


Domain name Name of the Informatica domain that you want to monitor.

Node host name Host name of the gateway node.

Node port number Gateway port number of the Informatica domain.

Domain user name User name of the Informatica administrator.



Domain password Password of the Informatica administrator.

Security domain name Required if the Informatica domain uses LDAP or Kerberos authentication.

PowerCenter Repository Service The name of the PowerCenter Repository Service.

PowerCenter Integration Service The name of the PowerCenter Integration Service.

Connection name The name of the connection that you want to create to the Proactive Monitoring repository database. The installer creates a connection object before it imports reporting workflows into the PowerCenter repository.

Connect string The connection string to the Proactive Monitoring repository database.

Location of the command line utilities

The path to the command line utilities.

Control file location The path to the pmrep control file.

Code page The code page of the PowerCenter Repository Service.

PowerCenter Repository DatabaseUse the following table to record PowerCenter repository database and user information that you need when you run the installer:


Database type Database type for the PowerCenter repository database.

Database user name User name of the PowerCenter repository database.

Database password Password for the PowerCenter user.

Database host Name of the machine that hosts the PowerCenter repository database.

Database port number Port number of the PowerCenter repository database.

Record Installation Information 25


SID/Service name The service name or database name. If the database is on Oracle, indicate whether to use the SID or service name in the JDBC connection string. For Oracle RAC databases, select from Oracle SID or Oracle service name. For other Oracle databases, select Oracle SID.

JDBC parameters Optional parameters to include in the database connection string. Use the parameters to optimize database operations for the database. Verify that the parameter string is valid.

Custom JDBC connection string Custom JDBC connection string to the DataDirect drivers

Read-only user name Name of the read-only user for the PowerCenter repository.

Read-only password Password of the read-only user.

RulePoint TopologyUse the following table to record RulePoint Topology information that you need when you run the installer:


Keystore file path and name The path and file name of the keystore file on the topology machine. Required if the domain uses https and you are using an existing keystore file.

Keystore Password Plain-text password for the keystore file.

Email NotificationsUse the following table to record Email Notifications information that you can configure when you run the installer:


SMTP host The fully qualified domain name of the SMTP server that you use to send alerts.

Port The port number of the SMTP server.



User name User account name of the SMTP server.

Password User account password.

Record Installation Information 27

Part II: InstallationThis part contains the following chapters:

• Proactive Monitoring Governance Installation on Windows, 29

• Proactive Monitoring Governance Installation on UNIX, 35

• Proactive Monitoring Operations Installation on Windows, 41

• Proactive Monitoring Operations Installation on UNIX, 47

28

C h a p t e r 3

Proactive Monitoring Governance Installation on Windows

This chapter includes the following topics:

• Installing the Governance Edition for Windows, 29

• Installing the Governance Edition on an Operations Edition for Windows, 34

Installing the Governance Edition for WindowsYou can install Proactive Monitoring for PowerCenter Governance in graphical mode on Windows.

1. Go to the root directory, right-click the Informatica_PMPC_Governance_3.0HF1.exe file and select Run as administrator.

The Introduction page appears.

2. Select Proactive Monitoring for PowerCenter Governance 3.0 HotFix 1.

3. Click Install.

The Prerequisites page displays the installation requirements. Verify that all requirements are met before you continue the installation.

4. Click Next.

The Installation Directory page appears.

5. Enter the directory where you want to install Proactive Monitoring for PowerCenter.

The default location of the installation directory is C:\Proactive_Monitoring

6. Click Next.

The License File page appears.

7. Enter the path and file name of the license file, and click Next.

The Proactive Monitoring Repository Database page appears.

8. Select the database for the Proactive Monitoring repository.

• Oracle


29

9. Enter the following information about the Proactive Monitoring repository database:

Property Description

Database user name

User name of the Proactive Monitoring database.

Database password

Password for the Proactive Monitoring user.



SID/Service name

The service name or database name. If the database is on Oracle, indicate whether to use the SID or service name in the JDBC connection string. For Oracle RAC databases, select from Oracle SID or Oracle service name. For other Oracle databases, select Oracle SID.

JDBC parameters

Optional parameters to include in the database connection string. Use the parameters to optimize database operations for the database. Verify that the parameter string is valid.

Custom JDBC connection string

Custom JDBC connection string for the DataDirect drivers.You can use the following syntax in the connection string:- Oracle. For example,jdbc:Informatica:oracle://<host_name>:<port_no>;ServiceName=<database name>

- Microsoft SQL Server. For example, jdbc:Informatica:sqlserver://<host_name>:<port_no>;DatabaseName=<database name>

10. Click Test Connection to verify that you can connect to the database.

If the connection to the database is successful, a success message appears.

11. Click Next.

The Proactive Monitoring Schemas page appears.

The installer creates the following default schemas for Proactive Monitoring for PowerCenter:

• RulePoint_Design

• RulePoint_RTAM

• RulePoint_Topology

• RulePoint_TopologyState

• RulePoint_Activity

• Proactive_Monitoring

12. Click Next to accept the default schema names or enter new schema names and then click Next.

The Informatica Domain and Application Details page appears.

13. Enter the domain information. To validate the domain information, select Validate the domain information.

30 Chapter 3: Proactive Monitoring Governance Installation on Windows

The installer validates the domain information through the command line utilities.










14. To configure Proactive Monitoring reports, select Enable Reporting.

15. Enter the following domain information:



The name of the PowerCenter Repository Service.


The name of the PowerCenter Integration Service.

Connection name The name of the connection that you want to create to the PowerCenter repository database. The installer creates a connection object before it imports reporting workflows into the repository.

Connect string Required if you configured the command line utilities. The connection string to the PowerCenter repository database.You can use the following syntax in the connection string:- On Oracle, use the syntax <database name>.world (same as TNSNAMES entry). For

example, oracle.world.- On Microsoft SQL Server, use the syntax <server name>@<database name>. For

example, sqlserver@mydatabase.

Location of the import control file

Required if you configured the command line utilities. The path to the pmrep control file.

Code page of the PowerCenter Repository Service

Required if you configured the command line utilities. The code page of the PowerCenter Repository Service. Default is utf-8.

16. Click Next.

The PowerCenter Repository Database page appears.

Installing the Governance Edition for Windows 31

17. Enter the following information about the PowerCenter repository database:



Database user name

User name of the PowerCenter repository database.

Database password

Password for the PowerCenter user.


Database port number

Port number of the PowerCenter repository database.

SID/Service name


JDBC parameters



Custom JDBC string for the DataDirect drivers.You can use the following syntax in the connection string:- Oracle. For example,jdbc:Informatica:oracle://<host_name>:<port_no>;ServiceName=<database name>


18. Click Next.

The PowerCenter Read-Only User Details page appears.

19. Enter the user name and password of the read-only user for the PowerCenter repository database.

20. Click Next.

The RulePoint Topology page appears.

21. Enter the topology host and port information:


Topology Host IP IP address of the server where you install Proactive Monitoring for PowerCenter.

Tomcat Port HTTP port number of the Tomcat server. The default port number is 8080.

22. Select Enable HTTPS for Web Application to enable secure connection for Proactive Monitoring for PowerCenter.

a. Enter the port number. By default, the port number is 8443.

b. Select either a keystore file generated by the installer, or use an existing keystore file.

c. If you choose to use an existing keystore file, enter the keystore password and the name of the keystore file.


23. Click Email Notification Configuration to configure email notifications to receive alerts for process failures in Proactive Monitoring for PowerCenter.

The Email Configurations dialog box appears.

a. Select Email Notification.

b. Enter the following email notification information:




From Sender email address from which you send outbound emails.

To Email recipient address to which you send notifications.

Priority Email messages with the priority that you want to receive. Select from the following options:- Critical- High- Medium- LowFor example, select Critical to receive email messages that have the priority as critical. When the default node fails, you receive an email alert of critical priority with the message that the default node has failed.

Verbosity Verbosity of the email notification. Select from the following options:- More- LessFor example, select Less to receive email messages with brief information of the alert.



c. Click Save.

24. Click Next.

The Pre-Installation Summary page appears.

25. Review the pre-installation summary, and click Install.

The Service Registration dialog box appears.

26. If you want to register services for RulePoint, click Yes. Otherwise, click No.

Note: If you do not register the services, you must manually start the Proactive Monitoring instance when the installation is complete.

The Installation Complete page appears.

27. Click Done to complete the installation procedure and exit the installer.

Installing the Governance Edition for Windows 33

Review the following files in the installation directory for information about the installation process:

• PMPC_Governance_3.0HF1_Install.log• Readme.txt

Installing the Governance Edition on an Operations Edition for Windows

You can install Governance Edition on an instance of Operations Edition in graphical mode on Windows. The installer verifies the installation directory and skips the screens that do not apply.

1. Go to the root directory, right-click the Informatica_PMPC_Governance_3.0HF1.exe file and select Run as administrator.


2. Select Install Proactive Monitoring for PowerCenter Governance 3.0HF1.

3. Click Install.


4. Click Next.


5. Enter the directory the location where you installed Proactive Monitoring for PowerCenter Operations.

The default location of the installation directory is C:\Proactive_Monitoring6. Click Next.




8. Click Done to complete the installation procedure and then exit the installer.




C h a p t e r 4

Proactive Monitoring Governance Installation on UNIX


• Installing the Governance Edition for UNIX, 35

• Installing the Governance Edition on an Operations Edition for UNIX, 39

Installing the Governance Edition for UNIXYou can install Proactive Monitoring for PowerCenter Governance in console mode on Linux.

1. Log in to the machine with a system user account.

2. Run the Informatica_PMPC_Governance_3.0HF1.bin -i console file from the directory where you downloaded the files.

3. Press 1 to install Proactive Monitoring for PowerCenter Governance.

4. Press Enter.

The Prerequisites section displays the installation requirements.

5. Press Enter.

Installation Directory section appears.

6. Enter the location where you installed Proactive Monitoring for PowerCenter Operations.

The default location of the installation directory is /home/Proactive_Monitoring7. If you enter a different installation directory, enter Y to confirm the installation directory path.

The License File section appears.

8. Enter the path and file name of the license file, and press Enter.

The Proactive Monitoring Repository Database section appears.

9. Enter the database on which you configure Proactive Monitoring for PowerCenter.

• Press 1 for Oracle.

• Press 2 for Microsoft SQL Server.

35



Database user name


Database password




SID/Service name


JDBC parameters





11. Choose whether you to use custom JDBC connection string, and then press Enter.

a. To enter the JDBC connection info using a custom JDBC connection string, press Y.

b. Otherwise, press N, and then enter the database connection information.

12. Press Enter.

The Proactive Monitoring Schemas section appears.The installer creates the following default schemas for Proactive Monitoring for PowerCenter:


• RulePoint_RTAM





13. Press Enter to accept the default schema names or enter new schema names and then click Enter.

The Informatica Domain and Application Details section appears.

14. Enter the domain name.

15. Specify an option to validate the domain information.

a. To validate the domain, press Y.

b. If you do not want to validate the domain, press N.

36 Chapter 4: Proactive Monitoring Governance Installation on UNIX







Location of the command line utilities The path to the command line utilities.


17. Specify an option to enable reporting for Proactive Monitoring.

a. To enable reporting, press Y.

b. If you do not want to enable reporting, press N.

18. Enter the following information to configure Proactive Monitoring reports.







Connect string Required if you configured the command line utilities.The connection string to the PowerCenter repository database.You can use the following syntax in the connection string:- On Oracle, use the syntax <database name>.world (same as TNSNAMES entry). For







19. Press Enter.

The PowerCenter Repository Database section appears.

Installing the Governance Edition for UNIX 37

20. Select the database on which you configure PowerCenter repository database.





Database user name


Database Password





SID/Service name


JDBC parameters








23. Press Enter.

The PowerCenter Read-Only User Details section appears.


25. Press Enter.

The RulePoint Topology section appears.

26. Enter the following topology information:




a. To enable HTTPS for RulePoint design, press Y.


b. Otherwise, press N.

Enter the following connection information, to enable HTTPS,:

Option Description

Port number Port number for the HTTPS connection. The default is 8443

Keystore file Select the following option to use a keystore file generated by the installer or a keystore file you create:Press 1 to use a keystore generated by the installer.Press 2 to use an existing keystore

27. Enter the following email notifications information to receive alerts for process failures in Proactive Monitoring for PowerCenter:

a. Enter Y to choose Email Configuration, and then press Enter.

b. If you do not want to configure email notifications during installation, enter N.

28. Press Enter.

The Pre-Installation Summary section appears.

29. Review the pre-installation summary, and press Enter to continue.

The Installation Complete section appears.

30. Press Enter to complete the installation and exit the installer.



Installing the Governance Edition on an Operations Edition for UNIX

You can install Governance Edition on an instance of Operations Edition in console mode on Linux. The installer verifies the installation directory and skips the screens that do not apply.


2. Run the Informatica_PMPC_Governance_3.0HF1.bin -i console from the directory where you downloaded the files.


4. Press Enter.

The Prerequisites section displays the installation requirements. Verify that all requirements are met before you continue the installation.

5. Press Enter.



The default location of the Installation directory is /home/Proactive_Monitoring

Installing the Governance Edition on an Operations Edition for UNIX 39

7. If you entered a different installation directory, press Y to confirm the installation directory path.

8. Press Enter.








C h a p t e r 5

Proactive Monitoring Operations Installation on Windows


• Installing the Operations Edition for Windows, 41

• Installing the Operations Edition on a Governance Edition for Windows, 46

Installing the Operations Edition for WindowsYou can install Proactive Monitoring for PowerCenter Operations in graphical mode on Windows.

1. Go to the root directory, right-click the Informatica_PMPC_Operations_3.0HF1.exe file and select Run as administrator.


2. Select Proactive Monitoring for PowerCenter Operations 3.0 HotFix 1.

3. Click Install.


4. Click Next.




The License File page appears.

7. Enter the path and file name of the license file, and click Next.

The Proactive Monitoring Repository Database page appears.

8. Select the database for the Proactive Monitoring repository.

• Oracle


41



Database user name


Database password




SID/Service name


JDBC parameters





10. Click Test Connection to verify that you can connect to the database.

If the connection to the database is successful, a success message appears.

11. Click Next.

The Proactive Monitoring Schemas page appears.The installer creates the following default schemas for Proactive Monitoring for PowerCenter:


• RulePoint_RTAM





12. Click Next to accept the default schema names or enter new schema names and then click Next

The Informatica Domain and Application Details page appears.

13. Enter the domain information. To validate the domain information, select Validate the domain information.

42 Chapter 5: Proactive Monitoring Operations Installation on Windows

The installer validates the domain information through the command line utilities.










14. To configure Proactive Monitoring reports, select Enable Reporting.







Connection name The name of the connection that you want to create to the PowerCenter repository database. The installer creates a connection object before it imports reporting workflows into the repository.

Connect string Required if you configured the command line utilities. The connection string to the PowerCenter repository database.You can use the following syntax in the connection string:- On Oracle, use the syntax <database name>.world (same as TNSNAMES entry). For







16. Click Next.

The PowerCenter Repository Database page appears.

Installing the Operations Edition for Windows 43




Database user name


Database Password





SID/Service name


JDBC parameters





18. Click Next.

The PowerCenter Read-Only User Details page appears.


20. Click Next.

The RulePoint Topology page appears.

21. Enter the topology host and port information:




22. Select Enable HTTPS for Web Application to enable secure connection for Proactive Monitoring for PowerCenter.

a. Enter the port number. By default, the port number is 8443.

b. Select either a keystore file generated by the installer, or use an existing keystore file.

c. Enter the keystore password and the name of the keystore file if you choose to use an existing keystore file.


23. Click Email Notification Configuration to configure email notifications to receive alerts for process failures in Proactive Monitoring for PowerCenter.

The Email Configurations dialog box appears.

a. Select Email Notification.

b. Enter the following email notification information:




From Sender email address from which you send outbound emails.

To Email recipient address to which you send notifications.

Priority Email messages with the priority that you want to receive. Select from the following options:- Critical- High- Medium- LowFor example, select Critical to receive email messages that have the priority as critical. When the default node fails, you receive an email alert of critical priority with the message that the default node has failed.

Verbosity Verbosity of the email notification. Select from the following options:- More- LessFor example, select Less to receive email messages with brief information of the alert.



c. Click Save.

24. Click Next.



The Service Registration dialog box appears.

26. If you want to register services for RulePoint, click Yes. Otherwise, click No.

Note: If you do not register the services, you must manually start the Proactive Monitoring instance when the installation is complete.



Installing the Operations Edition for Windows 45


• PMPC_Operations_3.0HF1_Install.log• Readme.txt

Installing the Operations Edition on a Governance Edition for Windows

You can install Operations Edition on an instance of Governance Edition in graphical mode on Windows. The installer verifies the installation directory and skips the screens that do not apply.

1. Go to the root directory, right-click the Informatica_PMPC_Operations_3.0HF1.exe file and select Run as administrator.


2. Select Proactive Monitoring for PowerCenter Operations 3.0 HotFix 1.

3. Click Install.


4. Click Next.











C h a p t e r 6

Proactive Monitoring Operations Installation on UNIX


• Installing the Operations Edition for UNIX, 47

• Installing the Operations Edition on a Governance Edition for UNIX, 51

Installing the Operations Edition for UNIXYou can install Proactive Monitoring for PowerCenter Operations in console mode on Linux.


2. Run the Informatica_PMPC_Operations_3.0HF1.bin -i console file from the directory where you downloaded the files.

3. Press 1 to install Proactive Monitoring for PowerCenter Operations.

4. Press Enter.

The Prerequisites section displays the installation requirements. Verify that all requirements are met before you continue the installation. .

5. Press Enter.



The default location of the installation directory is /home/Proactive_Monitoring7. If you enter a different installation directory, enter Y to confirm the installation directory path.

The License File section appears.

8. Enter the path and file name of the license file, and press Enter.

The Proactive Monitoring Repository Database section appears.

9. Enter the database on which you configure Proactive Monitoring for PowerCenter.



47



Database user name


Database password




SID/Service name


JDBC parameters








12. Press Enter.

The Proactive Monitoring Schemas section appears.The installer creates the following default schemas for Proactive Monitoring for PowerCenter:


• RulePoint_RTAM





13. Press Enter to accept the default schema names or enter new schema names and then click Enter.

The Informatica Domain and Application Details section appears.

14. Enter the domain name.

15. Specify an option to validate the domain information.

a. To validate the domain, press Y.

b. If you do not want to validate the domain, press N.

48 Chapter 6: Proactive Monitoring Operations Installation on UNIX







Location of the command line utilities The path to the command line utilities.


17. Specify an option to enable reporting for Proactive Monitoring.

a. To enable reporting, press Y.

b. If you do not want to enable reporting, press N.

18. Enter the following information to configure Proactive Monitoring reports.







Connect string Required if you configured the command line utilities. The connection string to the Proactive Monitoring repository database.You can use the following syntax in the connection string:- On Oracle, use the syntax <database name>.world (same as TNSNAMES entry). For







19. Press Enter.

The PowerCenter Repository Database section appears.

Installing the Operations Edition for UNIX 49

20. Select the database on which you configure PowerCenter repository database.





Database user name


Database Password





SID/Service name


JDBC parameters








23. Press Enter.

The PowerCenter Read-Only User Details section appears.


25. Press Enter.

The RulePoint Topology section appears.

26. Enter the following topology information:




a. To enable HTTPS for RulePoint design, press Y.


b. Otherwise, press N.

Enter the following connection information, to enable HTTPS:

Option Description

Port number Port number for the HTTPS connection. The default is 8443.

Keystore file Select the following option to use a keystore file generated by the installer or a keystore file you create:Press 1 to use a keystore generated by the installer.Press 2 to use an existing keystore.

27. Enter the following email notifications information to receive alerts for process failures in Proactive Monitoring for PowerCenter:

a. Enter Y to choose Email Configuration, and then press Enter.

b. If you do not want to configure email notifications during installation, enter N.

28. Press Enter.




30. Press Enter to complete the installation and then exit the installer.



Installing the Operations Edition on a Governance Edition for UNIX

You can install Operations Edition on an instance of Governance Edition in console mode on Linux.


2. Run the Informatica_PMPC_Operations_3.0HF1.bin -i console file from the directory where you downloaded the files.


4. Press Enter.

The Prerequisites section displays the installation requirements. Verify that all requirements are met before you continue the installation. .

5. Press Enter.


6. Enter the location where you installed Proactive Monitoring for PowerCenter Operations. The default location of the Installation directory is /home/dev/Proactive_Monitoring

7. If you entered a different installation directory, enter Y to confirm the installation directory path.

Installing the Operations Edition on a Governance Edition for UNIX 51

8. Press Enter.



The -Installation Complete section appears.

10. Review the PMPC_Operations_3.0HF1_Install.log file for errors in the installation directory.





Part III: Post-InstallationThis part contains the following chapter:

• Post-Installation, 54

53

C h a p t e r 7

Post-InstallationThis chapter includes the following topics:

• Post-Installation Overview, 54

• Configure Repository Database Permissions, 55

• Verify the Installation, 55

• Configure the Email Connection, 56

• Configure LDAP, 57

• Enable Dashboard Alerts, 58

• Import the Keystore File, 58

• Configure the Node Agent, 59

• Read the Release Guide, 59

• Read the Configuration Guide, 59

Post-Installation OverviewAfter you install the Proactive Monitoring for PowerCenter, you must perform some post-installation tasks. The post-installation tasks include verifying the installation, enabling dashboard alerts, and configuring repository database permissions.

To perform some of the post-installation tasks, you must log in to the client tools. For information about logging in to the client tools, see Appendix B, “Logging In to Client Tools” on page 71.

54

Configure Repository Database PermissionsAfter you install Proactive Monitoring, you need to configure permissions on the Proactive Monitoring repository database.

Grant Permissions on Microsoft SQL ServerIn the Proactive Monitoring repository database, grant execute permissions to the PowerCenter read-only user on user defined functions TO_DATE_MMDDYYYYHHMI and TO_DATE_MMDDYYYYHHMISS.

Log in to Microsoft SQL Server Management Studio as the database administrator and run the following commands:

GRANT EXECUTE ON db_datareader.TO_DATE_MMDDYYYYHHMI TO <PowerCenter read only user name>GRANT EXECUTE ON db_datareader.TO_DATE_MMDDYYYYHHMISS TO <PowerCenter read only user name>

Revoke User Permissions on OracleFor security reasons, you might want to revoke create table permissions on the Proactive Monitoring repository database.

To revoke the create table permissions for users on Oracle, run the following commands:

REVOKE CREATE TABLE FROM RULEPOINT_DESIGNREVOKE CREATE TABLE FROM RULEPOINT_TOPOLOGYREVOKE CREATE TABLE FROM RULEPOINT_ACTIVITYREVOKE CREATE TABLE FROM RULEPOINT_TOPOLOGYSTATEREVOKE CREATE TABLE FROM RULEPOINT_RTAMREVOKE CREATE TABLE FROM PROACTIVE_MONITORING

Verify the InstallationAfter you install Proactive Monitoring you can verify the installation. Log in to the RulePoint Console and verify that the services are running.

1. Open a web browser.

2. In the Address field, enter the RulePoint URL https://<host name>:<port number>/rulepoint.The port number is the port of the tomcat server. Default is 8080. The RulePoint login page appears.

3. Enter the user name and password.You can use the default username and password, Administrator/Administrator1.

4. Click Login.The RulePoint Console opens.

5. Click the Dashboard on the navigator pane.

6. Verify that the services are running.The status of the source controllers, event processors, and the responder controllers displays a green icon for successful running of services.

Configure Repository Database Permissions 55

Configure the Email ConnectionIn RulePoint, you can configure the email connection to receive alerts through emails.

1. Log in to the RulePoint Console.

2. On the Design tab, click the PMPC project in the Navigator.

3. In the Connections view, select email_connection from the list in the contents panel.

4. From the Actions menu, select Edit.

5. Enter the following email configuration information:

Properties Description

Email server Host name of the email server.

Port Port number to connect to the SMTP server.

User name Optional: Required when SMTP user authentication is configured.

Password Optional: Required when SMTP user authentication is configured.

Retry count Number of retry attempts. Default is 2.

Retry delay Waiting time between the connection attempts in milliseconds. Default is 10000.

6. To test that the connection details are correct, click Test Connection.

7. Click Save.

56 Chapter 7: Post-Installation

Configure LDAPYou can configure LDAP users to receive Proactive Monitoring alerts. Configure the LDAP server information and create the default LDAP users in RulePoint.

Create UsersYou can create users in RulePoint. The roles, permissions, and privileges that you assign to a user determine the tasks that the user can perform within RulePoint. When you create a user, you need to specify the authentication provider as local.


2. On the Administration tab, click User Management > Users view.

3. From the Action menu, select New User in the navigator or in the contents pane.

4. Under Details, select Type as Local, and enter the first name, last name, user name, and password for the user.

5. Click Next.

6. Click Select to select the each role for the user or click Select All to select all the roles.

7. Click Save.

Create RolesYou can create roles for users in RulePoint. You can associate one or more roles with a user. You must map privileges to the roles based on the type of operation you want the user to perform.


2. On the Administration tab, click User Management > Roles view.

3. Select New Role from the Actions menu in the contents pane.

4. Under Name, type a name for the role.

5. Under Description, type a description for the role.

6. Click Next.

7. Under Role, select the privileges you want to associate to the role, or click Select All to select all the privileges.

8. Click Save.

Note: The role that you assign to the users must have the ROLE_USER and ROLE_ADMIN privileges to log in to the Proactive Monitoring Management Console.

Add Users to Real-Time Alert ManagerTo enable Proactive Monitoring for PowerCenter alerts to the LDAP users, configure the Alert Recipients information and add the users to the appropriate personas.

1. Log in to the Proactive Monitoring Management Console.

2. Click the Settings tab.

3. Select Alert Recipients in the Navigator, select the domain, and then select Edit from the Actions menu.

Configure LDAP 57

The Alert Recipients Configuration dialog box appears.

4. In the RTAM List field, replace the RTAM user with the LDAP users that you created in RulePoint for each of the five users.

5. Click Save.

Enable Dashboard AlertsTo enable alert Real-Time Alert Manager to receive alerts on the dashboard, you must log in to Real-Time Alert Manager as native user or as LDAP user.

If you use LDAP authentication, log in as the LDAP users that you created in RulePoint.

If you use native authentication, log in as each user created during installation.

The following table lists the user names and passwords that you need to log in with:

User name Password

pcmonitor pcmonitor123

pcadmin pcadmin123

apparchitect apparchitect123

dataarchitect dataarchitect123

itsecurity itsecurity123

Import the Keystore FileIf the PowerCenter Repository Service and the Web Services Hub use the same keystore file, you must import the keystore file using the keytool.

1. To export the keystore file, run the following command from the <INFA_HOME>/java/jre/bin directory:

keytool -export -alias <alias_name> -file wsh.cert -keystore <service_keystore>2. Copy the wsh.cert file to the machine where you installed Proactive Monitoring for PowerCenter.

3. To import the keystore file, run the following command from the <Proactive monitoring installation directory>/rulepoint/system/java/bin directory:

keytool -importcert -file wsh.cert -keystore <Proactive monitoring installation directory>/rulepoint/system/java/lib/security/cacerts -alias <aliasname>

58 Chapter 7: Post-Installation

Configure the Node AgentYou can configure the node agent for operations. You can specify the frequency for data collection, number of processes to collect data on, and the processes to monitor for lifecycle changes.

The node agent periodically gathers CPU, memory, and process lifecycle details from the host machine and then stores the information in the Proactive Monitoring repository. The Proactive Monitoring solution uses the resource consumption information in rule processing and to add additional information to the alerts.

The installer creates the nodeagent.zip file in the Proactive Monitoring installation directory.

To configure the node agent, perform the following steps:

1. Copy the nodeagent.zip file to each node that you want to monitor.

2. Extract the nodeagent.zip file.

3. Run the script from the command line to start the node agent.On Windows, you can start the node agent from the Windows services list or from the command line:

nodeagent.bat start

On UNIX, you can start the node agent from the command line:

nodeagent.sh start

Read the Release GuideThe Proactive Monitoring for PowerCenter Release Guide lists new features and enhancements, behavior changes between versions, and tasks that you might need to perform after you install Proactive Monitoring for PowerCenter. Read the Proactive Monitoring for PowerCenter Release Guide to view the list of new functionality and changes.

Read the Configuration GuideAfter you install Proactive Monitoring you need complete configuration tasks such as configuring the services, alerts, and reports.

Refer to a configuration guide for information about completing the configuration through the Proactive Monitoring Management Console. Based on the edition of Proactive Monitoring you installed, refer to one of the following guides:

• Proactive Monitoring for PowerCenter Operations Configuration Guide

• Proactive Monitoring for PowerCenter Governance Configuration Guide

Configure the Node Agent 59

Part IV: Apply the HotFixThis part contains the following chapter:

• Apply the Hotfix , 61

60

C h a p t e r 8

Apply the HotfixThis chapter includes the following topics:

• HotFix Overview, 61

• Before You Apply the Hotfix, 61

• Apply the HotFix on Windows, 64

• Apply the HotFix on UNIX, 64

• After You Apply the HotFix, 65

HotFix OverviewYou can apply the hotfix to Proactive Monitoring for PowerCenter version 3.0. The hotfix has separate installers for the Governance and Operations editions. If you installed both editions in the same directory, you only need to apply the hotfix once. The hotfix process includes pre- and post-install tasks.

When you apply the hotfix, the installer performs the following tasks:

• Verifies the installation directory.

• Backs up existing directories, installs the new version of the product, and restores or updates required configuration files.

• Skips the screens that do not apply for the hotfix process.

Before You Apply the HotfixBefore you apply the hotfix, complete the following pre-installation tasks.

• Read the Release Notes for important information about the install and about fixed and known limitations.

• Verify the minimum system requirements for the hotfix process.

• Shut down the Proactive Monitoring instance.

• Close all command prompts on Windows.

• Back up the version 3.0 installation folder.

61

Read the Release NotesRead the Proactive Monitoring for PowerCenter Release Notes for updates to the installation and the hotfix process. You can also find information about known and fixed limitations for the release.

Verify Minimum System RequirementsVerify that your environment meets minimum system requirements for the installation process, temporary disk space, port availability, databases, and hardware.

Domain Requirement

Operating System - Windows- LinuxNote: Windows authentication is not supported for version 3.0 HotFix 1.

Database Server - Oracle- Microsoft SQL Server

Hardware - 64-bit Intel or AMD compatible- 16 GB RAM- 1 Gbps Network Interface Card- 40 GB disk space

PowerCenter - Upgrade PowerCenter to version 8.6.1 HotFix 13 through 10.1.

Web browser - Internet Explorer- Chrome


Support ChangesConsider the following operating system support changes in version 3.0 HotFix 1:

• Support for AIX, Solaris, and SUSE Linux is deferred for version 3.0 HotFix 1. Support will be reinstated in a future release.

• Support for Red Hat Enterprise Server version 6.4 is dropped.

• Support for Windows Server 2008 RTM SP2 and 2012 RTM is dropped. You cannot apply the hotfix if version 3.0 uses one of the dropped Windows versions.

Consider the following database support changes in version 3.0 HotFix 1:

• Support for IBM DB2 is deferred for version 3.0 HotFix 1. Support will be reinstated in a future release.

• Support for Oracle 10g R2 and 11gR1 is dropped. You cannot apply the hotfix if version 3.0 uses one of the dropped Oracle versions.


62 Chapter 8: Apply the Hotfix



Stop the Proactive Monitoring InstanceYou must run a script to stop the Proactive Monitoring before you apply the hotfix.

You can find the script in the following location: <installation directory>/bin

On Windows, run the following script from the command line to stop the Proactive Monitoring instance:

solutions.bat stop

Important: Ensure that you close all command line prompts on Windows before you apply the hotfix.

On UNIX, run the following script from the command line to stop the Proactive Monitoring instance:

solutions.sh stop

Download and Extract the InstallerThe installer files are compressed and distributed as a .zip file for Windows and a .tar file for UNIX. You need to download installer for Proactive Monitoring for PowerCenter (Proactive Monitoring).

Note: Make sure that you download the file to a local directory or a shared network drive that is mapped on your machine. You can then extract the installer files. However, you cannot run the installer from a mapped file. Copy the extracted files to a local drive and then run the installer.

Step 1. Download the installer

You can download the Proactive Monitoring installer in the following ways:

• Installation DVD. Download the compressed file from the installation DVD to a directory on your machine and then extract the installer files, or extract the installer files directly from the DVD to a directory on your machine. If you download the compressed file to a directory on your machine, verify the length of the entire installation directory path, including the compressed file name, is 60 characters or less.

• HTTP. Download the compressed file from the Informatica Electronic Software Download site to a directory on your machine and then extract the installer files.

Step 2. Extract the installer

On Windows, use a zip utility to extract the installer files to a directory on your machine. Verify the zip utility version is compatible with the Windows operating system version. When you unzip the file, verify that the zip utility also extracts empty folders.

On UNIX, use a native tar or GNU tar utility to extract the installer files to a directory on your machine. The user that runs the installer must have read and write permissions on the installer files directory and execute permissions on install.sh.

Before You Apply the Hotfix 63

Apply the HotFix on WindowsYou can apply the hotfix for Proactive Monitoring in graphical mode on Windows. The hotfix has separate installers for the Governance and Operations editions. If you installed both editions in the same directory, you only need to apply the hotfix once.

Before you apply the hotfix, verify that you back up the version 3.0 installation folder.

1. Go to the directory where you downloaded the installer files, right-click the Informatica_PMPC_<Edition>_3.0HF1.exe file and select Run as administrator.


2. Select Apply Hotfix for Proactive Monitoring for PowerCenter 3.0.

3. Click Next.


4. Specify the location of the installation directory where you installed the Proactive Monitoring for PowerCenter version 3.0.




The Install Complete page appears.


Review the PMPC_<Edition>_3.0HF1_Hotfix.log file in installation directory for information about apply the hotfix process.

Apply the HotFix on UNIXYou can apply the hotfix for Proactive Monitoring in console mode on UNIX. The hotfix has separate installers for the Governance and Operations editions. If you installed both editions in the same directory, you only need to apply the hotfix once.

Before you apply the hotfix, verify that you back up the version 3.0 installation folder.


2. Run the Informatica_PMPC_<Edition>_3.0HF1.bin file from the directory where you downloaded the files.

3. Press 2 to apply the hotfix for Proactive Monitoring for PowerCenter 3.0.

4. Press Enter.


5. Type the location of the installation directory where you installed Proactive Monitoring for PowerCenter 3.0. The default location of the installation directory is /home/Proactive_Monitoring

6. Press Enter.





8. Press Enter to complete the installation and then exit the installer.

Review the PMPC_<Edition>_3.0HF1_Hotfix.log file in installation directory for information about apply the hotfix process.

After You Apply the HotFixAfter you apply the hotfix, complete the following tasks.

• Edit the solution.properties file.

• Start the Proactive Monitoring instance.

• Import and redeploy objects in the RulePoint Console.

• Read the Release Guide to view the list of new features, enhancements, behavior changes, and tasks you need to perform after you apply hotfix.

Start the Proactive Monitoring InstanceYou must start the Proactive Monitoring instance after you apply the hotfix.

On Windows, run the following script from the command line to start the Proactive Monitoring instance:

solutions.bat start

On UNIX, run the following script from the command line to start thte Proactive Monitoring instance:

solutions.sh start

You can find the script in the following directory: <Proactive Monitoring installation directory>/Proactive_Monitoring/bin

Import the RulePoint ObjectsVersion 3.0 HotFix 1 includes fixes to multiple RulePoint objects. After you apply the hotfix, you need to import the common.xml file that contains updates to the objects.

To import the updated RulePoint objects, perform the following tasks:

1. Edit the common.xml file.

2. Import the common.xml file.

3. Redeploy the objects in the RulePoint Console.

After You Apply the HotFix 65

The following table lists the objects that are updated in version 3.0 HotFix 1:

Object Type Name

Analytic The following analytic objects are updated:- get_completed_sessions_last_day_csv- get_completed_workflows_last_day_csv- get_no_completed_sessions_last_day- get_no_completed_workflows_last_day- pc_get_workflow_runtype

Response The following response objects are updated:- PowerCenter completed sessions recorder response- PowerCenter completed workflows recorder response

Rule The following rule objects are updated:- PC_O10 Integration service health check- PC_O11 Repository service health check- PC_O12 Domain service health check- PC_O19 All Integration services health check- PC_O20 All Repository services health check- PC_OS14 Daily report of completed sessions- PC_OW12 Daily report of completed workflows- PC_OW16 Check for workflows becoming unscheduled

Source The following source objects are updated:- Node Agent Monitor- Node TopNStats Table Purge

Step 1. Edit the common.xml file.The installation directory contains an .xml import file with the parameters required to import the updated objects. You need to update the file to specify the names of the domain and the Proactive Monitoring schema.

Find the .xml file associated with the database type of the Proactive Monitoring repository. The common.xml file is in the following location: <Proactive Monitoring installation directory>\Solutions\PMPC\<Edition>_3.0\solution_xmls\<edition>\<database type>\

The following table describes the parameters that you need to update in the .xml import file.

Parameter to Replace Value

##PC_REPO_DOMAIN_NAME## The name of the Informatica domain.

##PM_SCHEMA## The name of the Proactive Monitoring schema. The default schema name is "Proactive_Monitoring."

The following example shows a sample import file:

<config> <serviceClassName>com.informatica.cep.sdk.service.api.builtin.sources.SqlSource</serviceClassName> <propertyDefinitions> <propertyDefinition> <propName>parameters</propName> <propValue> <rpie:null/> </propValue>


</propertyDefinition> <propertyDefinition> <propName>fetchSize</propName> <propValue>10</propValue> </propertyDefinition> <propertyDefinition> <propName>bufferResult</propName> <propValue>no</propValue> </propertyDefinition> <propertyDefinition> <propName>updateSql</propName> <propValue/> </propertyDefinition> <propertyDefinition> <propName>transactionSize</propName> <propValue>1</propValue> </propertyDefinition> <propertyDefinition> <propName>propertyMetadataMap</propName> <propValue>domain=##PC_REPO_DOMAIN_NAME##, rs=unknown, workflow_name=unknown, folder=unknown</propValue> </propertyDefinition> <propertyDefinition> <propName>markerId</propName> <propValue/> </propertyDefinition> <propertyDefinition> <propName>sql</propName> <propValue>select host_name,repo_tstamp, current_upd_tstamp from ( select host_name,repo_tstamp, current_upd_tstamp, extract (minute from diff) s1 from (select host_name, repo_tstamp, current_upd_tstamp, ( sysdate - to_timestamp (repo_tstamp, 'yyyy/MM/dd HH24:MI:SS') )diff from ##PM_SCHEMA##.na_heartbeat) ) T where T.s1 > 2 AND UPPER(host_name) in (select UPPER(host_name) from ##PM_SCHEMA##.NA_HOST_CONFIG)</propValue> </propertyDefinition> </propertyDefinitions> </config>

Step 2. Import the common.xml file.You must import the updated .xml file from the RulePoint Console.


2. On the Administration tab, click Import view.

3. Select PMPC project.

4. From the Actions menu, select Upload File.

The Upload File dialog box appears.

5. Click Choose File, and select the common.xml file from the location: <Proactive monitoring installation directory>\Solutions\PMPC\<Edition>_3.0\solution_xmls\<edition>\<database type>\

6. Click Upload.

7. Navigate to the Available Files view in the Contents panel, and select the uploaded .xml file.

8. From the Actions menu, select Start Import.

The Import dialog box appears.

9. Select Update collision option to overwrite the properties of objects in a project with the properties of the imported objects.

10. Click Import.

An import successful message appears.

After You Apply the HotFix 67

Step 3. Redeploy the objects.After you import the objects, you need filter them in the RulePoint Console and redeploy them.


2. On the Design tab, click All Objects, and select PMPC project.

3. Filter the state column with the keyword NEEDS_DEPLOYMENT, and then click the filter icon.

a. From the Actions menu, select Redeploy to redeploy the source, responder, rule, and response objects.

b. From the Actions menu, select Update Run Time to redeploy the analytic objects.

4. Click OK.

A redeploy successful message appears.

Read the Release GuideThe Proactive Monitoring for PowerCenter Release Guide lists new features and enhancements, behavior changes between versions, and tasks that you might need to perform after you install Proactive Monitoring for PowerCenter. Read the Proactive Monitoring for PowerCenter Release Guide to view the list of new functionality and changes.


A p p e n d i x A

Starting and Stopping Proactive Monitoring Components

This appendix includes the following topics:

• Starting and Stopping the Proactive Monitoring Instance, 69

• Starting and Stopping the Node Agent (Operations only), 69

Starting and Stopping the Proactive Monitoring Instance

The installer starts the services that run the Proactive Monitoring instance. You can run scripts to stop and start the Proactive Monitoring instance. You can find the scripts in the following directory: <Proactive Monitoring installation directory>/Proactive_Monitoring/bin.

Run the following scripts from the command line to start and stop Proactive Monitoring on Windows:

solutions.bat startsolutions.bat stop

Run the following scripts from the command line to start and stop Proactive Monitoring on UNIX:

solutions.sh startsolutions.sh stop

Starting and Stopping the Node Agent (Operations only)

After you register the node agent on each node that you want to monitor, you can start and stop the node agent.

On Windows, you can start and stop the node agent from the Windows services list or from the command line. Run the following scripts from the command line to start and stop the node agent:

nodeagent.bat start

69

nodeagent.bat stop

On UNIX, run the following scripts from the command line to start and stop the node agent:

nodeagent.sh startnodeagent.sh stop

70 Appendix A: Starting and Stopping Proactive Monitoring Components

A p p e n d i x B

Logging In to Client ToolsThis appendix includes the following topics:

• Logging In to the RulePoint Console, 71

• Logging In to the Proactive Monitoring Management Console, 71

• Logging In to the Real-Time Alert Manager Console, 72

• Logging In to the PowerCenter Client, 72

Logging In to the RulePoint ConsoleUse the Rulepoint URL to log in to the Rulepoint console. When you log in to the Rulepoint Console, you must specify the username and password.


2. In the Address field, enter the URL for the RulePoint console according to the security within the environment.

• If you enabled secure connections during installation, enter the following URL:

https://<host name>:<port number>/rulepoint• If you did not enable secure connections during installation, enter the following URL:

http://<host name>:<port number>/rulepointThe port number is the port of the tomcat server. Default is 8080.

The RulePoint login page appears.

3. Enter the user name and password.

4. Click Log In.

Logging In to the Proactive Monitoring Management Console

Use the Proactive Monitoring for PowerCenter URL to log in to the Management Console. When you log in to the Proactive Monitoring Console, you must specify the user name and password.


71

2. In the Address field, enter the URL for the Proactive Monitoring Console according to the security within the environment.


https://<host name>:<port number>/pmpc• If you did not enable secure connections during installation, enter the following URL:

http://<host name>:<port number>/pmpcThe port number is the port of the tomcat server. Default is 8080.

The Informatica Proactive Monitoring login page appears.


4. Click Log In.

Logging In to the Real-Time Alert Manager ConsoleUse the Real-Time Alert Manager URL to log in to the Real-Time Alert Manager Console. When you log in to the Real-Time Alert Manager, you must specify the user name and password.


2. In the Address field, enter the URL for Real-Time Alert Manager according to the security within the environment.


https://<host name>:<port number>/RTAM• If you did not enable secure connections during installation, enter the following URL:

http://<host name>:<port number>/RTAMThe port number is the port of the tomcat server. Default is 8080.

The Real-Time Alert Manager login page appears.

3. Enter your user name and password. If you are unsure what your login is, check with the RulePoint administrator.

4. Click Log In.

Logging In to the PowerCenter ClientWhen you log in to the PowerCenter Client, you connect to a PowerCenter repository.

1. From the Windows Start menu, click Programs > Informatica [version] > Client > [client tool name].

2. Select the repository in the Navigator and click Repository > Connect.

The Connect to Repository dialog box appears.


4. Select Native or the name of a specific security domain.

72 Appendix B: Logging In to Client Tools

The Security Domain field appears when the PowerCenter domain contains an LDAP security domain. If you do not know the security domain that your user account belongs to, contact the PowerCenter domain administrator.

5. To connect to a repository that you have connected to before, go to step 12.

To select an existing domain connection for the repository, go to step 10.

To enter the domain connection information for the repository, complete steps 6 through 9.

6. If theConnect to Repository dialog box is not expanded, click More to view the connection settings.

7. Click Add.

The Add Domain dialog box appears.

8. Enter the domain name, gateway host name, and gateway port number.

Note: Use the gateway HTTP port number to connect to the domain from the PowerCenter Client. You cannot connect to the domain using the HTTPS port number.

9. Click OK.

10. If the connection settings of the Connect to Repository dialog box are hidden, click More to view the connection settings.

11. In the connection settings, select the appropriate domain connection from the list.

12. Click Connect.

Logging In to the PowerCenter Client 73

A p p e n d i x C

Configure ReportingThis appendix includes the following topics:

• Prepare the Reports Workflow, 74

• Step 1. Create Connection Object, 74

• Step 2. Create a Folder in the Repository, 75

• Step 3. Edit the Import File, 75

• Step 4. Import the File, 75

• Step 5. Schedule the Reporting Workflow, 76

Prepare the Reports WorkflowWhen you installed Proactive Monitoring for PowerCenter, the installer created a workflow that transforms operations alert data and populates the reports. If you did not enable reporting during the installation, you must prepare the .xml import file and import it into the PowerCenter repository.

Perform the following tasks to prepare the reports workflow:

1. Create connection objects in the Workflow Manager to the Proactive Monitoring repository database and the PowerCenter repository database.

2. Create a folder in the PowerCenter repository to store the workflow objects.

3. Edit the import .xml file.

4. Import the file.

5. Schedule the workflow.

Step 1. Create Connection ObjectThe workflow needs to connect to the Proactive Monitoring repository database to write results to the database.

Log in to the PowerCenter Workflow Manager and create a connection object. The connection name must be the same as the one that you specified on the Reporting Configuration page during installation. If you do not enter the reporting configuration information during installation, specify a new name.

For information about creating connections, see the PowerCenter Workflow Administration Guide.

74

Step 2. Create a Folder in the RepositoryCreate a folder in the PowerCenter repository to store proactive monitoring objects.

Log in to the PowerCenter Repository Manager and create a folder to import the .xml file. Use a folder name such as "pmpc_workflow."For information about object import, see the PowerCenter Repository Guide.

Step 3. Edit the Import FileThe installer installs the reporting workflow .xml file that you need to edit and import into the PowerCenter repository.

1. Find the file named ETL_ALL_PMPC_v30HF1.xml on the machine where you installed Proactive Monitoring for PowerCenter.You can find the file in the following location: <Proactive Monitoring installation directory>/Solutions/PMPC/reporting/etl/<database type>/

2. Update the .xml file to replace the following placeholder values with values specific to your environment:

• REPORTING_DOMAIN. Replace with the name of the Informatica domain.

• REPORTING_IS_NAME. Replace with the name of the PowerCenter Integration Service to run these workflows.

• REPORTING_CONNECTION_NAME. Replace with the connection name for the Proactive Monitoring repository database.

• PM_SCHEMA. Replace with the Proactive Monitoring schema name. Default name is "Proactive_Monitoring."

3. Copy the file to the PowerCenter Client machine.

After you edit the file, you can import it into the PowerCenter repository.

Step 4. Import the FileAfter you edit the workflow .xml file, you must import it into the PowerCenter repository.

Log in to the PowerCenter Repository Manager, and import the ETL_ALL_PMPC_v30HF1.xml file into the folder that you created.

The Repository Manager imports a workflow named wf_pmpc_reports along with the associated mapping and session objects.

For information about object import, see the PowerCenter Repository Guide.

Step 2. Create a Folder in the Repository 75

Step 5. Schedule the Reporting WorkflowAfter you import the .xml file, you can schedule the workflow that populates the proactive monitoring reports.

By default, the wf_pmpc_reports workflow is scheduled to run every four hours. You can reschedule it based on your requirements. You might want to schedule the workflow during times of low activity for the application services.You can also run the workflow on demand to populate the reports initially.

For information about scheduling and running the workflow, see the PowerCenter Workflow Guide.

76 Appendix C: Configure Reporting

A p p e n d i x D

Installation and Configuration Checklist

This appendix includes the following topics:

• Installation and Configuration Checklist Overview, 77

• Before You Install, 77

• Proactive Monitoring for PowerCenter Installation, 78

• After You Install Checklist, 78

Installation and Configuration Checklist OverviewThe installation and configuration checklist summarizes the tasks that you must perform to complete an installation.

Before You InstallComplete the following tasks before you install Proactive Monitoring for PowerCenter:

Read the Release Notes for updates to installation process and support changes.

Verify system and disk space requirements to install Proactive Monitoring for PowerCenter.

Prepare the databases:

•Create a read-only user for the PowerCenter repository database.

•Create a database for the Proactive Monitoring repository.

Plan the installation to decide which tasks you want the installer to perform.

Download and extract the following installation files:

•Proactive Monitoring for PowerCenter

•Command line utilities

Verify the license key.

77

Configure the command line utilities:

• Install Microsoft Visual Studio on Windows.

•Copy domain files.

•Set environment variables.

•Create a PowerCenter folder to store the operations workflow.

•Configure the control file that the installer uses to import the operations workflow.

•Encrypt the password to enable secure communication for the command line utilities.

Create a system user account to perform the installation.

Record information that you need to run the installer.

Proactive Monitoring for PowerCenter InstallationUse the Proactive Monitoring for PowerCenter to install Proactive Monitoring components on a Windows or UNIX machine. You can install in graphical mode on Windows and in console mode on UNIX.

After You Install ChecklistComplete the following tasks after you install Proactive Monitoring for PowerCenter:

Configure permissions on the Proactive Monitoring repository database.

Log in to the RulePoint Console and complete the following tasks:

•Verify the installation.

•Configure the email connection.

•Configure LDAP users to receive alerts.

Log in to Real-Time Alert Manager and enable dashboard alerts.

If you run Proactive Monitoring in a secure environment, import the keytool.

If you monitor operations, configure the node agent on the machine that hosts the Informatica node.

Read the Proactive Monitoring for PowerCenter Release Guide for information about new features and changes to the release.

Configure Proactive Monitoring for PowerCenter. For more information about configuring Proactive Monitoring for PowerCenter, see the configuration guide based on the edition that you installed, either Governance or Operations.

78 Appendix D: Installation and Configuration Checklist

I n d e x

Aadd users to real-time manager 57apply hotfix

on unix 64on windows 64start the proactive monitoring instance 65stop the proactive monitoring instance 63verify minimum system requirements 62

architecture Informatica domain components 13Proactive Monitoring for PowerCenter 11proactive monitoring repository 13design components 13RulePoint topology 12

Ccommand line utilities

configuring 20Configure

LDAP 57create

users 57

Ddatabase

support changes 62disk space

requirements 16

Eemail notifications

record information for installation 26execute

permissions 55

IInformatica domain

record information for installation 24installation

planning 18process 10installing the governance edition for unix 35installing the governance edition for windows 29installing the governance edition on an operations edition for unix 39installing the governance edition on an operations edition for windows 34

installation (continued)installing the operations edition for unix 47installing the operations edition for windows 41installing the operations edition on a governance edition for unix 51installing the operations edition on a governance edition for windows 46overview 10

installation process overview 10

installer files extracting 19

Kkeystore file

record information for installation 26

Llicense key

verifying 20logging in

Real-Time Alert Manager 72PowerCenter Client 72Proactive Monitoring Console 71RulePoint console 71

MMicrosoft SQL Server

database requirements 18Microsoft Visual Studio

installing 20

Nnode agent

starting and stopping 69

Ooperating system

support changes 62Oracle

database requirements 18

Pplanning

installation 18

79

pmpasswd encrypting password 22

pmrep control file configure 22

post-install task configure repository database permisisons 55configure the email connection 56configure the node agent 59enable dashboard alerts 58import the keystore file 58verify the installation 55

PowerCenter Client logging in 72

PowerCenter repository pre-install task 16record information for installation 25

pre-install task configure command line utilities 20configure the control file 22create PowerCenter folder 21create system user account 23extract installer files 19install Microsoft Visual Studio 20prepare PowerCenter repository 16Proactive Monitoring repository 17, 18record email notifications 26record Informatica domain information 24record keystore information 26record license and installation directory 23record PowerCenter database information 25record Proactive Monitoring database information 24verify disk space requirements 16verify license key 20verify system requirements 15

Proactive Monitoring starting and stopping 69

Proactive Monitoring Console logging in 71

Proactive Monitoring repository pre-install task 17record information for installation 24

RReal-Time Alert Manager

logging in 72requirements

disk space 16revoke

user permission 55roles 57RulePoint

components 12RulePoint console

logging in 71

Sstarting and stopping

node agent 69Proactive Monitoring instance 69

support changes database 62operating system 62

system requirements pre-install task 15

80 Index

I n s t a l l a t i o n G u i d e - Informatica · PowerMart, Metadata Manager, Informatica Data...

Documents

Transcript of I n s t a l l a t i o n G u i d e - Informatica · PowerMart, Metadata Manager, Informatica Data...