Informatica B2B Data Transformation (Version 9.5.1 HF1)

Libraries Guide

Informatica B2B Data Transformation Libraries Guide

Version 9.5.1 HF1May 2013

Copyright (c) 2001-2013 Informatica Corporation. All rights reserved.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; and http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; and http://jsoncpp.sourceforge.net/LICENSE.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mit-license.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0).

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

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7676516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending.

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

NOTICES

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

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

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

Part Number: DT-LIB-95100-HF1-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1: Libraries for Industry Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Purpose of Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Library Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Obtaining Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Library Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing and Updating a Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Uninstalling a Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Version Compatibility of Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

XML-Based Industry Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: Using Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Creating a Library Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Creating a New Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Adding to an Existing Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrading Library Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Working with Library Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Identifying the Startup Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Changing the Startup Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Testing a Parser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Testing a Serializer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Troubleshooting the IntelliScript. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Editing Library Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Deploying a Project as a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3: Descriptions of the Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11ACORD AL3 Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

ACORD AL3 Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table of Contents i

XML of an ACORD AL3 Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

ACORD-MDM Mappers Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Output MDM JavaBeans File XML Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

ACORD LNA file XML Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Creating an ACORD-MDM Mapper Project in the Developer Tool. . . . . . . . . . . . . . . . . . . . 14

ASN.1 Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

ASN.1 Protocol Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

ASN.1 Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

XML Version of an ASN.1 Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing the ASN.1 Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Creating an ASN.1 Library Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

ASN-1Step Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

AsnToXml Document Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

BAI Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

BAI2 Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

XML Version of a BAI2 Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

BAI Lockbox Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

XML of a BAI Lockbox Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Bloomberg Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Bloomberg Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

XML Version of a Bloomberg Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Field Definition Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Creating a Bloomberg Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

COBOL Processing Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Importing a COBOL Data Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Test Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Editing COBOL Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

CREST Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

CREST Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

XML of a CREST Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

DTCC-NSCC Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

DTTC-NSCC Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

XML of a DTCC-NSCC Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Streamer Configuration for Parsing Large Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

EDIFACT Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

EDIFACT Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

XML of an EDIFACT Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Validation and Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

EDI-X12 Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

X12 Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

XML of an X12 Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

ii Table of Contents

Validation of X12 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

X12 Message Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

EDI Libraries Based on X12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

FIX Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

FIX Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

XML of a FIX Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

FpML Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

HIPAA Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

HIPAA Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

XML Version of a HIPAA Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Validation and Acknowledgment Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing and Configuring the HIPAA Validation Add-On Package. . . . . . . . . . . . . . . . . . . 42

Using Validation and Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

HIPAA Crosswalk Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

HIX Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

HIX Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

XML of a HIX Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Message Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

HL7 Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

HL7 Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

XML Version of an HL7 Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

IATA PADIS Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

IATA PADIS Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

XML of an IATA PADIS Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

IDC-IDSI Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

IDC-IDSI Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

XML of an IDC-IDSI Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

MDM JavaBeans Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Source JavaBeans XML File Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Output XML File Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Creating an MDM JavaBeans Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

NACHA Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

NACHA Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

XML of a NACHA Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

NCPDP Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

NCPDP Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

XML of an NCPDP Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

SEPA Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SWIFT Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SWIFT MT Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

XML Version of a SWIFT MT Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Installing Lookup Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Table of Contents iii

Message Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

SWIFT MT Parsers and Serializers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

MX Validators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

MT/MX Translators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Telekurs VDF Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Telekurs VDF Message Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

XML of a Telekurs VDF Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Thomson Reuters Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Thomson Reuters Report Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

XML Version of a Thomson Reuters Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Creating a Thomson Reuters Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 4: Library Customization Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Library Customization Tool Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Using the Library Customization Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Opening the Library Customization Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Creating a Library Customization Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Importing a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Improving the Example Source Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Switching the Example Source File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Editor and Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Editing a Message Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Generating and Testing the Customized Library Components. . . . . . . . . . . . . . . . . . . . . . 78

Deploying Customized Library Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Exporting a PDF Message Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Enabling Alerts for Editing XSD Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Message Structures and Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Hierarchical Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Global and Positional Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

DTCC-NSCC Message Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

EDIFACT Message Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

EDI-X12 Message Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

HIPAA Message Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

HL7 Message Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

SWIFT Message Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

iv Table of Contents

PrefaceThe Data Transformation Libraries Guide is written for developers and analysts who need to transform data to or from industry standard messaging formats. This guide explains how to use the library transformation components with the industry standards and how to customize the library components for specialized needs. This guide assumes that you understand the standards you are using and that you know how to deploy and run Data Transformation services.

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://mysupport.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product Documentation, and access to the Informatica user community.

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from http://mysupport.informatica.com.

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica How-To LibraryAs an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide

v

http://mysupport.informatica.commailto:infa_documentation@informatica.comhttp://mysupport.informatica.comhttp://www.informatica.comhttp://mysupport.informatica.com

solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at KB_Feedback@informatica.com.

Informatica Support YouTube ChannelYou can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through email at supportvideos@informatica.com or send a tweet to @INFASupport.

Informatica MarketplaceThe Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.

Informatica VelocityYou can access Informatica Velocity at http://mysupport.informatica.com. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com.

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com.

vi Preface

http://mysupport.informatica.commailto:KB_Feedback@informatica.comhttp://www.youtube.com/user/INFASupporthttp://www.informaticamarketplace.comhttp://mysupport.informatica.comhttp://mysupport.informatica.com

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Toll FreeBrazil 0800 891 0202Mexico 001 888 209 8853North America +1 877 463 2435

Toll FreeFrance 0805 804632Germany 0800 5891281Italy 800 915 985Netherlands 0800 2300001Portugal 800 208 360Spain 900 813 166Switzerland 0800 463 200United Kingdom 0800 023 4632

