5 . 0 i n f o r m a t i c a a x o n documentation/6/ax_50... · 5 . 0 i n f o r m a t i c a a x o n...

Informatica® Axon5.0

Installation Guide

Informatica Axon Installation Guide5.0September 2017

© Copyright Informatica LLC 2015, 2017

This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC.

Informatica and the Informatica logo are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners.

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.

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

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

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

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

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

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

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

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

This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.

This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http:// www.gnu.org/software/ kawa/Software-License.html.

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

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

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

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

This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/

Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5-current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/master/LICENSE; https://github.com/hjiang/jsonxx/blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/LICENSE; http://one-jar.sourceforge.net/index.php?page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-lang.org/license.html; https://github.com/tinkerpop/blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html; https://aws.amazon.com/asl/; https://github.com/twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.

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

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

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

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

DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

NOTICES

This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

The information in this documentation is subject to change without notice. If you find any problems in this documentation, please report them to us in writing at Informatica LLC 2100 Seaport Blvd. Redwood City, CA 94063.

Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.

Publication Date: 2017-10-11

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

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

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

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Introduction to Axon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: Before You Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Port Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Internal RPM Package Manager Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Tasks Before You Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Disable SELinux and Configure Port Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Verify Host Name Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configure Host Names for Related Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configure ulimit Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Obtain the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Disable Database Backup Cron Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Create Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Extract the Installer Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Run the Validation Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Obtain the Informatica Domain Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SSL Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Verify OpenSSL Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installer Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3: Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Running the Installer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installing Axon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing the Axon Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing Axon and the Axon Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Table of Contents

Chapter 4: After You Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Configure Access to Enterprise Information Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Connecting to an SSL-Enabled Enterprise Information Catalog Instance. . . . . . . . . . . . . . . . . . . 27

Configure Access to Informatica Data Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configure SSL-certified User Authority for Axon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Check the Status of the Micro Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configure Email Delivery Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Create a Daily Email Notification Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Create a Weekly Email Notification Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Create a Monthly Email Notification Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Logging In To Axon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 5: Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Running the Axon Uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Running the Axon Agent Uninstaller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Appendix A: Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Working with the Axon Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Start or Stop the Axon Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Monitor the Axon Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Modify Connection Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configure Synchronization Delay and Synchronization Interval. . . . . . . . . . . . . . . . . . . . . . 35

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Unable to Connect to Axon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Incorrect Host Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Validation Utility Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Bulk Upload Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Logged Out of Axon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Operating System User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Table of Contents 5

PrefaceThe Axon Installer Guide is intended to help an administrator in an enterprise to install Axon.

This guide covers the tasks that you can perform using the Axon installer.

Informatica Resources

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

As a member, you can:

• Access all of your Informatica resources in one place.

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

• View product availability information.

• Review your support cases.

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

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

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

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

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

6

HTTPS://NETWORK.INFORMATICA.COM/

http://kb.informatica.com

mailto:[email protected]

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


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

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

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

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

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

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

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

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

Preface 7

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

http://velocity.informatica.com


https://marketplace.informatica.com

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

http://network.informatica.com

C h a p t e r 1

OverviewThis chapter includes the following topics:

• Introduction to Axon, 8

• Installation Overview, 8

• Installation Process, 8

Introduction to AxonAxon is a knowledge repository and governance tool that stores the core data items and the business context of your organization. Owners, Stewards, Subject Matter Experts and other responsible stakeholders collaborate to progressively chart the business reality of data, its lineage, and usage across processes, policies, projects, and regulation.

Installation OverviewInformatica provides a validation utility to verify if your system meets the software requirements for installation and an installer to install Axon. Use the installer to install only Axon, only the Axon Agent, or both of them.

The Axon Agent is required by Axon to connect to Informatica Data Quality. You can install the Axon Agent on the same machine where you install Axon, or on a different machine. You must provide the details of your Informatica domain when you install the Axon Agent.

The Informatica domain is a collection of nodes and services that define the basic administrative unit for Informatica Data Quality.

Installation ProcessThe installation of Axon consists of multiple phases that include preparation for the installation, planning the deployment type, and post-installation tasks.

The Axon installation consists of the following phases:

8

Preparation

Set up the system to meet the operating system requirements to ensure that you can successfully install and run Axon and the Axon Agent. Run the validation utility to verify if your system meets the requirements.

Planning

Before you run the Axon installer, you must plan your deployment.

Integrating Data Quality. Determine whether you intend to retrieve data quality scores and display them in Axon dashboards. If yes, you must install both Axon and the Axon Agent. You can install the Axon Agent on the same machine where you install Axon or on a different machine.

Retrieving Enterprise Metadata. You also need to determine whether you want to discover and retrieve enterprise metadata from Enterprise Information Catalog. To integrate Axon with Enterprise Information Catalog, you need to configure certain advanced settings after you install Axon.

The following table lists the choices that the Axon installer provides. Plan your deployment based on these choices before you run the installer:

Choice Planning Task

Integration with Informatica Data Quality. Axon integrates with Informatica Data Quality to retrieve data quality scores and display them in the Axon dashboards.

Keep the details of your Informatica domain ready.

Choose to install Axon and the Axon Agent, or install only the Axon Agent if you have already installed Axon.

Integration with Informatica Enterprise Information Catalog. Axon integrates with Enterprise Information Catalog to discover and retrieve metadata from the catalog platform. The catalog represents an indexed inventory of all the data assets in the enterprise.

Keep the details of your Enterprise Information Catalog deployment ready.

Choose the advanced configuration step during Axon installation.

Perform the preparatory steps described in the Before You Run the Installer section, before you run the Axon installer.

After Installation

After you run the installer, perform the post-installation tasks. Access Axon by typing the URL in a web browser. Log in to verify if the installation is successful. Read the troubleshooting steps if you have issues with your installation.

