Informatica Vibe Data Stream for Machine
Data (Version 2.1.0)
Installation and Configuration
Guide
Informatica Vibe Data Stream for Machine Data Installation and Configuration Guide
Version 2.1.0
May 2014
Copyright (c) 2013-2014 Informatica Corporation. All rights reserved.
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use
and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in
any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S.
and/or international Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(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 and
Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world.
All other company and product names may be trade names or trademarks of their respective owners.
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 © ejtechnologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © is International Business Machines Corporation. All rights
reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright (c) 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.
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/licenseagreements/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/krb5current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; and https://github.com/lyokato/libgeohash/blob/master/LICENSE.
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/artisticlicense-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.
This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460;
8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending.
DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the
implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is
error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and
documentation is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT
INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT
LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Part Number: VDS-ICG-21000-0001
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Chapter 1: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Installation and Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2: Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Pre-Installation Tasks Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Obtain the Vibe Data Stream License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Pre-Installation Requirements for the Administration Components. . . . . . . . . . . . . . . . . . . . . . . 3
Verify Minimum System Requirements for the Administration Components. . . . . . . . . . . . . . . 4
Verify Port Availability for the Administration Components. . . . . . . . . . . . . . . . . . . . . . . . . 4
Pre-Installation Requirements for the Vibe Data Stream Node and Agent. . . . . . . . . . . . . . . . . . . 4
Verify Minimum System Requirements for the Vibe Data Stream Node. . . . . . . . . . . . . . . . . 5
Verify Port Availability for the Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Set Up a Keystore File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Set the File Descriptor Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Extract the Installer Files on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Extract the Installer Files on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 3: Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing Vibe Data Stream in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing Vibe Data Stream in Typical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing Vibe Data Stream in Custom Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing Vibe Data Stream in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installing Vibe Data Stream in Typical Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing Vibe Data Stream in Custom Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing Vibe Data Stream in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table of Contents
i
Vibe Data Stream Node Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing the Vibe Data Stream Node in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing the Vibe Data Stream Node in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . . . 32
Installing the Vibe Data Stream Node in Silent Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installing Vibe Data Stream Nodes on Remote Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configure Passwordless SSH Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring Passwordless SSH Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Installing Vibe Data Stream Nodes on Remote Systems. . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 4: Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Post-Installation Tasks Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Start the Administrator Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Starting or Stopping the Administrator Daemon on Linux. . . . . . . . . . . . . . . . . . . . . . . . . 38
Starting or Stopping the Administrator Daemon on Windows. . . . . . . . . . . . . . . . . . . . . . . 39
Create Multiple Vibe Data Stream Node Services on Windows. . . . . . . . . . . . . . . . . . . . . . . . . 39
Start the Agent and Vibe Data Stream Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Starting or Stopping the Agent on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Starting or Stopping the Agent on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Starting or Stopping the Vibe Data Stream Node on Linux. . . . . . . . . . . . . . . . . . . . . . . . 40
Starting or Stopping the Vibe Data Stream Node on Windows. . . . . . . . . . . . . . . . . . . . . . 40
Start the Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Starting or Stopping Informatica Domain on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Starting or Stopping Informatica Domain on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Create a Vibe Data Stream Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Log In to the Administrator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Creating the Vibe Data Stream Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 5: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Uninstallation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Before You Uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Vibe Data Stream Unistallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Uninstalling Vibe Data Stream in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Uninstalling the Vibe Data Stream Node in Graphical Mode. . . . . . . . . . . . . . . . . . . . . . . 44
Uninstalling the Remote Vibe Data Stream Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 6: Troubleshooting Vibe Data Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Troubleshooting the Administrator Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Troubleshooting the Vibe Data Stream Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Troubleshooting the Administrator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Appendix A: Configuring Extended JVM Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . 47
ii
Table of Contents
Appendix B: Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table of Contents
iii
Preface
The Informatica Vibe Data Stream for Machine Data Installation and Configuration Guide is written for system
administrators who are responsible for installing the Vibe Data Stream for Machine Data product. 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 your supporting applications.
Informatica Resources
Informatica My Support Portal
As an Informatica customer, you can access the Informatica My Support Portal at
http://mysupport.informatica.com.
The site contains product information, user group information, newsletters, access to the Informatica
customer support case management system (ATLAS), the Informatica How-To Library, the Informatica
Knowledge Base, Informatica Product Documentation, and access to the Informatica user community.
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you
have questions, comments, or ideas about this documentation, contact the Informatica Documentation team
through email at [email protected]. We will use your feedback to improve our
documentation. Let us know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your
product, navigate to Product Documentation from http://mysupport.informatica.com.
Informatica Web Site
You can access the Informatica corporate web site at http://www.informatica.com. The site contains
information about Informatica, its background, upcoming events, and sales offices. You will also find product
and partner information. The services area of the site includes important information about technical support,
training and education, and implementation services.
Informatica How-To Library
As an Informatica customer, you can access the Informatica How-To Library at
http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more
iv
about Informatica products and features. It includes articles and interactive demonstrations that provide
solutions to common problems, compare features and behaviors, and guide you through performing specific
real-world tasks.
Informatica Knowledge Base
As an Informatica customer, you can access the Informatica Knowledge Base at
http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known
technical issues about Informatica products. You can also find answers to frequently asked questions,
technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge
Base, contact the Informatica Knowledge Base team through email at [email protected].
Informatica Support YouTube Channel
You can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The
Informatica Support YouTube channel includes videos about solutions that guide you through performing
specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel,
contact the Support YouTube team through email at [email protected] or send a tweet to
@INFASupport.
Informatica Marketplace
The Informatica Marketplace is a forum where developers and partners can share solutions that augment,
extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions
available on the Marketplace, you can improve your productivity and speed up time to implementation on
your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.
Informatica Velocity
You can access Informatica Velocity at http://mysupport.informatica.com. 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 have questions, comments, or ideas
about Informatica Velocity, contact Informatica Professional Services at [email protected].
Informatica Global Customer Support
You can contact a Customer Support Center by telephone or through the Online Support.
Online Support requires a user name and password. You can request a user name and password at
http://mysupport.informatica.com.
The telephone numbers for Informatica Global Customer Support are available from the Informatica web site
at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.
Preface
v
CHAPTER 1
Installation and Configuration
This chapter includes the following topics:
•
Installation and Configuration Overview, 1
•
Installation Tasks, 2
Installation and Configuration Overview
An Informatica Vibe Data Stream for Machine Data (VDS) deployment consists of the VDS Node, the
Administrator Daemon and Informatica Administrator for VDS (the Administrator tool).
The following figure shows a sample VDS deployment:
A VDS Node is a Java program within which sources and targets exist. You can run multiple source services
and target services on a single node. Source services collect and dispatch data from a source data store,
1
such as a collection of log files. Target services receive and write that data to a target data store, such as a
Hadoop Distributed File System (HDFS) cluster. Source services typically run on the host on which the data
is stored or generated, while target services run on hosts that have access to the target data store.
You install the VDS Node on all the hosts on which you want to run source services or target services. The
installation process is the same on all the hosts, irrespective of whether you run a source service or target
service on it. The VDS Node gets the plugins from the Administrator Daemon, and the configuration and VDS
license details from Apache ZooKeeper. The VDS Node installation process also installs an Agent. The Agent
communicates with the Administrator Daemon and sends VDS Node states and statistics that you can use to
monitor VDS entities.
The Administrator Daemon sends VDS Node configuration and VDS license details to Apache ZooKeeper. It
also collects statistics and state information from all Agents, aggregates the information, and sends them to
the Administrator tool. The Administrator Daemon runs an HTTP server and has an embedded H2 database.
The VDS Nodes and Agents use the HTTP server to fetch configuration and libraries from the Administrator
Daemon. The database stores configuration details. The Administrator Daemon installation process also
installs the UM Topic Resolution Daemon (LBMRD). The LBMRD enables communication between the
Administrator Daemon, Agent, and the Administrator tool.
The Administrator tool is a web-based interface that you can use to create and deploy data flows and monitor
VDS entities. You can install the Administrator Daemon and the Administrator tool on a single host.
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
For more information about the components in the VDS deployment, see the Informatica Vibe Data Stream
for Machine Data User Guide.
Installation Tasks
To install VDS, perform the following tasks:
1.
Complete the pre-installation tasks to ensure that you can install the VDS components.
2.
Get the VDS license key.
3.
Install the the administration components, which include the Administrator Daemon, Administrator tool,
and Apache ZooKeeper, and the VDS Node.
4.
Complete the post-installation tasks. Start the VDS Node, Agent, and administration components.
After you complete the installation process, log in to the Administrator tool and create and configure the Vibe
Data Stream service.
2
Chapter 1: Installation and Configuration
CHAPTER 2
Pre-Installation Tasks
This chapter includes the following topics:
•
Pre-Installation Tasks Overview, 3
•
Obtain the Vibe Data Stream License Key, 3
•
Pre-Installation Requirements for the Administration Components, 3
•
Pre-Installation Requirements for the Vibe Data Stream Node and Agent, 4
•
Set Up a Keystore File, 5
•
Set the File Descriptor Limit, 6
•
Extract the Installer Files, 6
Pre-Installation Tasks Overview
Perform the pre-installation tasks for the VDS Node, Administrator Daemon, and Administrator tool.
VDS requires Apache ZooKeeper to store configuration. If you already have ZooKeeper installed, you can
use it for your configuration. If you have an earlier version, install ZooKeeper for VDS.
Obtain the Vibe Data Stream License Key
Contact Informatica Global Customer Support for the license key.
Pre-Installation Requirements for the Administration
Components
Perform the pre-installation tasks on the machine hosting the administration components.
3
Verify Minimum System Requirements for the Administration
Components
Verify that the machine where you install the administration components meets the system 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 following table describes the minimum system requirements for the administration components:
Processor
RAM
Disk Space
Operating System
4 CPU Cores
2.5 GB
2.5 GB
Red Hat Linux, Windows
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
Verify Port Availability for the Administration Components
The installer sets up the ports for the administration components, and it designates the ports to use on the
host where you install the them.
You can specify the port numbers to use for the administration components or you can use the default port
numbers provided by the installer. Verify that the port numbers are available on the machines where you
install the administration components.
The following table describes the ports used by the administration components:
Port Type
Description
Administrator Daemon
HTTP port
Port on which the Administrator Daemon runs an HTTP server from which the Agent
and VDS Node fetch the configurations. Default is 15381.
Topic Resolution
Daemon (LBMRD) port
Port for the Topic Resolution Daemon (LBMRD). Default is 15380.
Administrator tool port
Port number used by the Administrator tool. Default port in Windows is 7009. Default
port in Linux is 7008.
Administrator tool
shutdown port
Port number that controls server shutdown for the Administrator tool. The
Administrator tool listens for shutdown commands on this port.
Pre-Installation Requirements for the Vibe Data
Stream Node and Agent
Perform the pre-installation tasks on each machine hosting the VDS Node and Agent, since you have to
install VDS Nodes and Agents on multiple machines.
Note: The VDS Node installation process also installs an Agent that you can use to monitor VDS entities.
4
Chapter 2: Pre-Installation Tasks
Verify Minimum System Requirements for the Vibe Data Stream
Node
Verify that the machines where you install the VDS Node meet the system 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 following table describes the minimum system requirements for the VDS Node:
Processor
RAM
Disk Space
Operating System
2 CPU Cores
128 MB
128 MB to run the VDS Node
Red Hat Linux, Windows
300 MB to run the installer
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
Verify Port Availability for the Agent
The installer sets up the port for the Agent.
Verify that the default port number for the Agent set by the installer is available on the machines hosting VDS
nodes. You can specify a different port number for each Agent during configuration. If you do not use the
default Agent port number, verify that the port numbers you want to use are available in the individual
machines.
The following table describes the port used by the Agent:
Port Type
Description
Agent port
Port the Agent uses to communicate with the Administrator Daemon. Default
port is 15384.
Set Up a Keystore File
During installation, you can configure Informatica to use SSL certificates for secure communication between
the VDS components. The installer can generate a self-signed certificate, or you can provide the location of a
certificate signed by a certification authority.
You can use the keytool utility to generate a keystore file to store the SSL keys and certificates for a secure
connection. Keytool is a key and certificate management utility used to generate and administer SSL keys
and certificates. The keys and certificates are stored in a keystore file. You can use a self-signed certificate
or one signed by a certification authority (CA). You must provide SSL certificates in PEM format and in Java
Keystore (JKS) files. To use a certificate signed by a CA, use keytool to generate a Certificate Signing
Request (CSR) and apply for a digital identity certificate from a CA.
The Administrator Daemon and Administrator tool use the keystore files for internal and external
communication. The keystore file used by the Administrator Daemon needs a truststore file. The internal
Set Up a Keystore File
5
keystore and truststore file names should be infa_keystore.jks and infa_truststore.jks, and the directory must
contain the infa_keystore.pem and infa_truststore.pem files.
You can find the keytool utility in one of the following directories:
•
%JAVA_HOME%\jre\bin
•
InformaticaInstallDir\java\bin
For more information about using keytool, see the documentation on the following website:
http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html.
Set the File Descriptor Limit
Verify that the operating system meets the file descriptor requirement.
The Informatica service processes can use a large number of files. Set the file descriptor limit per process to
8000 or higher. The recommended limit is 16,000 file descriptors per process.
Extract the Installer Files
Before you perform the installation, extract the installer files. VDS includes installers for the Administrator
Daemon, the VDS Node, and the Administrator tool.
Extract the Installer Files on Linux
The installer files are compressed and distributed as .zip files.
VDS includes the following installer files:
•
vds-installer-linux-x86_64.zip
•
vds-node-installer-linux-x86_64.zip. The standalone VDS Node installer.
Use a native tar or GNU tar utility to extract the installer files to a directory on your machine.
You can extract the installer files in the following ways:
•
Installation DVD. Download the Informatica tar 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.
•
FTP download. Download the Informatica installation tar file from the Informatica Electronic Software
Download (ESD) site to a directory on your machine and then extract the installer files.
Extract the Installer Files on Windows
The installer files are compressed and distributed as a .zip file.
VDS includes the following installer files:
6
•
vds-installer-win-x86_64.zip.
•
vds-node-installer-win-x86_64.zip. The standalone VDS Node installer.
Chapter 2: Pre-Installation Tasks
Use a zip utility to extract the installer files to a directory on your machine. Verify that 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.
You can extract the installer files in the following ways:
•
Installation DVD. Download the Informatica .zip 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 .zip file to a directory on your machine, verify that the length of the
entire installation directory path, including the .zip file name, is 60 characters or less.
•
FTP download. Download the Informatica installation .zip file from the Informatica Electronic Software
Download (ESD) site to a directory on your machine and then extract the installer files.
Extract the Installer Files
7
CHAPTER 3
Installation
This chapter includes the following topics:
•
Installation Overview, 8
•
Installing Vibe Data Stream in Graphical Mode, 9
•
Installing Vibe Data Stream in Console Mode, 16
•
Vibe Data Stream Node Installation, 30
•
Installing Vibe Data Stream Nodes on Remote Systems, 35
Installation Overview
You can install Vibe Data Stream components in console mode on a Linux machine or in graphical mode on a
Windows machine.
When you install VDS, you install the following components:
•
Administration components. Includes the Administrator Daemon, Administrator tool, and Apache
ZooKeeper, an optional component. When you install the Administrator tool, you install the Informatica
Administrator web application that includes the domain Service Manager. After you install the Informatica
domain, you can log in to the Administrator tool to create the Vibe Data Stream Service.
•
VDS Node. The installation process installs a VDS Node and an Agent that you can use to monitor VDS
entities.
The VDS installation process includes typical and custom type installations.
You can select typical installation in the following scenarios:
•
To install all VDS components with minimum default configuration on a single machine.
•
To install the ZooKeeper that is included with the VDS installation package.
You can select custom installation in the following scenarios:
•
To choose the components you want to install and override default configuration.
•
To install the components on different machines.
•
To optionally install ZooKeeper. If you have already installed ZooKeeper, you can use provide the
configuration details during the installation process.
You can optionally set up secure communication between the VDS components. If you choose to set up
secure communication, the installer displays additional screens where you can specify the security
configuration.
8
Installing Vibe Data Stream in Graphical Mode
You can install VDS in graphical mode on Windows.
If you install VDS on the Linux platform, perform the installation in console mode or silent mode.
Installing Vibe Data Stream in Typical Mode
If you want to install all VDS components on a single machine and use the default configuration, select
Typical installation.
1.
Log in to the machine with a system user account.
2.
Begin installation. Run install.bat from the directory where you extracted the installation files.
The installer page appears.
3.
Click Next.
4.
Accept the terms of the license agreement.
5.
Click Next.
The Installation and Security Type page appears.
6.
Select the Typical installation type.
7.
To set up secure communication, storage, and configuration between the VDS components, select
Secure.
If you select Secure, the installer sets up HTTPS connection between the VDS components.
8.
Click Next.
The License and Installation Directory page appears.
9.
Enter the path and file name of the VDS license key.
10.
Enter the absolute path for the installation directory.
By default, the installer places VDS in the following location: <User Home Directory>\Informatica
\<version folder>\vds\
11.
Click Next.
The Informatica Administrator Configuration page appears.
12.
Enter the Informatica domain password.
13.
Click Next.
If you selected secure communication, storage, and configuration for the components, the Domain Secure Communication page appears. If you did not enable secure communication for the components,
Pre-Installation Summary page appears. Skip to step 20.
Installing Vibe Data Stream in Graphical Mode
9
14.
Enter the following properties to set up an HTTPS connection:
Property
Description
Enable HTTPS for Informatica Administrator
Select this option to secure the connection to
Informatica Administrator. To use unsecure HTTP
connection, clear the option.
By default, if secure communication is enabled for
the domain, the installer enables this option. You
can also enable this option even if you do not
enable secure communication for the domain.
Port
The port to use for communication between
Informatica Administrator and the Service Manager.
The default port for secure communication is 8443.
15.
Use a keystore file generated by the installer
Use a self-signed keystore file generated by the
installer. The installer creates a keystore file named
Default.keystore in the following location: <VDS
installation directory>\tomcat\conf\
Specify a keystore file and password
Use a keystore file that you create. You can use a
keystore file with a self-signed certificate or a
certificate signed by a certification authority.
Keystore password
A plain-text password for the keystore file. Required
if you use a keystore file that you create.
Keystore file directory
Location of the keystore file. Required if you use a
keystore file that you create.
Click Next.
The Domain Security - Secure Communication page appears.
16.
Specify whether to use the default Informatica SSL certificates or to use your SSL certificates to enable
secure communication.
To use the default SSL certificates provided by Informatica, select Use the default Informatica SSL
certificate files.
To use your SSL certificate, select Specify the location of the SSL certificate files and specify the
directories where the SSL certificate files that hold the SSL certificates are located.
You can provide a self-signed certificate or a certificate issued by a certificate authority (CA). You must
provide SSL certificates in PEM format and in Java Keystore (JKS) files.
10
Chapter 3: Installation
The following table describes the parameters that you must enter for the SSL certificate files:
Property
Description
Keystore file directory
Directory that contains the keystore files. The
directory must contain files named infa_keystore.jks
and infa_keystore.pem.
If the keystore files that you receive from the
certificate authority (CA) has a different name, you
must rename it to infa_keystore.jks and
infa_keystore.pem.
Keystore password
Password for the keystore infa_keystore.jks.
Truststore file directory
Directory that contains the truststore files. The
directory must contain files named
infa_truststore.jks and infa_truststore.pem.
If the truststore files that you receive from the
certificate authority (CA) have a different name, you
must rename it to infa_truststore.jks and
infa_truststore.pem.
Truststore password
17.
Password for the infa_truststore.jks file.
Click Next.
The Domain Security - Encryption Key page appears.
18.
Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain.
The following table describes the encryption key parameters that you must specify:
Property
Description
Keyword
Keyword to use to create a custom encryption key to
secure sensitive data in the domain. The keyword
must meet the following criteria:
-
Encryption key directory
From 8 to 20 characters long
Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces
Directory in which to store the encryption key on the
gateway node created when you create the
Informatica domain.
The default directory for the encryption key is <VDS
Installation Directory>/isp/config/
secret
19.
Click Next.
The Pre-Installation Summary page appears.
20.
Click Install.
The Post-Installation Summary page appears when the installation is complete.
Installing Vibe Data Stream in Graphical Mode
11
21.
Click Done to close the installer.
Installing Vibe Data Stream in Custom Mode
Select custom installation to choose the VDS components you want to install and override the default
configuration for each component.
1.
Log in to the machine with a system user account.
2.
Begin installation. Run install.bat from the directory where you extracted the installation files.
The installer page appears.
3.
Click Next.
4.
Accept the terms of the license agreement.
5.
Click Next.
The Installation and Security Type page appears.
6.
Select the Custom installation type.
7.
To set up secure communication, storage, and configuration between the VDS components, select
Secure.
If you select Secure, the installer sets up HTTPS connection between the VDS components.
8.
Click Next.
The Component Selection page appears.
9.
Select the VDS components you want to install.
The Component Selection page displays the following components:
Component
Description
Administration components
Select this option to install the Administrator
Daemon and Informatica Administrator.
Optionally, select Apache ZooKeeper if you want to
install the ZooKeeper that is part of the VDS
installer. If you already have ZooKeeper installed,
provide existing configuration information.
VDS Node
10.
Select this option to install the VDS Node.
Click Next.
The License and Installation Directory page appears.
11.
Enter the path and name of the VDS license key file.
12.
Enter the absolute path for the installation directory.
By default, the installer places VDS in the following location: <User Home Directory>\Informatica
\<version folder>\vds\
13.
Click Next.
The Pre-Installation Summary page appears.
14.
Click Install
If you chose to install the administration components, the Administrator components Configuration
page appears when the installation completes.
12
Chapter 3: Installation
If you did not choose to install the administration components, the VDS Node Configuration page
appears. Skip to step 17.
15.
Enter the following Administrator Daemon configuration details:
Field
Description
Unicast Topic Resolution Daemon Port
(LBMRD)
Port for the Topic Resolution Daemon (LBMRD).
Administrator Daemon HTTP port
or
Administrator Daemon HTTPS port
The default port is 15380.
Port on which the Administrator Daemon runs an HTTP or
HTTPS server from which the Agent and the Vibe Data
Stream fetch configuration.
If you selected secure communication for the components,
the Administrator Daemon runs an HTTPS server.
The default port is 15381.
Enter the following domain configuration details:
Field
Description
Domain Password
Password for the user account.
Domain Port
Port on which the domain is started. The default port is
7005.
H2 Database Port
Port of the H2 database.
Enter the network interface and Apache ZooKeeper configuration details:
Field
Description
Network Interface Address
The network interface if you are installing the components
on a multi-homed host.
The interface can have one of the following formats:
- IP Address - <IP Address>. For example, 10.65.43.75
- Interface name. For example, Eth0
Apache ZooKeeper IP Address and Ports
The IP address and port that the Administrator Daemon
uses to communicate with Apache ZooKeeper.
The IP address and port combination has the following
format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and
port combinations. If you have configured high availability
on ZooKeeper and one instance of ZooKeeper is down,
the Administrator Daemon connects to the next available
ZooKeeper server.
Note: You must specify this field if you have already
installed ZooKeeper.
16.
Click Next.
If you chose to install the VDS Node, the VDS Node Configuration page appears.
Installing Vibe Data Stream in Graphical Mode
13
17.
Enter the following VDS Node configuration details:
Field
Description
Administrator Daemon HTTP Server and
Port
or
The HTTP or HTTPS Server URL of the Administrator
Daemon. The Agent uses this URL to communicate with the
Administrator Daemon.
Administrator Daemon HTTPS Server and
Port
If you selected secure communication for the components,
the Administrator Daemon runs an HTTPS server.
The URL format has the following format:
http://<IP Address or hostname>:<port>
or
https://<IP Address or hostname>:<port>
The default port is 15381.
Host Name
Name of the machine where you install the VDS Node and
Agent.
The installer displays the host name by default. Verify that
the host name displays the name of the machine on which
you are installing the Agent.
Monitoring Port
The Agent uses this port to collect monitoring statistics from
the VDS Nodes.
The default port is 15384. You can change the port.
Optionally, if you only chose to install the VDS Node, enter the network interface and Apache ZooKeeper
configuration details:
Field
Description
Network Interface Address
The network interface if you are installing the components
on a multi-homed host.
The interface can have one of the following formats:
- IP Address - <IP Address>. For example, 10.65.43.75
- Interface name. For example, Eth0
Apache ZooKeeper IP Address and Ports
The IP address and port that the Administrator Daemon
uses to communicate with Apache ZooKeeper.
The IP address and port combination has the following
format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and
port combinations. If you have configured high availability
on ZooKeeper and one instance of ZooKeeper is down,
the Administrator Daemon connects to the next available
ZooKeeper server.
Note: You must specify this field if you have already
installed ZooKeeper.
18.
Click Next.
If you selected secure communication for the components, the Domain - Secure Communication page
appears.
If you did not enable secure communication for the components, the Post-Installation Summary page
appears. Skip to step 25.
14
Chapter 3: Installation
19.
20.
Enter the following properties to set up an HTTPS connection:
Property
Description
Use a keystore file generated by the installer
Use a self-signed keystore file generated by the
installer. The installer creates a keystore file named
Default.keystore in the following location:
<VDS installation directory>\tomcat
\conf\
Specify a keystore file and password
Use a keystore file that you create. You can use a
keystore file with a self-signed certificate or a
certificate signed by a certification authority.
Keystore password
A plain-text password for the keystore file. Required
if you use a keystore file that you create.
Keystore file directory
Location of the keystore file. Required if you use a
keystore file that you create.
Click Next.
The Security - Secure Communication page appears.
21.
Specify whether to use the default Informatica SSL certificates or to use your SSL certificates to enable
secure communication.
To use the default SSL certificates provided by Informatica, select Use the default Informatica SSL
certificate files.
To use your SSL certificate, select Specify the location of the SSL certificate files and specify the
directories where the SSL certificate files that hold the SSL certificates are located.
You can provide a self-signed certificate or a certificate issued by a certificate authority (CA). You must
provide SSL certificates in PEM format and in Java Keystore (JKS) files.
The following table describes the parameters that you must enter for the SSL certificate files:
Property
Description
Keystore file directory
Directory that contains the keystore files. The
directory must contain files named infa_keystore.jks
and infa_keystore.pem.
If the keystore files that you receive from the
certificate authority (CA) has a different name, you
must rename it to infa_keystore.jks and
infa_keystore.pem.
Keystore password
Password for the keystore infa_keystore.jks.
Installing Vibe Data Stream in Graphical Mode
15
Property
Description
Truststore file directory
Directory that contains the truststore files. The
directory must contain files named
infa_truststore.jks and infa_truststore.pem.
If the truststore files that you receive from the
certificate authority (CA) have a different name, you
must rename it to infa_truststore.jks and
infa_truststore.pem.
Truststore password
22.
Password for the infa_truststore.jks file.
Click Next.
The Domain Security - Encryption Key page appears.
23.
Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain.
The following table describes the encryption key parameters that you must specify:
Property
Description
Keyword
Keyword to use to create a custom encryption key to
secure sensitive data in the domain. The keyword
must meet the following criteria:
-
Encryption key directory
From 8 to 20 characters long
Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces
Directory in which to store the encryption key on the
gateway node created when you create the
Informatica domain.
The default directory for the encryption key is <VDS
Installation Directory>/isp/config/
secret
24.
Click Next.
The Post-Installation Summary page appears.
25.
Click Done to close the installer.
Installing Vibe Data Stream in Console Mode
You can install VDS in console mode on Linux.
16
Chapter 3: Installation
Installing Vibe Data Stream in Typical Mode
Select typical installation if you want to install all VDS components with their default settings on a single
machine. You can set up secure communication between the VDS components.
1.
Log in to the machine with a system user account.
2.
Open a command prompt window.
The installer page appears.
3.
Use a shell command line to run install.sh from the directory where you extracted the installation files.
Assign execute permissions before running the install.sh script or run the sh ./install.sh command.
The installer page appears.
4.
Press Enter.
5.
Press 1 to accept the terms of the license agreement.
The Component and Security Selection page appears.
6.
Press 1 for Typical installation.
7.
Optionally, to set up secure communication, storage, and configuration between the VDS components,
press 2.
If you enable security, the installer sets up HTTPS connection between the VDS components.
8.
Press Enter.
The License and Installation Directory page appears.
9.
Enter the path and file name of the VDS license key.
10.
Enter the absolute path for the installation directory.
By default, the installer places VDS in the following location: <User Home Directory>\Informatica
\<version folder>\vds\
11.
Press Enter.
The Informatica Administrator Configuration page appears.
12.
Enter the Informatica domain password and port.
13.
Press Enter.
If you selected secure communication, storage, and configuration for the components, the Domain Secure Communication page appears.
If you did not enable secure communication, storage, and configuration for the components, the
Informatica Administrator Configuration page appears. Skip to step 12.
14.
Specify the connection details to Informatica Administrator. Enter the following properties to set up an
HTTPS connection:
a.
Specify whether to set up a secure HTTPS connection for the Administrator tool.
The following table describes the options available to enable or disable a secure connection to
Informatica Administrator:
Option
Description
1 - Enable HTTPS for Informatica Administrator
Set up a secure connection to Administrator tool.
Installing Vibe Data Stream in Console Mode
17
b.
If you enable secure communication for the domain or if you enable HTTPS connection for the
Administrator tool, enter the keystore file and port number to use to secure the connection.
The following table describes the HTTPS connection information you must enter if you enable
HTTPS:
Option
Description
Port
Port for the HTTPS connection.
The default port for secure communication is
8443.
Keystore file
Select whether to use a keystore file generated
by the installer or a keystore file you create. You
can use a keystore file with a self-signed
certificate or a certificate signed by a certification
authority.
- 1 - Use a keystore generated by the installer
- 2 - Specify a keystore file and password
If you select to use a keystore file generated by
the installer, the installer creates a keystore file
named Default.keystore in the following location:
<VDS installation directory>\tomcat
\conf\
c.
15.
If you select to specify the keystore, enter the password and location of the keystore file.
Press Enter.
The Domain Security - Secure Communication page appears.
16.
Specify whether to use the default Informatica SSL certificates or your SSL certificates to enable secure
communication.
a.
18
Specify the SSL certificates to use.
Chapter 3: Installation
The following table describes the options available to secure the Informatica domain:
Option
Description
1 - Use the default Informatica SSL certificate
files
Use the default SSL certificates provided by
Informatica.
Note: If you do not provide an SSL certificate,
Informatica uses the same default private key for
all Informatica installations. If you use the default
Informatica keystore and truststore files, the
security of your domain could be compromised.
To ensure a high level of security for the domain,
select the option to specify the location of the
SSL certificate files.
2 - Specify the location of the SSL certificate files
Use SSL certificates that you provide. You must
specify the location of the keystore and truststore
files.
You can provide a self-signed certificate or a
certificate issued by a certificate authority (CA).
You must provide SSL certificates in PEM format
and in Java Keystore (JKS) files. Informatica
requires specific names for the SSL certificate
files for the Informatica domain. You must use the
same SSL certificates for all nodes in the domain.
Store the truststore and keystore files in a
directory accessible to all the nodes in the
domain and specify the same keystore file
directory and truststore file directory for all nodes
in the same domain.
b.
If you use your own SSL certificate, specify the location and passwords of the keystore and
truststore files.
You can provide a self-signed certificate or a certificate issued by a certificate authority (CA). You
must provide SSL certificates in PEM format and in Java Keystore (JKS) files.
The following table describes the parameters that you must enter for the SSL certificate files:
Property
Description
Keystore file directory
Directory that contains the keystore files. The
directory must contain files named
infa_keystore.jks and infa_keystore.pem.
If the keystore files that you receive from the
certificate authority (CA) has a different name,
you must rename it to infa_keystore.jks and
infa_keystore.pem.
Keystore password
Password for the keystore infa_keystore.jks.
Installing Vibe Data Stream in Console Mode
19
Property
Description
Truststore file directory
Directory that contains the truststore files. The
directory must contain files named
infa_truststore.jks and infa_truststore.pem.
If the truststore files that you receive from the
certificate authority (CA) have a different name,
you must rename it to infa_truststore.jks and
infa_truststore.pem.
Truststore password
17.
Password for the infa_truststore.jks file.
Press Enter.
The Domain Security - Encryption Key page appears.
18.
Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain.
The following table describes the encryption key parameters that you must specify:
Property
Description
Keyword
Keyword to use to create a custom encryption key to
secure sensitive data in the domain. The keyword
must meet the following criteria:
-
Encryption key directory
From 8 to 20 characters long
Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces
Directory in which to store the encryption key on the
gateway node created when you create the
Informatica domain.
The default directory for the encryption key is <VDS
Installation Directory>/isp/config/
secret
19.
Press Enter.
The Pre-Installation Summary page appears.
20.
Enter 1 to install.
The Post-Installation Summary page appears when the installation is complete.
21.
Press Enter to exit the installation process.
Installing Vibe Data Stream in Custom Mode
Select custom installation to choose the VDS components you want to install. You can override the default
configuration for each component and optionally set up secure communication between the VDS
components.
20
1.
Log in to the machine with a system user account.
2.
Open a command prompt window.
Chapter 3: Installation
3.
Use a shell command line to run install.sh from the directory where you extracted the installation files.
Assign execute permissions before running the install.sh script or run the sh ./install.sh command.
The installer page appears.
4.
Press Enter to continue.
5.
Press 1 to accept the terms of the license agreement.
The Component and Security Selection page appears.
6.
Press 2 for Custom installation.
7.
Optionally, to set up secure communication, storage, and configuration between the VDS components,
select Secure.
If you enable select Secure, the installer sets up HTTPS connection between the VDS components.
8.
Press Enter.
The Component Selection page appears.
9.
Select the VDS components you want to install.
The following table describes the components you can install from the Component Selection page:
Component
Description
1 - Administration components
Install the Administrator Daemon and
Informatica Administrator.
Optionally, select Apache ZooKeeper if you want to
install the ZooKeeper that is part of the VDS
installer. If you already have ZooKeeper installed,
provide existing configuration information.
2 - VDS Node
Select this option to install the VDS Node.
3 - All components
Install all VDS components.
The License and Installation Directory page appears.
10.
Enter the path and name of the VDS license key file.
11.
Enter the absolute path for the installation directory.
By default, the installer places VDS in the following location: <User Home Directory>\Informatica
\<version folder>\vds\
12.
Press Enter. If you chose to install the administration components, the Administrator Components
Configuration page appears.
Installing Vibe Data Stream in Console Mode
21
13.
Enter the following Administrator Daemon configuration details:
Field
Description
Administrator Daemon HTTP port
Port on which the Administrator Daemon runs an HTTP or
HTTPS server from which the Agent and the Vibe Data
Stream fetch configuration.
or
Administrator Daemon HTTPS port
If you selected secure communication for the components,
the Administrator Daemon runs an HTTPS server.
The default port is 15381.
LBMRD port
Port for the Topic Resolution Daemon (LBMRD).
The default port is 15380.
Apache ZooKeeper IP Address and Ports
The IP address and port that the Administrator Daemon
uses to communicate with Apache ZooKeeper.
The IP address and port combination has the following
format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and
port combinations. If you have configured high availability
on ZooKeeper and one instance of ZooKeeper is down,
the Administrator Daemon connects to the next available
ZooKeeper server.
Enter the following domain configuration properties:
14.
22
Field
Description
Domain Password
Password for the user account.
Domain Port
Port on which the domain is started. The default port is
7005.
H2 Database Port
Port of the H2 database.
Press Enter. If you chose to install the administration components, the VDS Node Configuration page
appears.
Chapter 3: Installation
15.
Enter the following VDS Node configuration details:
Field
Description
HTTP or HTTPS Server and Port
The HTTP or HTTPS Server URL of the Administrator
Daemon. The Agent uses this URL to communicate with the
Administrator Daemon.
If you selected secure communication for the components,
the Administrator Daemon runs an HTTPS server.
The URL format has the following format:
http://<IP Address or hostname>:<port>
or
https://<IP Address or hostname>:<port>
The default port is 15381.
Host Name
Name of the machine where you install the VDS Node and
Agent.
The installer displays the host name by default. Verify that
the host name displays the name of the machine on which
you are installing the Agent.
Monitoring port
The Agent uses this port to collect monitoring statistics from
the VDS Nodes.
The default port is 15384. You can change the port.
Apache ZooKeeper IP Addresses and Ports
The IP address and port that the VDS Node uses to
communicate with Apache ZooKeeper.
The IP address and port combination has the following
format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and
port combinations. If you have configured high availability on
ZooKeeper and one instance of ZooKeeper is down, the
VDS Node connects to the next available ZooKeeper server.
16.
Press Enter.
If you selected secure communication for the components, the Domain - Secure Communication page
appears.
If you did not enable secure communication, storage, and configuration for the components, the PreInstallation Summary page appears. Skip to step 23.
17.
Specify the connection details to Informatica Administrator. Enter the following properties to set up an
HTTPS connection:
a.
Specify whether to set up a secure HTTPS connection for the Informatica Administrator.
The following table describes the options available to enable or disable a secure connection to
Informatica Administrator:
Option
Description
1 - Enable HTTPS for Informatica Administrator
Set up a secure connection to Informatica
Administrator.
Installing Vibe Data Stream in Console Mode
23
b.
If you enable secure communication for the domain or if you enable an HTTPS connection for the
Informatica Administrator, enter the keystore file and port number to use to secure the connection.
The following table describes the HTTPS connection information you must enter if you enable
HTTPS:
Option
Description
Port
Port for the HTTPS connection.
The default port for secure communication is
8443.
Keystore file
Select whether to use a keystore file generated
by the installer or a keystore file you create. You
can use a keystore file with a self-signed
certificate or a certificate signed by a certification
authority.
- 1 - Use a keystore generated by the installer
- 2 - Specify a keystore file and password
If you select to use a keystore file generated by
the installer, the installer creates a keystore file
named Default.keystore in the following location:
<VDS installation directory>\tomcat
\conf\
c.
18.
If you select to specify the keystore, enter the password and location of the keystore file.
Press Enter.
The Domain Security - Secure Communication page appears.
19.
To enable secure communication, specify whether to use the default Informatica SSL certificates or your
SSL certificates.
a.
24
Specify the SSL certificates to use.
Chapter 3: Installation
The following table describes the options available to secure the Informatica domain:
Option
Description
1 - Use the default Informatica SSL certificate
files
Use the default SSL certificates provided by
Informatica.
Note: If you do not provide an SSL certificate,
Informatica uses the same default private key for
all Informatica installations. If you use the default
Informatica keystore and truststore files, the
security of your domain could be compromised.
To ensure a high level of security for the domain,
select the option to specify the location of the
SSL certificate files.
2 - Specify the location of the SSL certificate files
Use SSL certificates that you provide. You must
specify the location of the keystore and truststore
files.
You can provide a self-signed certificate or a
certificate issued by a certificate authority (CA).
You must provide SSL certificates in PEM format
and in Java Keystore (JKS) files. Informatica
requires specific names for the SSL certificate
files for the Informatica domain. You must use the
same SSL certificates for all nodes in the domain.
Store the truststore and keystore files in a
directory accessible to all the nodes in the
domain and specify the same keystore file
directory and truststore file directory for all nodes
in the same domain.
b.
If you use your own SSL certificate, specify the location and passwords of the keystore and
truststore files.
You can provide a self-signed certificate or a certificate issued by a certificate authority (CA). You
must provide SSL certificates in PEM format and in Java Keystore (JKS) files.
The following table describes the parameters that you must enter for the SSL certificate files:
Property
Description
Keystore file directory
Directory that contains the keystore files. The
directory must contain files named
infa_keystore.jks and infa_keystore.pem.
If the keystore files that you receive from the
certificate authority (CA) has a different name,
you must rename it to infa_keystore.jks and
infa_keystore.pem.
Keystore password
Password for the keystore infa_keystore.jks.
Installing Vibe Data Stream in Console Mode
25
Property
Description
Truststore file directory
Directory that contains the truststore files. The
directory must contain files named
infa_truststore.jks and infa_truststore.pem.
If the truststore files that you receive from the
certificate authority (CA) have a different name,
you must rename it to infa_truststore.jks and
infa_truststore.pem.
Truststore password
20.
Password for the infa_truststore.jks file.
Press Enter.
The Domain Security - Encryption Key page appears.
21.
Enter the keyword and directory for the encryption key for the Informatica domain.
Informatica uses an encryption key to secure sensitive data, such as passwords, that are stored in the
Informatica domain.
The following table describes the encryption key parameters that you must specify:
Property
Description
Keyword
Keyword to use to create a custom encryption key to
secure sensitive data in the domain. The keyword
must meet the following criteria:
-
Encryption key directory
From 8 to 20 characters long
Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces
Directory in which to store the encryption key on the
gateway node created when you create the
Informatica domain.
The default directory for the encryption key is <VDS
Installation Directory>/isp/config/
secret
22.
Press Enter.
The Pre-Installation Summary page appears.
23.
Press Enter.
The Post-Installation Summary page appears when the installation is complete.
24.
Press Enter to exit the installation process.
Installing Vibe Data Stream in Silent Mode
To install the VDS without user interaction, install in silent mode by using a properties file that contains the
installation options. The VDS installer reads the file to determine the installation options.
1.
26
Use a text editor to open and change the values of the properties in the SilentInput.properties file.
Chapter 3: Installation
The following table describes the installation properties that you can specify:
Property
Description
INSTALL_MODE
Indicates the installation mode.
If the value is 0, the components are installed in
typical mode. If the value is 1, the components are
installed in custom mode.
SECURE_MODE
Indicates if the secure communication, storage and
configuration must be enabled for the VDS
components.
If the value is 0, secure mode is not enabled. If the
value is 1, secure mode is enabled.
INSTALL_ADMINCOMPS
Indicates whether to install the Administration
components.
If the value is 0, the components are not installed. If
the value is 1, the components are installed.
INSTALL_AGENTNODE
Indicates whether to install the VDS Node.
If the value is 0, the VDS Node is not installed. If the
value is 1, the VDS Node is installed.
USER_INSTALL_DIR
The VDS installation directory. For example, C:\
\Informatica\\VDS\\2.1.0
LICENSE_KEY_LOC
The path and name of the VDS license key file.
IS_AGREED
Set this to true to accept the license agreement.
DOMAIN_PSSWD
The password to the Informatica domain.
DOMAIN_CNFRM_PSSWD
If you chose to install the Administration components, enter the following properties :
Property
Description
ADMIND_LBMRD_PORT
The LBMRD port.
ADMIND_HTTP_PORT
Port on which the Administrator Daemon runs an
HTTP or HTTPS server from which the VDS Node
and Agent fetch configuration.
Installing Vibe Data Stream in Console Mode
27
Property
Description
ZOOKEEPER_URL
The IP address and port that the Administrator
Daemon uses to communicate with Apache
ZooKeeper.
The IP address and port combination has the
following format:
<IP Address>:<port>
You can enter multiple comma-separated IP address
and port combinations. If you have configured high
availability on ZooKeeper and one instance of
ZooKeeper is down, the Administrator Daemon
connects to the next available ZooKeeper server.
H2_PORT
Port of the H2 database.
DOMAIN_PORT
Port on which the domain is started.
NETWORK_INTERFACE
Optional.
If you are installing the components on a multihomed host, specify the network interface
The interface can have one of the following formats:
- IP Address - <IP Address>. For example,
10.65.43.75
- Interface name. For example, Eth0
If you chose to install the VDS Node, enter the following properties:
Property
Description
DAEMON_URL
The HTTP Server URL of the Administrator Daemon.
The Agent uses this URL to communicate with the
Administrator Daemon.
The URL format has the following format:
http://<IP Address or
hostname>:<port>
The default port is 15381.
AGENT_HOSTNAME
Host name of the machine where you want to install
the VDS Node and Agent.
NODE_PORTNUMBER
The Agent uses this port to collect monitoring
statistics from the VDS Nodes.
The default port is 15384.
28
Chapter 3: Installation
If you chose secure communication, configuration and storage for the components, enter the following
properties:
Property
Description
HTTPS_PORT
The port number to use for the secure connection to
Informatica Administrator.
DEFAULT_HTTPS_ENABLED
Indicates whether the installer creates a keystore
file.
If the value is 1, the installer creates a keystore and
uses it for the HTTPS connection. If the value is 0,
the installer uses a keystore file that you specify.
CUSTOM_HTTPS_ENABLED
Indicates whether the installer uses an existing
keystore file.
If the value is 1, the installer uses a keystore file
that you specify.
KSTORE_PSSWD
The plain text password for the keystore file if
CUSTOM_HTTPS_ENABLED=1.
KSTORE_FILE_LOCATION
Absolute path and file name of the keystore file if
CUSTOM_HTTPS_ENABLED=1.
TLS_CUSTOM_SELECTION
Indicates whether to use SSL certificates that you
provide to enable secure communication in the
Informatica domain.
To use SSL certificates that you provide, set this
property to True.
NODE_KEYSTORE_DIR
Required if TLS_CUSTOM_SELECTION is set to
True. Directory that contains the keystore files. The
directory must contain files named infa_keystore.jks
and infa_keystore.pem.
NODE_KEYSTORE_PASSWD
Required if TLS_CUSTOM_SELECTION is set to
True. Password for the keystore infa_keystore.jks.
NODE_TRUSTSTORE_DIR
Required if TLS_CUSTOM_SELECTION is set to
True. Directory that contains the truststore files. The
directory must contain files named
infa_truststore.jks and infa_truststore.pem.
NODE_TRUSTSTORE_PASSWD
Required if TLS_CUSTOM_SELECTION is set to
True. Password for the infa_truststore.jks file.
Installing Vibe Data Stream in Console Mode
29
Property
Description
PASS_PHRASE_PASSWD
Keyword to use to create an encryption key to
secure sensitive data in the domain. The keyword
must meet the following criteria:
-
KEY_DEST_LOCATION
2.
Save the properties file.
3.
Run the silent installation.
•
In Windows: run silentInstall.bat
•
In Linux: run silentInstall.sh
From 8 to 20 characters long
Includes at least one uppercase letter
Includes at least one lowercase letter
Includes at least one number
Does not contain spaces
Directory in which to store the encryption key on the
node created during the installation.
Note: Assign execute permissions before running the install.sh script or run the sh ./install.sh command.
The silent installer runs in the background.
If you incorrectly configure the properties file or if the installation directory is not accessible, the silent
installation will fail. View the installation log file in the user home directory. For example, C:
\silentErrorLog.log. Correct the errors, and run the silent installation again.
Vibe Data Stream Node Installation
Install the VDS Node on all Linux and Windows hosts that run sources and targets.
You can install the VDS Node as part of the complete VDS installation or you can use the standalone VDS
Node installation package. If you want to install VDS Nodes on multiple machine, you can use the standalone
VDS Node. The VDS Node installation process also installs an Agent that you can use to monitor VDS
entities.
For more information about VDS entities and monitoring them, see the Vibe Data Stream for Machine Data
User Guide
Installing the Vibe Data Stream Node in Console Mode
You can install the VDS Node in console mode on Linux.
1.
Log in to the machine with a system user account.
2.
Run install.sh from the directory where you extracted the installation files. Assign execute permissions
before running the install.sh script or run the sh ./install.sh command.
3.
Enter the path to the installation directory.
By default, the installer places the VDS Node in the following location:
<User Home Directory>\Informatica\<version folder>\vds\
4.
Press Enter.
The Pre-Installation Summary page appears.
30
Chapter 3: Installation
5.
Enter the following VDS Node configuration details:
Field
Description
Administrator Daemon HTTP Server and
Port
or
The HTTP or HTTPS Server URL of the Administrator
Daemon. The Agent uses this URL to communicate with the
Administrator Daemon.
Administrator Daemon HTTPS Server and
Port
If you selected secure communication for the components,
the Administrator Daemon runs an HTTPS server.
The URL format has the following format:
http://<IP Address or hostname>:<port>
or
https://<IP Address or hostname>:<port>
The default port is 15381.
Host Name
Name of the machine where you install the VDS Node and
Agent.
The installer displays the host name by default. Verify that
the host name displays the name of the machine on which
you are installing the Agent.
Monitoring port
The Agent uses this port to collect monitoring statistics from
the VDS Nodes.
The default port is 15384. You can change the port.
Optionally, to enable secure communication, storage, and configuration, press 1.
Enter the network interface and Apache ZooKeeper configuration details:
Field
Description
Network Interface Address
Optional. The network interface if you are installing the
components on a multi-homed host.
The interface can have one of the following formats:
- IP Address - <IP Address>. For example, 10.65.43.75
- Interface name. For example, Eth0
Apache ZooKeeper IP Address and Ports
The IP address and port that the Administrator Daemon
uses to communicate with Apache ZooKeeper.
The IP address and port combination has the following
format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and
port combinations. If you have configured high availability
on ZooKeeper and one instance of ZooKeeper is down,
the Administrator Daemon connects to the next available
ZooKeeper server.
Note: You must specify this field if you have already
installed ZooKeeper.
6.
Press Enter.
The Post-Installation Summary page appears when the installation is complete.
7.
Press Enter to exit the installation process.
Vibe Data Stream Node Installation
31
Installing the Vibe Data Stream Node in Graphical Mode
You can install the VDS Node in graphical mode on Windows.
1.
Log in to the machine with a system user account.
2.
Begin installation. Run install.bat from the directory where you extracted the installation files.
The installer page appears.
3.
Click Next.
The Installation and Security Type page appears.
4.
Enter the absolute path for the installation directory.
By default, the installer places VDS in the following location: <User Home Directory>\Informatica
\<version folder>\vds\
5.
Click Next.
The Pre-Installation Summary page appears.
6.
Click Install
7.
Enter the following VDS Node configuration details:
Field
Description
Administrator Daemon HTTP Server and
Port
or
The HTTP or HTTPS Server URL of the Administrator
Daemon. The Agent uses this URL to communicate with the
Administrator Daemon.
Administrator Daemon HTTPS Server and
Port
If you selected secure communication for the components,
the Administrator Daemon runs an HTTPS server.
The URL format has the following format:
http://<IP Address or hostname>:<port>
or
https://<IP Address or hostname>:<port>
The default port is 15381.
Host Name
Name of the machine where you install the VDS Node and
Agent
The installer displays the host name by default. Verify that
the host name displays the name of the machine on which
you are installing the Agent.
Monitoring port
The Agent uses this port to collect monitoring statistics from
the VDS Nodes.
The default port is 15384. You can change the port.
Optionally, enable secure communication, storage, and configuration.
32
Chapter 3: Installation
Enter the network interface and Apache ZooKeeper configuration details:
Field
Description
Network Interface Address
Optional. The network interface if you are installing the
components on a multi-homed host.
The interface can have one of the following formats:
- IP Address - <IP Address>. For example, 10.65.43.75
- Interface name. For example, Eth0
Apache ZooKeeper IP Address and Ports
The IP address and port that the Administrator Daemon
uses to communicate with Apache ZooKeeper.
The IP address and port combination has the following
format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and
port combinations. If you have configured high availability
on ZooKeeper and one instance of ZooKeeper is down,
the Administrator Daemon connects to the next available
ZooKeeper server.
Note: You must specify this field if you have already
installed ZooKeeper.
8.
Click Next.
The Post-Installation Summary page appears.
9.
Click Done to close the installer.
Installing the Vibe Data Stream Node in Silent Node
To install the VDS Node without user interaction, install in silent mode by using a properties file that contains
the installation options. The VDS Node installer reads the file to determine the installation options.
1.
Use a text editor to open and change the values of the properties in the SilentInput.properties file.
The following table describes the installation properties that you can change:
Property
Description
USER_INSTALL_DIR
Agent installation directory. For example, C:\
\Informatica\\2.1.0\\VDS.
AGENT_HOSTNAME
Host name of the machine where you want to install
the VDS Node and Agent.
NODE_PORTNUMBER
The Agent uses this port to collect monitoring
statistics from the VDS Nodes.
The default port is 15384.
Vibe Data Stream Node Installation
33
Property
Description
DAEMON_URL
The HTTP Server URL of the Administrator Daemon.
The Agent uses this URL to communicate with the
Administrator Daemon.
The URL format has the following format:
<IP Address or hostname>:<port>
The default port is 15381.
ZOOKEEPER_URL
The IP address and port that the VDS Node uses to
communicate with Apache ZooKeeper.
The IP address and port combination has the
following format:
<IP Address>:<port>
You can enter multiple comma-separated IP address
and port combinations. If you have configured high
availability on ZooKeeper and one instance of
ZooKeeper is down, the VDS Node connects to the
next available ZooKeeper server.
Note: Do not use the http prefix with the IP address
and port combination.
SECURE_MODE
Indicates if the secure communication, storage and
configuration must be enabled for the VDS Node.
If the value is 0, secure mode is not enabled. If the
value is 1, secure mode is enabled.
NETWORK_INTERFACE
Optional. The network interface if you are installing
the components on a multi-homed host.
The interface can have one of the following formats:
- IP Address - <IP Address>. For example,
10.65.43.75
- Interface name. For example, Eth0
2.
Save the properties file.
3.
Run the silent installation.
•
In Windows: run silentInstall.bat
•
In Linux: run silentInstall.sh
Note: Assign execute permissions before running the install.sh script or run the sh ./install.sh command.
The silent installer runs in the background. The silent installation is complete when the nodeinstall.out and agent-install.out are created in the <VDS Node Installation Directory>\logs
directory.
The silent installation fails if you incorrectly configure the properties file or if the installation directory is
not accessible. View the installation log file in the user home directory. For example, C:
\silentErrorLog.log. Correct the errors, and run the silent installation again.
34
Chapter 3: Installation
Installing Vibe Data Stream Nodes on Remote
Systems
You can install VDS Nodes on remote Linux systems in silent mode.
After you install Vibe Data Stream, the installation process creates the remote VDS Node installation
directory remote_node_utils, in the VDS installation directory. Place the vds-node-installer-linuxx86_64.zip file in this directory before you perform remote installation.
Before you run the remote installation, enable passwordless connection between the machines where you
install the administration components and the machines where you install the VDS Nodes.
Configure Passwordless SSH Connections
Configure passwordless connections between the machines where you install the administration components
and the machines where you install the VDS Node. Because the remote installation process runs in silent
mode, you might want to configure passwordless SSH connections to avoid asking for input from users.
To configure passwordless connections, you can create an SSH key pair on the machine where you install
the administration components. The key pair consists of a public key and a private key. Copy the public key
to all the remote hosts.
Configuring Passwordless SSH Connections
Generate a pair of authentication keys on the host where you install the Administrator Daemon and
Administrator tool.
1.
To generate a pair of authentication keys, enter the following command:
ssh-keygen -t rsa
This command creates a public key and private key.
2.
To create an SSH directory on the remote system if it does not exist, enter the following command
ssh $USER@<Remote machine> mkdir -p ~/.ssh
3.
To copy the public key to the remote machines, enter the following command:
cat ~/.ssh/id_rsa.pub | ssh $USER@<Remote machine> 'cat >> .ssh/authorized_keys'
After you configure the passwordless connection, you can run the remote node installation on remote
systems.
Installing Vibe Data Stream Nodes on Remote Systems
To install VDS Nodes on remote systems in silent mode, use a properties file that contains the installation
options. The VDS Node remote installer reads the file to determine the installation options.
1.
Navigate to the remote_node_utils directory.
2.
Use a text editor to open and change the values of the properties in the SilentInput.properties file.
Installing Vibe Data Stream Nodes on Remote Systems
35
The following table describes the installation properties that you can change:
Property
Description
USER_INSTALL_DIR
VDS Node installation directory. For example, /
home/$USER/Informatica/2.1.0/vds
AGENT_HOSTNAME
Host name of the machine where you want to install
the VDS Node and Agent.
The default value is `hostname`.
NODE_PORTNUMBER
The port that the VDS Node uses to send monitoring
data.
The default port is 15384.
DAEMON_URL
The HTTP Server URL of the Administrator Daemon.
The Agent uses this URL to communicate with the
Administrator Daemon.
The URL format has the following format:
<IP Address or hostname>:<port>
The default port is 15381.
ZOOKEEPER_URL
The IP address and port that the VDS Node uses to
communicate with Apache ZooKeeper.
The IP address and port combination has the
following format:
<IP Address>:<port>
You can enter multiple comma-separated IP address
and port combinations. If you have configured high
availability on ZooKeeper and one instance of
ZooKeeper is down, the VDS Node connects to the
next available ZooKeeper server.
Note: Do not use the http prefix with the IP address
and port combination.
SECURE_MODE
Indicates if the secure communication, storage and
configuration must be enabled for the VDS Node.
If the value is 0, secure mode is not enabled. If the
value is 1, secure mode is enabled.
NETWORK_INTERFACE
Optional. The network interface if you are installing
the components on a multi-homed host.
The interface can have one of the following formats:- IP Address - <IP Address>. For example,
10.65.43.75
- Interface name. For example, Eth02
36
3.
Save the properties file.
4.
Use a text editor to open the hostsList and add the host names or IP addresses of the remote
machines, separated by newline characters.
Chapter 3: Installation
5.
To run the remote installation, use the following command:
./remote-node.sh install
The silent installer runs in the background. The silent installation is complete when the nodeinstall.out and vds-install.out are created in the <VDS Node Installation Directory>\node
\logs and <VDS Node Installation Directory>\agent\logs directories respectively.
The silent installation fails if you incorrectly configure the properties file or if the installation directory is
not accessible. View the installation log file in the user home directory. For example, /home/<username>/
silentErrorLog.log. Correct the errors, delete the files from the directory where the installation failed,
and run the silent installation again.
Installing Vibe Data Stream Nodes on Remote Systems
37
CHAPTER 4
Post-Installation Tasks
This chapter includes the following topics:
•
Post-Installation Tasks Overview, 38
•
Start the Administrator Daemon, 38
•
Create Multiple Vibe Data Stream Node Services on Windows, 39
•
Start the Agent and Vibe Data Stream Node, 39
•
Start the Informatica Domain, 40
•
Create a Vibe Data Stream Service, 41
Post-Installation Tasks Overview
After you install the VDS components and Apache ZooKeeper, start the VDS components and create the
VDS service.
Start the Administrator Daemon
After you complete the installations, use the admind.sh to start the Administrator Daemon. The admind.sh
script starts the Administrator Daemon, LBMRD, and Apache ZooKeeper.
The admind.sh script starts the ZooKeeper only if you install the ZooKeeper that is part of the VDS installer.
Starting or Stopping the Administrator Daemon on Linux
To start the Administrator Daemon, run the following command from the <Administrator Daemon
installation directory>/admind/bin folder:
./admind.sh start
To stop the Administrator Daemon, run the following command:
./admind.sh stop
The admind.sh also starts or stops the LBMRD and Apache ZooKeeper.
38
Starting or Stopping the Administrator Daemon on Windows
You can start and stop the Administrator Daemon service from the Windows Administrative Tools.
1.
From the Windows Administrative Tools, select Services.
2.
Right-click the Informatica Administrator Daemon service.
3.
Choose to start or stop the service.
Create Multiple Vibe Data Stream Node Services on
Windows
By default, the VDS Node installation process creates one Windows service. If you want to configure high
availability, you can create multiple VDS Node services.
To create a VDS Node service run the following command from the <VDS Node installation directory>
\node\bin folder:
node.bat install <node name>
Note: Do not include spaces in the node name.
To create multiple services, run the command multiple times.
Start the Agent and Vibe Data Stream Node
After you complete the installation, start the Agent and VDS Node on all hosts you installed them on. The
installation process does not automatically start the Agent and VDS Node. When you start the VDS Node, it
gets the plug-ins from the Administrator Daemon and configuration information from Apache ZooKeeper.
Note: When you start the Agent and VDS Node, verify that you have a valid license. If you do not have the
license, the Agent and VDS Node start, but do not send or receive information.
Starting or Stopping the Agent on Linux
To stop the Agent, run the following command from the <VDS Node installation directory>/agent/bin
folder:
./agent.sh start
To stop the Agent, run the following command:
./agent.sh stop
Starting or Stopping the Agent on Windows
You can use the Services window in the Control Panel to start and stop the Agent service.
1.
From the Windows Administrative Tools, select Services.
2.
Right-click the Informatica Agent.
3.
Choose to start or stop the service.
Create Multiple Vibe Data Stream Node Services on Windows
39
Starting or Stopping the Vibe Data Stream Node on Linux
To start the VDS Node, run the following command from the <VDS Node installation directory>/
node/bin folder:
./node.sh start <node name>
To stop the VDS Node, run the following command:
./node.sh stop <node name>
To start a VDS Node installed on a remote machine, run the following command:
./remote-node.sh start <node name>
To stop a VDS Node installed on a remote machine, run the following command:
./remote-node.sh stop <node name>
Note: <node name> is optional. If you do not specify <node name>, the node name is set to the host name.
Starting or Stopping the Vibe Data Stream Node on Windows
You can start and stop the VDS Node service from the Windows Administrative Tools.
1.
From the Windows Administrative Tools, select Services.
2.
Right-click the Informatica VDS Node <node name>.
3.
Choose to start or stop the service.
Start the Informatica Domain
To start the Informatica domain, use a command line program.
Starting or Stopping Informatica Domain on Linux
On Linux, run infaservice.sh to start and stop the Informatica domain. By default, infaservice.sh is installed in
the following directory:
<Informatica Administrator Tool installation directory>/tomcat/bin
1.
Go to the directory where infaservice.sh is located.
2.
At the command prompt, enter the following command to start the domain:
./infaservice.sh startup
To stop the domain, enter the following command:
./infaservice.sh shutdown
The Administrator tool might take a few minutes to start.
Note: If you use a softlink to specify the location of infaservice.sh, set the INFA_HOME environment
variable to the location of the Informatica installation directory.
Starting or Stopping Informatica Domain on Windows
On Windows, run infaservice.bat to start and stop the Informatica domain.
1.
40
Go to the directory where infaservice.bat is located.
Chapter 4: Post-Installation Tasks
By default, infaservice.bat is installed in the following directory:
<Informatica Administrator Tool installation directory>/tomcat/bin
2.
At the command prompt, enter the following command to start the domain:
infaservice.bat startup
To stop the domain, enter the following command:
infaservice.bat shutdown
The Administrator tool might take a few minutes to start or stop.
Create a Vibe Data Stream Service
Create the Vibe Data Stream service in the Administrator tool to create and monitor VDS data flows.
For more information about VDS data flows, see the Vibe Data Stream for Machine Data User Guide.
Log In to the Administrator Tool
You must have a administrator privileges to log in to Administrator tool.
1.
Start a web browser.
Informatica recommends that you use Google Chrome.
2.
In the Address field, enter the URL for the Administrator tool:
http://<host>:<port>/administrator
3.
On the login page, enter the user name and password.
4.
Click Log In.
Creating the Vibe Data Stream Service
Create the VDS Service in the Administrator tool.
1.
In the Administrator tool, click the Domain tab.
2.
Click Actions > New > VDS Service.
The New VDS Service window appears.
3.
Enter the following general properties for the service:
Property
Description
Name
Name of the VDS Service. The name is not case sensitive and must be unique
within the Informatica domain. The characters must be compatible with the code
page of the associated repository. The name cannot exceed 128 characters or
begin with @. It also cannot contain spaces or the following special characters:
`~%^*+={}\;:'"/?.,<>|!()][
Description
Description of the service. The description cannot exceed 765 characters.
Create a Vibe Data Stream Service
41
Property
Description
Location
Name of the Informatica domain and folder where you want to create the
service. Optionally, click Browse to select another folder in the Informatica
domain.
License
License assigned to the service. You do not need to select a license as it is
associated during installation.
Assign
Node on which the service runs. Select Single Node to assign the service to a
node.
Node
The host name or node in the Informatica domain where the service runs.
4.
Click Finish.
5.
Select the created Vibe Data Stream service in the Navigator of the Administrator tool.
6.
Click Apply Licenses in the Contents panel to register the service with the license.
Note: Start the Administrator Daemon and Apache ZooKeeper before you apply the license.
42
Chapter 4: Post-Installation Tasks
CHAPTER 5
Uninstallation
This chapter includes the following topics:
•
Uninstallation Overview, 43
•
Before You Uninstall, 43
•
Vibe Data Stream Unistallation, 44
Uninstallation Overview
The VDS installation process creates uninstallation directories that include uninstallers for each of VDS
components that you install. To completely uninstall VDS, you must uninstall the Administration components,
VDS Node, and Apache ZooKeeper. The uninstallation process deletes all files and clears all configurations
from a machine.
The following table lists the default uninstallation directories:
Component
Uninstallation Directory Name
VDS
<VDS Node installation directory>/Uninstaller_VDS
VDS Node
<VDS Node installation directory>/Uninstaller_node
To uninstall the components, use the uninstaller created during the installation.
The uninstallation mode depends on the mode used to install the components. For example, if you install the
Administrator Daemon in console, when you run the uninstaller, it runs in console mode.
Before You Uninstall
Before you uninstall VDS, stop all VDS components. The uninstallation process cannot remove the files that
are being used by a component that is running.
43
Vibe Data Stream Unistallation
You can uninstall VDS in graphical mode on Windows and in console mode on Linux.
Uninstalling Vibe Data Stream in Console Mode
You can uninstall the VDS in console mode on Linux.
1.
Go to the following directory:
<VDS installation directory>/Uninstaller_VDS
2.
Run the ./uninstall.sh command.
3.
Press Enter to continue with the uninstallation.
Uninstalling the Vibe Data Stream Node in Graphical Mode
You can uninstall the VDS Node in graphical mode on Linux or Windows. Before you run the uninstaller, stop
the VDS Node.
1.
Go to the following directory:
<VDS Node installation directory>/node/Uninstaller_node
2.
Begin uninstallation.
On Windows:
a.
Run uninstaller.exe to uninstall the VDS Node.
b.
Click Uninstall to continue with the uninstallation.
On Linux:
a.
Type the following command to run the uninstaller:
./uninstall.sh
b.
Press Enter to continue with the uninstallation.
Uninstalling the Remote Vibe Data Stream Node
You can uninstall the VDS Node on a remote machine in console mode on Linux. Before you run the
uninstaller, stop the VDS Node.
1.
Go to the following directory:
<remote_node_utils>
Note: Ensure that the SilentInput.properties file and the hostsList are present in this directory.
2.
44
Run the ./remote-node.sh uninstall command to uninstall the VDS Node.
Chapter 5: Uninstallation
CHAPTER 6
Troubleshooting Vibe Data
Stream
This chapter includes the following topics:
•
Troubleshooting the Administrator Daemon, 45
•
Troubleshooting the Vibe Data Stream Node, 45
•
Troubleshooting the Administrator Tool, 46
Troubleshooting the Administrator Daemon
The Administrator Daemon process stops unexpectedly when I try to start the Administrator Daemon.
This error might occur if you change the host name of the machine on which you install the Administrator
Daemon. After installation, do not change the host name of the machine on which you install the
Administrator Daemon. If you change the host name, you must reinstall the Administrator Daemon.
Troubleshooting the Vibe Data Stream Node
The VDS Node does not start after installation.
This error can occur if you have configured the VDS Node incorrectly. Check the <VDS Installation
Directory>/node/logs/<node-name>.out log file for errors and correct them. Also see the <VDS
Installation Directory>/node/logs/<node name>-node.log for other errors.
45
Troubleshooting the Administrator Tool
When I run the Administrator tool installation, the installer stops responding because the installer cannot
ping the domain.
This error might occur if you are using an unsupported operating system.
Verify that you are using a supported operating system. Stop the installation process and install the
Administrator tool again.
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
When I run the Administrator tool installation, the installation process completes successfully but the
domain is not created.
This error might occur if you are using an unsupported operating system.
Verify that you are using a supported operating system.
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
Contact Informatica Global Customer Support if the error persists.
The domain creation fails during installation. The exit code 255 appears in the
Informatica_Administrator_for_VDS_2.0_Service.log file.
This error might occur if you have not installed the Informatica patches and libraries. Verify that all the
Informatica patches and libraries are installed.
For more information about product requirements and supported platforms, see the Product Availability Matrix
on the Informatica My Support Portal:
https://mysupport.informatica.com/community/my-support/product-availability-matrices
When I run the Administrator tool installation, the installer fails because the installer cannot ping the
domain or start the Informatica service. The following message appears in the catalina.out log file:
Argument passed to the API is invalid.
Verify that the machine host name where you install the Administrator tool does not contain the underscore
(_) character. If the machine host name contains the underscore character, change the host name to one that
does not contain the underscore character.
46
Chapter 6: Troubleshooting Vibe Data Stream
APPENDIX A
Configuring Extended JVM
Parameters
You can configure the JVM parameter heap size in the Administrator Daemon configuration. The heap size
depends on the number of applications in your deployment.
By default the heap size allocated to Administrator Daemon is 2 GB. To change the heap size add the
following configuration in the admind.cnf located in the <Administrator Daemon Installation
Directory>/admind/config directory:
jvmOptions="-Xmx4G -Xms4G"
where
•
-Xmx4G is the maximum heap size
•
-Xms4G is the minimum heap size
47
APPENDIX B
Glossary
Administrator Daemon
Daemon process that facilitates the creation, management, deployment and undeployment of data flows
through the Administrator tool. The Administrator Daemon also aggregates statistics and state information
from Agents running on the hosts in the deployment, and sends them to the Administrator tool.
Agent
The Agent collects information about state and statistics from the VDS Node and communicates that
information to the Administrator Daemon over the HTTP port configured for the daemon. The Agent is
installed when you install a VDS Node.
data flow
Defines the path of data from source services to target services through zero or more transformations. You
can create, design, deploy, and undeploy data flows in the Administrator tool. Data flows can be simple data
flows or complex data flows such as, one-to-many, many-to-one, and many-to-many.
Informatica Administrator
Informatica Administrator (Administrator tool) is a web application that you can use to manage, monitor,
deploy, and undeploy data flows.
receiver type ID
A 32-bit value that uniquely identifies the Ultra Messaging receiver.
source service
A VDS Node contains one or more specialized threads that work together to transfer data from the
application host to a target data store or data engine. Source services are threads that consume and publish
events generated by the source application. Source services publish data in the form of Ultra Messaging
messages.
target service
Target services are the threads that subscribe to data published by source services and write the data to the
target. Target services run on hosts that have access to the target.
topic resolution domain
The domain of UDP multicast or unicast connectivity that allows Ultra Messaging topic resolution to occur.
Topic resolution enables receivers discover sources.
unicast topic resolution daemon (LBMRD)
A daemon process that performs the same topic resolution activities as multicast topic resolution. By default,
Ultra Messaging expects multicast connectivity between sources and targets. When only unicast connectivity
is available, you must run one or more unicast topic resolution daemons (LBMRD).
VDS Node
A VDS Node is a Java program within which sources and targets run. You can run multiple sources and
targets on a single node. You can also configure multiple nodes to run on a host.
Appendix B: Glossary
49
INDEX
A
L
Administrator Daemon
starting 38
stopping 38
Administrator tool
logging in 41
License key 3
H
HTTPS
installation requirements 5
I
Informatica Domain
starting 40
starting and stopping on Windows 40
stopping 40
Installation
overview 8
VDS in console mode 17, 20
VDS in custom mode 12, 20
VDS in graphical mode 9, 12
VDS in silent mode 26
VDS in typical mode 9, 17
VDS Node in console mode 30
VDS Node in graphical mode 32
VDS Node in silent mode 33
VDS Node on Linux 30
VDS Node on Windows 32
VDS on Linux 17, 20
VDS on Windows 9, 12
Installation and Configuration
Overview 1
installation requirements
keystore file 5
J
Java Development Kit
version 3
K
keystore file
installation requirements 5
50
S
Start
Administrator Daemon 38
Informatica Domain 40
VDS Node 40
Stop
Administrator Daemon 38
Informatica Domain 40
VDS Node 40
T
Troubleshooting
Administrator Daemon installation 45
Administrator tool installation 46
VDS Node installation 45
U
Uninstallation
Remote VDS Node in console mode 44
Remote VDS Node on Linux 44
VDS Node in graphical mode 44
VDS Node on Linux 44
VDS Node on Windows 44
VDS on Linux 44
V
VDS components
uninstalling 43
VDS Node
starting 40
stopping 40
Vibe Data Stream Service
creating 41

Computer Support.pub

500V CoolMOS™ CE Power MOSFET Product Brief - Infineon

Download

electronics lab. part 8 experiments

Communication cable with circuit integrity JE-H(St

FTK4828 - 회사 홈페이지(www.firstsilicon.co.kr)

download pdf - Sika Malaysia

MOSFET 75A 500V

Bio Pharma - SOFTPATH SYSTEM LLC

Getting Started