Standard RateBelgium +31 30 6022 797France +33 1 4138 9226Germany +49 1805 702702Netherlands +31 30 6022 797United Kingdom +44 1628 511445

Toll FreeAustralia 1 800 120 365Asia Pacific 00 080 00016360China 400 810 0900

Preface vii

viii

C H A P T E R 1

Libraries for Industry StandardsThis chapter includes the following topics:

Purpose of Libraries, 1

Obtaining Libraries, 2

Installing Libraries, 3

XML-Based Industry Standards, 4

Purpose of LibrariesData Transformation libraries contain predefined transformation components for use with the following industry messaging standards:

ACORD AL3

ACORD-MDM Mappers

ASN.1

BAI

Bloomberg Per Security, Back Office and Extended Back Office

CREST

DTCC-NSCC

EDIFACT

EDI-X12 and related EDI standards

FIX

FpML

HIPAA

HL7

IATA PADIS

IDC-IDSI

MDM JavaBeans

NACHA

NCPDP

SEPA

1

SWIFT

Telekurs VDF

Thomson Reuters DataScope Select

Each library contains a large number of components, such as parsers, serializers, and XML schemas, designed for use with industry standard and specific application messages. You can use these components to transform documents from industry standards to XML and from XML to other formats.

Library components offer the following advantages:

Saving time. You can use predefined library components, rather than designing and implementing the components yourself.

Standardized implementation. Ensures consistency among your applications.

Robust construction. Supports all options and syntactic intricacies unique to each industry standard.

Use Data Transformation Studio to import library components.

Library StructureA library is a directory that contains a family of fully configured Data Transformation components. All libraries contain parsers, serializers, and XML schemas. Some libraries contain additional components for purposes such as message validation, acknowledgments, and diagnostic displays.

When you create a project, you can import a library component instead of building your own from scratch. You can use a library component without modification, or you can edit it to meet your needs.

Each library is designed to work with a particular industry standard. For example, the HL7 library contains project components for each of the message types or data structures available in the HL7 messaging standard for medical information systems.

The subdirectories of the library contain Data Transformation projects that define the parsers, serializers, and schemas. The projects are organized by category. For example, the HL7 library contains subdirectories such as:

Admission Discharge and Transfer MessagesAncillary Data ReportingControl Section

The Admission Discharge and Transfer Messages directory, in turn, contains directories for specific types of HL7 messages such as:

ADT_A01_Admit_a_PatientADT_A02_Transfer_a_Patient

The directories at the lowest level of nesting typically contain two Data Transformation CMW project files, for the parser and the serializer, respectively. In addition, these directories contain TGP script files and XSD schema files that define the transformations.

Obtaining LibrariesThe Data Transformation libraries are updated and released at frequent intervals. To obtain a library, contact Informatica. Be sure to specify:

The name of the library that you need.

2 Chapter 1: Libraries for Industry Standards

Your Data Transformation version. With certain limitations, a single library release can be used with multiple Data Transformation versions.

Any special requirements, such as compatibility with existing projects created using a particular library version.

Library DocumentationIn addition to reading this book, be sure to read the documentation supplied with each library, such as a ReadMe file, Release Notes, or other explanatory material.

Installing LibrariesInstall the libraries on a Microsoft Windows computer where you run Data Transformation Studio. In the Studio, you can use the library components to create transformation projects. After you configure a project, you can deploy it as a service to a production environment that runs Data Transformation Engine.

Installing and Updating a LibraryBefore you can use a Data Transformation library, you must install it. Use the same steps to update a library.

1. Copy the library ZIP file to your local file system.

2. In the Studio, click Help > Data Transformation Libraries.

The Preferences dialog box appears.

3. In the left panel, select Data Transformation Libraries, and then click Add/Update in the right panel.

The Add Data Transformation Library dialog box appears.

4. Browse to the library ZIP file, and then click Next.

The Info page appears.

5. If you want to view the Release Notes for the library, click Release Notes.

6. Click Next.

7. Select one or more versions, and then click Finish.

The library appears in the following directory:

\DataTransformation\Libraries

Uninstalling a Library1. In the Studio, click Help > Data Transformation Libraries.

2. Select a library and click Remove.

Version Compatibility of LibrariesUse the libraries supplied with your current Data Transformation version. This ensures that you have the most recent version of each library component.

On occasion, you might deliberately want to use an older library version. You can do this for compatibility with existing applications that use components from the older library. Data Transformation Studio enables

Installing Libraries 3

you to import components from older library versions. As needed, the Studio upgrades the internal code of the components for compatibility with the current Data Transformation version, while preserving the transformation logic of the older version. For more information about upgrading projects, see the Data Transformation Administration Guide.

XML-Based Industry StandardsIn addition to the libraries supporting specific industry messaging standards, Data Transformation has been certified for use with the following XML-based standards. Certification means that Data Transformation has been tested and correctly processes XML data conforming to the standard.

Note: Some of the table entries are XML versions of standards for which there are Data Transformation libraries. The library schemas are not necessarily the same as the schemas defined in the standards.

ACORD XML

XML version of the ACORD AL3 standard for the insurance industry. For more information, see ACORD AL3 Library on page 12.

Bloomberg

XML version of the Bloomberg standard. For more information, see Bloomberg Library on page 22.

FIXML

XML version of the Financial Information eXchange standard. For more information, see FIX Library on page 39.

FpML

Financial products Markup Language for complex financial products. For more information, see http://www.fpml.org.

HL7 Version 3

XML version of the HL7 standard for the health industry. For more information, see HL7 Library on page 56.

IFX

Interactive Financial eXchange standard for sharing financial information. For more information, see http://www.ifxforum.org/standards.