Installation Process 9

C h a p t e r 2

Before You Run the InstallerThis chapter includes the following topics:

• System Requirements, 10

• Tasks Before You Run the Installer, 13

• Installer Directory Structure, 17

System RequirementsVerify that the system where you plan to install Axon meets the minimum requirements for the installation process. Ensure that the external ports are open.

The following table lists the minimum system requirements for Axon:

Component Description

Disk 200 GB

Memory 16 GB

CPU Cores 4

OS RedHat Linux version 7.x

Applications - unzip- tar- RPM- In- setfacl- YUM

You cannot install Axon on the same server where the Hadoop cluster for Enterprise Information Catalog is installed.

Important: Informatica recommends that you use a dedicated system to deploy Axon.

Port RequirementsThe packages and micro services that Axon installs use unique ports. You can choose to change some of the port numbers during installation. The installer sets up the ports for some of the third party services and

10

designates a range of dynamic ports to use for some application services. Verify that the port numbers are available before you start the installation process.

Axon uses the internal ports for internal communication, and the external ports for external communication.

The following table describes the default ports used by the micro services:

Port Type Default Port Number

Workflow Service (Camunda) Port 8081

Doc Upload Service Port 4000

Change Request Service Port 5000

Bulk Upload Service Port 7000

Bulk Upload PreValidator Port 7010

Bulk Upload Validator Port 7020

Bulk Upload Committer Port 7030

Notification Service Port 3000

Memcached Port 11211

Apache Server HTTP Port. This is an external port. 80

Apache Server HTTPS Port. This is an external port. Axon uses this port if you enable SSL communication.

443

The following table describes the ports used by Enterprise Information Catalog:


Enterprise Information Catalog Port 9085

The following table describes the port used by PostgreSQL database:


PostgreSQL Database Port 5432Note: Make sure this port number is available exclusively for the PostgreSQL database.

The following table describes the ports used by the process map configuration:


Process Configuration HTTP Port 2480

Process Configuration Internal Port 2424

System Requirements 11

The following table describes the ports used by the message broker:


Message Broker Port 5672

The following table describes the port used by Solr:

Port Type Description

Solr Configuration Port 8080

Internal RPM Package Manager FilesPrepare the system before you run the Axon installer. Verify that the required RPM Package Manager files (RPMs) required by Axon are available for use. Contact your IT department if you need help to have these RPMs installed.

Ensure that the following RPMs are available in your system before you run the Axon installer:

• apr-1.4.8

• apr-util-1.5.2

• autoconf-2.69

• automake-1.13.4

• glibc-2.17

• graphviz-2.30.1

• libevent-2.0.21

• libjpeg-turbo-1.2.90

• libmcrypt-2.5.8

• libpng-1.5.13

• libselinux-2.5

• libtool-ltdl-2.4.2

• libX11-1.6.3

• lksctp-tools-1.0.17

• mailcap-2.1.41

• mesa-libGLU-9.0.0

• openssl-libs-1.0.1e

• pcre-devel-8.32

• socat-1.7.2.2

• systemd-219

• systemd-sysv-219

• t1lib-5.1.2

• tk-8.5.13

• wxBase-2.8.12

12 Chapter 2: Before You Run the Installer

• wxGTK-2.8.12

• wxGTK-gl-2.8.12

• xorg-x11-fonts-75dpi-7.5

• xorg-x11-fonts-Type1-7.5

If any of these RPMs is missing, contact the IT department of your organization.

Tasks Before You Run the InstallerPerform the pre-installation tasks before you run the Axon installer. Contact the IT department of your organization if any of these tasks require additional resources.

Disable SELinux and Configure Port AccessVerify that SELinux is disabled before you run the Axon installer. Configure your firewall to allow the Axon installer and the application that it installs to access the external ports. Optionally, disable the firewall.

Run the following command to verify if SELinux is disabled on the system where you intend to run the Axon installer:

getenforce

The command should return the following result if SELinux is disabled:

Disabled

If SELinux is not disabled, contact the IT department of your organization.

Verify Host Name ConfigurationVerify that your host name has been configured with the correct IP address.

Run the following command to show the IP address of your host name:

hostname -i

Run the following command to show the fully qualified domain name of your host:

hostname -f

Configure Host Names for Related ComponentsIn the Linux system where you want to install Axon, you must map the host names and IP addresses of machines where other related components are installed, such as the Axon Agent and the Informatica Domain.

Perform the following tasks in the Linux system where you want to install Axon:

1. Open the hosts file from the following location:

/etc/hosts

Tasks Before You Run the Installer 13

2. At the end of the hosts file, add the IP addresses and domain name addresses for the following components:

• Axon Agent

• Informatica Domain

• Enterprise Information Catalog system

3. Save the file.

Configure ulimit ValuesAxon uses a large number of files and runs several processes. To prevent errors that result from the large number of files and process, change your Linux system settings with the ulimit command.

1. Open the /etc/security/limits.conf file.

2. Configure the following ulimit properties:

Property Description

nofile Set the file descriptor limit per process to 16000 or higher. Informatica recommends 32000 file descriptors per process.

nproc Set the user process to 1024 or higher. Informatica recommends 4096 user processes.

3. Exit and log in to the terminal for the changes to take effect.

Obtain the License KeyBefore you install Axon, verify that you have a valid license key. Contact Informatica Global Customer Support to obtain a license key. You must provide the location of the license key file during the installation process.

Disable Database Backup Cron JobInformatica Axon makes use of cron jobs for regular backups. By default, the cron job is enabled. If required, you can prevent automatic database backup using a flag that disables cron jobs. Make sure that you configure this flag before you run the installer.

