Informatica® Data Integration Hub

10.1

Developer Guide
Informatica Data Integration Hub Developer Guide
10.1
June 2016
© Copyright Informatica LLC 1993, 2020

This software and documentation contain proprietary information of Informatica LLC and are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any
form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. This Software may be protected by U.S. and/or
international Patents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III),
as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to
us in writing.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica
On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging,
Informatica Master Data Management, and Live Data Map are trademarks or registered trademarks of Informatica LLC in the United States and in jurisdictions
throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

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

This product includes software developed by the Apache Software Foundation ([Link] 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 [Link] 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 ([Link] 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:// [Link]/licenses/[Link]. 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 [Link] and [Link]

This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@[Link]>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at [Link] 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 [Link] [Link].

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 [Link]

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 [Link]

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:// [Link]/software/ kawa/[Link].

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 [Link]

This product includes software developed by Boost ([Link] or under the Boost software license. Permissions and limitations regarding this software
are subject to terms available at http:/ /[Link]/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:// [Link]/[Link].

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:// [Link]/org/documents/[Link] and at [Link]
This product includes software licensed under the terms at [Link] [Link] http://
[Link]/doc/ [Link], [Link] [Link] [Link] http://
[Link]/doc/ [Link], [Link] , [Link] [Link]
release/[Link], [Link] [Link] [Link] [Link]
license-agreements/fuse-message-broker-v-5-3- license-agreement; [Link] [Link] [Link]
[Link]; [Link] [Link] [Link] . [Link]
Consortium/Legal/2002/copyright-software-20021231; [Link] [Link] [Link]
[Link]; [Link] [Link] [Link] [Link]
software/tcltk/[Link], [Link] [Link] [Link] [Link]
iodbc/wiki/iODBC/License; [Link] [Link] [Link]
[Link]; [Link] [Link] [Link] [Link]
[Link] [Link] [Link] [Link] [Link]
EaselJS/blob/master/src/easeljs/display/[Link]; [Link] [Link] http://
[Link]/[Link]; [Link] [Link]
LICENSE; [Link] [Link] [Link]
master/LICENSE; [Link] [Link] [Link]
LICENSE; [Link] [Link] [Link]
[Link]/[Link]; [Link] [Link]
[Link]; [Link] [Link] [Link]
[Link]; [Link] and [Link]

This product includes software licensed under the Academic Free License ([Link] the Common Development and
Distribution License ([Link] the Common Public License ([Link] the Sun Binary
Code License Agreement Supplemental License Terms, the BSD License (http:// [Link]/licenses/[Link]), the new BSD License (http://
[Link]/licenses/BSD-3-Clause), the MIT License ([Link] the Artistic License ([Link]
licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 ([Link]

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 [Link] This product includes software developed by the Indiana University Extreme! Lab.
For further information please visit [Link]

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 [Link]

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

NOTICES

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

1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES
OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH
OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Publication Date: 2020-05-19

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Informatica Product Availability Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1: Introduction to Data Integration Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data Integration Hub Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Data Integration Hub Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Integration Hub Big Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Operation Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Changing the Operation Console Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Data Integration Hub Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Data Integration Hub Publications and Subscriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Publication Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Subscription Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Developer User Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2: PowerCenter Mappings and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . 21

PowerCenter Mappings and Workflows Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
PowerCenter Workflow Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Batch Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Real-time Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Automatic PowerCenter Mappings and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Automatic PowerCenter Mappings and Workflows Rules and Guidelines. . . . . . . . . . . . . . . 23
Automatic PowerCenter Mappings and Workflows Logs. . . . . . . . . . . . . . . . . . . . . . . . . . 24
Custom PowerCenter Mappings and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Supported Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Custom PowerCenter Mappings and Workflows Rules and Guidelines. . . . . . . . . . . . . . . . . 25
Developing PowerCenter Batch Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Developing PowerCenter Batch Workflows Rules and Guidelines. . . . . . . . . . . . . . . . . . . . 28
Developing PowerCenter Batch Workflows for Publications and Subscriptions Process. . . . . . 28
Step 1. Create the Source and Target Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Step 2. Create the Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Step 3. Create the PowerCenter Workflow and Session. . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Step 4. Save the PowerCenter Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Table of Contents
Developing PowerCenter Real-time Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Developing PowerCenter Real-time Workflows Rules and Guidelines. . . . . . . . . . . . . . . . . . 31
Developing Publication Real-time Workflows Process. . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Step 1. Create the Source and Target Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Step 2. Create the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Step 3. Create and Save the PowerCenter Workflow and Session. . . . . . . . . . . . . . . . . . . . 34
Step 4. Create the Topic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Step 5. Rename the Workflow Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Step 6. Create the Publication Real-time Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 3: Data Engineering Integration and Streaming Mapping and

Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Data Engineering Integration and Streaming Mapping and Workflows Overview. . . . . . . . . . . . . . 36
Data Engineering Integration and Streaming Mappings and Workflows in Data Integration Hub. . . . 37
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Developing Data Engineering Integration Mappings for Publications. . . . . . . . . . . . . . . . . . . . . 38
Step 1. Create Source and Target Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Step 2. Create Source and Target Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Step 3. Create a Mapping with Source and Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Step 4. Add Data Integration Hub Parameters to the Mapping. . . . . . . . . . . . . . . . . . . . . . 39
Step 5. Add an Expression Transformation to the Mapping. . . . . . . . . . . . . . . . . . . . . . . . 39
Step 6. Configure the Mapping Run-time Environment and Create an Application. . . . . . . . . . 40
Developing Data Engineering Streaming Mappings for Publications. . . . . . . . . . . . . . . . . . . . . . 40
Step 1. Create Source and Target Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Step 2. Create Source and Target Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 3. Create a Mapping with Source and Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 4. Add an Expression Transformation to the Mapping. . . . . . . . . . . . . . . . . . . . . . . . 41
Step 5. Add a Java Transformation to the Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 6. Configure the Mapping Run-time Environment and Create an Application. . . . . . . . . . 42
Developing Data Engineering Integration Mappings for Subscriptions. . . . . . . . . . . . . . . . . . . . 42
Step 1. Create Source and Target Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Step 2. Create Source and Target Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Step 3. Create a Mapping with Source and Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Step 4. Add Data Integration Hub Parameters to the Mapping. . . . . . . . . . . . . . . . . . . . . . 43
Step 5. Add a Filter Query to the Reader Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Step 6. Configure the Mapping Run-time Environment and Create an Application. . . . . . . . . . 44
Developing Data Engineering Integration Workflows for Publications. . . . . . . . . . . . . . . . . . . . . 44
Step 1. Develop Data Engineering Integration Mappings for Publications. . . . . . . . . . . . . . . 44
Step 2. Create a Publication Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Step 3. Deploy the Publication Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Developing Data Engineering Integration Workflows for Subscriptions. . . . . . . . . . . . . . . . . . . . 45
Step 1: Develop Data Engineering Integration Mappings for Subscriptions. . . . . . . . . . . . . . 46
Step 2. Create a Subscription Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Table of Contents 5
 Step 3. Deploy the Subscription Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4: Informatica Cloud Mappings and Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Informatica Cloud Mappings and Tasks Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Informatica Cloud Mappings in Data Integration Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Informatica Cloud Mappings Rules and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Data Integration Tasks in Data Integration Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Data Integration Tasks Rules and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Using Intelligent Structure Model in Data Integration Hub. . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5: Data Integration Hub Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Data Integration Hub Workflows Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Managing Data Integration Hub Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Data Integration Hub Workflow Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 6: Data Integration Hub Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Data Integration Hub Transformations Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Installing and Registering Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Configuring Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Handling Transformation Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Data Integration Hub Transformations Rules and Guidelines. . . . . . . . . . . . . . . . . . . . . . . 56
DX_Add_Document_To_Event Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Input Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
DX_Event_Attribute Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
DX_Event_Details Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
DX_Generate_Temporary_File Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
DX_Notification Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
DX_Publication_Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Input Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
DX_Start_Publication Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

6 Table of Contents
DX_Throw_Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Input Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Input/Output Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Data Integration Hub Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 7: Forms Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Forms Designer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Forms Designer User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Forms Designer Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Group Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 8: Data Integration Hub Publications and Subscriptions APIs. . . . . . . . 71

Publications and Subscriptions APIs Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Run Publication Subscription REST API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Run Publication Subscription REST API Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Run Publication Subscription REST API Action Response. . . . . . . . . . . . . . . . . . . . . . . . . 74
Run Publication Subscription Command Line API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Data Integration Hub Run Publication Subscription Command Line API Command Syntax. . . . 74
Run Publication Subscription Command Line API Notifications. . . . . . . . . . . . . . . . . . . . . 76
Change Publication Subscription Mode REST API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Change Publication Subscription Mode REST API Action Response. . . . . . . . . . . . . . . . . . . 77
Reprocess Event REST API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Reprocess Event REST API Action Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Event Status REST API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Event Status API Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 9: Data Extraction APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Data Extraction APIs Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Catalog API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Data Integration Hub Catalog API Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Data Integration Hub Events View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Table of Contents 7
Preface
Use the Data Integration Hub Developer Guide to learn how to create PowerCenter workflows, Data
Engineering Integration mappings, Data Quality mappings, and Informatica Cloud tasks to process Data
Integration Hub publications and subscriptions. It also provides reports on the data processed by Data
Integration Hub.

Informatica Resources
Informatica provides you with a range of product resources through the Informatica Network and other online
portals. Use the resources to get the most from your Informatica products and solutions and to learn from
other Informatica users and subject matter experts.

Informatica Network
The Informatica Network is the gateway to many resources, including the Informatica Knowledge Base and
Informatica Global Customer Support. To enter the Informatica Network, visit
[Link]

As an Informatica Network member, you have the following options:

• Search the Knowledge Base for product resources.

• View product availability information.
• Create and 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 find product resources such as how-to articles, best practices, video
tutorials, and answers to frequently asked questions.

To search the Knowledge Base, visit [Link] If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team at
KB_Feedback@[Link].

Informatica Documentation
Use the Informatica Documentation Portal to explore an extensive library of documentation for current and
recent product releases. To explore the Documentation Portal, visit [Link]

8
 If you have questions, comments, or ideas about the product documentation, contact the Informatica
Documentation team at infa_documentation@[Link].

Informatica Product Availability Matrices

Product Availability Matrices (PAMs) indicate the versions of the operating systems, databases, and types of
data sources and targets that a product release supports. You can browse the Informatica PAMs at
[Link]

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

You can find Informatica Velocity resources at [Link] If you have questions,
comments, or ideas about Informatica Velocity, contact Informatica Professional Services at
ips@[Link].

Informatica Marketplace
The Informatica Marketplace is a forum where you can find solutions that extend and enhance your
Informatica implementations. Leverage any of the hundreds of solutions from Informatica developers and
partners on the Marketplace to improve your productivity and speed up time to implementation on your
projects. You can find the Informatica Marketplace at [Link]

Informatica Global Customer Support

You can contact a Global Support Center by telephone or through the Informatica Network.

To find your local Informatica Global Customer Support telephone number, visit the Informatica website at
the following link:
[Link]

To find online support resources on the Informatica Network, visit [Link] and
select the eSupport option.

Preface 9
Chapter 1

Introduction to Data Integration

Hub
This chapter includes the following topics:

• Data Integration Hub Overview, 10

• Data Integration Hub Architecture, 13
• Data Integration Hub Big Data, 14
• Operation Console, 15
• Data Integration Hub Topics, 15
• Data Integration Hub Publications and Subscriptions, 16
• Developer User Role, 19

Data Integration Hub Overview

Data Integration Hub is an application integration solution that your organization can use to share and
synchronize data between different applications in the organization.

To publish data to Data Integration Hub, first define the data set that you want to manage, for example, sales,
customers, or orders. You define a data set by defining a topic. A topic defines the structure of the data that
Data Integration Hub stores in the publication repository and the type of publication repository where data is
stored. You can manage multiple topics that represent different data sets in Data Integration Hub.
Applications publish data to topics and subscribe to data sets that are represented by topics.

Multiple applications can publish to the same topic, for example, different ordering applications can publish
their orders to the same Orders topic. Multiple subscribers can consume the data from a topic. Different
subscribing applications can consume the data in different formats and in different latencies based on a
defined schedule.

Data Integration Hub stores the data that applications publish to topics in the Data Integration Hub
publication repository. Data Integration Hub keeps the data in the publication repository until all subscribers
consume the data and the retention period expires, and then deletes the data from the publication repository.

Applications can use PowerExchange® adapters and Informatica Intelligent Cloud Services® connectors to
share data from different sources, such as database tables, files, or any sources that Informatica supports.
Each application can be a publisher and a subscriber to different topics.

Publications publish to a specific topic. A publication defines the data source type and the location from
where Data Integration Hub retrieves the data that the application publishes. Subscriptions subscribe to one

10
or more topics. A subscription defines the data target type and the location in the subscribing application to
where Data Integration Hub sends the published data.

When you create a publication or a subscription, you can choose to use either an automatic Data Integration
Hub mapping or a custom Data Integration Hub mapping. Data Integration Hub creates automatic mappings
based on the data structure that you define in the topic. Custom Data Integration Hub mappings are based on
PowerCenter® workflows, Data Engineering Integration mappings, or Data Integration tasks that the
developer creates and maintains for the publication or the subscription.

Data Integration Hub operator uses Enterprise Data Catalog to discover and leverage existing Data
Integration Hub objects, and understand their lineage and impact on other entities in the enterprise.

Examples
You run a data center for a major retail chain. The main office has multiple applications. Some of the
applications are located on-premises and some are located on the cloud. Each retail branch has a point-of-
sale (POS) application and an inventory application. Your applications and branches require the following
data:

Customer service applications

Require up-to-date customer order data.

Sales applications

Require up-to-date product sales data.

Marketing application

Requires a weekly deals report.

Accounting application

Requires a monthly deals report.

Branch applications

Require up-to-date inventory and pricing data.

Business Intelligence (BI) application

Requires a weekly report of sales and marketing data and of user interaction data from the corporate
website, for the preceding 12 months.

With Data Integration Hub, you can address the following use-cases:

Share product catalog and prices.

You can share product price updates from the sales department with each branch, as follows:

1. Create a Products topic.

2. For the Product Information Management (PIM) application, define a publication that publishes
product details and prices to the Products topic and set the schedule to publish the data daily.
3. For each branch application, define a subscription to the Products topic and set the subscription to
consume the published data when it is available in Data Integration Hub.

Share daily sales details.

You can share the daily sales details that you receive from the stores with your central sales application
and your customer service applications, as follows:

1. Create a Sales topic.

2. For each branch application, define a publication to the Sales topic, and set the schedule to publish
daily.

Data Integration Hub Overview 11

 3. For the sales application, define a subscription to the Sales topic, and set the schedule to consume
the data when it is published.
4. For the customer service application, define a subscription to the Sales topic, and set the schedule
to consume the data once a week.

Share deal details from Salesforce.

You can share deal details from a Salesforce cloud application with the marketing and accounting
applications, as follows:

1. Create a Deals topic.

2. For the Salesforce application, define a cloud publication to the Deals topic, and set the schedule to
publish weekly.
3. For the marketing application, define a subscription to the Deals topic, and set the schedule to
consume the data once a week.
4. For the accounting application, define a subscription to the Deals topic, and set the schedule to
consume the data once a month.

Share business intelligence data.

You can share sales data from Salesforce, marketing data from the marketing application, and user
interaction data from the corporate website with the BI application as follows:

1. Create a Business Intelligence topic with a Hadoop publication repository and set the publication
data retention period to 365 days.
2. For the Salesforce application, define a cloud publication to the Business Intelligence topic, and set
the schedule to publish once a week.
3. For the marketing application, define a publication to the Business Intelligence topic, and set the
schedule to publish once a week.
4. For the corporate website application, define a cloud publication to the Business Intelligence topic,
and set the schedule to publish once a week.
5. For the BI application, define an aggregated subscription to the Business Intelligence topic, and set
the schedule to consume the data once a week.

12 Chapter 1: Introduction to Data Integration Hub

Data Integration Hub Architecture
The Data Integration Hub environment consists of user interface clients, data flow engines, Data Integration
Hub services and repositories, and external metadata repositories.

The following image shows the Data Integration Hub components:

Data Integration Hub contains the following components:

Data Integration Hub Operation Console Web client

User interface to manage applications, topics, publications, and subscriptions, and to monitor
publications, subscriptions, and events. Administrators also use the Operation Console to manage users
and system settings. Developers use the Operation Console to manage Data Integration Hub workflows
and connections.

Mappings designer clients

User interfaces to define sources and targets, build custom mappings, and create workflows and tasks.
Use the mappings designers if you use custom mappings.

Data flow engines

Engines that retrieve data from publication sources and send the data to subscription targets. You can
use different flow engines for different use cases. For example, use PowerCenter to publish and
subscribe to on-premises applications, and use Informatica Intelligent Cloud Services to publish and
subscribe to cloud applications.

Data Integration Hub Operation Console service

Service that processes actions that users perform on the Operation Console and creates the structure
for published data sets in the publication repository.

Data Integration Hub Server service

Service that starts and monitors Data Integration Hub workflows for publications and subscriptions.

Data Integration Hub publication repository

Database that stores published data until the subscribers consume the data. After the data retention
period ends, Data Integration Hub deletes the data from the publication repository.

Data Integration Hub Architecture 13

 Data Integration Hub metadata repository

Database that stores metadata for Data Integration Hub applications, topics, publications, subscriptions,
and events.

Operational data store

A repository that contains aggregated information for reporting purposes. When you install the Data
Integration Hub Dashboard and Reports component of Data Integration Hub, Data Integration Hub
creates the operational data store repository based on the database connection details that you supply.

PowerCenter metadata repository

Database that stores metadata for PowerCenter mappings, workflows, and transformations.

Cloud metadata repository

Database that stores metadata for cloud mappings and tasks.

Model Repository Service

Database that stores metadata for Data Engineering Integration and Data Quality mappings and
transformations.

Data sources and targets

Sources and targets that you use to publish and consume data. You can use the following types of
sources and targets:

• Database. Tables and columns.

• File. Binary, text, or unstructured files.
• Application connectors. Connection objects for applications. Available when you use a custom
mapping.
• Hadoop. Hadoop Distributed File System (HDFS) and Hive data warehouses.

Data Integration Hub Big Data

Publish and subscribe to high volumes of data, data streams, and data that you want to store for a long
period of time with Data Integration Hub. For example, store business intelligence data that you need to
review over time on the Data Integration Hub Hadoop publication repository, or publish from and subscribe to
Hadoop Distributed File System (HDFS) and Hive data warehouses.

If you want to keep the published data in the Hadoop publication repository after the data is consumed by all
subscribers, you can configure Data Integration Hub not to delete published data from the repository.

You can use both automatic mappings and custom mappings to publish and consume big data with Data
Integration Hub. For custom mapping publications you can use Informatica Data Engineering Integration
mappings and workflows and Informatica Data Engineering Streaming mappings. For custom mapping
subscriptions you use Informatica Data Engineering Integration mappings and workflows.

14 Chapter 1: Introduction to Data Integration Hub

Operation Console
Use the Operation Console user interface to manage applications, topics, publications, and subscriptions, and
to monitor publications, subscriptions, and events. Administrators also use the Operation Console to manage
users and system settings. Developers use the Operation Console to manage workflows and connections.

You can view the Operation Console in English or in Japanese. You can switch between the display
languages.

The Operation Console contains two areas:

Navigator

Use the navigator to navigate between tasks that you can perform in the Operation Console. The
navigator shows in the left pane of the Operation Console.

Current page

Main work area in which you perform the tasks that you select in the Navigator. The current page shows
in the right pane of the Operation Console.

Changing the Operation Console Language

You can view the Operation Console in English or in Japanese. You can switch between the display
languages.

1. In the browser from where you access Data Integration Hub, set the language to the required language.
2. The Help link opens the online help in English. To view the Japanese online help access the following
URL:
http(s)://<host>:<port>/dih-help-ja
Where:
• <host> is the host name or the IP address of the Data Integration Hub server.
• <port> is the port number of the Data Integration Hub server.
For example:
[Link]

Data Integration Hub Topics

A Data Integration Hub topic is an entity that represents a data domain that is published and consumed in
Data Integration Hub. A topic defines the canonical data structure and additional data definitions such as the
data retention period.

For example, a Sales topic that represents sales data. Applications from all the stores in the organization
publish sales data to the Sales topic. The accounting application subscribes to the Sales topic and consumes
published sales data from all stores, or, if a filter is applied, from specific stores.

Before you define publications and subscriptions for the data that is published and consumed in Data
Integration Hub, you need to define the canonical structure that will hold the data that is published to Data
Integration Hub in the Data Integration Hub publication repository. You define the canonical structure when
you define the topic. You can define multiple topics that represent different source data sets.

Operation Console 15
Data Integration Hub Publications and Subscriptions
Publications and subscriptions are entities that define how applications publish data to Data Integration Hub
and how applications consume data from Data Integration Hub. Publications publish data to a defined topic
and subscriptions subscribe to topics.

Publications and subscriptions control the data flow and the schedule of data publication or data
consumption. An application can be a publisher and a subscriber. Multiple applications can publish to the
same topic. Multiple applications can consume data from the same topic.

You can use automatic, custom, and modular publications and subscriptions to publish data and to consume
data. You can publish from and subscribe to different sources of data. Because the publishing process and
the consuming process are completely decoupled, the publishing source and the consuming target do not
have to be of the same data type. For example, you can publish data from a file and consume it into a
database.

Automatic publications and subscriptions can publish from and subscribe to a relational database, a file, or a
cloud application, or over a REST API.

Custom publications and subscriptions can publish from and subscribe to on-premises applications.

Modular publications and subscriptions can publish from and subscribe to cloud applications.

Publication Process
The publication process includes retrieving the data from the publisher, running any associated mappers,
such as a mapping or a task, and writing the data to the relevant topic in the Data Integration Hub publication
repository. After the publication process ends, subscribers can consume the published data from the
publication repository.

The publication process depends on the publication type.

• Automatic publications can run a Data Integration Hub workflow that is based on a PowerCenter batch
workflow or run over a REST API.
• Custom publications can either run a Data Integration Hub workflow that is based on a PowerCenter batch
workflow, PowerCenter real-time workflow, Data Engineering Integration mapping or workflow, Data
Engineering Streaming mapping, or Data Quality mapping or workflow, or run an Informatica Intelligent
Cloud Services task.
• Modular publications run an Informatica Intelligent Cloud Services mapping.

Publication Process with a Batch Workflow

The publication process for publications that run a Data Integration Hub batch workflow includes the
following stages:

1. When the publisher is ready to publish the data, the Data Integration Hub server runs the publication
batch workflow and sends a request to the relevant Integration Service, either the PowerCenter
Integration Service or the Data Integration Service.
2. The Integration Service extracts the data from the publisher and runs the automatic or custom mapping
on the data.
3. The Integration Service writes the data to the Data Integration Hub publication repository.
4. The Integration Service notifies the Data Integration Hub server that the published data is ready for
subscribers.

16 Chapter 1: Introduction to Data Integration Hub

5. The Data Integration Hub server changes the status of the publication event to complete and triggers
subscription processing.

The following image shows the main stages of the publication process for publications that run a batch
workflow:

Publication Process with a Real-time Workflow

The publication process for publications that run a Data Integration Hub real-time workflow includes the
following stages:

1. The developer runs the real-time workflow. The workflow writes the data to the relevant tables in the
Data Integration Hub publication repository.
2. The Data Integration Hub server triggers a scheduled process and checks for new data in the relevant
tables in the Data Integration Hub publication repository.
3. If new data is found, Data Integration Hub updates the publication ID and the publication date of the data
to indicate that the data is ready for consumption and creates a publication event in the Data Integration
Hub repository.
4. The Data Integration Hub server changes the status of the publication event to complete and triggers
subscription processing.

Publication Process with a Data Integration Task

The publication process for publications that run a Data Integration task includes the following stages:

1. When the publication is triggered, either according to schedule or by an external API, the Data Integration
Hub server triggers the Data Integration task that is defined for the publication through an Informatica
Intelligent Cloud Services REST API.
2. The publication process uses the Data Integration Hub cloud connector to write the data to Data
Integration Hub.
3. The Data Integration Hub server changes the status of the publication event to complete and triggers
subscription processing.

Data Integration Hub Publications and Subscriptions 17

 Publication Process of a Data-driven Publication
The publication process for data-driven publications includes the following stages:

1. After you create a a data-driven publication, you create a POST request to run the publication.
2. When you post the request, Data Integration Hub transfers published data from the request directly to
the Data Integration Hub publication repository, to the topic that you define in the publication.
3. Data Integration Hub creates a Data-driven Publication event, based on the event grouping that is
defined for the publication:
• If the grouping time is set to zero, that is, no grouping is defined for the publication, Data Integration
Hub creates an event each time data is published to the publication repository.
• If you define a grouping time, Data Integration Hub creates an event at the end of each grouping
period that contains publications. For example, if you configure the publication to group publications
every ten seconds, Data Integration Hub creates an event every ten seconds, providing that data was
published to the publication repository during the 10-second period.

Subscription Process
The subscription process includes retrieving the required data from the Data Integration Hub subscription
repository, running any associated mappers, such as a mapping or a task, and writing the data to one or more
subscriber targets. Data Integration Hub keeps the data in the subscription repository until the retention
period of the topic expires.

• Automatic subscriptions can run a Data Integration Hub workflow that is based on a PowerCenter batch
workflow or run over a REST API.
• Custom subscriptions can either run a Data Integration Hub workflow that is based on a PowerCenter
batch workflow, Data Engineering Integration mapping or workflow, Data Engineering Streaming mapping,
or Data Quality mapping or workflow, or run an Informatica Intelligent Cloud Services task.
• Modular subscriptions run an Informatica Intelligent Cloud Services mapping.

Subscription Process with a Batch Workflow

The subscription process for subscriptions that run a Data Integration Hub batch workflow includes the
following stages:

1. When the publication is ready for subscribers, the Data Integration Hub server runs the subscription
batch workflow and sends a request to the relevant Integration Service, either the PowerCenter
Integration Service or the Data Integration Service.
2. The Integration Service extracts the data from the Data Integration Hub publication repository, and runs
the automatic or custom mapping on the data.
3. The Integration Service sends the required data to the subscriber.
4. The Integration Service notifies the Data Integration Hub server after the subscriber consumed the
published data that they require.
5. The Data Integration Hub server changes the status of the subscription event to complete.

18 Chapter 1: Introduction to Data Integration Hub

 The following image shows the main stages of the subscription process for each subscription:

Subscription Process with a Data Integration Task

The subscription process for subscriptions that run a Data Integration task includes the following stages:

1. When the publication is ready for subscribers, the Data Integration Hub server triggers the Data
Integration task that is defined for the subscription through an Informatica Intelligent Cloud Services
REST API .
2. The subscription process uses the Data Integration Hub cloud connector to read data from Data
Integration Hub.
3. The Data Integration task reads the data from Data Integration Hub and then writes the data to the cloud
application.
4. The Data Integration Hub server changes the status of the subscription event to complete.

Subscription Process of a Data-driven Subscription

The subscription process for data-driven subscriptions includes the following stages:

1. When you configure the properties of a data-driven subscription, you enter the URL to where Data
Integration Hub sends notifications when data is ready to consume from the Data Integration Hub
publication repository, from the topic that you define in the subscription.
2. You create a POST request to run the subscription and fetch the data from the Data Integration Hub
publication repository, from the topic that you define in the subscription.
3. When Data Integration Hub sends notifications that data is ready to be consumed from the topic, you
post the request to run the subscription and to fetch the data.

Developer User Role

The Data Integration Hub developer is responsible for developing workflows, mappings, and tasks for custom
publications and subscriptions and for monitoring rules.

Developer User Role 19

 Custom publications and subscriptions

The developer can use a PowerCenter workflow, a Data Engineering Integration mapping, Data Quality
mapping, or an Informatica Cloud task to define the mappings in custom publications and subscriptions.
In publications, the workflow, mapping, or task defines the flow from the publishing application to the
Data Integration Hub publication repository. In subscriptions, the workflow, mapping, or task defines the
flow from the Data Integration Hub publication repository to the subscribing application.
PowerCenter workflow

The developer creates a workflow in PowerCenter Designer. The developer then creates a Data
Integration Hub workflow in the Operation Console and assigns the PowerCenter workflow to the
Data Integration Hub workflow. The developer can customize workflow parameters with the Data
Integration Hub Forms Designer.

The operator then selects the Data Integration Hub workflow when creating the publication or
subscription for an on-premises application.

Data Engineering Integration and Data Engineering Streaming mappings

The developer creates a mapping in the Developer tool. The developer then creates a Data
Integration Hub workflow in the Operation Console and assigns the Data Engineering Integration or
Data Engineering Streaming mapping to the Data Integration Hub workflow. The developer can
customize workflow parameters with the Forms Designer.

The operator then selects the Data Integration Hub workflow when creating a big data publication or
subscription.

Data Quality mapping

The developer creates a mapping in the Developer tool. The developer then creates a Data
Integration Hub workflow in the Operation Console and assigns the Data Quality mapping to the
Data Integration Hub workflow. The developer can customize workflow parameters with the Forms
Designer.

The operator then selects the Data Integration Hub workflow when creating the publication or
subscription for an on-premises application.

Informatica Cloud task

The developer creates a task in Informatica Cloud. The operator then selects the task when creating
the publication or subscription for a cloud application.

Monitoring rules

The developer creates a workflow in PowerCenter Designer. The developer then creates a Data
Integration Hub workflow in the Operation Console and assigns the PowerCenter workflow to the Data
Integration Hub workflow. The developer can customize workflow parameters with the Forms Designer.

The operator then selects the Data Integration Hub workflow when creating the monitoring rule.

The developer also manages source and target connections for publications and subscriptions in the
Operation Console.

20 Chapter 1: Introduction to Data Integration Hub

Chapter 2

PowerCenter Mappings and

Workflows
This chapter includes the following topics:

• PowerCenter Mappings and Workflows Overview, 21

• PowerCenter Workflow Types, 22
• Automatic PowerCenter Mappings and Workflows, 23
• Custom PowerCenter Mappings and Workflows, 24
• Developing PowerCenter Batch Workflows, 27
• Developing PowerCenter Real-time Workflows, 31

PowerCenter Mappings and Workflows Overview

PowerCenter is a processing engine that Data Integration Hub uses to run Data Integration Hub publications
and subscriptions from and to on-premises applications, to run publication pre-processes and subscription
post-processes, and to perform actions for monitoring rules that invoke workflows.

For automatic mapping publications and subscriptions, Data Integration Hub creates the PowerCenter
mappings that process the publications and subscriptions based on the data structure that you define in the
topic. For custom mapping publications and subscriptions, you use the PowerCenter Client tools to develop
the PowerCenter mappings and workflows that process the publications and subscriptions. You also develop
PowerCenter mappings and workflows for publication pre-processing, subscription post-processing, and
monitoring rules that invoke PowerCenter workflows.

After you develop the workflow in PowerCenter, you use the Data Integration Hub Operation Console to
import the PowerCenter workflow into a Data Integration Hub workflow. For details, see GUID-315620DD-
DADD-4F87-927A-77BD6F30F2F8.

The Data Integration Hub operator then creates a publication, a subscription, or a monitoring rule in the Data
Integration Hub Operation Console, and selects the Data Integration Hub workflow or workflows which are
based on the PowerCenter workflow. For more information, see the Data Integration Hub Operator Guide.

You can find sample workflows in the following directory: <DIHInstallationDir>/samples. Each sample
workflow has an associated readme file that describes the sample workflow and contains instructions.

21
PowerCenter Workflow Types
Data Integration Hub uses PowerCenter batch workflows for publications and subscriptions with automatic
mappings.

You can use PowerCenter workflows for publications and subscriptions with custom mappings, publication
pre-processing, subscription post-processing, and monitoring rules that invoke PowerCenter workflows. The
type of PowerCenter workflow that you can use depends on the type of process for which you want to use the
workflow:

PowerCenter Batch Workflows

You can use batch workflows for all processes.

PowerCenter Real-time Workflows

You can use real-time workflows for custom publications.

Batch Workflows
Batch workflows run according to a trigger and not continuously. Data Integration Hub uses batch workflows
to process publications and subscriptions, to run publication pre-processes and subscription post-processes,
and to perform actions for monitoring rules that invoke workflows. Batch workflows use the PowerCenter
Web Services Hub to communicate with PowerCenter.

The following operations can trigger a batch workflow:

• Scheduled publication or subscription starts.

• Operator manually runs the workflow.
• DX_Start_Publication transformation sends a request to the Data Integration Hub server.
• DX_Notification transformation sends a request to the Data Integration Hub server to start subscription
workflows for a completed publication or a request to start a post-processing workflow for a subscription.
• A publication process or a subscription process meets the conditions of a monitoring rule that is
configured to invoke a workflow.
When an publication or a subscription operation triggers a batch workflow, Data Integration Hub creates an
event with a processing status. If the trigger occurs for a scheduled subscription, the event for the
subscription has a delayed status from the time the data is ready to consume until the scheduled
subscription start time. When a monitoring rule invokes a workflow, Data Integration Hub does not create an
event.

Real-time Workflows
Data Integration Hub uses real-time workflows to process publications. Real-time workflows process data
from real-time sources on demand. Real-time sources can be web-service providers, Apache Kafka, or Java
Message Service (JMS) queues.

Real-time workflows are not started by Data Integration Hub. Running and maintaining the workflows is the
responsibility of the Data Integration Hub developer. You can run real-time workflows continuously or on
demand.

When publishing through a real-time workflow, you group the published data into single publications at
predefined time intervals. At the scheduled publication time, Data Integration Hub creates an event with a
processing status.

22 Chapter 2: PowerCenter Mappings and Workflows

Automatic PowerCenter Mappings and Workflows
When you create a publication or a subscription with an automatic mapping, Data Integration Hub creates
PowerCenter components that process the publication or subscription according to the definitions that you
set in the Publication or Subscription wizard.

Data Integration Hub creates the following PowerCenter entities for a publication or a subscription with an
automatic mapping:

• Batch workflow. Scheduled batch workflow that the Data Integration Hub triggers to process the data.
• Data processing session. Session with transformations that extract the data from the publication source
or write the data to the subscription target. The session also includes a mapping, source and target
objects.
• Reporting session. Session that sends and receives notifications about the publication or subscription
process. This session updates the publication or subscription events after processing. The session also
includes a mapping, source and target objects.
• Metadata folders in the PowerCenter repository. The folders contain workflow, mapping, and session
information. A separate folder contains publication or subscription metadata. When you create an
automatic publication mapping, PowerCenter creates subscription source shortcuts based on the
publication target.

Automatic PowerCenter Mappings and Workflows Rules and

Guidelines
When you publish or consume data sets with automatic mappings, consider the following rules and
guidelines:

• Data Integration Hub creates PowerCenter entities for each automatic mapping. Each PowerCenter entity
name starts with the prefix DIH__. Do not manually change or delete the PowerCenter entities.
• You cannot use high precision processing in PowerCenter to run automatic mappings. To use high
precision, use a custom mapping.
• Do not manually change or delete tables in the publication repository that store data sets from
publications with automatic mappings.
• Automatic mappings run with the DIH__STAGING and the DIH__REPO PowerCenter connections. To
prevent publication or subscription failure, do not change or delete the connections.
• When you publish varbinary or nvarchar datatypes from a Microsoft SQL Server database source,
PowerCenter converts the data size limit to a fixed size of 100 MB. If you create a subscription with an
automatic mapping that writes the published data to a Microsoft SQL Server database target, you must
change the data size limit to MAX when you create the target tables before you run the subscription
workflow.
• When you use tables from a default schema to publish from a relational database or to subscribe to a
relational database, the schema name is not persistent.
• When you use tables from a non default schema to publish from a relational database or to subscribe to a
relational database, the schema name is persistent.
• Schema names are saved in the Mapping tab of the PowerCenter session in the following locations:
- For publications, the schema name is saved in the Source properties in the Owner Name field.

- For subscriptions, the schema name is saved in the Target properties in the Target Name Prefix field.

Automatic PowerCenter Mappings and Workflows 23

 Automatic PowerCenter Mappings and Workflows Logs
When you publish or consume data sets with automatic mappings, the PowerCenter Integration Service
creates the following logs:
Publication workflow logs

The PowerCenter Integration Service creates publication workflows with the following settings:

Parameter Value

Save Workflow Log By Runs

Save Workflow Log for These Runs $PMWorkflowLogCount

The value of $PMWorkflowLogCount in the PowerCenter Integration Service determines the number of
logs that the Integration Service creates for each workflow run.

Publication session logs

The PowerCenter Integration Service creates publication workflow sessions with the following settings:

Parameter Value

Save Session Log By Runs

Save Session Log for These Runs $PMSessionLogCount

The value of $PMSessionLogCount in the PowerCenter Integration Service determines the number of
logs that the Integration Service creates for each session run.

Subscription logs

The PowerCenter Integration Service creates subscription workflows with a concurrent run set. The
number of logs is unlimited with timestamps.

Custom PowerCenter Mappings and Workflows

You can develop PowerCenter workflows and import them to Data Integration Hub for the following use-
cases:

• You need to prepare data before you publish it from an on-premises application.
• You require additional processing or transformation to the data set to publish from or to consume into an
on-premises application.
• You need to add logic to data to which you subscribe, for either an on-premises or a cloud application.
• You create a monitoring rule that invokes a workflow when a publication process or a subscription
process meets the conditions of the rule.
You develop the workflows for these use-cases in a similar way that you develop other PowerCenter
workflows. The operator then selects the workflow to use in a publication or a subscription with a custom
mapping, in a publication pre-process or a subscription post-process, or in a monitoring rule, as applicable.

24 Chapter 2: PowerCenter Mappings and Workflows

Supported Datatypes
When you publish data sets to the publication repository with a PowerCenter workflow, you can publish
datatypes based on the database type of the publication repository.

The following table describes the supported datatypes you can publish to the publication repository:

Database Type Datatypes

Oracle - blob
- clob
- number
- number($p, $s)
- timestamp up to 29 bit
- varchar2($l char)

Microsoft SQL Server - bigint

- datetime
- decimal($p,$s)
- float
- int
- nvarchar($l)
- nvarchar(MAX)
- varbinary(MAX)

Custom PowerCenter Mappings and Workflows Rules and

Guidelines
When you develop PowerCenter workflows to use in publications and subscriptions with custom mappings,
publication pre-processes, subscription post-processes, and monitoring rules, consider the following rules
and guidelines:
General rules and guidelines

• Before you develop workflows for Data Integration Hub in PowerCenter, verify that the Data
Integration Hub PowerCenter client and server plug-ins are installed and registered to the
PowerCenter repository. For details, see the Data Integration Hub Installation and Configuration Guide.
• Name and store PowerCenter entities for custom mappings in different folders with a different
naming convention from the naming convention of PowerCenter entities for custom mappings.
• Data Integration Hub uses a separate reporting session to update the status of publication and of
subscription events that use an automatic mapping. It is recommended to create separate sessions
for data processing and reporting, similar to automatic mappings. You can use a workflow for an
automatic mapping as a reference.
• You can use user-defined session parameters in custom workflows and define their values in Data
Integration Hub or in a parameter file. You can manage the values of user-defined session
parameters in Data Integration Hub in the Forms Designer. You cannot manage the values of built-in
session parameters in Data Integration Hub. For more information about session parameters, see the
section "Working with Session Parameters" in the PowerCenter Advanced Workflow Guide.
Note: Data Integration Hub does not support session parameters in the format $InputFile_$
$CustomVariable.
• Informatica recommends that custom publications and subscriptions that use PowerCenter
mappings use the same event statuses and types as those that Data Integration Hub assigns to
automatic mappings. For details, see the Data Integration Hub Operator Guide. You assign event
statuses and types in the DX_Event_Details transformation.

Custom PowerCenter Mappings and Workflows 25

 • To prevent naming conflicts, do not use _DIH__ in the parameter names, and do not use workflow and
mapping parameters with the same names as workflow and mapping parameters that Data
Integration Hub uses in workflows for publications and subscriptions with automatic mappings.
• If you publish from a database source or write to a database target with a different database type
from the publication repository database type, Data Integration Hub converts the data to a data type
that the publication repository database supports. Therefore, if you consume the published data from
the publication repository to a different target database, verify that the data type conversion does not
create run-time errors during processing. For example, if you publish data from a Microsoft SQL
Server database source to an Oracle publication repository, and then consume the published data to
a Microsoft SQL Server database target, MIN or MAX values might be converted to a value that is
higher or lower than values that the Microsoft SQL Server database target supports.
• To use the workflow in Data Integration Hub as a publication workflow or a subscription workflow,
create a Data Integration Hub workflow in the Data Integration Hub Operation Console by selecting
the workflow in the PowerCenter repository or by selecting the exported workflow definition file. For
more information, see GUID-315620DD-DADD-4F87-927A-77BD6F30F2F8.
• For additional rules and guidelines that apply to batch workflows, see “Developing PowerCenter Batch
Workflows Rules and Guidelines” on page 28.
• For additional rules and guidelines that apply to real-time workflows, see “Developing PowerCenter
Real-time Workflows Rules and Guidelines” on page 31.

Publication rules and guidelines

• If you publish from a database source, you cannot use the following special characters in table
names and in column names of a publication target: space ( ), dash (-), and period (.). The publication
process replaces the characters with underscores (_).
• When you develop a publication pre-process workflow, call the DX_Start_Publication transformation
at the end of the pre-processing workflow, for example in a separate mapping. The transformation
instructs the Data Integration Hub server to trigger the publication process. When you configure the
DX_Start_Publication transformation, consider the following guidelines:
- When a publication pre-process starts a single publication, use the DXEventId port. The event ID
ensures that Data Integration Hub uses the same event for both the publication pre-process
workflow and the publication workflow and changes the event status accordingly.
Note: If you do not define a DXEventId port you must define a DXPublicationName port.
- When a publication pre-process starts multiple publications, do not use the event ID in the
DX_Start_Publication transformation. In this case, you can use the Event Details PowerCenter
transformation to change the event status.
Note: Do not call the DX_Start_Publication transformation more than once in a workflow. If you do,
Data Integration Hub starts the publication multiple times.
• When you develop a workflow for a publication with a file source, if the path of the source file is
parameterized, Data Integration Hub picks up the file and moves it to the Data Integration Hub
document store. If the path of the source file is hard coded, a PowerCenter source picks up and
processes the file. For source files with a parameterized file path, the following rules apply:
- For flat file sources, the source file type must be indirect.

- For pass-through file sources, the source file type must be direct.
• When you select a Data Integration Hub workflow that is based on a PowerCenter workflow to use in
a publication with a custom mapping, Data Integration Hub creates the structure of the published
data set in the publication repository based on the target definitions of the workflow.

26 Chapter 2: PowerCenter Mappings and Workflows

 Subscription rules and guidelines

• When you develop a subscription post-processing workflow, call the DX_Notification transformation
at the end of the workflow. You can find a sample post-processing workflow in the following
directory: <DIHInstallationDir>/samples/post_processing_workflow.
• When you develop a workflow for a compound subscription, define the behavior if the compound
subscription starts manually before all published data sets are ready to consume. For example, you
can instruct the mapping to fail the workflow or to ignore empty tables. Published data sets that are
not ready to consume have the publication instance ID 0.
• When you develop a workflow for a subscription with a file target, you can parameterize the target file
path. The following rules and guidelines apply when you parameterize the file path:
- For flat file targets, the target file parameter must start with $OutputFile.

- For pass-through file targets, the target file parameter must start with $OutputFile_DIHRepoFile_.

- When the Data Integration Hub operator creates the subscription in the Data Integration Hub
Operation Console, they must specify the target output file name as the value for the output file
parameter.
- The value of the output file parameter can contain a pattern that ensures that the name is unique for
each file, for example ($sequence).
• When you develop a workflow for a subscription that consumes data from topic tables where delta
detection is applied, add Update Strategy transformations to the mapping, and define the update
strategy for data that exists in the target application. Add one of the following flags for each row in
topic tables where delta detection is applied:

Flag Operation

I Insert row

U Update row

D Delete row

N No operation

Developing PowerCenter Batch Workflows

You develop PowerCenter batch workflows for Data Integration Hub custom mappings in the same way that
you develop other PowerCenter workflows. Data Integration Hub transformations interact directly with Data
Integration Hub.

Developing PowerCenter Batch Workflows 27

 Developing PowerCenter Batch Workflows Rules and Guidelines
When you develop PowerCenter batch workflows to use in publications and subscriptions with custom
mappings and in monitoring rules, consider the following rules and guidelines:

• When you add PowerCenter transformations to a PowerCenter mapping, you can add workflow
parameters that the corresponding Data Integration Hub workflow can use. You can use the Forms
Designer, in the Data Integration Hub Operation Console, to customize the layout and behavior of the
workflow parameters that appear when the operator creates or edits a publication or a subscription with a
custom mapping.
• If you edit the PowerCenter workflow or mapping, you must update the associated Data Integration Hub
workflow by re-selecting the PowerCenter workflow or the XML file in the Data Integration Hub Operation
Console. During the update process, you can resolve changes to workflow parameters and parameter
types. When you change the type of a workflow parameter type, the import process deletes the values for
the imported parameters and you must manually enter the parameter values.
For general rules and guidelines on developing PowerCenter workflows to use with Data Integration Hub, see
GUID-8D713C6A-1BBD-49DD-8AE7-E1011AEE1F3E.

Developing PowerCenter Batch Workflows for Publications and

Subscriptions Process
To develop a batch workflow in PowerCenter that processes Data Integration Hub data, perform the following
steps:

1. Create the source and target definitions.

2. Create the mapping and add transformations.
3. Create the workflow and the session.
4. Save the PowerCenter workflow to the PowerCenter repository.

Note: This process is not applicable for monitoring rule workflows. There are no limitations on how you
define workflows for monitoring rules.

Step 1. Create the Source and Target Definitions

When you develop a publication workflow, you create the source based on the structure of the database or
file that you want to publish and set the target to the publication repository.

If you publish from a database source, verify that you publish datatypes that the publication repository can
store.

When you develop a subscription workflow, you create a source based on the topic structure from the
publication repository. You can copy the source from the publication metadata folder in the PowerCenter
repository.

You create the source and target definitions in the PowerCenter Designer in the same way that you create
source and target definitions for other mappings. For general information about source and target definitions,
see the PowerCenter Designer Guide.

28 Chapter 2: PowerCenter Mappings and Workflows

Creating the Source Definition for a Subscription Workflow
In the PowerCenter Designer, create the source and define the source properties of a subscription workflow.
When you develop a publication workflow, you define the source based on the application from which you
want to publish data.

The source definition process includes the following steps:

1. Create the source object. Set the source connection to DIH__STAGING. You create a source based on the
topic structure from the publication repository. You can copy the source from the publication metadata
folder in the PowerCenter repository.
2. Add variables to filter the published data to consume. For example, you can select to consume data from
a specific table in the publication repository.
3. Add the required fields that determine the data set to consume. You can define multiple data sets to
consume, similar to an aggregated or a compound subscription with an automatic mapping.

The following table describes the fields to add to the source object of a subscription workflow:

Field Description

DIH__PUBLICATION_INSTANCE_ID Required. Identifiers of one or more published data sets in a comma-

separated list. Each data set that an application publishes has a unique
identifier. To filter the data to consume, use the value from the $
$<topicName>__PublicationInstanceIDs workflow parameter.
The parameter datatype must be number(19) if you write to an Oracle
database target or number(19,0) if you write to a Microsoft SQL Server
database target.

DIH__PUBLICATION_INSTANCE_DATE Date and time that each application started publishing the data sets, in a
comma-separated list. If you use database partitions, you can filter the data
to consume by using the value from the $
$<topic_name>__PublicationInstanceDatesSQL workflow parameter. The
value format depends on the publication repository database type.
On an Oracle database, the datatype must be date and the value must be in
the following format:
YYYY-MM-DD HH24:MI:SS
On a Microsoft SQL Server database, the datatype must be datetime and the
value must be in the following format:
yyyy-mm-dd hh:mi:ss (24h)
Note: If you want to filter the data to consume with a different transformation,
you can use the $$<topic_name>__PublicationInstanceDates parameter
instead.

You can filter data to consume in the Source Filter attribute of the Source Qualifier transformation in
subscription workflow. The following example shows the field syntax to filter by ID and date range in a single
line:
MY_TABLE.DIH__PUBLICATION_INSTANCE_ID in ($$myTopic__PublicationInstanceIDs)
AND MY_TABLE.DIH__PUBLICATION_INSTANCE_DATE in ($$myTopic__PublicationInstanceDatesSQL)

Developing PowerCenter Batch Workflows 29

 Creating the Target Definition
In the PowerCenter Designer, create the target and add ports to store properties for running the workflow.
You can also add properties to store other Data Integration Hub values that you want to send back from
PowerCenter.

The target definition process includes the following steps:

1. Create the target object. If you develop a publication workflow, use the DIH__STAGING connection in the
target definition. The database target type must match the publication repository database type.
2. If you develop a publication workflow, add the required fields that determine the data set to publish.

The following table describes the required fields to add to the target object of a publication:

Parameter Description

DIH__PUBLICATION_INSTANCE_ID Required. Identifier of the published data set. Each data set that an
application publishes has a unique identifier. The field uses the value from
the $$publicationInstanceID workflow parameter.

DIH__PUBLICATION_INSTANCE_DATE Required. Date and time that the application started publishing the data set.
The field uses the value from the $$publicationInstanceDate workflow
parameter. The value format depends on the publication repository database
type.
On an Oracle database, the value must be in the following format:
to_date('<DATE>', 'YYYY-MM-DD HH24:MI:SS')
On a Microsoft SQL Server database, the value must be in the following
format:
convert(datetime,'<DATE>',120)

Step 2. Create the Mapping

Create a mapping that contains the source definition, target definition, and transformations that you want to
use to process data for Data Integration Hub.

You create a mapping for Data Integration Hub in the same way you build other PowerCenter mappings. Use
Data Integration Hub transformations and Unstructured Data transformations to add product-specific
functionality to the mapping. You can also add other PowerCenter transformation to the mapping.

Step 3. Create the PowerCenter Workflow and Session

Create the workflow and the session that runs the mapping. You create the workflow in the same way you
create other PowerCenter workflows.

1. In the Workflow Designer, create the workflow and the session object. For general information about
creating workflows and sessions, see the PowerCenter Advanced Workflow Guide.
2. Add the transformations that notify the Data Integration Hub server that the publication or that the
subscription process ended.
• If you develop a publication workflow, add the DX_Notification transformation to trigger the
subscription workflows and change the publication event status.
• If you develop a subscription workflow, add the DX_Event_Details to change the subscription event
status.

30 Chapter 2: PowerCenter Mappings and Workflows

 3. Save the session object.
4. Test the workflow to ensure that it works correctly.

Step 4. Save the PowerCenter Workflow

Save the workflow to the PowerCenter repository. After you save the workflow, you can export it from
PowerCenter to an XML file that will be used as the workflow definition file. You must use the Repository
Manager to export the workflow.

Note: Do not save the workflow to a folder where the folder name is prefixed by DIH__pub or by DIH__sub.

Developing PowerCenter Real-time Workflows

You develop PowerCenter workflows for Data Integration Hub in the same way that you develop other
PowerCenter workflows. Data Integration Hub transformations interact directly with Data Integration Hub.

Developing PowerCenter Real-time Workflows Rules and

Guidelines
When you develop PowerCenter real-time workflows to use in publications with custom mappings, consider
the following rules and guidelines:

• Make sure to name and store PowerCenter entities for custom mappings in different folders with a
different naming convention from the naming convention of PowerCenter entities for automatic
mappings.
• You must enable the property Enable high precision in the session that writes data to the Data Integration
Hub publication repository.
• To prevent naming conflicts, do not use _DIH__ in the parameter names, and do not use workflow and
mapping parameters with the same names as workflow and mapping parameters that Data Integration
Hub uses in workflows for publications with automatic mappings.
• The workflows do not generate error messages. Maintaining the workflows is the responsibility of the
Data Integration Hub developer.
• If you have multiple tables in a topic and you want to ensure that the records for all tables are included in
the same publication, change the value of the system property [Link]. For information,
see the Data Integration Hub Administrator Guide.
• If you edit the PowerCenter workflow or mapping, you must update the associated Data Integration Hub
workflow by re-selecting the PowerCenter workflow or the XML file in the Data Integration Hub Operation
Console.

For general rules and guidelines on developing PowerCenter workflows to use with Data Integration Hub, see
GUID-8D713C6A-1BBD-49DD-8AE7-E1011AEE1F3E.

Developing PowerCenter Real-time Workflows 31

 Developing Publication Real-time Workflows Process
To develop a workflow in PowerCenter that processes Data Integration Hub real time publications, perform
the following tasks:

1. Create the source and target definitions.

2. Create the mapping and add transformations.
3. Create the workflow and the session and save the workflow.
4. In the Data Integration Hub Operation Console, create a topic to which the application will publish the
real-time data. Base the topic structure on the PowerCenter workflow or on the workflow definition file.
Data Integration Hub creates the topic in PowerCenter and names the target according to the Data
Integration Hub naming conventions.
5. In the workflow that you created in step 3, rename the target to the name of the topic target in
PowerCenter and save the workflow. Optionally, export the workflow to an XML workflow definition file.
6. In the Data Integration Hub Operation Console, create a publication real-time workflow and select the
PowerCenter workflow that you modified in step 5.

Step 1. Create the Source and Target Definitions

When you develop a publication real-time workflow, you create the source based on real-time data that you
want to publish. You set the target of the publication real-time workflow to the Data Integration Hub
publication repository. You can also add properties to store other Data Integration Hub values that you want
to send from PowerCenter.

You define the source of a publication real-time workflow based on the following real-time data:

• Data in the Apache Kafka stream

• Structure of the JMS
• Web service source

You create the source and the target definitions in the PowerCenter Designer in the same way that you create
source and target definitions for other mappings. For general information about source and target definitions,
see the PowerCenter Designer Guide.

When you create the source and the target definitions, consider the following guidelines:

• Use the DIH__STAGING connection in the target definition.

• The database target type must match the database type of the Data Integration Hub publication
repository.
• The target must contain DIH__PUBLICATION_INSTANCE_ID and DIH__PUBLICATION_INSTANCE_DATE
columns.

32 Chapter 2: PowerCenter Mappings and Workflows

 The following image shows an example of a target with the DIH__PUBLICATION_INSTANCE_ID and
DIH__PUBLICATION_INSTANCE_DATE columns:

Step 2. Create the Mapping

Create a mapping that contains the source definition, the target definition, and the transformations that you
want to use in the real-time publication workflow.

You create a mapping for Data Integration Hub in the same way that you build other PowerCenter mappings.

When you create the source and the mapping, consider the following guidelines:

• Add the DX_Publication_Parameters transformation to the mapping. You can also add other PowerCenter
transformation to the mapping.
• In the DXPublicationName port of the DX_Publication_Parameters transformation enter the name of the
publication to which the workflow publishes. The DX_Publication_Parameters transformation adds
placeholders for the publication instance ID and for the publication date in the Data Integration Hub
publication repository.
• Connect the port DXPublicationInstanceId from the DX_Publication_Parameters transformation to the
DIH__PUBLICATION_INSTANCE_ID column in the target.
• Connect the port DXPublicationInstanceDate from the DX_Publication_Parameters transformation to the
DIH__PUBLICATION_INSTANCE_DATE column in the target.

Developing PowerCenter Real-time Workflows 33

 The following image shows an example mapping that includes the DX_Publication_Parameters
transformation. The mapping also includes an expression that sets the publication name:

Step 3. Create and Save the PowerCenter Workflow and Session

Create the real-time workflow and the session that runs the mapping. You create the workflow in the same
way that you create other PowerCenter workflows.

1. In the Workflow Designer, create the workflow and the session object. You must configure the session
as a real-time session. For general information about creating workflows and sessions, see the
PowerCenter Advanced Workflow Guide.
2. Save the session object.
3. Test the workflow to ensure that it works correctly.
4. Save the workflow to the PowerCenter repository. Optionally, use the Repository Manager to export the
workflow from PowerCenter to an XML file.
Note: Do not save the workflow to a folder where the folder name is prefixed by DIH__pub or by
DIH__sub.

Step 4. Create the Topic

Create the topic to which the application will publish the real-time data. The topic defines the data structure
and additional data definitions such as the data retention period.

You create the topic in the Data Integration Hub Operation Console.

When you create the topic, consider the following guidelines:

• You define the topic structure in the Structure page of the Topic wizard.
• From the Add Tables list, choose From PowerCenter.
• In the Add Tables from PowerCenter Workflow dialog box, choose one of the following options:
- Choose Select a workflow from the PowerCenter repository to add tables from the real-time workflow.

- Choose Select a workflow definition file (.xml) to add tables from the XML file that you exported from
the real-time workflow.

34 Chapter 2: PowerCenter Mappings and Workflows

 For more information, see the Data Integration Hub Operator Guide.

Step 5. Rename the Workflow Target

Rename the target of the PowerCenter real-time workflow to the name of the topic target in PowerCenter.
You rename the target in the PowerCenter Designer.

1. In the navigation pane, access the folder of the topic that you created and expand the folder tree.
2. Expand the Targets subfolder and copy the target name into the clipboard.
3. Access the folder of the workflow and expand the folder tree.
4. Expand the Targets subfolder and replace the target name with the name that you copied from the topic
folder.
5. Save the session object.
6. Test the workflow to ensure that it works correctly.
7. Save the PowerCenter workflow to the PowerCenter repository. Optionally, use the Repository Manager
to export the workflow from PowerCenter to an XML file.
Note: Do not save the workflow to a folder where the folder name is prefixed by DIH__pub or by
DIH__sub.

Step 6. Create the Publication Real-time Workflow

Create the Data Integration Hub real-time workflow that will publish the real-time data. The Data Integration
Hub operator can use the workflow to create a real-time publication.

You create the workflow in the Data Integration Hub Operation Console, in the Workflows page.

When you create the workflow, consider the following guidelines:

• You define the topic structure in the Structure page of the Topic wizard.
• In Flow Type, choose PowerCenter Real-time workflow.
• In Type, choose Publication.
The Data Integration Hub operator selects the workflow in the Create Custom Real Time Publication wizard,
in the Mapping page.

Developing PowerCenter Real-time Workflows 35

Chapter 3

Data Engineering Integration and

Streaming Mapping and
Workflows
This chapter includes the following topics:

• Data Engineering Integration and Streaming Mapping and Workflows Overview, 36

• Data Engineering Integration and Streaming Mappings and Workflows in Data Integration Hub, 37
• Before You Begin, 38
• Developing Data Engineering Integration Mappings for Publications, 38
• Developing Data Engineering Streaming Mappings for Publications, 40
• Developing Data Engineering Integration Mappings for Subscriptions, 42
• Developing Data Engineering Integration Workflows for Publications, 44
• Developing Data Engineering Integration Workflows for Subscriptions, 45

Data Engineering Integration and Streaming Mapping

and Workflows Overview
Data Integration Hub uses Data Engineering Integration and Data Engineering Streaming to run Data
Integration Hub big data publications and subscriptions.

You use Data Engineering Integration mappings to run custom batch publications and subscriptions that
publish and consume large, diverse, and fast changing data sets. You use Data Engineering Integration
workflows with multiple mappings in a workflow to run multiple custom batch publications and subscriptions
that publish and consume large, diverse, and fast changing data sets. You use Data Engineering Streaming
mappings to run custom multi-latency publications that publish streams of data in real time.

You create a Data Engineering Integration workflow by using multiple Data Engineering Integration mappings.

The Data Integration Service runs the Data Engineering Integration mapping, Data Engineering Streaming
mappings, Data Engineering Integration workflows on the Hadoop environment.

You use the Developer tool to develop the Data Engineering Integration, Data Engineering Streaming
mappings, and Data Engineering Integration Workflow that process the publications and subscriptions. You

36
 then use the Data Integration Hub Operation Console to import the mappings into a Data Integration Hub
workflow. For details, see GUID-315620DD-DADD-4F87-927A-77BD6F30F2F8.

The Data Integration Hub operator creates a publication or a subscription in the Data Integration Hub
Operation Console, and selects the Data Integration Hub workflow which is based on the Data Engineering
Integration, Data Engineering Streaming mapping, or Data Engineering Integration Workflow. For more
information, see the Data Integration Hub Operator Guide.

Sample mappings
You can find sample mappings in the following locations:

• Data Engineering Integration mappings: <DIHInstallationDir>/samples/bdm_mappings. Each sample

mapping has an associated readme file that describes the sample mapping and contains guidelines for
using the mapping as a basis to create your own mappings.
• Data Engineering Streaming mappings: <DIHInstallationDir>/samples/bds_mappings. Under this folder,
there are sub-folders with sample mappings for an Oracle publication repository and for a Microsoft SQL
Server publication repository. The readme file that resides in this folder describes the sample mappings
and contains guidelines for using the mappings as a basis to create your own mappings.
• Data Engineering Integration Workflow: <DIHInstallationDir>/samples/bdm_workflows. Under this
folder, there are sub-folders with sample workflows for an Oracle publication repository and for a
Microsoft SQL Server publication repository. The readme file that resides in this folder describes the
sample workflows and contains guidelines for using the workflows as a basis to create your own
workflows.

Data Engineering Integration and Streaming

Mappings and Workflows in Data Integration Hub
You use Data Engineering Integration mappings and workflows in Data Integration Hub publications and
subscriptions with custom batch mappings. You use Data Engineering Streaming mappings and workflows in
Data Integration Hub publications with custom multi-latency mappings.

In publication mappings, the source is the publishing application and the target is the Data Integration Hub
publication repository. In subscription mappings, the source is the Data Integration Hub publication
repository, and the target is the subscribing application.

You can use user-defined mapping parameters in custom batch mappings and define their values in Data
Integration Hub or in a parameter file. You can manage the values of mapping parameters based on
developer tool mappings. You cannot manage the values of built-in mapping parameters in Data Integration
Hub. For more information about mapping parameters, see the Informatica Developer Tool Guide.

Note: Data Integration Hub does not support session parameters in the following formats: $InputFile_,
$OutputFile_.

Data Engineering Integration and Streaming Mappings and Workflows in Data Integration Hub 37
Before You Begin
Before you develop Data Engineering Integration, Data Engineering Streaming mappings, or Data Engineering
Integration workflows to use in Data Integration Hub, verify that the following conditions exist:

• The following Data Integration Hub components are installed:

- Data Integration Hub Hadoop Service.

- Data Integration Hub Data Engineering Integration.

• The topic to which to publish data and from which to consume data is configured in Data Integration Hub.
The topic must be a Hadoop-based topic.
• The following connections are configured in Data Integration Hub:
- Connection to the publishing application.

- Connection to the subscribing application.

• A Hadoop connection to where to run the mappings exists in your environment. The connection must be a
cluster connection, and must push mapping logic to the Hadoop cluster.
Before you develop Data Engineering Streaming mappings, copy the runtime .jar files from
<DIHInstallationDir>/ powercenter/lib to the following location:
BDS_HOME/services/shared/hadoop/$Distribution/extras/spark-auxjars/

Developing Data Engineering Integration Mappings

for Publications
To develop a Data Engineering Integration mapping for a publication, perform the following steps in the
Developer tool:

1. Create source and target connections. The source connection is a connection to the publishing
application and the target connection is a Hive connection to the Data Integration Hub publication
repository.
2. Create source and target data objects.
3. Create a mapping and add the source and target objects to the mapping.
4. Add Data Integration Hub parameters to the mapping.
5. Add an Expression transformation to the mapping, configure ports in the transformation, and connect
ports between the source, the transformation, and the target.
6. Configure the mapping run-time environment and create an application from the mapping.
The following image shows a sample publication mapping:

38 Chapter 3: Data Engineering Integration and Streaming Mapping and Workflows

Step 1. Create Source and Target Connections
1. Create a Streaming source connection to the publishing application.
2. Create a target connection to the Data Integration Hub publication repository.

Step 2. Create Source and Target Data Objects

Create data objects under Physical Data Objects.

1. Create a source data object and define the column projection in the source connection to publish.
2. Create a target data object and select the table in the target connection to where to publish the data
from the source. The object must be a relational data object.

Step 3. Create a Mapping with Source and Target

1. Create and name a new mapping.
2. Add the source physical data object to the mapping as a Reader.
3. Add the target physical data object to the mapping as a Writer.

Step 4. Add Data Integration Hub Parameters to the Mapping

u Add the following parameters to the mapping:
DXPublicationInstanceID
DXPublicationInstanceDate
DXPublicationInstancePartitionDate

Step 5. Add an Expression Transformation to the Mapping

1. Add an Expression transformation to the mapping, between the source and target objects.

Developing Data Engineering Integration Mappings for Publications 39

 2. Link all the ports from the source object to the identical ports in the Expression transformation. For
example, if your topic table includes the column EMPNO, link the EMPNO port in the source object to the
EMPNO port in the Expression transformation.
3. Configure the following additional ports in the Expression transformation:
DXPublicationInstanceID
DXPublicationInstanceDate
DXPublicationInstancePartitionDate
The data type of all ports is string, and the minimum precision is 200.
4. Link all the ports from the Expression transformation to the identical ports in the target object. For
example, link the EMPNO port in the Expression transformation to the EMPNO port in the target object, and
link the DXPublicationInstanceID port in the Expression transformation to the
dih__PublicationInstanceID port in the target object.
5. Save the mapping.

Step 6. Configure the Mapping Run-time Environment and Create

an Application
1. In the Properties pane select Run-time, and then, under Validation Environments, select Hadoop and
then select Hive. Verify that Native is not selected.
2. Create an application from the mapping.
The mapping is deployed to the Data Integration Service for Hadoop environment.

Developing Data Engineering Streaming Mappings for

Publications
To develop a Data Engineering Streaming mapping for a publication, perform the following steps in the
Developer tool:

1. Create source and target connections. The source connection is a connection to the publishing
application and the target connection is a connection to the Data Integration Hub publication repository.
2. Create source and target data objects.
3. Create a mapping and add the source and target objects to the mapping.
4. Add an Expression transformation to the mapping, configure ports in the transformation, and connect
ports between the source and the transformation.
5. Add a Java transformation to the mapping and map fields from the Expression transformation to the
Java transformation and from the Java transformation to the target.
6. Configure the mapping run-time environment and create an application from the mapping.

Step 1. Create Source and Target Connections

1. Create a Streaming source connection to the publishing application.
2. Create a target connection to the Data Integration Hub publication repository.

40 Chapter 3: Data Engineering Integration and Streaming Mapping and Workflows

Step 2. Create Source and Target Data Objects
Create data objects under Physical Data Objects.

1. Create a source data object and define the column projection in the source connection to publish.
2. Create a target data object and select the table in the target connection to where to publish the data
from the source. The object must be a relational data object.

Step 3. Create a Mapping with Source and Target

1. Create and name a new mapping.
2. Add the source physical data object to the mapping as a Reader.
3. Add the target physical data object to the mapping as a Writer.

Step 4. Add an Expression Transformation to the Mapping

1. Add an Expression transformation to the mapping, between the source and target objects.
2. Link all the ports from the source object to the identical ports in the Expression transformation.
3. Configure the following additional ports in the Expression transformation:

Port Description

PublicationName Name of the publication.

DX_SERVER_URL A valid Data Integration Hub RMI URL. For example: rmi://localhost:18095.

Step 5. Add a Java Transformation to the Mapping

1. Copy the Java transformation from the sample mapping. You can find sample mappings in the following
location: <DIHInstallationDir>/samples/bds_mappings. Under this folder, there are sub-folders with
sample mappings for an Oracle publication repository and for a Microsoft SQL Server publication
repository.
2. Map the following fields from the Expression transformation to the Java transformation:
• PublicationName
• DX_SERVER_URL
3. Map the following fields from the Java transformation to the topic table in the target object:

Java Transformation Field Topic Table Field

DXPublicationInstanceID DIH__PUBLICATION_INSTANCE_ID

DXPublicationInstanceDate DIH__PUBLICATION_INSTANCE_DATE

4. In the target transformation, open the target data object and change the data type of
DIH__PUBLICATION_INSTANCE_ID from decimal to bigint .
5. Save the mapping.

Developing Data Engineering Streaming Mappings for Publications 41

 Step 6. Configure the Mapping Run-time Environment and Create
an Application
1. In the Properties pane select Run-time, and then, under Validation Environments, select Hadoop and
then select Spark. Verify that Native is not selected.
2. Create an application from the mapping.
The mapping is deployed to the Data Integration Service for Hadoop environment.

Developing Data Engineering Integration Mappings

for Subscriptions
To develop a Data Engineering Integration mapping for a subscription, perform the following steps in the
Developer tool:

1. Create source and target connections. The source connection is a Hive connection to the Data
Integration Hub publication repository and the target connection is a connection to the subscribing
application.
2. Create source and target data objects.
3. Create a mapping, add the source and target objects to the mapping, and connect ports between the
source and the target.
4. Add Data Integration Hub parameters to the mapping.
5. Add a Filter query to the source. You can filter subscriptions by publication instance ID, publication date,
and publication date partition.
Note: If you are creating a mapping for an unbound subscription you do not need add a filter query to the
mapping.
6. Configure the mapping run-time environment and create an application from the mapping.
The following image shows a sample subscription mapping:

42 Chapter 3: Data Engineering Integration and Streaming Mapping and Workflows

Step 1. Create Source and Target Connections
1. Create a Hive source connection to the Data Integration Hub publication repository. Hive must belong to
the cluster where the mappings run.
2. Create an Oracle or a Flat File target connection to the subscribing application.

Step 2. Create Source and Target Data Objects

Create data objects under Physical Data Objects.

1. Create a source data object and select the table in the source connection to consume. The object must
be a relational Hive data object.
2. Create a target data object and select the table in the target connection subscribes to the data. The
object can be a relational data object or a flat file data object.

Step 3. Create a Mapping with Source and Target

1. Create and name a new mapping.
2. Add the source physical data object to the mapping as a Reader.
3. Add the target physical data object to the mapping as a Writer.
4. Link all the ports from the source object to the identical ports in the target object. For example, if your
topic table includes the column ENAME, link the ENAME port in the source object to the ENAME port in the
target object.

Step 4. Add Data Integration Hub Parameters to the Mapping

u Add the following parameters to the mapping:
<TOPIC_NAME>__DXPublicationInstanceIDs
<TOPIC_NAME>__DXPublicationInstanceDates
<TOPIC_NAME>__DXPublicationInstancePartitionDate
Where <TOPIC_NAME> is the name of the topic from which the subscriber consumes the data.

Step 5. Add a Filter Query to the Reader Object

If you are creating a mapping for an unbound subscription do not add a filter query to the mapping.

1. Configure a Filter query on the source with the following mapping parameters:
<TOPIC_NAME>__DXPublicationInstanceIDs
<TOPIC_NAME>__DXPublicationInstanceDates
<TOPIC_NAME>__DXPublicationInstancePartitionDate
Where <TOPIC_NAME> is the name of the topic from which the subscriber consumes the data.
Do not enclose filter query parameters within quotation marks.
For example, use the following format for a filter query with a filter condition on the partition date
parameter:
dih__publication_instance_id in ($MY_TOPIC__PublicationInstanceIDs) and
dih__publication_instance_date in ($MY_TOPIC__PublicationInstanceDates) and
publication_date_partition in ($MY_TOPIC__PublicationInstancePartition_Date)
2. Save the mapping.

Developing Data Engineering Integration Mappings for Subscriptions 43

 Step 6. Configure the Mapping Run-time Environment and Create
an Application
1. In the Properties pane select Run-time, and then, under Validation Environments, select Hadoop and
then select Hive. Verify that Native is not selected.
2. Create an application from the mapping.
The mapping is deployed to the Data Integration Service for Hadoop environment.

Developing Data Engineering Integration Workflows

for Publications
To develop a Data Engineering Integration workflow for a publication, perform the following steps in the
Developer tool:

1. Develop a Data Engineering Integration mapping for publications.

2. Create a workflow for publication and include the publication mapping or mappings that belong to the
same topic. You can include multiple mappings in a single pipeline that is characterized by a Start_Event
and End_Event.
3. Validate the mapping and workflow and deploy the workflow to an application in the Data Integration
Service.
4. Create Data Engineering Integration workflows for publication in the Data Integration Hub console.

Step 1. Develop Data Engineering Integration Mappings for

Publications
Develop Data Engineering Integration mappings for publications as described in “Developing Data
Engineering Integration Mappings for Publications” on page 38.

Step 2. Create a Publication Workflow

Create a publication workflow as follows:

1. Create a workflow for publication. You can include multiple mappings in a single pipeline within a
Start_Event and an End_Event.

44 Chapter 3: Data Engineering Integration and Streaming Mapping and Workflows

 2. Create the following workflow parameters in the Properties > Parameters menu:
• DXPublicationInstanceID
• DXPublicationInstanceDate
• DXPublicationInstancePartitionDate

3. Assign workflow parameters to corresponding mapping parameters for every mapping included within
the workflow. Use the following workflow menu: Workflow > Mapping > Properties > Input > Mapping
Parameters.

4. Save the workflow.

Step 3. Deploy the Publication Workflow

Select publication workflows and deploy them to the Data Integration Service of the Data Integration Hub
console. The Data Integration Hub administrator can now access the workflow to create a Data Engineering
Integration workflow for publications.

Developing Data Engineering Integration Workflows

for Subscriptions
To develop a Data Engineering Integration workflow for a subscription, perform the following steps in the
Developer tool:

1. Develop Data Engineering Integration Mapping for subscriptions.

Developing Data Engineering Integration Workflows for Subscriptions 45

 2. Create a workflow for subscription and include the subscription mapping or mappings that belong to the
same topic. You can include multiple mappings in a single pipeline that is characterized by a Start_Event
and End_Event.
3. Validate the mapping and workflow and deploy the workflow to an application in the Data Integration
Service.
4. Create Data Engineering Integration workflows for subscription in the Data Integration Hub console.

Step 1: Develop Data Engineering Integration Mappings for

Subscriptions
Develop Data Engineering Integration mappings for subscriptions as described in “Developing Data
Engineering Integration Mappings for Subscriptions” on page 42.

Step 2. Create a Subscription Workflow

Create a subscription workflow as follows:

1. Create a workflow for subscription. You can include multiple mappings in a single pipeline included
within a Start_Event and an End_Event.

2. Create the following workflow parameters in the Properties > Parameters menu:
• DXPublicationInstanceID
• DXPublicationInstanceDate
• DXPublicationInstancePartitionDate

3. Assign workflow parameters to corresponding mapping parameters for every mapping included within
the workflow. Use the following workflow menu: Workflow > Mapping > Properties > Input > Mapping
Parameters.

46 Chapter 3: Data Engineering Integration and Streaming Mapping and Workflows

 4. Save the workflow.

Step 3. Deploy the Subscription Workflow

Select subscription workflows and deploy them to the Data Integration Service of the Data Integration Hub
console. The Data Integration Hub administrator can now access the workflow to create Data Engineering
Integration workflows for subscriptions.

Developing Data Engineering Integration Workflows for Subscriptions 47

Chapter 4

Informatica Cloud Mappings and

Tasks
This chapter includes the following topics:

• Informatica Cloud Mappings and Tasks Overview, 48

• Informatica Cloud Mappings in Data Integration Hub, 48
• Data Integration Tasks in Data Integration Hub, 49

Informatica Cloud Mappings and Tasks Overview

Data Integration Hub uses Informatica Cloud mappings and tasks to publish data from source cloud
applications to the Data Integration Hub publication repository and to consume data from the publication
repository by target cloud applications.

In publications and subscriptions with automatic mappings, you use Informatica Cloud mappings to define
the data processing.

In publications and subscriptions with automatic mappings, you use Data Synchronization tasks and Mapping
Configuration tasks to define the data processing.

You develop Informatica Cloud mappings and tasks for Data Integration Hub in the same way that you
develop other Informatica Cloud mappings and tasks. You use the Data Integration Hub connection as the
target in publication mappings and tasks and as the source in subscription mappings and tasks.

Before you develop mappings and tasks in Informatica Cloud for Data Integration Hub, verify that the cloud
Data Integration Hub connector is installed and a connection that uses the connector exists. For details, see
the Data Integration Hub Administrator Guide.

Informatica Cloud Mappings in Data Integration Hub

You use Informatica Cloud mappings in Data Integration Hub publications and subscriptions with automatic
mappings.

In publication mappings, the publishing application is the source of the mapping and the Data Integration Hub
publication repository is the target of the mapping. In subscription mappings, the Data Integration Hub

48
 publication repository is the source of the mapping and the subscribing application is the target of the
mapping.

You can create a generic, parameterized mapping and use it for multiple publications and subscriptions. You
can parameterize any element of the mapping, for example, source and target connections, field mappings,
and transformations. The operator fills in the parameter values when they create the publication or
subscription in the Data Integration Hub Operation Console.

Informatica Cloud Mappings Rules and Guidelines

When you develop Informatica Cloud mappings to use in Data Integration Hub publications and subscriptions
with automatic mappings, consider the following rules and guidelines:

• Do not run mappings that you create for Data Integration Hub from within Informatica Cloud. You must
run Data Integration Hub mappings from Data Integration Hub by running the publication or the
subscription to which the mapping is associated.
• When you use the Data Integration Hub connection, if the mapping is not parametized, the target object in
a publication mapping and the source object in a subscription mapping presents the list of topics defined
in Data Integration Hub. The format of the list is [Link].
• If a mapping is parameterized, you can use it as both a publication mapping and a subscription mapping.
• If a mapping is not parameterized, and you want to distinguish between publication mappings and
subscription mappings, indicate the type of the mapping in the mapping name. For example, name a
publication mapping Pub_<MappingName>, and name a subscription mapping Sub_<MappingName>.
• You can add expression and filter transformations to the mapping.
• If the mapping includes parameters, when the operator creates the publication or subscription, the
parameters show in the Input Parameters tab of the publication or subscription wizard.

Data Integration Tasks in Data Integration Hub

You use Data Integration tasks in Data Integration Hub publications and subscriptions with custom
mappings.

In publication tasks, the publishing application is the source of the task and the Data Integration Hub
publication repository is the target of the task. In subscription tasks, the Data Integration Hub publication
repository is the source of the task and the subscribing application is the target of the task.

When you develop a Data Integration task for a Data Integration Hub publication, you select the Data
Integration Hub connection as the target object. When you develop a Data Integration task for a Data
Integration Hub subscription, you select the Data Integration Hub connection as the source object.

Note: You do not use Data Integration tasks in data-driven publications and subscriptions.

Data Integration Tasks Rules and Guidelines

When you develop Data Integration mappings and tasks to use in Data Integration Hub publications and
subscriptions with custom mappings, consider these rules and guidelines.

Data Integration Tasks in Data Integration Hub 49

 General rules and guidelines

Consider the following rules and guidelines when you create Data Integration mappings and tasks:

• Do not run tasks that you create for Data Integration Hub from within Informatica Intelligent Cloud
Services. You must run the tasks from Data Integration Hub by running the publication or the
subscription to which the task is associated.
• When you use the Data Integration Hub connection, the target object in a publication mapping or task
and the source object in a subscription mapping or task presents the list of topics defined in Data
Integration Hub. The format of the list is [Link].
• Data Integration Hub determines the scheduling of the publication or the subscription based on the
settings that the operator defined for the publication or the subscription. When you create the Data
Integration task, in the Schedule page of the task wizard, verify that the option Do not run this task on
a schedule is selected.
• To distinguish between publication tasks and subscription tasks, indicate the type of the task in the
task name. When you select a task for a publication or for a subscription, you can easily select an
appropriate task.
For example, name a publication task Pub_<TaskName>, and name a subscription task
Sub_<TaskName>.

Synchronization task rules and guidelines

Consider the following rules and guidelines when you create synchronization tasks and mappings:

• The task operation for publication tasks is an insert operation.

• When you create a publication task, select the Data Integration Hub connection as the target. When
you create a subscription task, select the Data Integration Hub connection as the source.
• Synchronization tasks do not support multiple sources. Therefore, when you create a synchronization
task for a publication or a subscription with multiple sources, create a relationship between the
sources for the following use-cases:
- Publications: when you publish from multiple tables.

- Subscriptions: when you subscribe to multiple tables, or when the subscription is a compound
subscription.

Mapping task rules and guidelines

Consider the following rules and guidelines when you create mapping tasks and mappings:

• The mapping operation is an insert operation for both publication and subscription mappings.
• When you create a publication mapping, select the Data Integration Hub connection when you
configure the target properties. When you create a subscription mapping, select the Data Integration
Hub connection when you configure the source properties.
•

For instructions on creating Informatica Intelligent Cloud Services mappings and tasks for Data Integration
Hub, see the Data Integration Hub Connector Guide.

Using Intelligent Structure Model in Data Integration Hub

Data Integration Hub supports unstructured flat files to publish data. You can use intelligent structure models
to structure data from unstructured or semi-structured files and create custom cloud mappings that use
intelligent structure models and publish unstructured data to Data Integration Hub.

For more information about how to use intelligent structure model in Data Integration Hub to publish
unstructured or semi-structured data refer to the H2L ...

50 Chapter 4: Informatica Cloud Mappings and Tasks

Chapter 5

Data Integration Hub Workflows

This chapter includes the following topics:

• Data Integration Hub Workflows Overview, 51

• Managing Data Integration Hub Workflows, 51
• Data Integration Hub Workflow Properties, 52

Data Integration Hub Workflows Overview

A workflow is a set of instructions that define how to process documents that partners send to Data
Integration Hub. A Data Integration Hub workflow represents a PowerCenter workflow and mapping.

You can create a workflow in Data Integration Hub from a PowerCenter workflow by either of these methods:

• Select a workflow directly from the PowerCenter repository.

• Export the PowerCenter workflow to an XML file using the Repository Manager tool. You then select the
XML file to import as the workflow definition file.

Along with the workflow definition file, you define basic workflow properties, and save the new workflow.

You can create multiple workflows and associate them with an application. You can associate one workflow
with one or more profiles. Real-time workflows use the JMS queue to communicate with PowerCenter.

If you assign event attributes that the dashboard uses in reports to a workflow, the event attribute value must
be numeric. An event attribute is numeric if the lexical syntax rules in the Java Language Specification define
it as a FloatValue.

Managing Data Integration Hub Workflows

Use the Navigator to add, edit, and delete Data Integration Hub workflows . Each workflow represents a
PowerCenter workflow or Informatica Intelligent Cloud Services (Data Integration) mapping.

1. In the Navigator, click Partner Management > Workflows.

The Workflows page appears.
2. Choose to create, edit, or delete a workflow.

51
 • To create a workflow, click New Workflow and define the workflow properties. For more information,
see “Data Integration Hub Workflow Properties” on page 52.
• To edit a workflow, click the Edit icon next to the workflow that you want to edit and change the
workflow properties.
Note: If the workflow is associated with profiles, the Operation Console displays a list of the
associated profiles. If the changes to the workflow might cause problems in processing documents
for the partner defined in the profile, disable the profile and review the changes to the profile before
you enable the profile again.
• To delete a workflow, click the Delete icon next to the workflow that you want to delete and confirm
the deletion.
Note: If you delete the workflow, you also delete all of the dependent objects for that workflow.
3. If the workflow contains parameters, you can add values to the parameters on the Workflow Parameters
tab of the Create Workflow page. You can customize the layout and behavior of the parameters with the
Forms Designer. For more information, see Customizing Workflow Parameters Use the Forms Designer
to customize user interface layout and field behavior for workflows that contain parameters in the
Operation Console and in the Partners Portal Message Profile wizard. The steps in this task are similar
to the steps you follow to customize partner attributes and account attributes. .
4. To associate event attributes with the workflow, add event attributes on the Event Attributes tab.
5. To manually run an outbound batch workflow, click Partner Management > Profiles and run the profile
that is associated with the batch workflow.
6. To manually run a scheduled batch workflow, click Events > Event List and release the events for the
batch workflow.

Data Integration Hub Workflow Properties

A Data Integration Hub workflow contains an associated PowerCenter workflow or Informatica Intelligent
Cloud Services (Data Integration) mapping, and other properties such as name and description. You define
the properties when you create or edit a workflow.

A Data Integration Hub workflow definition contains the following general properties:
Workflow Name

Name of the workflow. The name can contain up to 64 characters and can include spaces and special
characters.

Description

Optional description of the workflow. The description appears as a tooltip when the operator selects a
workflow in the Profiles and Monitors pages.

Application

Name of the application to which the workflow belongs. Select <none> to create a workflow without an
application.

Flow Type

The flow type depends on the application that is used to process documents.

52 Chapter 5: Data Integration Hub Workflows

 Consider the following guidelines when you select the flow type:

• Select Informatica Cloud workflow to associate the workflow with a Informatica Intelligent Cloud
Services (Cloud Data Integration) mapping. A Cloud Data Integration mapping reads from a source
and writes to a target defined in the mapping. Use the mapping to process and transfer files over
Informatica Cloud.
• Select PowerCenter Batch workflow to associate the workflow with a PowerCenter batch workflow. A
PowerCenter batch workflow reads from a file, database, or another source. The workflow runs once
and stops after completion. You can use the PowerCenter batch workflows to process documents
from B2B Data Exchange. You can also use the workflows to generate documents for B2B Data
Exchange, such as outbound reports. Use the PowerCenter workflow export file as the workflow
definition file.
• Select PowerCenter Real-time workflow to associate the workflow with a real-time workflow. A
PowerCenter real-time workflow runs continuously and reads from real-time sources. You can use
these workflows to process documents from B2B Data Exchange. Use the PowerCenter mapping or
workflow export file as the workflow definition file.
• Select Java (advanced) to use Java classes as the flow engine in test mode or development mode.
Use the Java class file as the workflow definition file.

Workflow
A PowerCenter workflow that you want to add to Data Integration Hub. Select one of the following
options:

• Select a workflow from the PowerCenter repository. Select a PowerCenter workflow that you saved
in the PowerCenter repository. To show all workflows in the repository, click Show All. To search for a
workflow by name, enter a string in the Folder Name text box and then click Search.
• Select a workflow definition file (XML). Select an XML PowerCenter workflow definition file that you
exported from the PowerCenter repository. To select a file, click the browse button, browse to the
location of the required file, select the file, and then click Upload.

Data Integration Hub Workflow Properties 53

Chapter 6

Data Integration Hub

Transformations
This chapter includes the following topics:

• Data Integration Hub Transformations Overview, 54

• DX_Add_Document_To_Event Transformation, 57
• DX_Event_Attribute Transformation, 58
• DX_Event_Details Transformation, 59
• DX_Generate_Temporary_File Transformation, 60
• DX_Notification Transformation, 61
• DX_Publication_Parameters, 63
• DX_Start_Publication Transformation, 63
• DX_Throw_Error, 65

Data Integration Hub Transformations Overview

A Data Integration Hub transformation is a set of functions that process Data Integration Hub data in
PowerCenter.

When you install Data Integration Hub, you can install a set of transformations that you use in PowerCenter
workflows to process Data Integration Hub data. When you create mappings, you can use the
transformations to perform the functions that you require in the same way you use other PowerCenter
transformations.

Data Integration Hub transformations are custom Java transformations that you use to access the Data
Integration Hub API without writing Java code. You can use these transformations, the Unstructured Data
transformation, and other transformations to process publications and subscriptions.

The following table describes the Data Integration Hub transformations:

Transformation Description

DX_Add_Document_To_Event Attaches a document to an event.

DX_Event_Attrribute Gets or sets the values of event attributes.

54
 Transformation Description

DX_Event_Details Gets or sets the values of a property of an event.

DX_Generate_Temporary_File Generates a file name for a file in the Data Integration Hub document store.

DX_Notification Notifies the Data Integration Hub server that processing was successful.

DX_Publication_Parameters Adds placeholders for the publication instance ID and for the publication date in the
Data Integration Hub publication repository.

DX_Start_Publication Starts a publication process.

DX_Throw_Error Sets an event status to error if the transformation fails.

Installing and Registering Transformations

To add Data Integration Hub transformations to PowerCenter, use the Data Integration Hub installer.

You install the following components:

• Data Integration Hub PowerCenter server plug-in. Use the Administrator tool to register the plug-in.
• Data Integration Hub PowerCenter Client plug-in. The installer registers the plug-in during the installation
process.
After you install and register the plug-ins, verify that the transformations are enabled in the PowerCenter
Designer. For more information about installing and configuring the plug-ins, see the Data Integration Hub
Installation and Configuration Guide.

Configuring Transformations
After you add a Data Integration Hub transformation to a mapping, you edit and configure the transformation
based on your document processing requirements.

When you edit a Data Integration Hub transformation, you can configure the transformation components on
the following tabs:

• Transformation tab. Rename the transformation and add a description.

• Ports. Add, edit, or delete ports. You can also designate ports as input or output ports.
• Properties tab. Configure transformation properties, such as module and function identifiers, transaction
properties, and the runtime location. The properties that appear on this tab are the same as the properties
for other PowerCenter Custom transformations. For more information about the Properties tab, see the
PowerCenter Transformation Guide.
• DX Properties tab. Set the default values for the ports in the transformation. You can also set the default
values for other Data Integration Hub transformation properties.

Handling Transformation Errors

You can use certain transformation ports to define how to handle errors that occur during a workflow run.

Each Data Integration Hub transformation uses the following ports to handle errors:

• DXErrorCode. When a transformation fails, the transformation sets the DXErrorCode to a value greater
than zero.

Data Integration Hub Transformations Overview 55

 • DXErrorMessage. When a transformation fails, the transformation sends an error message that describes
the failure to the DXErrorMessage port.
When a transformation generates an error, the transformation writes the error to the PowerCenter session
log. The error log includes the exception class, description, cause, and stack trace. The logging level is based
on the PowerCenter configuration. Up to 1K of the document associated with the error will be included in the
log.

If the option to set the event status to error when a transformation fails is set to true, the transformation also
sets the status of the event to error.

You can set the error handling ports as input ports to prevent the transformation from running if an input
error occurs.

Data Integration Hub Transformations Rules and Guidelines

When you work with Data Integration Hub transformations in PowerCenter, follow rules and guidelines to
optimize performance and prevent errors.

The following list describes rules and guidelines for working with Data Integration Hub transformations:

• Data Integration Hub transformations are based on the PowerCenter Custom transformation and they
provide the same configuration options as other custom transformations. You can use them as you use
other PowerCenter transformations.
• Data Integration Hub transformations are connected transformations. Connected transformations pass
data to or from other transformations.
• Data Integration Hub transformations are passive transformations.
• If a transformation port has a corresponding Data Integration Hub property, the value of the port takes
precedence over the value of the property during runtime. When the session runs, if the value of the port is
not null, the PowerCenter Integration Service uses the value of the port for processing. If the value of the
port is null, the PowerCenter Integration Service uses the value of the Data Integration Hub property for
processing.
• Port names are case insensitive and prefix insensitive. DXEventID, dxEVENTid, and eventid are all treated
as the same port.
• When you run a PowerCenter workflow that uses a Data Integration Hub transformation, PowerCenter tries
to connect to the Data Integration Hub repository to get the list of event statuses and types to use in the
transformation. An error message indicates a failed connection. If the connection fails, PowerCenter gets
the event type values from the Client plug-in configuration file. To resolve connection errors, verify that
the connection section in the [Link] file contains the following configuration:
[DX_REPOSITORY]
; ODBC connection string to the DX repository
; CONNECTION_STRING=DRIVER={DataDirect 7.0 Oracle Wire Protocol};
UID=%1;PWD=%2;Host=localhost;Port=1521;SN=orcl
; CUSTOM_CONNECTION_STRING
; ODBC DSN to the DX repository
; DSN_NAME=dxOdbcResourceName
USER_NAME=DX
USER_PASSWD=DX
EVENT_TYPE_NAME=SELECT event_type_name FROM dx_event_type ORDER BY 1
EVENT_STATUS_NAME=SELECT event_status_name FROM dx_event_status ORDER BY 1

56 Chapter 6: Data Integration Hub Transformations

DX_Add_Document_To_Event Transformation
The DX_Add_Document_To_Event transformation attaches a document to an event.

You can use the transformation to add a document that you create in previous transformations. For example,
you can use the transformation to attach a log file to an event.

Input Ports
Configure input ports for the DX_Add_Document_To_Event transformation on the Ports tab.

The following table describes the DX_Add_Document_To_Event input ports:

Port Type Description

DXDescription string Description of the document to attach to the event.

DXMIMEType string MIME type of the document to attach to the event.

DXEncoding string Character encoding of the document to attach to the event. This is the character set
to use to convert strings to byte arrays.

DXTemporaryFilePath string Optional. Path and file name generated by the DX_Generate_Temporary_File
transformation where the workflow stores the new file. The
DX_Add_Document_To_Event transformation saves the file as a new document
reference in the document store and attaches the file reference to the event.
You can set this port or set the DXData and DXDataByReference ports. If this port
and the DXData and DXDataByReference ports are not set, the transformation
creates an empty document and adds it to the event.

Input/Output Ports
Configure input/output ports for the DX_Add_Document_To_Event transformation on the Ports tab.

The following table describes the DX_Add_Document_To_Event input/output ports:

Port Type Description

DXEventId string Required. Identifier of the event to which to attach the document.

DXDataByReference string Indicates whether the DXData port contains the document data or a document
reference. If the value is true, the DXData port contains a document reference. If the
value is null or false, the DXData port contains the document data.

DXDocumentId string Identifier of the document to attach to the event.

DXErrorMessage string Error message generated by the transformation.

DXErrorCode string Error code generated by the transformation. If the transformation fails, the value of
the DXErrorCode port is greater than zero.

DX_Add_Document_To_Event Transformation 57
 Data Integration Hub Properties
Configure properties for the DX_Add_Document_To_Event transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Add_Document_To_Event
transformation:

Property Description

Description Description of the document to attach to the event.

Document Role Role of the document when it is attached to an event. Select one of the following roles:
- SOURCE. The document is attached to an event as a source document. When you view
the event in the Operation Console, you can view the attached document in the Input
section.
- TARGET. The document is attached to an event as a target document. When you view
the event in the Operation Console, you can view the attached document in the Output
section.
- LOG. The document is attached to an event as a log document. When you view the
event in the Operation Console, you can view the attached document in the Logging
Information section.

Generate an error in case Indicates whether to set the status of the event to error when the transformation
a failure occurs in this generates an error.
transformation Selected by default.

DX_Event_Attribute Transformation
The DX_Event_Attribute gets or sets event attribute values.

To use this transformation, you first configure an event attribute in the Operation Console. You then add
ports to the transformation. Each port represents the event attribute that you want to get or set.

The port name must match the event attribute name. However, the attribute name is not case sensitive. For
example, the event_att1 attribute and the EVENT_ATT1 are treated as the same attribute.

Event names are prefix sensitive. For example, the DX_event_att1 attribute and the event_att1 attribute are
not treated as the same attribute.

If you set a value for the port, the transformation sets the event attribute to this value. To get the value of an
event attribute, create an empty port.

58 Chapter 6: Data Integration Hub Transformations

 Input/Output Ports
Configure input/output ports for the DX_Event_Attribute transformation on the Ports tab.

The following table describes the DX_Event_Attribute input/output ports:

Port Type Description

DXEventId string Required. Identifier of the event associated with the attribute to get or to update.

DXErrorMessage string Error message generated by the transformation.

DXErrorCode string Error code generated by the transformation. If the transformation fails, the value of the
DXErrorCode port is greater than zero.

Data Integration Hub Properties

Configure properties for the DX_Event_Attribute transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Event_Attribute transformation:

Property Description

Event attribute name Name of the event attribute to update. You configure the property in the Operation
Console. If the value is null, the transformation generates an error.
Note: Optional property. It is recommended that you use the <Attribute> port
instead. This property is retained for backward compatibility.

Generate an error in case a Indicates whether to set the status of the event to error when the transformation
failure occurs in this generates an error.
transformation Selected by default.

DX_Event_Details Transformation
The DX_Event_Details transformation gets or sets multiple properties for an event.

The transformation ports represent the properties of an event. The transformation sets the property of the
event based on the value that the input port passes to the transformation. The transformation passes the
value of the property through an output port to the event.

DX_Event_Details Transformation 59
 Input/Output Ports
Configure input/output ports for the DX_Event_Details transformation on the Ports tab.

The following table describes the DX_Event_Details input/output ports:

Port Type Description

DXStatusName string Status of the event. The status indicates the stages that the event passes during
processing.

DXEventId string Required. Identifier of the event associated with the properties to get or update.

DXTypeName string Type of the event.

DXSubject string Subject of the event.

DXErrorMessage string Error message generated by the transformation.

DXErrorCode string Error code generated by the transformation. If the transformation fails, the value of the
DXErrorCode port is greater than zero.

Data Integration Hub Properties

Configure properties for the DX_Event_Details transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Event_Details transformation:

Property Description

Event Status Status of the event.

Event Type Type of the event.

Generate an error in case a failure occurs in Indicates whether to set the status of the event to error when the
this transformation transformation generates an error.
Selected by default.

DX_Generate_Temporary_File Transformation
The DX_Generate_Temporary_File transformation generates a path and a file name for a document to store in
the Data Integration Hub document store.

Use the transformation to generate a unique file name in a temporary directory within the document store.
For example, if you use an Unstructured Data transformation to write data to a temporary file, you can use the
DX_Generate_Temporary_File transformation to generate a file name for a file in the document store. You
then assign the file name and path to the file.

After you create the file in the temporary directory, you can use it in other transformations. For example, you
can use the DX_Add_Document_To_Event transformation to attach the file to an event. PowerCenter copies
the file from the temporary directory to the directory that contains all of the documents that it adds to events.

60 Chapter 6: Data Integration Hub Transformations

 Input/Output Ports
Configure input/output ports for the DX_Generate_Temporary_File transformation on the Ports tab.

The following table describes the DX_Generate_Temporary_File input/output ports:

Port Type Description

DXEventId string Required. Identifier of the event to associate with the generated file.

DXTemporaryFilePath string Path and file name of the temporary file.

DXErrorMessage string Error message generated by the transformation.

DXErrorCode string Error code generated by the transformation. If the transformation fails, the value of
the DXErrorCode port is greater than zero.

Data Integration Hub Properties

Configure properties for the DX_Generate_Temporary_File transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Generate_Temporary_File
transformation:

Property Description

Do not use a temporary folder in Indicates whether to generate the file path within the temporary directory in the
the generated file path Data Integration Hub document store, or to generate the file path directly in the
regular documents directory. Select this option to increase performance for
documents that PowerCenter passes by reference and eliminate the additional
backup that the temporary directory provides.
Cleared by default.

Set the event status to Error if the Indicates whether to set the status of the event to Error when the transformation
transformation fails generates an error.
Selected by default.

DX_Notification Transformation
The DX_Notification transformation sets the status of an event and optionally notifies the Data Integration
Hub server that the processing completed.

When you use the transformation in a publication workflow, you can notify the Data Integration Hub server
that the publication process is complete and the published data is ready to consume. The Data Integration
Hub server then creates child events for the subscriptions and triggers the subscription batch workflows for
subscriptions that consume the data when it is published. Scheduled subscription events remain pending
until the scheduled subscribers start to consume the data. The notification that the transformation sends is
optional. Therefore, you can use the transformation to change the event status to error without triggering the
subscriptions if the publication process ended with errors.

When you use the transformation in a subscription post-processing workflow, you must notify the Data
Integration Hub server that the subscription post-process is complete and send the post-processing status to

DX_Notification Transformation 61
 the server. The Data Integration Hub server then creates a child event for the subscription that evoked the
post-processing workflow, with the status of the post-process.

Input/Output Ports
Configure input/output ports for the DX_Notification transformation on the Ports tab.

The following table describes the DX_Notification input/output ports:

Port Type Description

DXEventId string Required. Identifier of the event for which you want to set the status. You can get the
value from the $$DxeventId parameter.

DXStatusName string Name of the status to set. If the value is null, the transformation sets the value based
on the transformation properties.

DXNotifySubscribers string Required. Indicates whether to send a notification to the Data Integration Hub server.
Possible values:
- True. The transformation sends a notification to the Data Integration Hub server.
The Data Integration Hub server triggers the subscription batch workflow and
creates a child event for each subscription.
- False. The transformation sets the event status without a notification to the Data
Integration Hub server.

DXErrorMessage string Error message generated by the transformation.

DXErrorCode string Error code generated by the transformation. If the transformation fails, the value of
the DXErrorCode port is greater than zero.

Data Integration Hub Properties

Configure properties for the DX_Notification transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Notification transformation:

Property Description

Event Status Status of the event to create.

Default is Complete.

Notify the hub that the Indicates whether to send a notification to the Data Integration Hub server that
publication is ready for the workflow run ended successfuly. If selected, the Data Integration Hub server
subscribers creates a child event for each subscription and triggers a subscription batch
workflow for subscriptions that you define to consume the data when it is
published.
Selected by default.

Generate an error in case a Indicates whether to set the status of the event to error when the transformation
failure occurs in this generates an error.
transformation Selected by default.

62 Chapter 6: Data Integration Hub Transformations

DX_Publication_Parameters
The DX_Publication_Parameters transformation adds placeholders for the publication instance ID and for the
publication date in the Data Integration Hub publication repository.

You use the transformation to add the placeholders for publications that use custom mappings with real-time
workflows.

Input Ports
Configure input ports for the DX_Publication_Parameters transformation on the Ports tab.

The following table describes the DX_Publication_Parameters input ports:

Port Type Description

DXPublicationName string Name of the publication. The name must be identical to the name of the publication
that the workflow that runs the transformation publishes.
The name is not case-sensitive and can contain up to 64 alphanumeric characters and
underscores.

Output Ports
Configure output ports for the DX_Publication_Parameters transformation on the Ports tab.

The following table describes the DX_Publication_Parameters output ports:

Port Description

DXPublicationInstanceId Adds a placeholder for DIH__PUBLICATION_INSTANCE_ID in the Data Integration Hub

publication repository. DIH__PUBLICATION_INSTANCE_ID identifies the data set that the
application published.
When you create a publication real-time workflow, you connect this port to the
DIH__PUBLICATION_INSTANCE_ID column of the target.

DXPublicationInstanceDate Adds a placeholder for DIH__PUBLICATION_INSTANCE_DATE in the Data Integration Hub

publication repository. DIH__PUBLICATION_INSTANCE_DATE is the date and time that
the application started publishing the data set.
When you create a publication real-time workflow, you connect this port to the
DIH__PUBLICATION_INSTANCE_DATE column of the target.

DX_Start_Publication Transformation
The DX_Start_Publication transformation instructs the Data Integration Hub PowerCenter Integration Service
to trigger the publication workflow for the specified publication.

You use the transformation to start a publication from PowerCenter. For example, if you run a publication pre-
process workflow that prepares the data before the publication process can start, add the
DX_Start_Publication transformation at the end of the workflow. PowerCenter sends a request to the Data
Integration Hub server, and the Data Integration Hub server triggers the publication workflow that publishes
the data to the publication repository.

DX_Publication_Parameters 63
 Note: Do not call the DX_Start_Publication transformation more than once in a workflow. If you do, Data
Integration Hub starts the publication multiple times.

If you use a PowerCenter parameter file, you can pass the contents of the file to the
DXParameterFileContents port and use the parameters in the publication workflow.

Input/Output Ports
Configure input/output ports for the DX_Start_Publication transformation on the Ports tab.

Note: You can add ports with specific parameters to pass to the workflow. The parameters type must be
string. You cannot add Passthrough input ports to the transformation.

The following table describes the DX_Start_Publication input/output ports:

Port Type Description

DXPublicationName string Optional. Name of the publication to start. The name must match the name of
the publication in the Operation Console.
Note: If you do not define a DXPublicationName port you must define a
DXEventId port.

DXEventId string Identifier of the event that is associated with the publication pre-process and
with the publication. You can get the value from the $$DXEventId parameter.
Recommended when a publication pre-process starts a single publication.
Ensures that Data Integration Hub uses the same event for both the publication
pre-process workflow and the publication workflow and changes the event
status accordingly.
When a publication pre-process starts multiple publications, do not use the
event ID in the DX_Start_Publication transformation. In this case, you can use
the Event Details PowerCenter transformation to change the event status.
Note: If you do not define a DXEventId port you must define a
DXPublicationName port.

DXParameterFileContents string Parameter names and values from a PowerCenter parameter file. You cannot
use a file path in the value of the port.

DXErrorMessage string Error message that the transformation generates.

DXErrorCode string Error code that the transformation generates. If the transformation fails, the
value of the DXErrorCode port is greater than zero.

Data Integration Hub Properties

Configure properties for the DX_Start_Publication transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Start_Publication transformation:

Property Description

Generate an error in case a failure occurs in Indicates whether to set the status of the event to error when the
this transformation transformation generates an error.
Selected by default.

64 Chapter 6: Data Integration Hub Transformations

DX_Throw_Error
The DX_Throw_Error transformation generates an error if an error occurs when the workflow runs.

Use the transformation to perform the following actions:

• Set the status of the associated event to error.

• Create the error message from the value of the DXDescription port.
• Attach the error message to the associated event.
• Send the error to the session log.

Input Ports
Configure input ports for the DX_Throw_Error transformation on the Ports tab.

The following table describes the DX_Throw_Error input ports:

Port Type Description

DXDescription string Description of the error to send to the session log. This error is also the description for
the log document attached to the event.

DXMessageType string Optional. Type of the error event. Alphanumeric value to associate with the event. Any
value is valid.

DXMIMEType string MIME type of the document to attach to the event.

Input/Output Ports
Configure input/output ports for the DX_Throw_Error transformation on the Ports tab.

The following table describes the DX_Throw_Error input/output ports:

Port Type Description

DXEventId string Required. Identifier of the event that is associated with the error.

DXData string Log document to attach to the event. This port can contain the data of the document
binary or a file path to the document. If the value of the parameter is null, the transformation
creates an empty document and adds the document to the event.
text
To attach a document with text data, set the datatype of the port to string or text. To
attach a document with binary data, change the datatype of the port to binary.

DXDataByReference string Indicates whether the DXData port contains the document data or a document
reference. Possible values:
- True. The DXData port contains a document reference.
- False. The DXData port contains the document data.
- Null. The DXData port contains the document data.

DXErrorMessage string Error message generated by the transformation.

DXErrorCode string Error code generated by the transformation. If the transformation fails, the value of
the DXErrorCode port is greater than zero.

DX_Throw_Error 65
 Data Integration Hub Properties
Configure properties for the DX_Throw_Error transformation on the DX Properties tab.

The following table describes the Data Integration Hub properties of the DX_Throw_Error transformation:

Property Description

Error log document description Description of the error log document that the transformation attaches to
the event.

Message type Alphanumeric value to associate with the event. You can enter any value.

Generate an error in case a failure Indicates whether to set the status of the event to error when the
occurs in this transformation transformation generates an error.
Selected by default.

66 Chapter 6: Data Integration Hub Transformations

Chapter 7

Forms Designer
This chapter includes the following topics:

• Forms Designer Overview, 67

• Forms Designer User Interface, 67
• Element Properties, 69
• Group Properties, 70

Forms Designer Overview

The Forms Designer is a tool that developers and administrators can use to customize user interface and
field behavior on Operations Console pages with a dynamic interface. You can use the Forms Designer to
customize pages that display workflow parameters.

In the Forms Designer, you use the Designer tab to customize behavior and appearance of fields. For
example, you can arrange large lists of workflow parameters in tabs or create dependencies between fields
so that a specific parameter only appears if another parameter has a value. You can also mark fields as
mandatory or read-only and determine the field type. For example, you can define a field as a text field or a
number field. You can preview the customized layout on the Preview tab.

Forms Designer User Interface

The Designer tab displays the elements to customize. You can use the Actions menu to add groups, such as
tabs, columns, headers, or disclosures. You can also drag and drop elements to group and nest the fields in
up to four levels.

The Designer tab displays information about the elements, such as label and type. The information appears
in read-only mode.

67
 The following table describes the element properties that you can view on the Designer tab:

Column Description

ID Unique identifier of the element. For example, the name of the workflow parameter as defined in
PowerCenter.

Label Label of the element as it appears on the form. The label can be different from the ID of the
element.

Type Type of the element, such as text or date.

Representation Representation of the element in the form. For example, the element can be an entry field, a radio
button, or a drop-down list.

Mandatory Indicates whether the element is mandatory.

Read-Only Indicates whether the element is read-only.

Depends On Name of the element or group on which the parameter depends.

Forms Designer Actions

On the Designer tab, you can add a tab, column, header, or disclosure. If you select an element, you can edit
the element properties.

The following table describes the actions that you can perform on the Designer tab:

Action Description

Edit Opens a dialog box that you use to edit the properties of an element.
Available when you select an element.

Create Tab Creates a tab. You can drag and drop elements into tabs and move tabs up or down the element
list to determine the tab order. The top tab is visible by default.
You can nest tabs up to two levels.

Create Column Creates a column. When you add two or more columns, elements that you drag and drop into a
column appear side by side on the form.
You can nest columns up to two levels.

Create Header Creates a header. A header is a separator with a title that you use to group elements without hiding
them from the form.
You can nest headers up to two levels.

Create Create a disclosure. A disclosure is a header with a title and an expand arrow. When you click the
Disclosure arrow, an element group appears. By default, disclosures appear minimized on the form.
You can nest disclosures up to two levels.

Delete Group Deletes a tab, column, header, or disclosure. Deleting the group does not delete the elements from
the form.
Available when you select a group.

Move to Group Moves elements from one tab, column, header, or disclosure group to another group.
Available when you select an element.

68 Chapter 7: Forms Designer

Element Properties
When you edit an element in the Details dialog box, you can change element properties such as label, type,
and default value.

The dialog box appears when you select an element. If you select a group, you can edit only the label, type,
and field dependency for the group.

The following table describes the element properties:

Property Description

Label Required. Name of the element to display in the form. The label can be different from the ID.

Description Textual description of the parameter. The description appears in a tooltip when you hover over
the element in the form.

Mandatory Requires users to enter a value for the element in the form.

Read Only Defines the element as read-only and the users cannot change the element value.

Hidden Hides the element from the form. Select this check box for workflow parameters that operators
cannot edit.

Type Type of data for the element value. Choose one of the following options:
- Boolean. If you select this option, the Check box representation is selected by default.
- Date. If you select this option, the Date picker representation is selected by default.
- Number. If you select this option, the Entry field representation is selected by default.
- Text

Representation Type of input that users enter for the element value. Choose one of the following options:
- Entry field
- Dropdown list
- Radio button
- List
- Check box

Default Value Value that appears when the form appears.

Values A list of valid values for the parameter. If you select a list or dropdown list representation, enter
one or more values. The values list is not case sensitive.
Note: If you populate list values from an external source, do not change the values in the list. The
values from the external source override any manual changes you make to the list.

Minimum Minimum valid value for the element. For string elements, the value you enter in this property
determines the minimum number of characters. For number elements, the value you enter in this
property determines the minimum numeric value.
Available when you select a string or number element type.

Maximum Maximum valid value for the element. For string elements, the value you enter in this property
determines the maximum number of characters. For number elements, the value you enter in this
property determines the maximum numeric value.
Available when you select a string or number element type.

Field Dependency Set of conditions that determines whether to link the element to another element or group in the
form. For example, you can choose to enable the element only after users enters a value in a
different element.

Element Properties 69
Group Properties
When you create or edit a tab, column, header, or disclosure in the Details dialog box, you can change the
label, type or field dependency properties.

The following table describes the group properties:

Property Description

Label Mandatory. Name of the group to display in the form.

Type Mandatory. Type of the group. Choose from one of the following options:
-Tab
-Column
-Header
-Disclosure

Field Dependency Set of conditions that determines whether to link the group to another element or group in the
form. For example, you can choose to enable a tab only after users entered a specific value in a
different element.

70 Chapter 7: Forms Designer

Chapter 8

Data Integration Hub Publications

and Subscriptions APIs
This chapter includes the following topics:

• Publications and Subscriptions APIs Overview, 71

• Run Publication Subscription REST API , 72
• Run Publication Subscription Command Line API , 74
• Change Publication Subscription Mode REST API, 76
• Reprocess Event REST API, 77
• Event Status REST API, 78

Publications and Subscriptions APIs Overview

Use the Data Integration Hub publications and subscriptions APIs to run publications and subscriptions, to
enable and disable publications and subscriptions, to reprocess publication and subscription events, to query
the status of publication and subscription events, and to extract data from the Data Integration Hub catalog.

You can use the following publications and subscriptions APIs:

• Run Publication Subscription REST API. Starts a publication or a subscription, including disabled
publications and subscriptions, and returns the event ID of the publication or the subscription event that
Data Integration Hub generates.
Note: You can use the Run Publication Subscription REST API to publish data and subscribe to data with
publications and subscriptions that trigger a Data Integration task. You cannot use the API to publish data
and subscribe to data with data-driven publications and subscriptions.
• Run Publication Subscription command line API. Starts a publication or a subscription from a command
line utility and returns the event ID of the publication or the subscription event that Data Integration Hub
generates. You cannot run disabled publications and subscriptions with the command line API. You
cannot call the command line API from a remote server.
Tip: Use the Run Publication Subscription REST API to start the running of publications and subscriptions
from a remote server.
• Change Publication Subscription Mode REST API. Changes the mode of a publication or a subscription,
that is, enables a disabled publication or subscription and disables an enabled publication or subscription.
• Reprocess Event REST API. Reprocesses a publication or subscription event, including events of disabled
publications and subscriptions.

71
 • Event Status REST API. Returns the status of a publication or subscription event.

Run Publication Subscription REST API

Use the Data Integration Hub Run Publication Subscription REST API to run a specific publication or a
specific subscription. You can run the publication or the subscription regardless of its mode, that is, you can
run both enabled and disabled publications and subscriptions.

Note: You can use the Run Publication Subscription REST API to publish data and subscribe to data with
publications and subscriptions that trigger a Data Integration task. You cannot use the API to publish data
and subscribe to data with data-driven publications and subscriptions.

The Run Publication Subscription API returns the response code of the action that you perform. If the
publication or subscription runs successfully, the API returns the event ID of the publication or the
subscription event that Data Integration Hub generates. You can run the Data Integration Hub Event Status
API to query the status of the publication or subscription event.

To run a publication or a subscription from the API, you must use a Data Integration Hub user with
permissions and privileges for the publication or for the subscription that you want to run. For more
information, see the Data Integration Hub Administrator Guide.

Sample Files
The <DIH_InstallationDir>\samples\rest_api_samples folder contains sample client applications and a
readme file that describes the applications.

Run Publication Subscription REST API Request

The Data Integration Hub uses different REST URLs for running a publication and for running a subscription.

To run a publication, use the following REST URL:

[Link]
For example:
[Link]
To run a subscription, use the following REST URL:
[Link]
For example:
[Link]
Request syntax for running a publication

To run a publication, use the following request syntax:

{
"publicationName": "<publicationName>",
"parameters": [
{"name": "param1", "value": "value"},
{"name": "param2", "value": "value"}
],
"paramFileContent": "<content of parameter file>",
"runPreprocess": "<true/false>",
"runDisabled": "<true/false>"
}

72 Chapter 8: Data Integration Hub Publications and Subscriptions APIs

 The following list describes the elements of the request:

• publicationName. Name of the publication to run.

• parameters. Optional request parameters.
• paramFileContent. Content of optional parameter file.
• runPreprocess. Whether or not to run a publication pre-process before the publication runs.
• runDisabled. Whether or not to run a publication that is in a Disabled status.

For example:
{
"publicationName": "daily_sales",
"parameters": [
{"name": "SRC_SAP", "value": "[Link]"},
{"name": "TGT_ORA", "value": "oracle_sap_staging"}
],
"paramFileContent": "[DWH_PROJECT.WF:wkf_daily_loading] \n $
$platform=rh7",
"runPreprocess": "false",
"runDisabled": "true"
}
Request syntax for running a subscription

To run a subscription, use the following request syntax:

{
"subscriptionName": "<subscriptionName>",
"parameters": [
{"name": "param1", "value": "value"},
{"name": "param2", "value": "value"}
],
"paramFileContent": "<content of parameter file>",
"runDisabled": "<true/false>"
}
The following list describes the elements of the request:

• subscriptionName. Name of the subscription to run.

• parameters. Optional request parameters.
• paramFileContent. Content of optional parameter file.
• runDisabled. Whether or not to run a subscription that is in a Disabled status.

For example:
{
"subscriptionName": "daily_report",
"parameters": [
{"name": "SRC_ORA", "value": "oracle_sap_staging"},
{"name": "SuccessEmail", "value": "customer@[Link]"}
],
"paramFileContent": "[DWH_PROJECT.WF:wkf_daily_loading] \n $
$platform=rh7",
"runDisabled": "true"
}

Run Publication Subscription REST API 73

 Run Publication Subscription REST API Action Response
When you use the Data Integration Hub Run Publication Subscription REST API to start the running of a
publication or of a subscription, Data Integration Hub returns the response code of the action that you
perform in the REST API response.

Running a publication or a subscription from the REST API returns one of the following response codes:

• SUCCESS. Data Integration Hub triggered the publication or the subscription successfully. The status
message includes the event ID of the publication or the subscription event that Data Integration Hub
generates.
• FAILED. Data Integration Hub could not trigger the publication or the subscription. The response provides
the reason for the failure. For example, Data Integration Hub did not run the subscription because no
publications are ready for consumption by the subscription.

Run Publication Subscription Command Line API

Use the Data Integration Hub Run Publication Subscription command line API to start the running of a
specific publication and of a specific subscription from a command line utility. The API is available on
Windows and UNIX operating systems.

You can run the Run Publication Subscription command line API from the Data Integration Hub server.

Tip: Use the Run Publication Subscription REST API to start the running of publications and subscriptions
from a remote server.

The Run Publication Subscription API returns the response code of the action that you perform. If the
publication or subscription runs successfully, the API returns the event ID of the publication or the
subscription event that Data Integration Hub generates. You can run the Data Integration Hub Event Status
API to query the status of the publication or subscription event.

To run a publication or a subscription from the API, you must use a Data Integration Hub user with
permissions and privileges for the publication or for the subscription that you want to run. For more
information, see the Data Integration Hub Administrator Guide.

Data Integration Hub Run Publication Subscription Command Line

API Command Syntax
The Data Integration Hub Run Publication Subscription command line API uses the following syntax:
runsubscriptionpublication
<-c|--command> publication|subscription
<-n|--name> name
<-u|--user> user
<-p|--password> password
[-r|--preprocess]
[-f|--file "<parameters file path>"]
[-v|--parameter "<key>=<value>"...]
[--server "<hostname:port>"]
Note: When you run a publication or a subscription with both the --file and the --parameter options, Data
Integration Hub orders the parameters according to the following sequence:

1. Parameters defined in the workflow-specific section of the parameters file that you specify in --file.
2. Parameters that you define in --parameter.

74 Chapter 8: Data Integration Hub Publications and Subscriptions APIs

3. Parameters defined in the Global section of the parameters file that you specify in --file.

The command line API is in the following location: <DIHInstallationDir>/dx-tools

The following table describes the Data Integration Hub Run Publication Subscription command line API
options and arguments:

Option Argument Description

-c command Required. Command to run the publication or to run the subscription. Enter
--command one of following commands:
- publication. Instructs Data Integration Hub to trigger the publication
workflow for the publication that you define in the --name option.
- subscription. Instructs Data Integration Hub to trigger the subscription
workflow for the subscription that you define in the --name option.

-n name Required. Name of the publication to run or of the subscription to run. Data
--name Integration Hub verifies the permissions and privileges to run the publication
or the subscription against this user.

-u user name Optional. User name of an Operation Console user account with the Manage
--user Data privileges to run the runsubscriptionpublication command. To run
a subscription or a publication with the command, the user account must have
run subscription or run publication privileges.
If you use Informatica domain authentication or Informatica domain with
Kerberos authentication, the user name must specify the Informatica security
domain, separated by the @ symbol. For example:
Administrator@SecurityDomain

-U Environment variable Optional. Environment variable that contains a user name.

User name of an Operation Console user account with the Manage Data
privileges to run the runsubscriptionpublication command. To run a
subscription or a publication with the command, the user account must have
run subscription or run publication privileges.
If you use Informatica domain authentication or Informatica domain with
Kerberos authentication, the user name must specify the Informatica security
domain, separated by the @ symbol. For example:
Administrator@SecurityDomain
Note: You must specify at least one of the user name options, -u or -U.

-p password Optional. Password for the Operation Console user that runs the
--password runsubscriptionpublication command.

-P Environment variable Optional. Environment variable that contains the a password.

Password for the Operation Console user that runs the
runsubscriptionpublication command. The password must be
encrypted. Use dxencrypt for the encrypted value.
Note: You must specify at least one of the password options, -p or -P.

-r - Optional for the publication command. For publications where a pre-process is

--preprocess defined, this command runs the pre-process.

-f parameters_file_path Optional. A path to a workflow parameter file.

--file Data Integration Hub uses the content of the file as the content of the
workflow parameter file.

Run Publication Subscription Command Line API 75

 Option Argument Description

-v <key>=<value> Optional. A key-value pair pass as a custom workflow parameter:

--parameter - When the API runs a publication, Data Integration Hub passes the parameter
to the publication workflow.
- When the API runs a publication pre-process, using the --preprocess
option, Data Integration Hub passes the parameter to the pre-process
workflow.
- When the API runs a subscription, Data Integration Hub passes the
parameter to the subscription workflow.
You can enter multiple parameters. For example:
-c subscription -v "employee_ID=148" -v "department=sales"
Note: The parameter or parameters must be defined for the workflow of the
entity that the API runs. Data Integration Hub does not pass undefined
parameters to PowerCenter, and does not display an error.

--server hostname:port Optional. Host name and port number of the Data Integration Hub server. If
you do not enter a value, the Run Publication Subscription API connects to the
localhost server with the default port 18095.
You must enclose the value in quotation marks. For example:
-c subscription --server "localhost:18096"

Run Publication Subscription Command Line API Notifications

When you use the Data Integration Hub command line API to start the running of a publication or of a
subscription, Data Integration Hub notifies you whether the command has succeeded or not.

If the command succeeds, the notification includes the event ID of the publication or the subscription event
that Data Integration Hub generates.

If the command fails, the notification includes an error message with the cause of the failure. A failure can be
caused by one of the following reasons:

• The publication or the subscription is disabled.

• Publication in process. Applicable to relational database publications only. Data Integration Hub cannot
run the publication because the publication is currently running.
• No publications to consume. Applicable to subscriptions only. Data Integration Hub did not run the
subscription because no publications are ready for consumption by the subscription.

Change Publication Subscription Mode REST API

Use the Data Integration Hub Change Publication Subscription Mode REST API to change the mode of a
publication or a subscription, that is, to enable a disabled publication or subscription or to disable an enabled
publication or subscription.

To change the mode of a publication, use the following REST URL:

[Link]
Where:

For example:
[Link]

76 Chapter 8: Data Integration Hub Publications and Subscriptions APIs

 To change the mode of a subscription, use the following REST URL:
https:[Link]
Where :

For example:
[Link]
Request syntax for changing the mode of a publication

To change the mode of a publication, use the following request syntax:

{
"publicationName": "<publicationName>",
"mode": "<enable/disable>"
}
For example:
{
"publicationName": "daily_sales",
"mode": "enable"
}
Request syntax for changing the mode of a subscription

To change the mode of a subscription, use the following request syntax:

{
"subscriptionName": "<subscriptionName>",
"mode": "<enable/disable>"
}
For example:
{
"subscriptionName": "daily_reports",
"mode": "disable"
}

Change Publication Subscription Mode REST API Action Response

When you use the Data Integration Hub REST API to change the mode of a publication or of a subscription,
Data Integration Hub returns the response code of the action that you perform in the REST API response.

Changing the mode of a publication or a subscription from the REST API returns one of the following
response codes:

• When Data Integration Hub changes the mode of the publication or the subscription successfully, the API
returns a SUCCESS response.
• When Data Integration Hub fails to change the mode of the publication or the subscription, the response
provides the reason for the failure. For example, when you do not have sufficient permissions to perform
the operation.

Reprocess Event REST API

Use the Data Integration Hub Reprocess Event REST API to reprocess publication and subscription events,
including events of disabled publications and subscriptions.

To reprocess a publication or a subscription event, use the following REST URL:

[Link]

Reprocess Event REST API 77

 For example:
[Link]
Use the following syntax to reprocess an event:
{
"eventId" : "<eventId>"
}
For example:
{
"eventId" : "40558"
}

Sample File
The <DIH_InstallationDir>\samples\rest_api_samples folder contains a sample client application and a
readme file that describes the application.

Reprocess Event REST API Action Response

When you use the Data Integration Hub Reprocess Event REST API to reprocess a publication or a
subscription event, Data Integration Hub returns the response code of the action that you perform in the
REST API response.

The response includes the following information:

Property Description

responseCode Response of the action:

- 0: success.
- Any number higher than 0: error.

reprocessEventId New event ID that Data Integration Hub generates for the publication or for the subscription when
it reprocesses the existing event.

message Error message. If the response code is 0 (success), the API returns the message null.

Event Status REST API

When you use a Data Integration Hub Run Publication Subscription API to start the running of a publication or
of a subscription and the action succeeds, Data Integration Hub returns the event ID of the publication or the
subscription event that it generates.

The manner in which Data Integration Hub returns the event ID depends on the API that you use to run the
publication or the subscription:

• When you run the REST API, Data Integration Hub returns the event ID in the REST API response.
• When you run the command line API, Data Integration Hub returns the event ID in the command line
notification.
You can use the Data Integration Hub Event Status REST API to query the status of the publication or
subscription event according to the event ID. You can see whether the publication or subscription process is
still running, and after the process is complete, you can see whether it completed successfully. If the process
fails, the response to the query includes the cause of the failure.

78 Chapter 8: Data Integration Hub Publications and Subscriptions APIs

 Note: For a list of event statuses, see Event Statuses For publications, Data Integration Hub assigns the
following event statuses: .

To query the status of an event, use a GET command with the following REST URL:
[Link]
Where:

For example:
[Link]

Event Status API Response

When you use the Data Integration Hub Event Status API to query the status of a publication or a subscription
event, the API returns the event response in an [Link] model class.

The response includes the following information:

Property Description

responseCode Response of the Run Publication Subscription API action.

eventId ID of the event that Data Integration Hub generates for the publication or for the
subscription.

eventType Type of the event that Data Integration Hub generates for the publication or for the
subscription.

topicName Name of the topic that is associated with the publication or with the subscription.

publicationName or Name of the publication or of the subscription.

subscriptionName

applicationName Name of the publishing or of the subscribing application.

eventStatus Status of the event that Data Integration Hub generates for the publication or for the
subscription.

eventStartTimeLong Time when the publication or the subscription event started. System time in milliseconds
as returned by Java API [Link].

eventEndTimeLong Time when the publication or the subscription event ended. System time in milliseconds as
returned by Java API [Link].

referencedEventsList Applicable for file publication events, aggregated subscription events, and compound
subscription events. List of event IDs that are related to the file publication, the aggregated
subscription, or the compound subscription event.
For example, the referencedEventsList of a file publication event includes the file events of
the files that are published as part of the publication event.

isFinal Is the event in a final state.

isError Is the event in Error status.

sourceSuccessRows Number of source rows that Data Integration Hub read successfully.

Event Status REST API 79

 Property Description

sourceFailedRows Number of source rows that Data Integration Hub failed to read.

targetFailedRows Number of target rows that Data Integration Hub failed to write.

targetSuccessRows Number of target rows that Data Integration Hub wrote successfully.

detailedMessage Applicable for events in an Error status. If the error is caused by Data Integration Hub,
detailedMessage returns the error message from the Data Integration Hub event. For any
other error, for example an authentication failure or an incorrect REST URL request,
detailedMessage includes a message that describes the cause of the error.

Sample Event Status API Responses

Response to a request to query the status of publication event 4003:

{
"responseCode": "SUCCESS",
"eventId": 4003,
"eventType": "Publication",
"topicName": "top_120",
"publicationName": "ng_pub_120_1",
"applicationName": "app1",
"eventStatus": "Complete",
"eventStartTimeLong": 1431078308560,
"eventEndTimeLong": 1431078313780,
"isFinal": true,
"isError": false,
"sourceSuccessRows": 10,
"sourceFailedRows": 0,
"targetFailedRows": 0,
"targetSuccessRows: 10}
Response to a request to query the status of aggregated subscription event 3009, which includes
subscription events 3008 and 3007:
{
"responseCode": "SUCCESS",
"eventId": 3009,
"eventType": "Aggregated Subscription",
"topicName": "topic1",
"subscriptionName": "sub1",
"applicationName": "app1",
"eventStatus": "Complete",
"eventStartTimeLong": 1431065700088,
"eventEndTimeLong": 1431065704372,
"referencedEventsList": "3008,3007"
"isFinal": true,
"isError": false,
"sourceSuccessRows": 15,
"sourceFailedRows": 0,
"targetFailedRows": 0,
"targetSuccessRows: 15
}
Response to a request to query the status of publication event 3016, where the publication process failed:
Response:

{
"responseCode": "SUCCESS",
"eventId": 3016,
"eventType": "Publication",

80 Chapter 8: Data Integration Hub Publications and Subscriptions APIs

 "topicName": "top_120",
"publicationName": "ng_pub_120_1",
"applicationName": "app1",
"eventStatus": "Error",
"eventStartTimeLong": 1431066353202,
"eventEndTimeLong": 1431066357162,
"isFinal": true,
"isError": true,
"sourceSuccessRows": 2,
"sourceFailedRows": 1,
"targetFailedRows": 1,
"targetSuccessRows: 2
"detailedMessage": "Error while copying several rows :\nSrcFailedRows:
1\nTgtFailedRows: 1\nSrcSuccessRows: 2\nTgtSuccessRows: 2\nPowerCenter workflow:
s__DIH_pub_ng_pub_120_1\nPowerCenter session: s__DIH_pub_ng_pub_120_1\n\nCheck the
PowerCenter session log for more information."
}

Event Status REST API 81

Chapter 9

Data Extraction APIs

This chapter includes the following topics:

• Data Extraction APIs Overview, 82

• Catalog API, 82
• Data Integration Hub Events View, 87

Data Extraction APIs Overview

Use the data extraction APIs to extract data from Data Integration Hub.

You can use the following Data Integration Hub APIs for data extraction:

• Catalog API. Extracts data from the Data Integration Hub catalog, including topic, publication, and
subscription metadata.
• Events API. Provides a database view of Data Integration Hub events.

Catalog API
Use the Catalog API to extract data from the Data Integration Hub catalog, including topic metadata and
metadata about the publications and subscriptions that are associated with each topic.

You can extract metadata pertaining to topics, publications, and subscriptions for which you have both View
privileges and Read access permissions.

To extract data from the catalog, use the following REST URL:
[Link]

Data Integration Hub Catalog API Response

When you use the Data Integration Hub Catalog API to extract data from the Data Integration Hub catalog, the
API returns a JSON string that contains metadata about all the topics for which you have the required
privileges and permissions.

The string includes the following data for each topic in the response:

82
topicName

Name of the topic.

topicDesc

Textual description of the topic.

topicType

Type of the topic: Delta or Full.

topicTables

For each table in the topic, an entry with the table name and detailed information about each of the table
fields.

publications

For each publication that is associated with the topic, the following data is provided:
publicationName

Name of the publication.

publicationDesc

Textual description of the publication.

applicationName

Application from which the publication publishes data or files.

publicationSourceType

Type of publication source.

publicationConnectionName

For relational database publications and for HDFS publications: name of the connection from where
the publication workflow reads the data or the files to be published.

publicationDBType

For relational database publications: type of database.

subscriptions

For each subscription that is associated with the topic, the following data is provided:
subscriptionName

Name of the subscription.

subscriptionDesc

Textual description of the subscription.

applicationName

Application that consumes data or files from the topic.

subscriptionTargetType

Type of subscription target.

subscriptionConnectionName

For relational database subscriptions and for HDFS subscriptions: name of the connection to where
the subscription workflow writes the data or the files that the application consumes.

subscriptionDBType

For relational database subscriptions: type of database.

Catalog API 83
 Sample Data Integration Hub Catalog API Response
The following example shows a response to a request to extract data from the Data Integration Hub catalog:

{
"responseCode": "SUCCESS",
"catalogTopics": [
{
"topicName": "FileTopic",
"topicDesc": null,
"topicType": "Delta"
"topicTables": [
{
"tableName": "Orders"
"tableFields":[
{
"name":"_Name_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_Type_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_ParentId_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
}
}
],
"publications": [
{
"publicationName": "FilePub",
"publicationDesc": null,
"applicationName": "FileApp",
"publicationSourceType": "FLAT_FILE",
"publicationConnectionName": null,
"publicationDBType": null
}
],
"subscriptions": [
{
"subscriptionName": "FileSub",
"subscriptionDesc": null,
"applicationName": "FileApp",
"subscriptionTargetType": "FLAT_FILE",
"subscriptionConnectionName": null,
"subscriptionDBType": null
}
]
},

84 Chapter 9: Data Extraction APIs

{
"topicName": "OrderTopic",
"topicDesc": null,
"topicType": "Delta",
"topicTables": [
{
"tableName": "OrderTable"
"tableFields":[
{
"name":"_Name_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_Type_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_ParentId_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_StartDate_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_EndDate_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
}
},
{
"tableName": "CustomerTable"
"tableFields":[
{
"name":"_Name_"
"fieldType":"STRING"
"nullable":false

Catalog API 85
 "scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_Type_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_ParentId_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_ExpectedRevenue_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
},
{
"name":"_IsActive_"
"fieldType":"STRING"
"nullable":false
"scale":-1
"precision":255
"length":255
"primaryKey":false
"filterAccelerator":false
"encrypted":true
}
},
{

},
],
"publications": [
{
"publicationName": "OrdersPublication",
"publicationDesc": null,
"applicationName": "OrderPublications",
"publicationSourceType": "RDBMS",
"publicationConnectionName": "OrderSource",
"publicationDBType": "SQLSERVER"
}
],
"subscriptions": [
{
"subscriptionName": "OrdersSubscription",
"subscriptionDesc": null,
"applicationName": "OrderSubscriptions",

86 Chapter 9: Data Extraction APIs

 "subscriptionTargetType": "FLAT_FILE",
"subscriptionConnectionName": null,
"subscriptionDBType": null
},
{
"subscriptionName": "OrderSubs",
"subscriptionDesc": null,
"applicationName": "OrderSubscriptions",
"subscriptionTargetType": "RDBMS",
"subscriptionConnectionName": "OrderTarget",
"subscriptionDBType": "SQLSERVER"
}
]
}
]
}
]
}

Data Integration Hub Events View

Use your SQL client to view Data Integration Hub events in the Data Integration Hub repository.

In your SQL client, the events view resides under the Data Integration Hub database, in
DX_VIEW_PUB_SUB_EVENT.

The view contains the following columns:

EVENT_ID

ID of the event.

EVENT_TYPE

Type of event, such as publication, subscription, file, and system events.

PUBLICATION_SUBSCRIPTION_NAME

Name of the publication or of the subscription that generated the event.

APPLICATION_NAME

Name of the application that is associated with the publication or of the subscription that generated the
event.

TOPIC_NAME

Name of the topic that is associated with the publication or of the subscription that generated the event.

EVENT_STATUS
Status of the event, such as error, complete, and pending events.

EVENT_START_TIME

Date and time when the event started.

EVENT_END_TIME

Date and time when the event ended.

EVENT_DURATION

Duration of the event. Data Integration Hub calculates the duration based on EVENT_START_TIME and
EVENT_END_TIME.

Data Integration Hub Events View 87

 SOURCE_SUCCESS_ROWS

Number of rows that Data Integration Hub read successfully from the source.

SOURCE_FAILED_ROWS

Number of rows that Data Integration Hub failed to read from the source.

TARGET_SUCCESS_ROWS

Number rows that Data Integration Hub read successfully from the target.

TARGET_FAILED_ROWS

Number of rows that Data Integration Hub failed to read from the target.

Note:

• In publications, source refers to the publishing application and target refers to the Data Integration Hub
publication repository.
• In subscriptions, source refers to the Data Integration Hub publication repository and target refers to the
subscribing application.
• The number of successful source and target rows and the number of failed source and target rows show
only for events that were created in the Data Integration Hub repository after the installation of Data
Integration Hub version 9.6.2, or after an upgrade of an older version of Data Integration Hub to version
9.6.2.

88 Chapter 9: Data Extraction APIs

Index

A Big Data Streaming mappings (continued)

publication connections 39, 40
API publication data objects 39, 41
publication subscription mode 76 run-time environment 42
reprocess event 77
run publication subscription 72, 74
architecture
components 13
C
automatic mapping catalog API
mapping guidelines 49 description 82
mappings 49 response 82
automatic PowerCenter mappings catalog API response
description 23 example 84
guidelines 23 change mode API
logs 24 REST API 77
automatic PowerCenter workflows change mode REST API
description 23 action status 77
guidelines 23 change mode REST API action
logs 24 status 77
cloud
mapping 48

B task 48, 49
cloud mapping
B2B Data Exchange workflow definition 48
definition 51 cloud task
B2B Data Exchange workflows definition 48
managing 51 publication process 17
batch workflow subscription process 19
definition 22 command line API
developing 28 run publication subscription 74
publication process 16 create application
subscription process 18 Big Data Management mappings 40, 44
batch workflows Big Data Streaming mappings 42
guidelines 28 create mapping
big data Big Data Management 39, 41, 43
description 14 Big Data Streaming 39, 41
Big Data Management custom mapping
create mapping 39, 41, 43 mapping guidelines 49
Big Data Management mappings mappings 49
create application 40, 44 task guidelines 49
creating 39, 41, 43 tasks 49
expression 39 custom mappings
filter 43 developing 27
parameters 39, 43 custom PowerCenter mappings
publication connections 39, 40 description 24
publication data objects 39, 41 guidelines 25
run-time environment 40, 44 custom PowerCenter workflows
subscription connections 43 description 24
subscription data objects 43 guidelines 25
Big Data Streaming
create mapping 39, 41
Big Data Streaming mappings
create application 42
D
creating 39, 41 Data Engineering Integration
expression 41 mappings 36–38, 42
Java transformation 41 publication mappings 38

89
Data Engineering Integration (continued) example
subscription mappings 42 catalog API response 84
Data Engineering Integration mappings expression
before you begin 38 Big Data Management mappings 39
description 36 Big Data Streaming mappings 41
developing 38, 42
Data Engineering Streaming
mappings 36–38, 40
publication mappings 40
F
Data Engineering Streaming mappings filter
before you begin 38 Big Data Management mappings 43
description 36 forms designer
developing 40 actions 68
data extraction APIs definition 67
catalog API 82 Designer tab 67
description 82 element properties 69
events view 87 group properties 70
data-driven
publication process 18
subscription process 19
develop
G
Data Engineering Integration mappings 38, 42 guidelines
Data Engineering Streaming mappings 40 automatic PowerCenter mappings and workflows 23
developing batch workflow custom PowerCenter mappings and workflows 25
process 28 PowerCenter batch workflows 28
developing real-time workflows
process 32
DX_Add_Document_To_Event
definition 57
I
ports 57 Informatica Cloud
properties 58 mappings 49
DX_Event_Attribute Informatica Intelligent Cloud Services
definition 58 mappings 49
ports 59 tasks 49
properties 59
DX_Event_Details
definition 59
ports 60
J
properties 60 Java transformation
DX_Generate_Temporary_File Big Data Streaming mappings 41
definition 60
ports 61
properties 61
DX_Notification
L
definition 61 logs
ports 62 automatic PowerCenter mappings and workflows 24
properties 62
DX_Publication_Parameters
definition 63
ports 63
M
DX_Start_Publication mappings
definition 63 Data Engineering Integration 36–38, 42
ports 64 Data Engineering Streaming 36–38, 40
properties 64 guidelines 49
DX_Throw_Error PowerCenter 21
definition 65
ports 65
properties 66
O
operation console

E description 15
overview
event status API description 10
process status 78–80
response 79, 80
events view
description 87

90 Index
P real-time workflows
developing 32
parameters guidelines 31
Big Data Management mappings 39, 43 reprocess event
PowerCenter REST API 77
create mapping 30 reprocess event API
creating source definition 29 REST API 78
creating target definition 30 reprocess event API REST API
creating the workflow 30 action status 78
export workflow 31, 34 reprocess event API REST API action
mappings 21 status 78
save workflow 31, 34 REST API
sources and targets 28 publication subscription mode 76
workflow 21, 22 reprocess event 77
PowerCenter batch workflows run publication subscription 72
guidelines 28 run publication subscription API
PowerCenter mappings command line 76
automatic 23 command line API 74
custom 24 process status 78–80
PowerCenter workflow REST API 72, 74
type 22 run publication subscription command line api
PowerCenter workflows command syntax 74
automatic 23 run publication subscription command line API
batch 27 notifications 76
custom 24 run publication subscription process
developing custom mappings 27 status 78–80
publication run publication subscription REST API
definition 16 action status 74
process 16 request 72
publication connections run publication subscription REST API action
Big Data Management 39, 40 status 74
Big Data Streaming 39, 40 run publication subscription status
publication data objects event status API 78–80
Big Data Management 39, 41 run-time environment
Big Data Streaming 39, 41 Big Data Management mappings 40, 44
publication mappings Big Data Streaming mappings 42
Data Engineering Integration 38
Data Engineering Streaming 40
publication process
batch workflow 16
S
cloud task 17 subscription
data-driven 18 definition 16
real-time 17 process 18
publication repository subscription connections
datatypes 25 Big Data Management 43
publication source subscription data objects
Big Data Management 39, 40 Big Data Management 43
Big Data Streaming 39, 40 subscription mappings
publication subscription mode Data Engineering Integration 42
REST API 76 subscription process
publication target batch workflow 18
Big Data Management 39–41 cloud task 19
Big Data Streaming 39–41 data-driven 19
publications and subscriptions APIs subscription source
description 71 Big Data Management 43
subscription target
Big Data Management 43

R
real-time workflow
create mapping 33
T
create topic 34, 35 tasks
creating the workflow 34 guidelines 49
definition 22 topic
publication process 17 overview 15
renaming the workflow target 35 Transformation
sources and targets 32 DX_Add_Document_To_Event 57
DX_Event_Attribute 58

Index 91
Transformation (continued)
DX_Event_Details 59 W
DX_Generate_Temporary_File 60 workflow
DX_Notification 61 B2B Data Exchange 51
DX_Publication_Parameters 63 PowerCenter 21, 22
DX_Start_Publication 63 type 22
DX_Throw_Error 65 workflows
Transformations properties 52
configuring 55 Workflows
definition 54 real-time workflow 31
error handling 55
guidelines 56
installing plug-ins 55

U
user roles
developer 19

92 Index