MISMO

Mortgage Industry Standards Maintenance Organization for mortgage and investment products and services. For more information, see http://www.mismo.org.

NIEM

National Information Exchange Model for exchange of information between US governmental agencies and private industries. For more information, see http://www.niem.gov/.

OAGi

Open Applications Group Inc. standard for business process interoperability. For more information, see http://www.openapplications.org.

4 Chapter 1: Libraries for Industry Standards

http://www.fpml.orghttp://www.ifxforum.org/standardshttp://www.mismo.orghttp://www.mismo.orghttp://www.openapplications.org

RosettaNet

Standard for B2B commerce and collaborative processes. For more information, see http://www.rosettanet.org.

SEPA

Single Euro Payments Area electronic payments standard. For more information, see SEPA Library on page 65.

SWIFT MX

XML version of the SWIFT standard for the financial industry. For more information, see SWIFT Library on page 65.

TWIST

Transaction Workflow Innovation Standards Team for electronic commerce. For more information, see http://www.twiststandards.org.

UNIFI (ISO 20022)

UNIversal Financial Industry messaging standard. For more information, see http://www.iso20022.org.

XML-Based Industry Standards 5

http://www.rosettanet.orghttp://www.twiststandards.orghttp://www.iso20022.org

C H A P T E R 2

Using LibrariesThis chapter includes the following topics:

Creating a Library Project, 6

Working with Library Projects, 7

Creating a Library ProjectYou can create a new project that contains a library component, or you can import a library component to an existing project.

Creating a New ProjectTo create a project containing a library component:

1. In Data Transformation Studio, select File > New > Project.

The New Project wizard appears.

2. Under the Data Transformation node, select Library Project and click Next.

3. Enter a project name and specify a storage location.

The default location is the Studio workspace directory.

4. On the Select Message page, expand the tree to display the library name, the library version, and the specific message or data structure that you want to process.

For example, if you want to process HL7 version 2.3 ADT_A01 messages, expand the tree to the following directory:

HL7\2_3\Admission Discharge and Transfer Messages\ADT_A01_Admit_a_Patient5. Select the specific parser or serializer component that you want to use in the project.

For example, select the following parser:ADT_A01_Admit_a_Patient_Parser

6. Click Finish.

Data Transformation Studio imports the required library components, such as the CMW, TGP, and XSD files, to a new project. The Data Transformation Explorer view displays the new project.

6

Adding to an Existing ProjectTo add a library component to an existing project:

1. Create a new project that contains the library component.

2. In the Data Transformation Explorer, expand the existing project to which you want to add the library component.

3. To add a parser or serializer, right-click the Scripts node and click Add File.

Browse to the new library project, select the TGP script file, and click Open. The Studio copies the file to the existing project.

You might need to add multiple TGP files. For example, a TGP file that defines a main parser might other TGP files that define secondary parsers. If you are not sure exactly which TGP files are required, it is safest to add all of them. Unused TGP files have no effect on the project.

4. To add an XML Schema, right-click the XSD node and click Add File.

Browse to the new library project, select the XSD file, and click Open. The Studio copies the file to the existing project.

Be sure to add all the XSD files that the library component requires. If you are not sure which XSD files are required, add all of them.

5. You can delete the new library project if you do not need it for other purposes.

Upgrading Library VersionsAfter you import a library component to a project, there is no link between the project and the library. If you install a new version of the library, the project is not automatically updated.

To update the project, re-import the component and test the project for any differences in behavior.

Working with Library ProjectsYou can display, edit, test, and deploy library projects in the Studio, in the same way as other Data Transformation projects. For more information, see the Data Transformation Getting Started Guide and the Data Transformation Studio User Guide.

The following paragraphs offer some tips for Studio operations that are often useful with library components.

Identifying the Startup ComponentLibrary projects typically have a complex structure, with numerous components defined at the top level and nested levels of the IntelliScript script. The structure is designed to support all the options defined in the industry standard.

Each project has a startup component that Data Transformation activates when you run the project.

To identify the startup component of a library project:

1. Open the project in Data Transformation Studio.

2. Click Run > Run.

This opens the Choose Startup Component window, which displays the name of the startup component.

Working with Library Projects 7

Changing the Startup Component1. Open the TGP script file in an IntelliScript editor.

2. Right-click the desired component and click Set as Startup Component.

Testing a ParserTo test how a parser processes a source document, run it on an example source document and examine the output. Alternatively, you can view its operation graphically.

Running a Parser on an Example Source DocumentThe library parsers are configured without an example source document. You can add an example source to test the parser operation.

1. Open the TGP script file of the project in the script panel of the IntelliScript editor.

2. Locate the definition of the startup component in the script.

In most library projects, it is the first component in the TGP file.

3. Expand the tree, and set the example_source property to LocalFile. 4. Browse to the source document that is nested within the LocalFile component.

The example pane of the IntelliScript editor displays the test document.

5. Click IntelliScript > Mark Example to highlight the data that the parser finds in the document.

6. Click Run > Run to activate the parser.

7. In the Events view, examine the log and confirm that the parser ran without error.

8. To view the parser output, double-click the Results/Output.xml file in the Data Transformation Explorer.

Displaying the Parser Results GraphicallyYou can use the color-coding feature of Data Transformation Studio to test the operation of a parser.

1. Open the TGP script file of the project in the script panel of the IntelliScript editor.

2. Click IntelliScript > Test Document and browse to a source document.

The example pane of the IntelliScript editor displays the document.

3. Click IntelliScript > Mark Example.

The Studio runs the parser and highlights the anchors that the parser found in the document.