To disable the cron job that backs up your database periodically, set the following environment variable to false:

AXON_ENABLE_CRON_JOB=false

If you need to take a backup of the databases at any point in time, you can perform the following tasks:

• Create a file with the name backup.sh, with the following content:

#!/bin/sh/bin/su -postgres -c "<INSTALLATION_DIRECTORY>/scripts/axon_db_backup.sh <BACKUP_DIRECTORY>/`date+%Y_%m_%d_%H%M`"

where <INSTALLATION_DIRECTORY> is the Axon installation directory and <BACKUP_DIRECTORY> is the directory where you choose to store your backup.

• Make sure that the PostgreSQL user has the required permissions on <INSTALLATION_DIRECTORY>/scripts/axon_db_backup.sh and <BACKUP_DIRECTORY>.


Create DirectoriesCreate the following directories before you run the installer:

1. Create an installation directory. The Axon installer creates a home directory inside the installation directory. The installer installs Axon in the home directory. The installer stores the uninstaller.sh and other files in the installation directory. The installation directory is referred to as <INSTALLATION_DIRECTORY> in this document.

2. Create a temporary directory for the installer binaries. This temporary directory is referred to as <SOURCE_BINARIES_DIRECTORY> in this document. Extract the installer files to this directory. Make sure that you download the installer zip file to a local directory or a shared network drive that is mapped on your machine. You can then securely copy the installer file to the installer folder and extract the installer files.

3. Optionally, create a directory for the Axon installer to install the Axon Agent.

Extract the Installer FilesThe installer files are compressed and distributed as a tar file. Use an extraction utility to untar the installer files to the installation directory on your machine. When you untar the file, verify that the extraction utility also extracts empty folders.

Run the Validation UtilityInformatica provides a validation utility that you can run to verify if your system meets the requirements to run the Axon installer.

You can download the validation utility from the following URL: https://download.informatica.com/infa/downloads/Axon/installer-prerequisite-tester.zip

Run the following command as a root user to run the validation utility:

sh validate.sh <SOURCE_BINARIES_DIRECTORY>

Optionally, execute the following command as a sudo user to run the validation utility:

sudo sh validate.sh <SOURCE_BINARIES_DIRECTORY>

The validation utility checks if your system meets the following requirements:

• System requirements

• SELinux configuration

• Internal RPMs

• Application RPMs

The validation utility displays status messages when it runs. Follow the instructions given in the messages before you proceed with running the Axon installer. After you run the validation utility, you can also check the log directory for log messages. This log directory is present in the same directory as the validate.sh file.

Axon installs PHP version 5.6. Uninstall any other version of PHP from your system before you run the installer.

If any of the application RPMs that are installed by the Axon installer are already present in your system, uninstall them before you run the installer.

For a list of RPMs required by the Axon installer, see the Internal RPM Package Manager Files topic in the Before You Run the Installer chapter.

Tasks Before You Run the Installer 15

https://download.informatica.com/infa/downloads/Axon/installer-prerequisite-tester.zip

Obtain the Informatica Domain DetailsAxon can connect to the Informatica domain to extract profile and scorecard information from Data Quality. Axon can extract enterprise metadata information from Enterprise Information Catalog.

You must provide the following details of your Informatica domain if you choose to install the Axon Agent when you run the Axon installer:

• Domain name

• Node port number

• Model Repository Service node name

• Model Repository Service domain host name

• Model Repository Service username and password

• Model Repository Service name

• Model Repository Service security domain

• Model Repository Service SSL details

• Data Integration Service node name

• Data Integration Service domain host name

• Data Integration Service username and password

• Data Integration Service name

• Data Integration Service security domain

• Data Integration Service SSL details

You must provide the following details of your Enterprise Information Catalog installation if you choose to do an advanced installation:

• Enterprise Information Catalog server name

• Port number

• Username and password

• Namespace

• Axon Resource name

SSL CommunicationAxon can use HTTP and HTTPS for communication. To use HTTPS communication, you must configure SSL during installation. Keep the SSL certificate and key file ready before you start the installation.

You must have the following information ready before you start the installation:

• HTTPS port information

• SSL certificate and the path to the file. The certificate must be in .crt format.

• SSL key file and the path to the file. The key must be in .key format.


Verify OpenSSL VersionDuring installation, the Axon installer verifies that OpenSSL version is openssl-libs-1.0.1e in your host machine. If the host machine has an OpenSSL version later than openssl-libs-1.0.1e, you must modify two installer files to use your installed version of OpenSSL.

1. Open the <VALIDATION_UTILITY_DIRECTORY>/config/internal-packages.conf file.

The content of the internal-packages.conf file appears.

2. Update the openssl-libs-1.0.1e entry with the version of OpenSSL that is installed in your host machine.

3. Open the <SOURCE_BINARIES_DIRECTORY>/properties/SystemRPMs.properties file where you extracted the Axon installer file.

The content of the SystemRPMs.properties file appears.

4. Update the openssl-libs-1.0.1e entry with the version of OpenSSL that is installed in your host machine.

Installer Directory StructureYou must extract the Axon installer file to the temporary directory for installer binaries, <SOURCE_BINARIES_DIRECTORY>, on the system before you run the installer.

The installer file decompresses the following files and directories to the installation directory:

• Messages

• install.sh

• Server

• properties

• source

Installer Directory Structure 17

C h a p t e r 3

Running the InstallerThis chapter includes the following topics:

• Running the Installer Overview, 18

• Running the Installer, 18

Running the Installer OverviewInformatica provides an installer to install Informatica Axon on a machine running RedHat Linux version 7.x. Run the installer using a shell. You can run only one instance of Axon on a machine at any given point of time.

