Preliminary Steps

Before you begin the ETL process using flat files as your source, you must:

Configuring Informatica

  1. Create a database connection for source/target.
    • Create one target for all Connect tables and one source per database source.
    • Specify data source.
    • Choose Code Page “ISO Western European” for UNIX servers and “MS Windows Latin 1” for Windows NT servers.
  2. Configure the Informatica server. Under Server Configuration, Edit Server, Advanced. Under Server Variables, set attribute value for $PMRootDir.

Creating a Session

  1. Create File Wait. (Choose General, Advanced Options, and under Event Based Scheduling, specify the Indicator File to Wait For. Note that system variables such as $PMSourceFileDir will not work here.)
  2. Create a file list.
  3. Create the Post Session Command. (Choose General, Post-Session + Email, and under Command, specify the next command to run.) For example:
                                pmcmd start Administrator koladmin informatica2
                                Designs_CustAttributes_StgToTrg 0 0 usage:pmcmd start {user_name,
                                %user_env_var} {password, %password_env_var} [hostname:]portno
                                [folder_name:]{session_name, batch_name} session_flag wait_flag
                            
  4. Schedule the session. (Select the Time tab. Under Schedule, specify that the session should run every 1 minute. Under Duration, specify the session should run forever.)
  5. Specify paths for log files. (Click the Log Files tab. Specify/Verify Server Path to Log File and Reject File using customer name based on the server variables.)

Performing a Unit Test from the Staging Host through Informatica

  1. Create a UDE, based on the specified format for the KANA Connect data type (such as Customer Master, Attributes, or Subscriptions). This example shows a Customer Attributes UDE (at_gender.dat).
  2. Create a file list. The files will be processed sequentially. This example shows a file list to process two files (at_gender.dat and at_beta.dat).
  3. Create an indicator file. This file is deleted immediately after Informatica reads it.
  4. Use SecureFX (or another SSH2 compliant file transfer tool) to transfer the UDEs, file lists and indicator files into the Staging Host Directory specified in the Informatica mapping. Note that you must move indicator files last, because the presence of the indicator files tells Informatica it can run the sessions.