Testing a SerializerTo test a library serializer:

1. Prepare an XML test input document conforming to the schema that is defined in the project.

An easy way to generate the XML document is to create a library parser project, and run it on a source document. The output of the parser is an XML document that you can use as the test input of the serializer.

2. Set the serializer as the startup component of the library project.

3. Optionally, set the example_source property of the serializer to the XML test input document.

8 Chapter 2: Using Libraries

If you omit this step, Data Transformation Studio prompts you for the test document when you run the project.

4. Run the project.

5. In the Events view, confirm that the serializer ran without error.

6. To view the serializer output, double-click the output file in the Results folder of the Data Transformation Explorer.

Troubleshooting the IntelliScriptIf you need to edit or troubleshoot the IntelliScript, here are some tips that can help you understand its configuration.

Troubleshooting Graphically1. Open the parser in an IntelliScript editor.

2. Display an example source document in the example pane of the IntelliScript editor, and click IntelliScript > Mark Example.

3. Right-click one of the highlighted anchors, and click View Instance.

Data Transformation Studio highlights the portion of the IntelliScript that defines the anchor.

4. Right-click one of the anchors in the IntelliScript, and click View Marking.

Data Transformation Studio highlights the anchor in the test document.

Troubleshooting With the Event LogTo troubleshoot a parser or a serializer by examining the event log:

1. Open the parser or serializer in an IntelliScript editor.

2. Run the parser or serializer on a source document.

3. In the Events view, expand the Execution node of the event log.

4. Double-click one of the events, for example, a Marker event. 5. Data Transformation Studio highlights the anchor or component that caused the event, in both the

IntelliScript pane and the example pane.

Editing Library ComponentsNote: This section describes generic editing methods applicable to all libraries. For some libraries, you can use the Library Customization Tool to edit the library components. The tool is much more convenient than the editing methods described here. For more information, see Chapter 4, Library Customization Tool on page 75.

After you import a library component, you can use it without modification, or you can edit it to meet your requirements. Editing the copy of a component that you import to a project has no effect on the original library component.

The following paragraphs describe some examples of editing operations that you can perform.

Configuring Optional or Mandatory Message FieldsA messaging standard might define a particular field as optional. In your applications, the field might be mandatory.

Working with Library Projects 9

You can change the designation of the corresponding anchor from optional to mandatory. If the anchor is mandatory and an input lacks the anchor, Data Transformation reports a failure. This does not necessarily stop the transformation of the rest of input. For more information about failure handling, see the Data Transformation Studio User Guide.

Conversely, a standard might consider a field to be mandatory, but your applications might treat it as optional. In the library components, you can change the corresponding anchor from mandatory to optional. If an input lacks the anchor, Data Transformation does not report a failure.

1. Open the library component in the script panel of the IntelliScript editor.

2. Identify the anchor that corresponds to the message field.

3. Click the >> icon next to the anchor name to display its advanced properties.

4. Select or clear the optional property of the component.

Adding a SegmentSome messaging standards, such as HL7 or EDI, group data fields into units such as segments. You can modify a library component to support a custom segment.

One way to do this is to identify a portion of the IntelliScript that processes a similar segment. Copy and paste the IntelliScript components, and edit them as required. You might need to add a secondary parser and serializer to process the new segment. If necessary, edit the XML schema to support the new segment definition.

Using a Proprietary XML SchemaYou might need to transform an industry-standard message to a proprietary XML schema that differs from the library schema. To do this, use a library parser to transform the message to the library schema. Then, configure a mapper that transforms the XML to the proprietary schema. For more information about mappers, see the Data Transformation Studio User Guide.

Documenting CustomizationsDocument the editing operations that you perform on library components. The documentation can be very helpful if you later update the library component and need to reproduce the customizations.

Deploying a Project as a ServiceWhen you finish testing, you can deploy the project as a Data Transformation service that runs in Data Transformation Engine.

For more information about deploying services, see the Data Transformation Studio User Guide. For more information about running services, see the Data Transformation Engine Developer Guide.

10 Chapter 2: Using Libraries

C H A P T E R 3

Descriptions of the LibrariesThis chapter includes the following topics:

ACORD AL3 Library, 12

ACORD-MDM Mappers Library, 13

ASN.1 Library, 15

BAI Library, 20

Bloomberg Library, 22

COBOL Processing Library, 26

CREST Library, 29

DTCC-NSCC Library, 30

EDIFACT Library, 32

EDI-X12 Library, 34

EDI Libraries Based on X12, 38

FIX Library, 39

FpML Library, 40

HIPAA Library, 40

HIX Library, 54

HL7 Library, 56

IATA PADIS Library, 57

IDC-IDSI Library, 58

MDM JavaBeans Library, 60

NACHA Library, 63

NCPDP Library, 64

SEPA Library, 65

SWIFT Library, 65

11

Telekurs VDF Library, 71

Thomson Reuters Library, 72

ACORD AL3 LibraryThe ACORD AL3 library implements the AL3 messaging standard used in the insurance industry. AL3 is maintained by the Association for Cooperative Operations Research and Development (ACORD), a nonprofit insurance association. AL3 messages handle the transmission of insurance information such as policies and claims. For more information, see http://www.acord.org/standards/al3.aspx.

Data Transformation Studio displays the name of the ACORD AL3 library as ACORD.

The ACORD AL3 library transformations do not validate their input. If the input is invalid, the transformations might fail or they might generate unexpected output.

ACORD AL3 Message StructureACORD has a positional format. It uses question marks as placeholders for missing data.

The following sample is an excerpt of an ACORD message that deals with watercraft insurance:

1MHG176 IBM716ESTEDL ??????????????????231225 AFW50270000010406111100051 70 2004061111000512TRG212 70 3P PBOAT FMG0001040611 040511 PCH20040611200405112TCG1352TAG212 00003278 P06260822WTRP PRODUCER2ACI200 Stephen F. Newman, Inc.1600 Delaware Avenue, Suite 999 Seneca NY14999168371685633875BIS172 B10001 P Ester W. Powell??????????????????????????????00003278??????????????????????9BIS168 B10001 3672 Almond driveHopatka NY14888 71660901665ISI183 B200015BISB10001 ?? ?????????? ????????????????5SNG117 B200015BISB10001 01DECJane W. Fieldstone??1???????????????????5BPI285 F100015BISB10001 P06260822 ??????????FISH 040511050511

XML of an ACORD AL3 MessageThe ACORD AL3 library processes XML structures such as the following example:

1MHG176 IBM716ESTEDL ?????????????? 231225 AFW 5027 000001 0406111100051 70

12 Chapter 3: Descriptions of the Libraries

http://www.acord.org/standards/al3.aspx

200406111100051

ACORD-MDM Mappers LibraryThe ACORD-MDM Mappers library contains mappers that translate MDM JavaBeans output XML files to ACORD LNA XML files and back to output MDM JavaBeans XML files.

Before you run the mappers, you use Data Transformation Studio to transform the MDM JavaBeans XML file to the output XML file. For more information about the MDM JavaBeans library, see MDM JavaBeans Library on page 60.

You can use the Developer tool or Data Transformation Studio to import and run the mappers. If you use the Developer tool, you import and run the mappers as XMap objects. If you use Data Transformation Studio, you cannot modify the XMap scripts for the mappers.

The following table describes the files in the XMap directory of the ACORD-MDM Mappers library:

File Name Description

ACORD_LNA_to_MDM_.xml Mapper that translates from an ACORD LNA file to an output MDM JavaBeans XML file with the Developer tool.

MDM_to_ACORD_LNA_.xml Mapper that translates from an output MDM JavaBeans XML file to an ACORD LNA file with the Developer tool.

The following table describes the folders in the ACORD MDM Mappings directory of the ACORD-MDM Mappers library:

Folder Name Description

ACORD_LNA_to_MDM Folder with mapper files that translate from an ACORD LNA file to an output MDM JavaBeans XML file with Data Transformation Studio. You cannot modify the mapper scripts after you import the files.

MDM_to_ACORD_LNA Folder with mapper that translate from an output MDM JavaBeans XML file to an ACORD LNA file with Data Transformation Studio. You cannot modify the mapper scripts after you import the files.

Output MDM JavaBeans File XML StructureThe ACORD-MDM Mappers library translates to and from output MDM JavaBeans XML files. The MDM JavaBeans library generates the output XML file with the following name: input.xml

The following example shows the XML structure of an output MDM JavaBeans XML file:

Policy Z9876543210

ACORD-MDM Mappers Library 13

123456 01231212121234567890 Values Inquiry

ACORD LNA file XML StructureThe ACORD-MDM Mappers library translates to and from ACORD LNA files.

The following example shows the XML structure of an ACORD LNA file:

01231212121234567890 Values Inquiry http://www.acord.org/schema/ws-porttypes/PnP/1/FundArrangementValuesInquiry 1.0 2007-03-29 10:49:01 Policy Z9876543210 123456 12345

Creating an ACORD-MDM Mapper Project in the Developer ToolImport the mappers to the Developer tool to create a Data Processor transformation with XMap objects.

Before you translate from an output MDM JavaBeans XML file to an ACORD LNA file, use the MDM JavaBeans library to generate the output XML file from an MDM JavaBeans file.

Note: If you do not need to modify the XMap scripts after you import the mappers, you can import the mappers to Data Transformation Studio. Import the mappers in the same way that you import the other libraries.

1. In the Developer tool, click File > Import.

The Import wizard opens to the Select screen.

2. Select Informatica > Import Object Metadata File (Advanced) and click Next.

The Import File screen appears.

3. Click Browse and select the mapper XML file that you want to import.

The Select Objects to Import screen appears.

4. In the Source pane, select the XMap and the schemas for the mapper and click Add to Target.

14 Chapter 3: Descriptions of the Libraries

5. Click Next.

The Summary screen appears.

6. Click Finish.

The Developer tool imports the mapper and creates a Data Processor transformation with XMap objects.

For more information about XMap and the Developer tool, see the Informatica Developer User Guide.

ASN.1 LibraryThe ASN.1 library enables you to process data that complies with the Abstract Syntax Notation One (ASN.1) standard.

The ASN.1 standard, maintained by the ISO and ITU-T organizations, is widely used in the telecommunication industry. The standard provides a protocol specification syntax that enables the representation of any data in compact structures. The standard allows the data to be encoded in several binary or text formats. For more information about the standard, see http://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One.

The library provides a Data Transformation service that parses ASN.1 protocol specifications. The input of the service is a protocol specification (*.asn) file. The output is a Data Transformation project that contains the following features:

An XML schema used to represent the ASN.1 data.

A parser, serializer, and mapper that contain an AsnToXml document processor. The processor input is encoded data conforming to the protocol specification. The output is an XML representation of the same data.

The installation and configuration procedures for the ASN.1 library differ from those of other Data Transformation libraries. The ASN.1 library does not provide a set of predefined transformations for specific message types. Rather, it provides tools that create the transformations on demand. By using these tools, you can configure transformations that process any ASN.1 source data.

