Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Identity Resolution 10.5 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Defining a System
  4. Flattening IDTs
  5. Link Tables
  6. Loading a System
  7. Static Clustering
  8. Simple Search
  9. Search Performance
  10. Miscellaneous Issues
  11. Limitations
  12. Error Messages

Design Guide

Design Guide

Back Next

Flat File Input from a Named Pipe

Flat File Input from a Named Pipe

The IIR Table Loader can read input data from a named pipe. Relate cannot read Win32 pipes at this stage.

UNIX Platforms

On UNIX platforms the IIR input processor can read input from a Named Pipe. This means that it is possible to read data from another database without the need to create large intermediate files.
The concept is identical on all UNIX platforms, although the command used to create a named pipe may vary between implementations. The following example in applicable to LINUX.
mkfifo $SSAWORKDIR/inpipe
To use the pipe, specify its name as the Physical-File parameter in the Logical-File-Definition of the input file: 

logical-file-definition
*======================
NAME= 												lf-input
PHYSICAL-FILE= 									"+/inpipe"
COMMENT= 											"named pipe for the loader"
VIEW= 												DATAIN
INPUT-FORMAT= 										TEXT
AUTO-ID-NAME= 										Job1

Windows Platforms

To use a named pipe on Windows environments, you need to specify the name of the pipe in the Microsoft format:
\\server\pipe\pipe_name
where
  • server
     is the server name or dot (.) for the current machine
  • pipe
     the word "pipe"
  • pipe_name
     the pathname of the named pipe file
To use the pipe, specify its name as the
Physical-File
parameter in the Logical-File-Definition of the input file: 

logical-file-definition
*======================
NAME= 												lf-input
COMMENT= 											"input file"
PHYSICAL-FILE= 									"\\.\pipe\pipe_name"
VIEW= 												DATAIN
FORMAT= 												TEXT
AUTO-ID-NAME= 										JobN

logical-file-definition
*======================
NAME= 												lf-input
COMMENT= 											"input file"
PHYSICAL-FILE= 									"\\.\pipe\pipe_name"
VIEW= 												DATAIN
FORMAT= 												TEXT
AUTO-ID-NAME= 										JobN
0 COMMENTS
We’d like to hear from you!