The Axon installer provides an interactive wizard. Use the wizard to configure the installation parameters. You can choose to install the Axon Agent when you install Axon. Install the Axon Agent to enable communication between Axon and Informatica Data Quality.

Run the install.sh file from the temporary directory for installer binaries, <SOURCE_BINARIES_DIRECTORY>, where you untarred the installer as one of the following users:

• root

• sudo

Running the InstallerInstall Axon using a console. When you run the installer, the words "Quit", "Back" and "Help" are reserved words. Do not use them as input text. Enter help for getting additional context-sensitive information during the installation process. Enter Quit to exit the installer at any point in time.

1. Log in to the machine with a root user or sudo user.

2. Ensure that there are no Axon-related services running and uninstall any previous versions of Axon that you may have.

3. From the command line, run the install.sh file.

• To run the command as a root user, execute the sh install.sh command.

• To run the command as a sudo user, execute the sudo sh install.sh command.

18

4. Type the number corresponding to one of the following options to continue:

Option Description

1. Install Axon. Run the installer to install Axon.

2. Install Axon Agent. Run the installer to install the Axon Agent.

3. Install both Axon and Axon Agent. Run the installer to install both Axon and the Axon Agent.

Installing AxonSelect the option to install only Axon if you do not want to install the Axon Agent. Informatica recommends that you run the validation utility before you run the Axon installer.

Run the install.sh file and select option 1.

Step 1 of 6

Review the information on the screen, and press the Enter key to continue.

Step 2 of 6

Enter the path to the installation directory and license key. The installer performs a check to validate the system requirements and verifies whether the license key file exists in the directory location that you provided.

Step 3 of 6

Review the pre-installation summary information. Press the Enter key to continue. If you want to make changes to the information you provided, type in Back and press Enter.

Step 4 of 6

Review the installation progress.

Step 5 of 6

After the installation progress reaches 100%, you can choose to set some advanced configurations. Type 1 to continue with the advanced configuration. Type 2 to skip to step 6.

Step 5A of 6

Type 1 if you want to enable HTTPS authentication, and then enter the values for the following parameters:

• HTTPS port number

• File path to the SSL certificate. The certificate must be in .crt format.

• File path to the SSL key. The key must be in .key format.

• Memcache port number

Type 2 if you do not want to enable HTTPS authentication.

Step 5B of 6

Specify the port numbers of the following micro services. At each step, press the Enter key to proceed with the default port.

• Workflow service port

• Document upload port

• Change request service port

Running the Installer 19

• Bulk upload service port

• Bulk upload pre-validator port

• Bulk upload validator port

• Bulk upload committer port

• Notification service port

Step 5C of 6

Specify the port numbers for the OrientDB database configurations. At each step, press the Enter key to proceed with the default port.

• Process configuration HTTP port

• Process configuration internal port

Step 5D of 6

Specify the port number for the message broker. Press the Enter key to proceed with the default port.

Step 5E of 6

Specify the Tomcat port number for Apache Solr that Axon uses for search indexing. Press the Enter key to proceed with the default port.

Type 1 to integrate Axon with Enterprise Information Catalog. Type 2 to skip to step 6.

Note: If you want to integrate Axon with Enterprise Information Catalog at a later stage after installation, see the Configure Access to Enterprise Information Catalog topic in the After You Run the Installer chapter.

Step 5F of 6

Enter values for the following parameters of the Enterprise Information Catalog installation:

• Enterprise Information Catalog URL in the format http://<host_name>• Enterprise Information Catalog port number. Press the Enter key to proceed with the default port.

• Enterprise Information Catalog user name

• Enterprise Information Catalog password

• Enterprise Information Catalog namespace

• Enterprise Information Catalog resource name for your Axon installation

The installer begins installing Axon.

Note: The Axon installation process might take some time to complete. You can track the progress of this step by viewing the logs available at <INSTALLATION_DIRECTORY>/Configure.log.

Step 6 of 6

Review the installation summary to verify that all components are successfully installed.

Press the Enter key to complete the installation.

Installing the Axon AgentSelect the option to install the Axon Agent if you already installed Axon and you want to extract profile and scorecard information from Informatica Data Quality. You can install the Axon Agent on the same system where you have installed Axon, or you can install the Axon Agent on a separate system. You must know the details of the Informatica domain before you proceed.


20 Chapter 3: Running the Installer

Note: The console is refreshed and the installation screen is cleared. You might want to note down any important information on the screen.

Step 1 of 9


Step 2 of 9

Choose the version of the Informatica domain that you want Axon to connect to.

Step 3 of 9

Enter the path to the directory where you want the installer to install the Axon Agent.

Step 4 of 9

Review the pre-installation summary information. Press the Enter key to continue. If you want to make changes to the information you provided, type Back and press Enter.

Step 5 of 9


Step 6 of 9

Specify the details of the Model Repository Service (MRS). Enter values for the following parameters:

• Domain name

• Node port

• MRS domain host

• MRS node name

• MRS user name

• MRS password

• MRS service name

• MRS security domain. Choose LDAP or your native domain as the security domain. Press the Enter key to proceed with the native domain as default.

• SSL security. Specify whether SSL security is enabled for your MRS system. If you select yes, you must provide the local path to the trust store file. Press the Enter key to proceed with no SSL security as the default option.

Step 7 of 9

Specify the details of the Data Integration Service (DIS). Enter values for the following parameters:

• Node port

• DIS domain host

• DIS node name

• DIS user name

• DIS password

• DIS service name

• DIS security domain. Choose LDAP or your native domain as the security domain. Press the Enter key to proceed with the native domain as default.