The current ASN.1 library release enables processing input in the ASN.1 BER encoding. For information about processing other ASN.1 encodings, contact Informatica.

The ASN.1 library transformations do not validate their input. If the input is invalid, the transformations might fail or they might generate unexpected output.

The library includes a copy of the OSS Nokalva ASN-1Step utility that you can use to edit ASN.1 files.

You can access the ASN.1 library services through the C/C++ API or the .NET API.

ASN.1 Protocol SpecificationAn ASN.1 protocol specification is a schema for an ASN.1 data structure. The specification is a text file that typically has an *.asn extension.

The following lines are excerpts from a protocol specification, illustrating the definition of a nested data structure:

MobileTerminatedCall ::= [APPLICATION 10] SEQUENCE{ basicCallInformation MtBasicCallInformation OPTIONAL, locationInformation LocationInformation OPTIONAL, equipmentInformation EquipmentInformation OPTIONAL,

ASN.1 Library 15

http://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One

basicServiceUsedList BasicServiceUsedList OPTIONAL, supplServiceUsedList SupplServiceUsedList OPTIONAL, camelServiceUsed CamelServiceUsed OPTIONAL, valueAddedServiceUsedList ValueAddedServiceUsedList OPTIONAL, dualServiceRequested DualServiceCode OPTIONAL, operatorSpecInformation OperatorSpecInfoList OPTIONAL}

...

ChargeableSubscriber ::= CHOICE { simChargeableSubscriber SimChargeableSubscriber, minChargeableSubscriber MinChargeableSubscriber}

...

SimChargeableSubscriber ::= [APPLICATION 199] SEQUENCE{ imsi Imsi OPTIONAL, msisdn Msisdn OPTIONAL}

The entire structure is called a protocol data unit (PDU). A single protocol specification can define multiple PDUs, in other words, multiple kinds of data structures having different top-level elements.

ASN.1 Message StructureAn ASN.1 source can contain any number of messages. Each message is a data structure that conforms to the protocol specification. The source can contain separator strings between the messages, and there can be a header string before the first message.

The data is typically encoded in a binary format. The following figure illustrates data in the BER encoding. The data is not human-readable.

XML Version of an ASN.1 MessageThe AsnToXml document processor converts the data to the ASN.1 XER encoding, which is an XML representation. The following figure illustrates the XML that corresponds to the protocol specification described above.

16 Chapter 3: Descriptions of the Libraries

45404200 85290469

Installing the ASN.1 LibraryTo create transformations that process ASN.1 data, install the library on the development environment. To run the transformations as services, install the library on the production environment.

1. For each development environment, perform the following actions:

a. Run the hostinf utility. The following message appears:

HOST = "/"b. Copy the line that contains the host name and code.

2. Send an email to Informatica Global Customer Support. Include the following information:

The type of machine for each production environment

The host name and code for each development environment

Informatica Global Customer Support sends you the ossinfo license files.3. The step you take to install the ASN.1 Library depends on the environment:

Environment Actions

Development 1. Close Data Transformation Studio.2. Copy the installation file to the Data Transformation installation directory, and then unzip it.

Production 1. Copy the installation file to the Data Transformation installation directory.2. On a Windows machine, unzip the installation file. On a Linux or UNIX machine, untar the

installation file.

4. For each machine, save the associated ossinfo license file in the Data Transformation installation directory.

For example, if you installed Data Transformation in the default location on a Windows platform, save the ossinfo file in the following directory:

c:\Informatica\9.5.0\DataTransformation

UninstallingOn a Windows platform, uninstall the ASN.1 library before you uninstall Data Transformation. On a UNIX-type platform, the order of uninstallation is not important.

If you uninstall Data Transformation before the ASN.1 library on Windows, the uninstallation does not completely remove the library. To complete the removal:

1. Restart Windows.

2. In the Windows Explorer, delete the Data Transformation installation directory.

3. Delete the following directory: C:\Program Files\Common Files\InstallShield\Universal\common\Gen1

ASN.1 Library 17

UpgradingBefore you install a new version of the ASN.1 library, you must uninstall the previous version.

Creating an ASN.1 Library ProjectTo configure an ASN.1 transformation, you must create a Data Transformation import project. The import wizard prompts you to select a *.asn protocol specification.

The result of the import is a Data Transformation project containing the following components:

_schema.xsd

An XML schema that is equivalent to the protocol specification.

_parser.tgp

A parser that operates on the ASN.1 data. The parser is configured with an AsnToXml document processor that converts the input to XML. You can edit the IntelliScript and insert components that parse the XML.

_serializer.tgp

A serializer that operates on the ASN.1 data. The serializer is configured with an AsnToXml document processor that converts the input to XML. You can edit the IntelliScript and insert components that serialize the XML.

_mapper.tgp

A mapper that operates on the ASN.1 data. The mapper is configured with an AsnToXml document processor that converts the input to XML. You can edit the IntelliScript and insert components that map the XML.

_x_common.tgp

The library uses this file internally when it generates the project. Optionally, you can delete the file.

To create the project:

1. In Data Transformation Studio, click File > New > Project.

The New Project wizard appears.

2. Under the Data Transformation category, select an Import Project, and then click Next.

3. Enter a name and storage location for the project.

The default location is the Studio workspace.

4. On the Select Import Type page, select an ASN.1 Project.

5. Browse to the file containing the protocol specification.

Typically, the file has an *.asn extension. The Studio copies the file into the project directory.6. Click Finish.

The project appears in the Data Transformation Explorer view.

7. Double click the parser, serializer, or mapper file to open it in the script panel of the IntelliScript editor.

The transformation contains only the AsnToXml document processor. It does not contain an example source, anchors, or actions.

