COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Framework Manager => Topic started by: Chai17 on 18 Sep 2013 10:18:33 AM

Title: Importing data from Informatica to Cognos FM Model
Post by: Chai17 on 18 Sep 2013 10:18:33 AM
Hey Gurus,

We are currently using Informatica for our ETL and may have to create a model based on Informatica. If any of you have been there before, can someone please guide me in:

1. What information do I need before hand?
2. What are the steps involved?
3. What are possible challenges that maybe I should be aware of?

I remember I saw a blog post once about  brining Informatica data into Cognos FM. But, I am simply unable to find it right now.

Thanks for your help in advance,
Chai
Title: Re: Importing data from Informatica to Cognos FM Model
Post by: blom0344 on 19 Sep 2013 04:52:49 AM
Informatica supplies the ETL engine, the mappings and scheduling. The actual model may be deduced by importing tables using RI or by using a specialized modelling tool (like ERWin / Powerdesigner) Perhaps you are confusing  Powerdesigner (Sybase) with Powercenter (Informatica)  ?
Title: Re: Importing data from Informatica to Cognos FM Model
Post by: Chai17 on 19 Sep 2013 01:03:36 PM
Hey Guru,

Thanks for your response.

The feature I am referring to as attached in the document. Can you please guide me with my queries if you know any information?

Thanks a lot in advance,

Best,
Chai
Title: Re: Importing data from Informatica to Cognos FM Model
Post by: bdbits on 19 Sep 2013 04:05:21 PM
Even though it looks like you can, I am not sure what you will gain by using Informatica metadata over importing the design from the target database. I guess you could try it, and if it does not work well, take the more traditional approach directly from the database itself.
Title: Re: Importing data from Informatica to Cognos FM Model
Post by: blom0344 on 20 Sep 2013 02:35:33 AM
I agree with bdbits.  Importing the defined INFA targets may be technically possible, but it will not yield anything more then the actual tables from the database. Importing other ETL components would make little sense..