Note: If you choose LDAP as your security domain, you must point the Axon Agent to connect to your organization's LDAP server. For more information, see the Modify Connection Details topic in the Appendix A: Reference chapter.


• SSL security. Specify whether SSL security is enabled for your DIS system. If you select yes, you must provide the local path to the trust store file. Press the Enter key to proceed with no SSL security as the default option.

Step 8 of 9

Specify the details of the Axon installation. Enter values for the following parameters:

• HTTPS authentication

• Axon URL in the format http(s)://<hostname>:<port number>Note: Do not enter a forward slash (/) after the URL.

• Axon user name

Note: If you use Single Sign-On (SSO) for Axon, do not enter the SSO user name. Enter the user name that is configured in the Axon application.

• Axon password

Note: If you use Single Sign-On (SSO) for Axon, do not enter the SSO password. Enter the password that is configured in the Axon application.

• Axon Agent HTTP port

Step 9 of 9



To verify that the Axon Agent is running, check the following log file:

<Axon_Agent_Home>/logs/dq-axon/dqagent.log

Installing Axon and the Axon AgentSelect the option to install Axon and the Axon Agent to enable communication with Informatica Data Quality. Informatica recommends that you run the validation utility before you run the Axon installer.


The installer will first install Axon.

Step 1 of 6


Step 2 of 6

Enter the path to the installation directory and license key. The installer performs a check to validate the system requirements and verifies whether the license key file exists in the directory location that you provided.

Step 3 of 6

Review the pre-installation summary information. Press the Enter key to continue. If you want to make changes to the information you provided, type in Back and press Enter.

Step 4 of 6


Step 5 of 6

After the installation progress reaches 100%, you can choose to set some advanced configurations. Type 1 to continue with the advanced configuration. Type 2 to skip to step 6.


Step 5A of 6

Type 1 if you want to enable HTTPS authentication, and then enter the values for the following parameters:

• HTTPS port number

• File path to the SSL certificate. The certificate must be in .crt format.

• File path to the SSL key. The key must be in .key format.

• Memcache port number

Type 2 if you do not want to enable HTTPS authentication.

Step 5B of 6

Specify the port numbers of the following micro services. At each step, press the Enter key to proceed with the default port.

• Workflow service port

• Document upload port

• Change request service port

• Bulk upload service port

• Bulk upload pre-validator port

• Bulk upload validator port

• Bulk upload committer port

• Notification service port

Step 5C of 6

Specify the port numbers for the OrientDB database configurations. At each step, press the Enter key to proceed with the default port.

• Process configuration HTTP port

• Process configuration internal port

Step 5D of 6

Specify the port number for the message broker. Press the Enter key to proceed with the default port.

Step 5E of 6

Specify the Tomcat port number for Apache Solr that Axon uses for search indexing. Press the Enter key to proceed with the default port.

Type 1 to integrate Axon with Enterprise Information Catalog. Type 2 to skip to step 6.

Note: If you want to integrate Axon with Enterprise Information Catalog at a later stage after installation, see the Configure Access to Enterprise Information Catalog topic in the After You Run the Installer chapter.

Step 5F of 6

Enter values for the following parameters of the Enterprise Information Catalog installation:

• Enterprise Information Catalog URL in the format http://<host_name>• Enterprise Information Catalog port number. Press the Enter key to proceed with the default port.

• Enterprise Information Catalog user name

• Enterprise Information Catalog password

• Enterprise Information Catalog namespace


• Enterprise Information Catalog resource name for your Axon installation

The installer begins installing Axon.

Note: The Axon installation process might take some time to complete. You can track the progress of this step by viewing the logs available at <INSTALLATION_DIRECTORY>/Configure.log.

Step 6 of 6



Continue with the installation of the Axon Agent.

Note: The console is refreshed and the installation screen is cleared. You might want to note down any important information on the screen.

Step 1 of 9


Step 2 of 9

Choose the version of the Informatica domain that you want Axon to connect to.

Step 3 of 9

Enter the path to the directory where you want the installer to install the Axon Agent.

Step 4 of 9

Review the pre-installation summary information. Press the Enter key to continue. If you want to make changes to the information you provided, type Back and press Enter.

Step 5 of 9


Step 6 of 9

Specify the details of the Model Repository Service (MRS). Enter values for the following parameters:

• Domain name

• Node port

• MRS domain host

• MRS node name

• MRS user name

• MRS password

• MRS service name

• MRS security domain. Choose LDAP or your native domain as the security domain. Press the Enter key to proceed with the native domain as default.

• SSL security. Specify whether SSL security is enabled for your MRS system. If you select yes, you must provide the local path to the trust store file. Press the Enter key to proceed with no SSL security as the default option.

Step 7 of 9

Specify the details of the Data Integration Service (DIS). Enter values for the following parameters:

• Node port

• DIS domain host


• DIS node name

• DIS user name

• DIS password

• DIS service name

• DIS security domain. Choose LDAP or your native domain as the security domain. Press the Enter key to proceed with the native domain as default.

Note: If you choose LDAP as your security domain, you must point the Axon Agent to connect to your organization's LDAP server. For more information, see the Modify Connection Details topic in the Appendix A: Reference chapter.

• SSL security. Specify whether SSL security is enabled for your DIS system. If you select yes, you must provide the local path to the trust store file. Press the Enter key to proceed with no SSL security as the default option.

Step 8 of 9

Specify the details of the Axon installation. Enter values for the following parameters:

• HTTPS authentication

• Axon URL in the format http(s)://<hostname>:<port number>Note: Do not enter a forward slash (/) after the URL.

• Axon user name

Note: If you use Single Sign-On (SSO) for Axon, do not enter the SSO user name. Enter the user name that is configured in the Axon application.