8. Configure the properties of the AsnToXml processor as required.

The properties are described in the following section.

9. Add an example source to the project.

18 Chapter 3: Descriptions of the Libraries

The example source must contain one or more messages that conform to the protocol specification. In the current release, the example must be in the BER encoding (a *.ber file).

10. Display the example source.

It appears as an XML representation of the input data.

11. Under the contains line, add components such as anchors and actions that process the XML and generate output.

12. Test the transformation, and deploy it as a Data Transformation service.

ASN-1Step UtilityAs a utility for editing and validating ASN.1 files, the library includes a copy of the ASN-1Step development environment. You can install ASN-1Step on a Windows computer. You can use ASN-1Step to edit ASN.1 protocol specifications and source data.

1. Run the ASN.1Step setup file.

It has a name such as asnstep_winVVV.exe, where VVV is a version number.2. At the prompt, select the option to Specify Location of ossinfo Manually.

3. Browse to the Data Transformation installation directory where you stored the ossinfo license file. 4. Follow the on-screen instructions to complete the installation.

For more information about using ASN-1Step, see the online help included in the utility.

AsnToXml Document ProcessorNote: This processor is available if you install the Data Transformation ASN.1 library. You can use the processor only in an ASN.1 library project.

The AsnToXml document processor converts ASN.1 data to XML.

In the current release, the processor input must have the BER encoding, defined in the ASN.1 standard. The output XML is identical to the ASN.1 XER encoding.

The following table describes the properties of the AsnToXml document processor:

Property Description

asn_file Defines an ASN.1 specification file.

header Defines a header to exclude from the XML. The header property has the following options:- NewlineSearch. The header is a newline.- OffsetSearch. The header is defined by the number of characters from the beginning of

the file.- PatternSearch. The header is defined by a regular expression.- TextSearch. The header is defined by an explicit string or a string that you retrieve

dynamically from the source document.

no_constraints Determines whether the ASN file is processed with constraints. The no_constraints property has the following options:- true. The ASN file is processed without constraints.- false. The ASN file is processed with constraints.Default is false.

ASN.1 Library 19

Property Description

pdu_type Defines the PDU type. Use this property to clarify an ambiguity.

process_first_message Determines whether the entire CDR file is processed. The process_first_message property has the following options:- true. Only the first record is processed.- false. The entire CDR file is processed.Default is false.

separator Defines text to ignore between records. The separator property has the following options:- NewlineSearch. The separator is a newline.- OffsetSearch. The separator is defined by the number of characters from the end of the

previous record.- PatternSearch. The separator is defined by a regular expression.- TextSearch. The separator is defined by an explicit string or a string that you retrieve

dynamically from the source document.

ExampleIn an ASN.1 BER file, there is a header before the first message and separators between the subsequent messages. The header and the separators are random sequences of hexadecimal 00 and FF bytes, of any length. For example, a header or separator might have the following form:

00 00 FF 00 FF FF FF 00 FF 00The following configuration enables the AsnToXml processor to find the header and separators. The header and separator properties use regular expressions to define the pattern.

pre_processor = AsnToXml asn_file = SGSN-CDR-def-v2009A.asn header = PatternSearch pattern = "[\x00|\xFF]+" separator = PatternSearch pattern = "[\x00|\xFF]+"

The processor ignores the headers and separators, and it processes the messages between them.

BAI LibraryThe BAI library implements the following specifications developed by the BAI financial service industry organization:

Cash Management Balance Reporting Specifications Version 2 (BAI2)

Lockbox Communications Standards for Banks (BAI Lockbox)

The BAI library transformations do not validate their input. If the input is invalid, the transformations might fail or they might generate unexpected output.

For more information about the specifications, see http://www.bai.org/operations/reportingcodes.asp.

20 Chapter 3: Descriptions of the Libraries

http://www.bai.org/operations/reportingcodes.asp

BAI2 Message StructureBAI2 messages have a record format. Each record ends with a line break and contains comma-delimited fields.

The first two digits of each record indicate the record type. In the following excerpt, the 01 record is a file header, containing information such as the sender and receiver IDs. The 02 records label account groups. The other records contain the data for specific bank transactions. The 88 records are continuation lines.

01,122099999,123456789,040621,0200,1,65,,2/02,031001234,122099999,1,040620,2359,,2/03,0123456789,,010,+4350000,,,040,2830000,,/88,072,1020000,,,074,500000,,/16,115,450000,S,100000,200000,150000,,,/16,115,10000000,S,5000000,4000000,1000000/88,AX13612,B096132,AMALGAMATED CORP. LOCKBOX88,DEPOSIT-MISC. RECEIVABLES49,9150000,4/03,9876543210,,010,-500000,,,100,1000000,,,400,2000000,,,190/88,500000,,,110,1000000,,,072,500000,,,074,500000,,,040/88,-1500000,,/16,115,500000,S,,200000,300000,,,LOCK BOX NO.6875149,4000000,5/98,13150000,2,11/02,053003456,122099999,1,040620,2359,,2/03,4589761203,,010,10000000,,,040,5000000,,,074,4000000,,/...

XML Version of a BAI2 MessageThe BAI library processes XML representations of BAI2 messages such as the following example:

/ , 072000096 072000096 060322 0433 1 80 2 000000000 072000096 1 060321 0433 2 1000000001 015 +0000016668216 040 +0000016668216

BAI Library 21

BAI Lockbox Message StructureBAI Lockbox messages have a positional structure. The following excerpt is an example:

100412109254801210002480611210505 241210925480121000248000000000040008000801 5001001020174506112141210925480121000248 60010010000377969111000614634566970 071324 MAYDAY 4001001601034145204 0000016750 4001001602034145409 0000009500

