Informatica Axon Data Governance 5.2. Administrator Guide

Transcription

1 Informatica Axon Data Governance 5.2 Administrator Guide

2 Informatica Axon Data Governance Administrator Guide 5.2 March 2018 Copyright Informatica LLC 2015, 2018 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 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 , 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 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 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 ( 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 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 ( software copyright The JBoss Group, LLC, all rights reserved; software copyright 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 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 ( ) , 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 and This product includes Curl software which is Copyright , Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at 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 ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at license.html. The product includes software copyright , The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at 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 This product includes software developed by Boost ( or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at / This product includes software copyright University of Cambridge. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at and at This product includes software licensed under the terms at license.html, httpunit.sourceforge.net/doc/ license.html, release/license.html, license-agreements/fuse-message-broker-v-5-3- license-agreement; licence.html;

3 Consortium/Legal/2002/copyright-software ; license.html; software/tcltk/license.html, iodbc/wiki/iodbc/license; index.html; EaselJS/blob/master/src/easeljs/display/Bitmap.js; jdbc.postgresql.org/license.html; LICENSE; master/license; LICENSE; intro.html; LICENSE.txt; and This product includes software licensed under the Academic Free License ( the Common Development and Distribution License ( the Common Public License ( the Sun Binary Code License Agreement Supplemental License Terms, the BSD License ( the new BSD License ( opensource.org/licenses/bsd-3-clause), the MIT License ( the Artistic License ( licenses/artistic-license-1.0) and the Initial Developer s Public License Version 1.0 ( This product includes software copyright Joe WaInes, XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by the Indiana University Extreme! Lab. For further information please visit 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 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, report them to us at infa_documentation@informatica.com. 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:

4 Table of Contents Preface... 7 Informatica Resources Informatica Network Informatica Knowledge Base Informatica Documentation Informatica Product Availability Matrixes Informatica Velocity Informatica Marketplace Informatica Global Customer Support Chapter 1: Overview... 9 Introduction to Axon Administration Overview Axon Architecture Administration Process Chapter 2: Configuring Axon User Roles Configure Roles Object Permissions Assign Permissions to Roles Change Default Administrator Password Provide Permissions to the Axon Folders Default Workflows Create a Default Workflow Add Users Bulk Upload Users to the People Facet Manually Add Users to the People Facet Configure Glossary Rules Engine Configure Dropdowns Configure Static Pages Specify Support Address Configure Single Sign-On Create a New Application in the IDP Configure Axon Details for the New Application in the IDP Generate a SAML Metadata for Axon in the IDP Configure Axon and Enter the SAML Metadata Values Clear the Axon Cache and Restart Services Configure Access Control Configure Access to Enterprise Data Catalog Table of Contents

5 Connect to an SSL-Enabled Enterprise Data Catalog Instance Configure Access to Informatica Data Quality Configure Access to 27 Specify Prefix for Object Reference Numbers Update Cache with Configuration Values Chapter 3: Customizing Axon Display Your Organization Logo Customize the Axon Interface Theme Chapter 4: Monitoring Axon View System Information View Licensed Users Manage Locks Monitor Scheduled Jobs Configure Notifications Configure Delivery Options Create a Daily Notification Schedule Create a Weekly Notification Schedule Create a Monthly Notification Schedule Working with the Axon Agent Start or Stop the Axon Agent Monitor the Axon Agent Modify Connection Details Configure Synchronization Delay and Synchronization Interval Working With Services Back Up and Restore Database Back Up Database Restore Database Restore Axon Settings Chapter 5: Troubleshooting Axon Cannot Log In to Axon Cannot Log In to Axon Using SSO Axon Does Not Load in the Browser Cannot Open, Create or Save Objects Data Quality Dashboards Do Not Display Data Cannot Start the HTTPD Service because SSL is Password-Protected Troubleshooting Bulk Upload Troubleshooting Change Requests Troubleshooting Document Upload Troubleshooting Maps Troubleshooting Notifications Table of Contents 5

6 Troubleshooting Search Troubleshooting Value Lists Troubleshooting Workflows Index Table of Contents

7 Preface The Axon Data Governance Administrator Guide is intended to help an administrator configure Axon. This guide covers the tasks that you can perform to configure Axon after it is installed in your organization. This guide assumes that you have installed Axon successfully. For details on installing Axon, see the Axon Data Governance 5.2 Installation Guide in the Informatica Knowledge Base. Informatica Resources Informatica Network Informatica Network hosts Informatica Global Customer Support, the Informatica Knowledge Base, and other product resources. To access Informatica Network, visit 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 Base Use 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 If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at KB_Feedback@informatica.com. Informatica Documentation To get the latest documentation for your product, browse the Informatica Knowledge Base at If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. 7

8 Informatica Product Availability Matrixes Product 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 Informatica Velocity Informatica 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 If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com. Informatica Marketplace The 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 Informatica Global Customer Support You 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: If you are an Informatica Network member, you can use Online Support at 8 Preface

9 C h a p t e r 1 Overview This chapter includes the following topics: Introduction to Axon, 9 Administration Overview, 9 Axon Architecture, 10 Administration Process, 12 Introduction to Axon Axon Data Governance is a knowledge repository tool that you can use to document the data items that require governance. Data owners, data stewards, subject matter experts, and other responsible stakeholders collaborate across the organization to progressively chart the business reality of data, its lineage, and usage across processes, policies, projects, and regulation. Administration Overview As an administrator, you can perform various administrative tasks, such as managing users, configuring roles, assigning permissions, adding users, customizing the Axon interface, and troubleshooting issues. Audience The audience for this guide is the Axon administrator. You can perform many of the administrative tasks in the Axon Admin Panel. The Admin Panel is available in the Axon interface if you have the Admin or SuperAdmin profile. To access the Admin Panel, perform the following steps: 1. Log in to Axon with an Admin or SuperAdmin profile. 2. From the Axon toolbar, click the Admin Panel menu item under your user name. You can perform some of the administrative tasks from the Linux environment. To work in the Linux environment, you must have sudo user or root user privileges. For information about the tasks that WebUsers can perform, see the Axon Data Governance 5.2 User Guide. 9

10 Axon Architecture The following image shows the architecture components of Axon: The following sections describe the architecture components: Axon The Axon application consists of the core Axon component, several application services and microservices, and databases. These components exchange information with each other using REST APIs. Component Axon Core Axon Agent Description The service that allows Axon users to implement data governance in their organization through a Web interface. Axon uses the Apache HTTPD service for the Web interface. The service that reads Data Quality rules in Axon and retrieves the scores from Informatica Data Quality according to the schedules defined in Axon. Services Axon uses several application services and microservices to provide specific functionality that enable you to implement data governance. These services are independent modular services that work together to enhance Axon capabilities. Component Notification Change Request Description The service that notifies Axon users about changes to user roles, status of workflows and change requests, and status of bulk upload tasks. Change requests provide a controlled and audited process to make changes to Axon objects. Axon uses the Camunda service for managing and executing workflows within a change request. 10 Chapter 1: Overview

11 Component Bulk Upload Document Upload Value List Unison Description The service that uploads a large number of Axon objects and saves them to the PostgreSQL database. The service that attaches and maintains reference documents to an Axon object. The service that creates or updates a large number of values for data set attributes and saves the values to the PostgreSQL database. The service that enables Unison Search. When you run a Unison search, Axon searches for the objects and the linked objects in all the available facets. Persistent Layer The components in the persistent layer store data that can be retrieved by the application services and microservices. Component Objects Database Graph Database Search Engine Messaging Description Axon stores all user-created objects in a PostgreSQL database. This is the primary data store. Axon stores object relationships and relationship graphs in an OrientDB database. The objects in this database are generated from the objects database. Axon uses this database for maps and Unison Search. The service that enables Quick Search. When you run a Quick Search, Axon searches the objects database and displays all results that match the search terms that you enter. Axon uses the Apache Solr service to enable Quick Search. The messaging queues that Axon requests and processes based on the rules defined by the administrator. Axon uses the RabbitMQ service as the message broker. Informatica Products Axon connects to other Informatica products to retrieve and display metadata so that you can make informed business decisions. Component Enterprise Data Catalog Data Quality Secure@Source Description Enterprise Data Catalog brings together all data assets in an enterprise and presents a comprehensive view of the data assets and their relationships. Axon integrates with Enterprise Data Catalog to discover and retrieve enterprise metadata. Data Quality is a comprehensive set of tools that measure and verify if your enterprise data complies with quality standards. Axon integrates with Data Quality to retrieve data quality scores and display them in Axon dashboards. Secure@Source is a data security product that identifies sensitive data across your organization. Axon integrates with Secure@Source to display the security level for your enterprise data and metadata. Axon Architecture 11

12 External Components Axon connects to external components to securely retrieve user credentials so that users can seamlessly log in to Axon. Component SSO Identity Provider Description Third-party Identity Providers (IDPs) that integrate with Axon to provide Single Sign-on (SSO) for Axon users in your organization. Administration Process As an Axon administrator, you can perform the following types of administrative tasks after installing Axon: Configuration: One-time tasks that are required to set up Axon after installation. Customization: Settings that change the look and feel of your specific Axon instance. Monitoring: Regular operational tasks that are required to keep Axon running without problems. Troubleshooting: Maintenance activities that are required to fix problems when errors occur. 12 Chapter 1: Overview

13 C h a p t e r 2 Configuring Axon As the administrator, you can configure Axon Data Governance to provide correct permissions to the users so that they can log on to Axon successfully and work with the Axon objects. You can also configure Axon to connect with other Informatica products. The tasks are one-time configurations that set up Axon for use in your organization. User Roles A role is a collection of permissions. Permissions that you assign to a role determine the actions that users who are assigned the role can perform. When you assign a role to a user, you also define the scope of the permissions by specifying the facet for which the role applies. A user can perform one or more of the following types of tasks based on the permissions that you assign: New. Create objects. Edit. Edit objects. View. View objects. Stakeholders have business or technical expertise on the object. The following types of stakeholder roles are available in Axon: Authority Role Knowledge Role Ownership Role SMR Role Stewardship Role As an administrator, you can assign one of the stakeholder roles to any Axon user. When you make a user a stakeholder for an object, other users see that the stakeholder user has ownership or responsibility for the object. Typically, you assign stakeholder roles to Axon users according to the specific expertise that the users demonstrate. If an Axon user is not available to perform a task that is required by a role, you can assign the same stakeholder role to another user. Configure Roles Axon provides a number of default roles. You can configure new roles based on the needs of your organization. 13

14 2. In the menu on the left, click Roles and Responsibilities under DG Operating Model. 3. Click Edit. 4. In the Roles and Responsibilities page, click the + icon to add a new role. 5. Configure the following properties: Option PrimaryName Description Default Module Role Type Description Provide a name for the role. Provide a description for the role. Select the checkbox to make this a default role when you save an object. All objects need at least one default role. If you select this option, you must assign the Edit permission to the role. From the drop-down menu, select a module. In the object page, you can filter the grid by module to quickly find the role. From the drop-down menu, select a role type. The role type affects dashboards and scorecards. 6. Click Save and Close. Object Permissions Configure the actions that a role can perform by assigning permissions. When you assign permissions to a role, all users who are assigned the role inherit the permissions. You can grant the following permissions: New Edit View A role with the New permission can create objects within the same facet as the object for which you have assigned the role. A role that has the Edit permission on an object can edit and update the object properties. A user with the View permission can view objects. All Axon users have the View permission. The following table lists the permissions for Axon users when they search for "Deleted" objects in Unison search: User Profile Deleted Objects Appear in Unison Search Can Open Deleted Objects from Unison Search User not logged into Axon No No WebUser with no stakeholder role No No 14 Chapter 2: Configuring Axon

15 User Profile Deleted Objects Appear in Unison Search Can Open Deleted Objects from Unison Search WebUser with stakeholder role No No Admin or SuperAdmin Yes Yes The following table lists the permissions for Axon users when they search for "Non-Public" objects in Unison search: User Profile Non-Public Objects Appear in Unison Search Can Open Non-Public Objects from Unison Search User not logged into Axon No No WebUser with no stakeholder role Yes No WebUser with stakeholder role Yes Yes Admin or SuperAdmin Yes Yes Assign Permissions to Roles Permissions define the level of access that users have on objects in a facet. You must define the scope of the permission by selecting the facet for which the role is valid. All users who are assigned the role inherit the permissions. 2. In the menu on the left of the page, click Role Permissions under DG Operating Model. 3. Click Edit. 4. Click the + icon against the role that you want to update. 5. Configure the following properties: Option Module Role Permission Description From the drop-down menu, select the facet for which the permissions is valid. From the drop-down menu, select the role for which the permission is valid. From the drop-down menu, select the type of permission that you want to assign to the role. 6. Click Save and Close. Change Default Administrator Password Informatica recommends that you change the default administrator password after you install Axon. 1. From the Axon toolbar, click the My Account menu item under your user name. Change Default Administrator Password 15

16 2. In the About Me tab, click Edit. 3. In the Password and Confirm fields, enter your new administrator password. 4. Click Save and Close. Provide Permissions to the Axon Folders You must provide read, write, and execute permissions recursively to the cache and logs folders. This step makes sure that the Axon web interface appears correctly for all users. 1. Enter the following command to provide the permissions to the cache folder: chmod -R 777 <INSTALLATION_DIR>/axonhome/axon/app/cache/ 2. Enter the following command to provide the permissions to the logs folder: chmod -R 777 <INSTALLATION_DIR>/axonhome/axon/app/logs/ Default Workflows Default workflows are specific to a facet and apply to all the objects in the facet. Each facet can have multiple default workflows. If you want multiple objects to follow a workflow, create a default workflow. For example, you can use one or more default workflows to control changes to any objects in the Glossary facet. A SuperAdmin user can configure and manage default workflows. Create and edit a default workflow from the Admin Panel menu. To edit a default workflow, you must select a facet and workflow. You can assign tasks to different roles that are defined for the facet. Create a Default Workflow You can create default workflows for a facet. The default workflow applies to all the objects in the facet. You must have a SuperAdmin profile to create a default workflow. 1. From the Axon toolbar, click Admin Panel under the user name. The Admin Dashboard appears with the Axon version details, status of Axon services, and Axon message queues. 2. On the left navigation pane, click DG Operating Model > Default Workflows. 3. Select the facet for which you want to configure a workflow. 4. Choose to add a new workflow. 5. Enter a name for the workflow. The name must contain a minimum of six characters. 6. Provide a description for the workflow. Axon creates a canvas with many swimlanes based on the roles that are defined for the facet. 7. In Workflow Diagram section, create a workflow diagram on the canvas. Use the Toolbar to add objects and connect them. Use the Properties panel to specify additional properties for the objects. 16 Chapter 2: Configuring Axon

17 8. In the workflow diagram, specify the required fields for the following items: User Task. You need to enter a name and due date for a user task. Exclusive Gateway. Specify short, unique labels for the lines that start from an exclusive gateway. The labels serve decision routing actions when you run the workflow. A gateway and the preceding user task must be close to one another in the same swimlane because they both are a logical unit and must be performed by the same user. 9. Click Save. Add Users You can add users to Axon by manually creating a People object or by bulk uploading People objects. To manually create a People object or to bulk upload People, you must have the Admin or SuperAdmin profile. Before you can create People objects, you must create the necessary Org Unit objects. You can create Org Units manually or by bulk importing objects. When you add a People object, you may require to configure the Manager property. The Manager property specifies the reporting structure. Ensure that the Manager accounts are available in Axon before you create the People objects. If your organization uses Single Sign-On, you can link the People facet to an external databases such as LDAP. You can link the Org Unit facet to a HR view. If you link the People facet to an external database, you do not create People and Org Unit objects. Bulk Upload Users to the People Facet You can bulk upload a large number of People objects to Axon. Specify data in a Microsoft Excel sheet and upload the sheet to Axon. You must have the Admin or SuperAdmin profile to bulk upload data to Axon. 1. In the Axon toolbar, click Upload from file from the Create menu. Axon displays the Upload from File page. Use the wizard to make choices related to bulk uploading of data. 2. In the Choose File step of the wizard, download an object template for People. 3. Configure the following properties in the Microsoft Excel file: Field First Name Last Name Function Function Description Description Description Required. First name of the user. Specify the name as it is recorded in the LDAP directory server of your organization. Required. Last name of the user. Specify the name as it is recorded in the LDAP directory server of your organization. Job title or role of the user. Job description of the role of the user. Description about the user. Add Users 17

18 Field Password Org Unit Reference Profile Office Location Internal Mail Code Office Telephone Mobile/Cell LAN ID Employment Type Lifecycle Description Required. address of the user. Must be unique. Axon sends s to this address. A password to provide access to the user. The user can change the password later. Not required if you enable Single Sign-On authentication. Required. The reference identifier of the organizational unit that the user is associated with. Required. A user profile that controls the tasks that the user can perform and the objects that the user can view. Select one of the following user profiles: - WebUser - Admin - SuperAdmin - Data Importer Office location of the user. Internal office mail code of the user. Office phone number of the user. Mobile phone number of the user. Network ID of the user. LAN ID might be required if you want to enable Single Sign-On authentication. If the LAN ID column is empty, you must not map the LAN ID column of the template to any field in the Axon Field column when you perform a bulk upload. Required. The type of employment of the user. Specify whether the employment of the user is external or internal. Required. The status of the employment of the user. You can select one of the following default statuses: - Working - Temporarily Inactive - Pending Deactivation - Left the Company An administrator can configure these values. Specify customized values if your organization does not have the default values. 4. Select the file from your computer and choose to update existing objects or upload new items. 5. Click Next - Map Columns. 6. In the Map Columns step of the wizard, map the columns in the Excel file to the properties that Axon supports. You can select the column that is present in the Excel file that you want to map to the Axon field from the drop-down menu from the Column in Uploaded File property. 7. To continue with the bulk upload wizard steps, click Next - Start Upload. 8. In the Upload step of the wizard, review the progress of the upload task. Axon displays a progress bar and a message to indicate the progress of the upload task. 18 Chapter 2: Configuring Axon

19 Manually Add Users to the People Facet You create users in the People facet like how you create other objects in Axon. You must be logged in with an Admin profile to create People. 1. From the toolbar, click Create. 2. From the sub-menu, click People under Organizational. 3. Configure the following properties in the Summary tab: Option Password Confirm Profile Axon Status First Name Last Name Description Org Unit Function Name Function Description Description address of the person. Must be unique. Axon sends s to this address. Optional. Provide a password. The user can change the password later. Not required when using Single Sign-On Repeat the password. User profile assigned to the person. The object is always saved with the WebUser profile, regardless of the value that you select here. Note: To change the profile after you save the object, open the object in Edit mode and select a different profile value. Status of the object. First name of the user. Specify the name as it is recorded in the LDAP directory of your organization. Last name of the user. Specify the name as it is recorded in the LDAP directory of your organization. Other relevant information about the user. Axon displays this information in the About Me section. Organization unit that the user is associated with. Job title or role of the user. Job description of the role of the user. 4. Click Save & Close to save the user details. Configure Glossary Rules Engine You can configure Axon to customize the search behavior and automate connections to Glossary items are made. You need a SuperAdmin profile to access the Automatic Glossary Assignment Dashboard page. In this page, you can find links that describe the application of the glossary term around the business. 2. In the super admin menu on the left of the page, click Glossary Rules Engine under Operational Management. Configure Glossary Rules Engine 19

20 3. Configure the following properties in the Summary tab of the Automatic Glossary Assignment Dashboard page: Option Choose System Only Process Uncategorised Attributes? Choose Commit Mode Include RI Copy-Across Categoriser? Include Custom Rules? Include PK Copy-Down Categoriser? Include Closure Categoriser? Later Passes Can Overwrite Earlier Ones? Description From the drop-down menu, select the system you want to run rules against. Select Yes to apply changes to glossaries that currently have no glossary assigned to them. Select No to alter existing glossary assignments. Select Dry Run Mode to highlight changes that can be made without affecting any data. Select Full Commit Mode to apply changes to glossaries in Axon. Choose to copy glossary information across the attribute lineage. Select No to not copy glossary information across the attribute lineage Choose to include any rule based assignment. Select No to exclude any rule based assignment. Choose to copy data set glossary information to the primary key attributes within the data set. Choose to trigger additional logic as configured on the Axon instance. Choose to avoid lower ranked rules to affect previous pass rules. 4. In the Manually Override Rule property, enter a comma separated list of rule IDs. Axon runs only the given collection of rules. 5. Review the attributes that match the rules and search engine settings. When you run these changes in full commit mode, the values Axon changes the glossary assignment based on the summary in the Affected Items grid. 6. Click Run. Configure Dropdowns You can assign classifications when you create objects. If you have a SuperAdmin profile, you can create new classifications or modify the default classifications to suit the needs of your organization. 2. In the menu on the left, click Dropdown Configurations under Meta-Model Administration. 3. In the Dropdown Configurations page, select a module from the drop-down list in the Choice property. Axon filters the list of choices to display the options available in the facet that you selected. 4. Click the module that you want to edit. Axon displays the configuration menu editor. 5. In the configuration page, click the + icon to add a new item to the drop-down menu. For example, if you selected Process Duration Type, you can add more values, such as seconds and minutes. 20 Chapter 2: Configuring Axon

21 6. Configure the following properties: Option PrimaryName Description Description Specify a name that Axon will display in the drop-down menu. Specify a description that Axon will display in the drop-down menu. 7. Click Save and Close. Configure Static Pages Axon contains a number of static HTML pages. If you have a SuperAdmin profile, you can customize the static pages. 2. In the menu on the left, click Static Page Editor under Meta-Model Administration. To create a new static page, click + New Static Page from the Actions menu. To edit an existing static page, click the title of the static page. 3. Configure the static page properties. Option Title Link Context Content Homepage Description Specify a title for the static page. Axon does not display the title anywhere. Specify a link for the static page. Axon configures the URL of the page in the following format: <Axon_URL>/<link> Specify a description for the static page. Axon does not display the context anywhere. Specify the content that is displayed in the static page. You can use HTML tags to format the content. Choose to make this page the homepage. 4. Click Save and Close. Specify Support Address To contact the support team, Axon users can click the? icon and then select Contact Support. You can change the default address for Axon support when users choose to contact the support team. You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. Configure Static Pages 21

22 3. In the Group dropdown, select Options. 4. Click Edit. 5. In the Support field, enter the default address for Axon support. 6. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 7. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 8. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Configure Single Sign-On When you enable Single Sign-On (SSO), users can log in to Axon using login credentials that are common to other applications in your organization. Axon uses SSO to authenticate users based on the Identity Provider (IDP) credentials. To enable SSO, you must configure Axon as an application in the IDP tool. Axon supports any IDP that uses SAML 2.0 authentication. The steps to configure SSO for Axon are shown in the following diagram: 22 Chapter 2: Configuring Axon

23 Create a New Application in the IDP You must first add Axon as an application in the IDP. 1. Log in to the IDP configuration page and choose to add a new SAML 2.0 application. 2. Enter the new application name as Axon. Configure Axon Details for the New Application in the IDP To configure Axon in the IDP, perform the following tasks: 1. Set the name ID format and username format of users to . This step makes sure that the IDP expects the Axon user's name ID and username in the format of an address 2. Set the SSO domain URL to This URL is the endpoint for SSO login to Axon. 3. Set the audience URL to This URL is the service provider metadata that is obtained from Axon. 4. Set the following properties for the SAML attributes: Property orgunit Value Organization unit of the Axon user status Status of the Axon user in the IDP database. Set the value to 1. firstname lastname orgunitdescription orgunittitle First name of the Axon user Last name of the Axon user Organization unit description for the Axon user Title of the Axon user in the organization unit address of the Axon user Note: Make sure that these 7 properties are configured for every Axon user in your organization. If a property is not configured, you must add the property in the IDP and enter valid values of the property for each Axon user. 5. In the IDP, provide access to the new Axon application to all Axon users and user groups. Generate a SAML Metadata for Axon in the IDP After you have configured Axon in the IDP, you must obtain the SAML metadata. The SAML metadata is used when you configure Axon to use the IDP. The SAML metadata contains the following properties: Identity Provider Endpoint SSO Entity ID X.509 Certificate Make a note of the values of these properties. You must enter these values when you configure Axon. Note: The SAML metadata is based on the configuration parameters that you have entered in the IDP. If you modify any of the parameters in the IDP, you must generate new SAML metadata values. Configure Single Sign-On 23

24 Configure Axon and Enter the SAML Metadata Values Perform the following steps to configure Axon to use SSO: You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 3. In the Group dropdown, select SAML Configuration. 4. Click Edit. 5. In the SSO URL field, enter http(s)://<axon_url>/saml/login. This URL redirects the user from the Axon login page to the SSO login page. 6. In the IDP Endpoint, IDP Entity ID and IDP X.509 Certificate fields, enter the values of the properties that you noted in the SAML assertion. Note: Enter the value of the X.509 certificate in a single line without any line breaks. 7. Click Save. Clear the Axon Cache and Restart Services After you have configured Axon in the identity management tool and configured the Axon SAML files, you must update the Axon cache with the new configuration values. 1. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 2. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 3. Run the following command to restart the HTTPD service: service httpd restart Configure Access Control You can define access control for users that log in to Axon. You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 3. In the Group dropdown, select Environment. 4. Click the Edit button, and then click the Edit icon. 5. In the Provide Access Control List Configuration window, define the Access Control List (ACL) method and role for Axon users. 6. Click Save to save your changes in the Provide Access Control List Configuration window. 7. Click Save in the main Configure Axon page to save your settings. 8. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 24 Chapter 2: Configuring Axon

25 9. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 10. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Configure Access to Enterprise Data Catalog If you selected the advanced configuration option during Axon installation, you would have entered the configuration settings for Enterprise Data Catalog. If you did not select advanced configuration during Axon installation or if you want to update the connection settings for Enterprise Data Catalog after the installation, go to the Axon Admin Panel. You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 3. In the Group dropdown, select Enterprise Data Catalog. 4. Click Edit, and configure the following properties: Property Enterprise Data Catalog Server Host Enterprise Data Catalog Server Port Enterprise Data Catalog Server Login User Name Enterprise Data Catalog Server Login Password Enterprise Data Catalog Server Login Namespace Enterprise Data Catalog Axon Resource Name Description URL of the Enterprise Data Catalog service in the following format: http(s)://<host_name> or http(s)://<ip_address> Port number of the Enterprise Data Catalog service User name to log in to Enterprise Data Catalog server Password to log in to Enterprise Data Catalog server User security domain of Enterprise Data Catalog server Resource name in Enterprise Data Catalog that is configured to connect to your specific Axon application 5. Click Save. 6. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 7. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 8. Run the following command to restart the HTTPD service: service httpd restart Configure Access to Enterprise Data Catalog 25

26 Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Connect to an SSL-Enabled Enterprise Data Catalog Instance To connect Axon to an instance of Enterprise Data 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, make sure that the output displays the following libraries: nss-sysinit el7.x86_64 nss-tools el7.x86_64 nss-util el7_2.x86_64 nss el7.x86_64 You can connect to an SSL enabled instance of Enterprise Data Catalog if the console displays the following information after you run the command: curl (x86_64-redhat-linux-gnu) libcurl/ 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 Quality If you have installed the Axon Agent, you must specify the details of the Axon Agent installation in Axon. Axon uses the parameters you specify to connect to Informatica Data Quality. You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 26 Chapter 2: Configuring Axon

27 3. In the Group dropdown, select Data Quality. 4. Click Edit, and configure the following properties: Property Data Quality Server Host Data Quality Server Port Description Host name of the system where you installed the Axon Agent Port number on which the Axon Agent runs 5. Click Save. 6. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 7. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 8. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Configure Access to Secure@Source If you selected the advanced configuration option during Axon installation, you would have entered the configuration settings for Secure@Source. If you did not select advanced configuration during Axon installation or if you want to update the connection settings for Secure@Source after the installation, go to the Axon Admin Panel. You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 3. In the Group dropdown, select Secure@Source. 4. Click Edit, and configure the following properties: Property Secure@Source Server Host Secure@Source Server Port Secure@Source Server Login User Name Secure@Source Server Login Password Description URL of the Secure@Source service in the following format: http(s)://<host_name> or http(s)://<ip_address> Port number of the Secure@Source service User name to log in to the Secure@Source server Password to log in to the Secure@Source server Configure Access to Secure@Source 27

28 Property Server Login Namespace Description User security domain of 5. Click Save. 6. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 7. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 8. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Specify Prefix for Object Reference Numbers Each Axon object is stored in the database with a unique reference number. For each object type, you must specify the prefix for the reference number. This helps you quickly identify an object type when you search for the objects in the database. For example, if you prefix policy reference numbers with "POL-", you can identify the POL object as a policy. You must have the Super Admin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 3. In the Group dropdown, select Reference Number Settings. 4. Click the Edit button, and then click the Edit icon. 5. In the Facets Reference Number window, enter the prefixes for the Axon object types. 6. Click Save to save your changes in the Facets Reference Number window. 7. Click Save in the main Configure Axon page to save your settings. 8. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 9. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 10. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. 28 Chapter 2: Configuring Axon

29 Update Cache with Configuration Values Some Axon configurations in the Admin Panel are saved to the Axon database, but these configuration values are not loaded to the Axon cache. To make the configuration changes available to the Axon users, you must update the Axon cache with the new configuration values. You must update the Axon cache when you perform the following configurations: Change the support address Configure delivery options Configure a SAML 2.0 application to work with Axon Configure Access Control Configure access to Enterprise Data Catalog Configure access to Data Quality Configure access to Secure@Source Specify prefix for the reference numbers of Axon objects After you make the above configurations, perform the following steps in the Linux environment to clear the Axon cache and load the cache with the new configuration values: 1. Run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 2. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 3. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Update Cache with Configuration Values 29

30 C h a p t e r 3 Customizing Axon You can change the look and feel of the Axon Data Governance instance to match the specific needs of your organization. Display Your Organization Logo You can replace the logo in the Axon toolbar with the logo of your organization. 2. In the menu on the left, under the Customize & Configure category, click Change Logo. 3. In the Upload Logo field, click Browse to select the image file that contains the logo of your organization. 4. Click Save to upload the file to Axon. 5. Run the following commands in the Linux environment to stop the HTTPD and Memcached services, clear the contents of the cache directory, and start the HTTPD and Memcached services: service httpd stop <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached stop rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached start service httpd start Customize the Axon Interface Theme You can change the colors of the Axon interface to reflect the theme and colors of your organization. 2. In the menu on the left, under the Customize & Configure category, click Customize Styles. 3. In the Upload Custom CSS field, enter the stylesheet content for the theme and colors of your organization. 4. Click Save. 5. Run the following commands in the Linux environment to stop the HTTPD and Memcached services, clear the contents of the cache directory, and start the HTTPD and Memcached services: service httpd stop <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached stop rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached start service httpd start 30

31 C h a p t e r 4 Monitoring Axon As the administrator, you can monitor the health of Axon Data Governance. You can verify if the application services and microservices are running. You can also view the privileges of Axon users, schedule jobs, create notifications, and back up the database. These are tasks that you must do on a regular basis to keep Axon running. View System Information Administrators can view system information from the Admin Panel. Axon displays static information and real time information. Use the system information to troubleshoot Axon before you contact Informatica Global Customer Support. Axon displays the following static information in the Admin Panel: Axon version Axon build Axon core Build date Axon displays the following real time data in the Admin Panel: Status of the Axon services Axon message queue Axon represents the status of Axon services using colors, and reports the health of the application services. A green-colored dot next to a service means that the service is healthy. A red-colored dot indicates that the service has shut down. You can also check the status of specific services from the Linux environment. To check the status of a service, run the following command as a root user or sudo user: service <service_name> status For example, to check the status of the Search service, run the following command: service tomcat-solr status For the complete list of services used by Axon, see the Working with Services topic in the Monitoring Axon chapter. 31

32 View Licensed Users You can view the count and list of licensed users that have create or edit permissions in Axon. The licensed users include SuperAdmin, Admin, and any other user that is assigned a role with create or edit permissions. View the number of licensed users and the list of users to verify that the licenses are effectively used in your organization. For example, if you buy 20 licenses and if you find that your organization uses only 15 licenses, you can assign the remaining licenses to additional users. If the licenses used are more than 20, then you can revoke some of the licenses. Log in with the SuperAdmin profile to view the number of licensed users from the Admin Dashboard. To view the list of licensed users, click DG Operating Model > Licensed Users. You can filter the results based on the type of user profile, first name, and last name. Manage Locks Locks prevent users from editing an object. With an Admin profile, you can manage locked objects. A content manager can assign one of the following types of locks: Edit Lock This lock prevents other users from editing an object that is currently being edited by a content manager. After a content manager finishes editing the object and clicks Save and Close, Axon removes the edit lock. You can manually remove an edit lock if Axon does not automatically remove the edit clock after the content manager finishes editing the object. Permanent Lock Content managers can assign a permanent lock to an object that they are editing. Permanent locks persist even after the object is closed. This prevents other users from editing the item until the content manager who assigned the lock unlocks the object. Axon displays the name of the user who has assigned the permanent lock when you hover the cursor over the lock. As an administrator, you can unlock an object that has a permanent lock. Before you remove a permenant lock, you must contact the content manager who placed the lock to ensure that edits made to the object are not lost. Monitor Scheduled Jobs You can monitor the scheduled jobs created by the Jobber utility. You can view the details of scheduled jobs and the error messages for failed jobs. See all scheduled jobs To see the list of all jobs scheduled by Jobber, run the following command: <INSTALLATION_DIR>/axonhome/third-party-app/jobber/bin/jobber list See notification logs The <user_name> file contains the error messages, if any, for the notifications. To view the error messages, run the following command: 32 Chapter 4: Monitoring Axon

33 vi /var/spool/mail/<user_name> Configure Notifications You can create a time-based job scheduler to receive s from Axon. You must enter the details of the system in the Admin Panel. You must also define the schedule in the.jobber file. You can schedule notifications in the following time intervals: Daily Weekly Monthly Configure Delivery Options To receive notifications, you must enter the details of the server in Axon. You must have the SuperAdmin profile to perform this task. 2. In the menu on the left, under the Customize & Configure category, click Configure Axon. 3. In the Group dropdown, select Options. 4. Click Edit. 5. Configure the following properties: Option Mailer Transport Mailer Host Mailer User Name Mailer Password Mailer Port Disable Delivery Description protocol Your host address Your user name Your password server port Select the check box to disable delivery to Axon users 6. Click Save. 7. In the Linux environment, run the following command to clear the contents of the cache directory: rm -rf <INSTALLATION_DIRECTORY>/axonhome/axon/app/cache/* 8. Run the following command to restart the Memcached service: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 9. Run the following command to restart the HTTPD service: service httpd restart Note: When you clear the cache and restart the Memcached and HTTPD services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the Configure Notifications 33

34 cache after you save your changes in all the Configure Axon pages. Additionally, perform this action during a maintenance period when very few users are using Axon. Create a Daily Notification Schedule Perform the following steps to create a daily notification schedule: 1. Go to the following location: <INSTALLATION_DIR>. 2. Create a new file with the name script.sh. 3. Add the following code to the file: #!/bin/sh php <INSTALLATION_DIR>/axonhome/axon/app/console diaku:process-notifications -- timeframe=daily --env=prod 4. Open the.jobber file available in the <user_home_directory> location. If you have logged in as a sudo user, you must first copy the.jobber file from the /root location to the / <sudo_user_home_directory> location. 5. Configure the following properties in the.jobber file: Property name cmd time onerror Description Notification job name Enter <INSTALLATION_DIR>/script.sh Specify the daily schedule. The six asterisks * * * * * * represent <second> <minute> <hour> <date> <month> <day_of_the_week>. For example, to receive notifications at 5.00 p.m. everyday, enter the following value: * * * Enter Stop 6. Save your changes. 7. If you make changes to the.jobber file, you must reload the Jobber schedule settings. Run the following command to reload the settings: <INSTALLATION_DIR>/axonhome/third-party-app/jobber/bin/jobber reload To send periodic notifications to the Axon user, the Jobber utility runs the script.sh file that you created. You must have write permission in the <INSTALLATION_DIR> directory for the Jobber utility to run the script.sh file. Create a Weekly Notification Schedule Perform the following steps to create a weekly notification schedule: 1. Go to the following location: <INSTALLATION_DIR>. 2. Create a new file with the name script.sh. 3. Add the following code to the file: #!/bin/sh 34 Chapter 4: Monitoring Axon

35 php <INSTALLATION_DIR>/axonhome/axon/app/console diaku:process-notifications -- timeframe=weekly --env=prod 4. Open the.jobber file available in the <user_home_directory> location. If you have logged in as a sudo user, you must first copy the.jobber file from the /root location to the / <sudo_user_home_directory> location. 5. Configure the following properties in the.jobber file: Property name cmd time onerror Description Notification job name Enter <INSTALLATION_DIR>/script.sh Specify the daily schedule. The six asterisks * * * * * * represent <second> <minute> <hour> <date> <month> <day_of_the_week>. For example, to receive notifications at 9.00 a.m. on the third day of each week, enter the following value: * * 3 Enter Stop 6. Save your changes. 7. If you make changes to the.jobber file, you must reload the Jobber schedule settings. Run the following command to reload the settings: <INSTALLATION_DIR>/axonhome/third-party-app/jobber/bin/jobber reload To send periodic notifications to the Axon user, the Jobber utility runs the script.sh file that you created. You must have write permission in the <INSTALLATION_DIR> directory for the Jobber utility to run the script.sh file. Create a Monthly Notification Schedule Perform the following steps to create a monthly notification schedule: 1. Go to the following location: <INSTALLATION_DIR>. 2. Create a new file with the name script.sh. 3. Add the following code to the file: #!/bin/sh php <INSTALLATION_DIR>/axonhome/axon/app/console diaku:process-notifications -- timeframe=monthly --env=prod 4. Open the.jobber file available in the <user_home_directory> location. If you have logged in as a sudo user, you must first copy the.jobber file from the /root location to the / <sudo_user_home_directory> location. 5. Configure the following properties in the.jobber file: Property name Description Notification job name Configure Notifications 35

36 Property cmd time onerror Description Enter <INSTALLATION_DIR>/script.sh Specify the daily schedule. The six asterisks * * * * * * represent <second> <minute> <hour> <date> <month> <day_of_the_week>. For example, to receive notifications at 2.30 p.m. on the seventeenth day of each month, enter the following value: * * Enter Stop 6. Save your changes. 7. If you make changes to the.jobber file, you must reload the Jobber schedule settings. Run the following command to reload the settings: <INSTALLATION_DIR>/axonhome/third-party-app/jobber/bin/jobber reload To send periodic notifications to the Axon user, the Jobber utility runs the script.sh file that you created. You must have write permission in the <INSTALLATION_DIR> directory for the Jobber utility to run the script.sh file. Working with the Axon Agent The Axon Agent is the service that exchanges information between Axon and Informatica Data Quality. The Axon Agent reads the Data Quality rules in Axon that you create for profiles and scorecards. The Axon Agent also reads the scheduling information for the Data Quality rules. At the scheduled time, the Axon Agent retrieves Data Quality scores from Informatica Data Quality. The Axon Agent then updates the corresponding Data Quality rules in Axon with the scores. The following sections provide information on setting up and configuring the Axon Agent if it does not work as expected. Start or Stop the Axon Agent If 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 Agent When the Axon Agent is running, you can monitor its status by viewing the log file. Open the following file to monitor the Axon Agent: 36 Chapter 4: Monitoring Axon

37 <Axon_Agent_Home>/logs/dq-axon/dqagent.log Modify Connection Details You must configure the Axon Agent to connect to other components that are required by Axon. For example, if you update the LDAP namespace of the Informatica domain or update the Axon application URL, you must update the connection details in the Axon Agent to point to the new location. Connect to LDAP-Configured Informatica Domain To point the Axon Agent to the LDAP-configured Informatica domain, edit the dis.securitydomain and mrs.securitydomain properties 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> -- axon.username=admin@informatica.com --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 Interval You 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. Working with the Axon Agent 37

38 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 2. Modify the value for the axon.delayinterval property. Enter the synchronization interval in minutes. The default value is 1 minute. Working With Services Axon uses several application services and microservices to provide specific functionality that enable you to implement data governance. These services are independent modular services that work together to enhance Axon capabilities. Axon uses the following services: Service Bulk Upload Change Request Daemon Tools Document Upload Notification HTTPD Memcached Messaging Notification OdbConsumer OrientDB PostgreSQL Search Unison Search Value List Workflow Service Name axon_bulk_upload_microservice axon_changerequest_microservice axon_daemontools axon_document_upload_microservice jobber httpd memcached rabbitmq-server axon_notification_microservice OdbConsumer orientdb postgresql-9.4 tomcat-solr axon_unison_microservice axon_value_list_microservice camunda 38 Chapter 4: Monitoring Axon

39 Note: The Memcached and Notification services are located in the <INSTALLATION_DIR>/axonhome/ third-party-app/scripts directory. Check the Status of a Service To check the status of a service, run the following command as a root user or sudo user: service <service_name> status For example, to check the status of the Search service, run the following command: service tomcat-solr status To check the status of the Memcached or Notification service, run the following command: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/<memcached_or_jobber> status Start a Service To start a service that is shut down, run the following command as a root user or sudo user: service <service_name> start For example, to start the Document Upload service, run the following command: service axon_document_upload_microservice start To start the Memcached or Notification service, run the following command: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/<memcached_or_jobber> start Stop a Service To stop a running service, run the following command as a root user or sudo user: service <service_name> stop For example, to stop the Unison Search service, run the following command: service axon_unison_microservice stop To stop the Memcached or Notification service, run the following command: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/<memcached_or_jobber> stop Restart a Service To stop a running service and start it again, run the following command as a root user or sudo user: service <service_name> restart For example, to restart the Value List service, run the following command: service axon_value_list_microservice restart To restart the Memcached or Notification service, run the following command: <INSTALLATION_DIR>/axonhome/third-party-app/scripts/<memcached_or_jobber> restart Back Up and Restore Database You can back up the Axon PostgreSQL database and restore it to another Axon instance. You might want to back up and restore the Axon database under the following circumstances: You want to have the same data for multiple Axon instances. You want to restore data that you backed up earlier. Back Up and Restore Database 39

40 You want to move data from a test environment to a production environment. The postgres user must have the following permissions: Read and write permission for the <SOURCE_INSTALLATION_DIR>/scripts/axon_db_backup.sh and <BACKUP_DIR> directories. execute permission to run the backup script file db_backup.sh. Back Up Database To back up the database, run the script file axon_postgres_backup.sh that contains the details of the backup. Perform the following tasks to back up the Axon database at the source location. 1. Go to the <INSTALLATION_DIR>/scripts directory and run the following command to back up the database: sh axon_postgres_backup.sh 2. Go to the <INSTALLATION_DIR>/axonhome/db-backups/postgres_backups location to verify that the database backup file has been created. The database backup is an SQL file inside a subdirectory. This subdirectory name is based on the current date and time: <INSTALLATION_DIR>/axonhome/db-backups/ postgres_backups/<sub_dir>/<backup_sql_file> For example, your backup file might look like this: <INSTALLATION_DIR>/axonhome/db-backups/ postgres_backups/2018_03_24_0257/postgres_2018_03_24_ sql Restore Database Perform the following tasks to restore the Axon database to the destination location: 1. Run the following command to create a temporary directory: mkdir /<TEMP_DIR> 2. Run the following command to copy the backup file from the source host directory to the temporary directory that you have created: scp -r root@sourcehost:<installation_dir>/axonhome/db-backups/postgres_backups/ <SUB_DIR>/<TEMP_DIR> For example, run the following command: scp -r :<INSTALLATION_DIR>/axonhome/db-backups/postgres_backups/ 2018_03_24_0257/<TEMP_DIR> 3. In the postgresql.conf file, change the value of the max_connections property to 900 to increase the maximum number of connections to the database. The postgresql.conf file is available at the following location: /var/lib/pgsql/9.4/data/ 4. Go to the <DESTINATION_INSTALLATION_DIR>/bin destination location where you have installed Axon and run the following command to shut down the Axon instance: sh shutdown.sh 5. Run the following command to restart the PostgreSQL database service: service postgresql-9.4 restart 6. Run the following command to restore the database from the backup file to the destination location: psql -U postgres -f /<TEMP_DIR>/<SUB_DIR>/<backup_sql_file> For example, run the following command: psql -U postgres -f /<TEMP_DIR>/2017_10_24_0257/postgres_2017_10_24_ sql You can ignore any user or role error message that might be displayed. 40 Chapter 4: Monitoring Axon

41 7. Go to the <DESTINATION_INSTALLATION_DIR>/axonhome/axon/app location and run the following command to clear the cache: rm -rf cache/prod/* Restore Axon Settings After copying the database, perform the following tasks to restart Axon, reindex the database, and restore the Axon settings. 1. Go to the <DESTINATION_INSTALLATION_DIR>/bin location and run the following command to start Axon: sh startup.sh 2. Go to the <DESTINATION_INSTALLATION_DIR>/axonhome/axon directory and run the following commands to reindex the database: php app/console diaku:generate-solr php app/console diaku:reindex-solr php app/console diaku:notification:index-users php app/console diaku:workflow:index-groups php app/console diaku:workflow:index-users php app/console diaku:run-full-etl 3. Reapply your Axon customization settings in the.ymlc or.yml files. 4. Check the Enterprise Data Catalog and Informatica Data Quality settings to make sure that they point to the destination Axon instance. 5. Run the following commands to restart the essential Axon services: service axon_daemontools restart service OdbConsumer restart service axon_unison_microservice restart service httpd restart <INSTALLATION_DIR>/axonhome/third-party-app/scripts/memcached restart 6. Run the following command to grant recursive permission to the cache directory: setfacl -R -m u:apache:rwx <DESTINATION_INSTALLATION_DIR>/axonhome/axon/app/cache 7. Verify that all Axon services are running properly. Log in to Axon as an administrator, go to the Admin Panel, and view the Admin Dashboard. The Status of Axon Services section shows the services that are operational. Back Up and Restore Database 41

42 C h a p t e r 5 Troubleshooting Axon If you encounter errors while using Axon Data Governance, try the following solutions before you contact Informatica Global Customer Support. Cannot Log In to Axon If your Axon license expires, users cannot log in to Axon. Logged in users automatically log out of Axon at the time of license expiry. Perform the following tasks if your Axon license expires: Verify that the PostgreSQL Database Service is Running To verify that the PostgreSQL database service is running, run the following command in the Linux environment: service postgresql-9.4 status If the service is shut down, run the following command to restart the service: service postgresql-9.4 restart Replace Your Axon License Key To replace your Axon license key, perform the following steps: 1. Contact Informatica Global Customer Support to obtain a new license key. 2. Replace the expired license key file with the new license key file in the following directory: <INSTALLATION_DIR>/axonhome/license/ Note: Make sure that the new license key file and expired license key file share the same name. 3. Run the service httpd restart command to restart the HTTPD service. Cannot Log In to Axon Using SSO When you enable Single Sign-On (SSO), users can log in to Axon using login credentials that are common to other applications in your organization. Axon uses SSO to authenticate users based on the Identity Provider (IDP) credentials. If users cannot log in to Axon using SSO, perform the following tasks: 42

43 Verify the SSO Settings Make sure that you have configured the SSO settings correctly. For SSO configurations, see the Configure Single-Sign On topic in the Configuring Axon chapter. 1. In the IDP, make sure that Axon is configured as a SAML 2.0 application. 2. In the IDP, make sure that Axon details and the properties for the SAML attributes are entered correctly. 3. If you cannot access the SSO settings in Axon, run the following command from the Linux environment to disable SSO: php app/console informatica:sso-disable 4. In Axon, make sure that the values of the SAML metadata are entered correctly. Verify the SSO Settings in the SAML Response File After Axon users enter their SSO credentials, the IDP sends a SAML response to Axon. Open the response file and verify that the following properties display the correct values for the Axon users: Property orgunit Value Organization unit of the Axon user status Status of the Axon user in the IDP database. The value must be 1. firstname lastname orgunitdescription orgunittitle First name of the Axon user Last name of the Axon user Organization unit description for the Axon user Title of the Axon user in the organization unit address of the Axon user Cannot Log In to Axon Using SSO 43

44 For example, the values for the Axon user John Wilson might look like this: 44 Chapter 5: Troubleshooting Axon

45 Verify that the X.509 certificate values are correctly retrieved from the IDP. For example, the X.509 certificate value might look like this: If you have configured the properties in the IDP correctly, the values in the SAML response file must match the values you enter in the IDP. Axon Does Not Load in the Browser You can access Axon by typing the fully qualified host name in the address bar of a web browser. If Axon does not load in the browser, perform the following tasks. Axon Does Not Load in the Browser 45