• Axon password

Note: If you use Single Sign-On (SSO) for Axon, do not enter the SSO password. Enter the password that is configured in the Axon application.

• Axon Agent HTTP port

Step 9 of 9



To verify that the Axon Agent is running, check the following log file:



C h a p t e r 4

After You Run the InstallerAfter you install Axon, perform the following post-installation tasks.

Configure Access to Enterprise Information CatalogDuring Axon installation, if you selected advanced configuration, you would have entered the configuration settings for Enterprise Information Catalog. If you did not select advanced configuration during Axon installation, or if you want to update the connection settings for Enterprise Information Catalog after the installation, modify the parameters.yml file. Do not add unwanted spaces or tabs to the parameters.yml file.

1. Open the parameters.yml file available in the following location:

<INSTALLATION_DIRECTORY>/axonhome/axon/app/config/parameters.yml2. Configure the following properties:

Option Description

eic_server_host Host name of the Enterprise Information Catalog service

eic_server_port Port number of the Enterprise Information Catalog service

eic_server_login_username User name to log in to Enterprise Information Catalog

eic_server_login_password Password to log in to Enterprise Information Catalog

eic_server_login_namespace User security domain of Enterprise Information Catalog

eic_axon_resources_name Resource name in Enterprise Information Catalog that is configured to connect to your specific Axon application

3. Run the following command to clear the cache:

rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/*

4. Type the following commands to restart the micro services:

service memcached restartservice httpd restart

26

Connecting to an SSL-Enabled Enterprise Information Catalog Instance

To connect Axon to an instance of Enterprise Information Catalog that has SSL enabled, you must upgrade cURL and the related libraries after you install Axon. Else, the facets in Axon will not display objects.

Run the following command to check the existing version of cURL and the related libraries:

curl -V

Run the following yum command to upgrade cURL:

yum upgrade curl

Run the following yum command to upgrade Network Security Services (NSS):

yum upgrade nss

Run the following command to verify the version of NSS after upgrade:

rpm -qa | grep nss

After you run the rpm -qa | grep nss command, ensure that the output displays the following libraries:

nss-sysinit-3.21.0-17.el7.x86_64 nss-tools-3.21.0-17.el7.x86_64 nss-util-3.21.0-2.2.el7_2.x86_64 nss-3.21.0-17.el7.x86_64

You can connect to an SSL enabled instance of Enterprise Information Catalog if the console displays the following information after you run the command:

curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.21 Basic ECC zlib/1.2.7 libidn/1.28 libssh2/1.4.3

Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp

Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets

Configure Access to Informatica Data QualityYou must update the parameters.yml file to connect to Informatica Data Quality. Do not add unwanted spaces or tabs to the parameters.yml file.



Option Description

agent_host Host name of the system where you installed the Axon Agent

agent_port Port number on which the Axon Agent runs


Connecting to an SSL-Enabled Enterprise Information Catalog Instance 27

rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/*4. Type the following commands to restart the micro services:


Configure SSL-certified User Authority for AxonYou must provide Axon users the necessary SSL authentication by a Certified Authority so that their browser access to Axon is secure.

1. Open the diaku_web.conf file available in the following location:

/etc/httpd/conf.d/diaku_web.conf2. Uncomment the SSLCaCertificateFile property and enter the full path to your SSL CA file.

Check the Status of the Micro ServicesYou can verify if all the micro services installed by Axon have started after you finished running the installer.

The following table lists the micro services and the command you must run in the console to check their status:

Service Name Status Check

Document Upload service axon_document_upload_microservice status

Notification service axon_notification_microservice status

Change Request service axon_changerequest_microservice status

OrientDB service orientdb status

Camunda ps -ef | grep camunda

RabbitMQ service rabbitmq-server status

Httpd service httpd status

OdbConsumer service OdbConsumer status

Memcached service memcached status

Solr service tomcat-solr status

PostgreSQL service postgresql-9.4 status

28 Chapter 4: After You Run the Installer

Service Name Status Check

DaemonTools service daemontools status

Bulk Upload service axon_bulk_upload_microservice status

You can also check the status of the micro services from the Axon application. Log in to Axon as an administrator and go to the Admin Dashboard. The Status of Axon Services section shows the micro services that are operational.

Configuring Email NotificationsYou can create a time-based job scheduler to receive emails from Axon. You must enter the details of your email system in the parameters.yml file. You must also create and configure a crontab (cron table) file to specify shell commands that run periodically on a given schedule.

You can schedule email notifications in the following time intervals:

• Daily

• Weekly

• Monthly

Configure Email Delivery OptionsYou must update the parameters.yml file with the details of your email server. Do not add unwanted spaces or tabs to the parameters.yml file.



Property Description

mailer_transport Email protocol

mailer_host Your email host address

mailer_user Your email user name

mailer_password Your email password

mailer_port Email server port

disable_delivery Set to false


rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/*

Configuring Email Notifications 29

4. Type the following commands to restart the micro services:


Create a Daily Email Notification SchedulePerform the following steps to create a daily email notification schedule.

1. Go to the following location /etc/cron.daily.

2. Create a new file with the name script.sh.

3. Add the following code to the file:

#!/bin/shphp <INSTALLATION_DIR>/axonhome/axon/app/console diaku:process-notifications --timeframe=daily --env=prod

4. From the console, type crontab -e The console displays the crontab editor.

5. Type the following command:

<min> <hr> * * * /etc/cron.daily/script.shFor example, to receive email notifications at 10.30 pm every day, type the following command:

30 22 * * * /etc/cron.daily/script.sh6. Save your changes.

Create a Weekly Email Notification SchedulePerform the following steps to create a weekly email notification schedule.

1. Go to the following location /etc/cron.weekly.



#!/bin/shphp <INSTALLATION_DIR>/axonhome/axon/app/console diaku:process-notifications --timeframe=weekly --env=prod



<min> <hr> * * <day> /etc/cron.weekly/script.shFor example, to receive email notifications at 6.30 am every Sunday, type the following command:

30 6 * * 0 /etc/cron.weekly/script.sh6. Save your changes.

Create a Monthly Email Notification SchedulePerform the following steps to create a monthly notification schedule.

1. Go to the following location /etc/cron.monthly.

30 Chapter 4: After You Run the Installer



#!/bin/shphp <INSTALLATION_DIR>/axonhome/axon/app/console diaku:process-notifications --timeframe=monthly --env=prod



<min> <hr> <date> * * /etc/cron.monthly/script.shFor example, to receive email notifications at 6.30 am on the 28th of every month, type the following command:

30 6 28 * * /etc/cron.monthly/script.sh6. Save your changes.

Logging In To AxonIf you have not configured Single Sign-On, use the URL displayed by the Axon installer after the installation completes, to log in to Axon from a browser. To configure Single Sign-On for authentication, see the Enabling Single Sign-on in Axon How-to Article.

1. Open a browser.

2. In the address field, type the URL for the Axon login page in the following format: http(s)://<hostname>:<port number>/

3. From the Axon home page, on the top right corner of the toolbar, click Login.

4. Enter your login credentials. The following are the default login credentials for the Super Admin user:Username: [email protected]: changeme

5. Click Login.

6. Axon refreshes the page and displays your username in the toolbar. This indicates that you have successfully logged in.

7. Modify the password for your login credentials.

Logging In To Axon 31

C h a p t e r 5

UninstallationThis chapter includes the following topics:

• Running the Axon Uninstaller, 32

• Running the Axon Agent Uninstaller, 32

Running the Axon UninstallerRun the uninstaller file to remove all the Axon files present in the Axon home and installation directories. Important: The Axon uninstaller removes the the PostgreSQL database and the backup files stored in the <INSTALLATION_DIRECTORY>/axonhome/db-backups/postgres_backups directory. Copy these files to another location if you require these files after uninstalling Axon.

1. Use the root user or sudo user credentials and log in to the machine where you have installed Axon.

2. Navigate to the following directory to access the uninstaller.sh file.

<INSTALLATION_DIRECTORY>/Uninstaller_axon3. Run the uninstaller. The uninstaller stops the Axon services that are currently running and removes all

the Axon and third-party packages and tar files from the machine.

• To run the uninstaller as a root user, type sh uninstaller.sh• To run the uninstaller as a sudo user, type sudo sh uninstaller.sh

4. Review the uninstallation summary file at the following location: <user_home_directory>/Configure.log

To verify that uninstallation is complete, check whether all micro services have stopped. For more information, see the Check the Status of the Micro Services topic in the After You Run the Installer chapter.

Running the Axon Agent UninstallerRun the Axon Agent uninstaller to remove the Axon Agent from your system.

1. Navigate to the following directory

<AXONAGENT_INSTALLATION>/Uninstaller_agent2. Run the uninstaller.

• To run the uninstaller as a root user, type sh uninstaller.sh

32

• To run the uninstaller as a sudo user, type sudo sh uninstaller.sh3. In the Uninstallation step, review the information and hit Enter to continue with the uninstallation of the

Axon Agent.

4. In the Uninstalling step, review the progress of the uninstallation.

5. In the Post-Uninstallation Summary screen, review the information.

6. Hit the Enter key to complete the uninstallation.

Running the Axon Agent Uninstaller 33

A p p e n d i x A

ReferenceThis appendix includes the following topics:

• Working with the Axon Agent, 34

• Troubleshooting, 36

• Operating System User Accounts, 38

Working with the Axon AgentThe following sections provide information on setting up and configuring the Axon Agent if it does not work as expected.

Start or Stop the Axon AgentIf the Axon Agent stops, you can restart the Axon Agent. For example, if you want to modify the connection details of the Axon Agent, you must stop and restart the Axon Agent.

Run the following command to start the Axon Agent:

<Axon_Agent_Home>/sh startup.sh

Run the following command to stop the Axon Agent:

<Axon_Agent_Home>/sh shutdown.sh

When the Axon Agent starts, it verifies that the Informatica Domain, Model Repository Service, and the Data Integration Service are running. The Axon Agent does not start if any of these components is not running.

Monitor the Axon AgentWhen the Axon Agent is running, you can monitor its status by viewing the log file.

Open the following log file to monitor the Axon Agent:


34

Modify Connection DetailsYou must configure the Axon Agent to connect to other components that are required by Axon. For example, if you update the LDAP namespace or move the Axon application to a new location, you must update the connection details of the Axon Agent to point to the new location.

Connect to LDAP Server

To point the Axon Agent to the LDAP server, edit the mrs.securityDomain property in the following file:

<Axon_Agent_Home>/conf/application-mrs-dis.properties

Connect to Informatica Domain, Model Repository Service, or Data Integration Service

To point the Axon Agent to a new location for the Informatica Domain, Model Repository Service, or the Data Integration Service, edit the properties in the following file:

<Axon_Agent_Home>/conf/application-mrs-dis.properties

Connect to Axon

To point the Axon Agent to a new location for the Axon application, edit the properties in the following file:

<Axon_Agent_Home>/conf/application-axon.properties

Change Password

To change the password for Axon, Model Repository Service, or Data Integration Service, run the following command during startup:

<Axon_Agent_Home>/sh startup.sh --mrs.userName=Administrator --mrs.password=<MRS_password> --dis.userName=Administrator --dis.password=<DIS_password> [email protected] --axon.password=<Axon_password>

Note: Do not update the password by modifying the application-mrs-dis.properties and application-axon.properties files.

Configure Synchronization Delay and Synchronization IntervalYou can update the synchronization delay and synchronization interval between Axon and the Axon Agent.

Synchronization Delay

After the Axon Agent starts, it synchronizes with Axon. Synchronization delay is the time after which Axon and the Axon Agent start synchronization after the Axon Agent is started. For example, if you set the synchronization delay to 5 minutes, Axon and the Axon Agent start the synchronization task 5 minutes after the Axon Agent starts.

1. To configure the synchronization delay, modify the following file:Axon_Agent_Home>/conf/application-app.properties

2. Modify the value for the app.syncDelay property. Enter the synchronization delay in minutes. The default value is 1 minute.

Synchronization Interval

Synchronization interval is the frequency at which Axon and the Axon Agent synchronize with each other. For example, if you set the synchronization interval to 3 minutes, Axon and the Axon Agent synchronize with each other every 3 minutes.

1. To configure the synchronization interval, modify the following file:<Axon_Agent_Home>/conf/application-axon.properties

Working with the Axon Agent 35

2. Modify the value for the axon.delayInterval property. Enter the synchronization interval in minutes. The default value is 1 minute.

TroubleshootingThe following sections provide information that help you troubleshoot the Axon application if it does not work as expected.

Unable to Connect to AxonYou can access Axon by typing the Fully Qualified Domain name or the IP address of the server and the port number in the address bar of a web browser. If you are unable to access Axon, perform the following steps:

Verify the Firewall Settings

You must enable the firewall of the machine where you installed Axon to allow requests for the port.

Verify that the Micro Services are Running

Ensure that all the micro services are running after the installation. If Axon or any of the micro services is not running, run the startup.sh script. If you want to manually stop the Axon services, run the shutdown.sh script.

The startup.sh and shutdown.sh files are available in the <INSTALLATION_DIRECTORY>/bin/ directory.

Verify that the Cache Folder has Recursive Permission

Check the following log files:

• /etc/httpd/logs/<hostname>-error_log for HTTP authentication

• /etc/httpd/logs/<hostanme>-ssl_error_log for HTTPS authentication

• <INSTALLATION_DIR>/axonhome/axon/app/logs/prod.logIf the log files show a write permission error, run the setfacl -R -m u:apache:rwx INSTALLATION_DIRECTORY>/axonhome/axon/app/cache command to grant recursive permission to the cache folder.

Incorrect Host NameIf you encounter an error with the host name during installation, verify that the host name has been configured with the correct IP address.

Run the following command to show the IP address of your host name:

hostname -i

Run the following command to show the fully qualified domain name of your host:

hostname -f

36 Appendix A: Reference

Validation Utility ErrorsYou might see errors relating to some package libraries when you run the validation utility. Perform the following tasks to resolve errors that Axon displays during the validation check.

OpenSSL Error

Upgrade your version of OpenSSL to openssl-libs-1.0.1e if you see the following error when you run the validation utility:

error: Failed dependencies:openssl-libs >= 1:1.0.1e-37 is needed by mod_ssl-1:2.4.6-45.el7.centos.x86_64If the host machine has an OpenSSL version later than openssl-libs-1.0.1e, you must modify two installer files to use your installed version of OpenSSL. For more information, see the Verify OpenSSL Version topic in the Before You Run the Installer chapter.

PHP Library Error

The validation utility might display the following error if you have a version of PHP which is lower than the one required by Axon:

error: Failed dependencies:php-common < 5.6 conflicts with php56w-common-5.6.31-1.w7.x86_64

To resolve this error, uninstall the lower version of the PHP library from your system before you run the installer.

Bulk Upload FailsIf Axon users get a connection error or access error during bulk upload, you must modify the hosts file in that Axon user's system. This error appears when the user enters the IP address in the browser address bar to log in to Axon.

Perform the following tasks in the Axon user's system.

1. Open the hosts file available in the following location:

C:\Windows\System32\drivers\etc2. At the end of the hosts file, add the IP address and domain name address for your Axon host. Open the

parameters.yml file to see the domain name address for your Axon host. Alternatively, run the hostname -f command to see the domain name address for your Axon host.

For example, if the parameters.yml file says bulk_upload_host: AXONL70VM01.informatica.com, add the entry 192.0.2.5 AXONL70VM01.informatica.com to the hosts file.

To bulk upload data, Axon users must enter this host name instead of the IP address in the browser address bar.

Logged Out of AxonIf your Axon license expires, users who have logged in will log out of Axon. Perform the following tasks if your Axon license expires:

1. Contact Informatica Global Customer Support to obtain a new license key.

2. Open the etc/php.d/zendguardloader.ini file.

3. For the zend_loader.license_path property, enter the full path to your new license key file.

4. To restart the Axon service, run the service httpd restart command.

Troubleshooting 37

Operating System User AccountsThe following table describes the Operating System user accounts that are created by third-party packages. Axon uses these user accounts during installation.

User Name Description Home Directory User Shell

epmd Erlang Port Mapper Daemon /tmp /sbin/nologin

rabbitmq RabbitMQ messaging server /var/lib/rabbitmq /bin/bash

postgres PostgreSQL Server /var/lib/pgsql /bin/bash

memcached Memcached daemon /run/memcached /sbin/nologin

apache Apache /usr/share/httpd /sbin/nologin

38 Appendix A: Reference

5 . 0 i n f o r m a t i c a a x o n documentation/6/ax_50... · 5 . 0 i n f o r m a t i c a a x o n...

Documents