XML of a BAI Lockbox MessageThe BAI library processes XML representations of BAI Lockbox messages such as the following example:

00 4121092548 0121000248 061121 0505 4121092548 0121000248 0000000000 400 80 0080 1 001 001 0201745 061121 4121092548 0121000248 1 1 377969 11100061

Bloomberg LibraryThe Bloomberg library validates Bloomberg response messages and converts them to XML.

The Bloomberg library performs the following types of validation:

Field datatype and width

Business rules defined by Informatica

Codes defined by Thomson Reuters

The Bloomberg field type definitions change on a daily basis. The Data Transformation Bloomberg library can create a service from a sample request or response message. The service contains a parser for small input files and a streamer for large input files.

22 Chapter 3: Descriptions of the Libraries

The following table describes the files that the service produces:

File Description

output.xml Contains all of the data in the original Bloomberg request or response.

errors.xml Contains a detailed description of errors in the input.

errorsFound.txt Boolean flag that indicates whether the service detected errors in the input.

Note: When you use a streamer to process large files, some comments do not appear in the output.

Bloomberg Message StructureA Bloomberg message is made up of a header section, a field-definition section, and a data section. The header section and the field-definition section are optional.

The following example of a Bloomberg message shows a header section, a field-definition section, and a data section:

START-OF-FILERUNDATE=20110911PROGRAMNAME=getdataREPLYFILENAME=DLMRT_comma_bulklist.outFIRMNAME=dl927PROGRAMFLAG=oneshotCOLUMNHEADER=yesSECMASTER=yesCREDITRISK=yesDELIMITER=,OUTPUTFORMAT=bulklist

START-OF-FIELDSCALL_SCHEDULEEND-OF-FIELDS

TIMESTARTED=Sun Sep 11 10:44:19 EDT 2011START-OF-DATAUS4581401001 US|10|1| |US4581401001 US Equity|0|1| |431022KW1 Equity|10|1| |431022KW1 Corp |10/02/2009|100.0000431022KW1 Govt |10/02/2009|100.0000US694032BD48 Muni |11/01/2007|103.203500END-OF-DATATIMEFINISHED=Sun Sep 11 10:44:22 EDT 2011END-OF-FILE

XML Version of a Bloomberg MessageThe following example shows the XML version of a Bloomberg message:

20110911 getdata

Bloomberg Library 23

DLMRT_comma_bulklist.out dl927 oneshot yes yes yes , bulklist 10/02/2009 100.0000 10/02/2009 100.0000 11/01/2007 103.203500

Field Definition FilesThe fields in Bloomberg responses are defined in files. You can get the most up-to-date files from the Bloomberg FTP site.

24 Chapter 3: Descriptions of the Libraries

The following table describes the field definition files:

File Description

lookup.out Defines valid values for fields and the structure of bulk format fields.

fields.csv Defines fields for Per Security, Back Office, and Extended Back Office.

crisk_fields.csv Defines fields for the Credit Risk Module.

backoffice_fields.xls Defines fields for Back Office.

backoffice_extended_fields.xls Defines fields for Extended Back Office.

Creating a Bloomberg ServiceCreate a Bloomberg service when you install the Bloomberg library, or when the Bloomberg field definition files change.

Before you create a Bloomberg service, you must install the Bloomberg library, and then restart Data Transformation Studio.

1. Click File > New > Project.

The New Project dialog box appears.

2. Select Data Transformation > Import Project, and then click Next.

The Import Data Transformation Project page appears.

3. Enter a name for the project, and then click Next.

The Select Import Type page appears.

4. Select one of the following import types:

Bloomberg Back Office file

Bloomberg Extended Back Office file

Bloomberg Per Security file

5. Click Next.

6. Browse to a Bloomberg request or response file, and then click Finish.

The Bloomberg project appears in the Studio with a parser script and a streamer script.

7. Click Project > Properties.

The Project Properties dialog box appears.

8. Select Disable automatic output, and then click OK.

9. If you want to run a streamer service, open the TGP script for the streamer, and then set the streamer as the startup component.

10. Deploy the project to the repository.

The service is available for use by Data Transformation Engine.

Bloomberg Library 25

COBOL Processing LibraryThe COBOL Processing library transforms COBOL EBCDIC data to and from XML.

When you import a COBOL data definition from a copybook into Data Transformation Studio, the Studio creates a Data Transformation project that contains the following components:

A schema that defines an XML representation of the COBOL data structure.

A parser that transforms input data from the COBOL EBCDIC data definition to XML.

A serializer that transforms XML to COBOL.

You can deploy the parser and serializer as Data Transformation services that process COBOL data, and you can incorporate them into other projects.

Importing a COBOL Data Definition

1. Click File > New > Project.

The New Project wizard appears.

Note: You must use File > New > Project for this purpose. Do not use File > Import, which imports existing Data Transformation or Eclipse projects.

2. Under the Data Transformation node, select Import Project.

3. On the next wizard page, enter a name for the project, and select the storage location.

The default location is the Data Transformation Studio workspace folder.

4. On the next page, browse to the COBOL data definition file, in other words, to a COBOL copybook.

5. Click Finish.

Data Transformation Studio generates a project containing an XSD schema file, a parser, and a serializer for the COBOL data.

Supported COBOL FeaturesThe COBOL import supports data definitions of any complexity. For example, the data definitions can use the packed decimal (COMP-3), binary (COMP-1, COMP-2, or COMP-4), and logical decimal point (99v99) data types. They can contain features such as REDEFINES, O