Setting up MySQL Database Connections in Informatica Cloud

The following video walks you through creating a connection to a MySQL database in Informatica Cloud.

Read more

Setting up DB2 Database Connections in Informatica Cloud

The following video walks you through creating a connection to a DB2 database in Informatica Cloud.

Read more

Setting up Microsoft Access Database Connections in Informatica Cloud

The following video walks you through creating a connection to a Microsoft Access database in Informatica Cloud.

Read more

Setting up Oracle Database Connections in Informatica Cloud

The following video walks you through creating a connection to an Oracle database in Informatica Cloud.

Read more

Setting up Microsoft SQL Server 2008 Database Connections in Informatica Cloud

The following video walks you through creating a connection to a SQL Server 2008 database in Informatica Cloud.

Read more

Setting up Microsoft SQL Serve Database Connections in Informatica Cloud

The following video walks you through creating a connection to Microsoft SQL Server in Informatica Cloud.

Read more

Creating Connections (Endpoints)

Setting Up a Salesforce (Sandbox or Production) Connection

You can create a separate connection in Informatica Cloud for each of your Salesforce environments - including any Sandbox or Production environments. When you create the connection, be sure to enter the correct login credentials for the environment.

Also, if accessing a sandbox, be sure to change the Service URL to match the URL you use to access your sandbox (generally, this is "test.salesforce.com"):

You can choose to enter a security token, or you can leave this field blank and add the Informatica Cloud servers and agent machine(s) to the list of trusted IP addresses in Salesforce. For more information on this, view the following document: Salesforce.com Integration: Using a Security Token or Configuring Trusted IP Address Ranges.

Note that when you click the Test button, above, the call is made from the Informatica Cloud servers. When you run a task that uses a Salesforce connection, the call is made from the agent machine.

Troubleshooting a Sandbox Connection
In some cases, for a sandbox connection, you may need to add the Salesforce server name to the Service URL. If the connection fails when you click the Test button, log into your Salesforce sandbox org (as you normally would) and look at your browser's URL field. Copy the server name - "cs3.salesforce.com", for example, and insert it (replacing "www.salesforce.com" or "test.salesforce.com") into the Service URL. Your service URL should look something like this: https://cs3.salesforce.com/services/Soap/u/19.0.


Various Database Connections in Informatica Cloud

Below are  various database connection types in Informatica Cloud.

1.Microsoft SQL Server

2.Microsoft SQL Server 2008

3.Oracle 

4.Microsoft Access

5.DB2

6.MySQL     


Read more

Data Quality Assessment Service Overview

Read more

Data Replication Service Overview

Read more

Getting Started Tutorial

Read more

Informatica 9 Developers Guide



Here you go with Informatica 9 Designers Guide.

Read more

Informatica Data Loader

 
Overview on Informatica Data Loader. You may get some valuable information.

For slide show click on below link:
http://tinyurl.com/cwf9cp











 

Read more

Informatica World 2010 Opening Video

Choose the Best ETL tool for your Org

Read more

Informatica 9 Opening Video

Read more

Informatica Metadata Queries

In Informatica normally we come across situation like we need to find all mapping which use a particular table as source or something similar .It is very difficult to find it through Informatica tools.In such a situation Repository tables are very useful.

Repository tables name start with OPB and are continuously updated when we make changes.Along with OPB tables REP views are also present.
It is very dangerous to modify these tables so due care should be taken while dealing with OPB Tables.

In this article we will focus on some useful meta data queries

Purpose : Search for a table in Source Qualifiers Sql Override:
Query : 
select distinct SUB.subj_name, MAP.mapping_name
from  opb_widget_attr WID,  opb_mapping MAP,  opb_widget_inst WIDINST,
 opb_subject SUB
where WID.widget_id = WIDINST.widget_id
and WID.widget_type = WIDINST.widget_type
and WID.widget_type = 3
and WID.attr_id = 1
and WIDINST.mapping_id = MAP.mapping_id
and MAP.subject_id = SUB.subj_id
and upper(WID.attr_value) like '%TNAME%' ;

Description : This query will give list of all mappings where a particular table is being used in sql override.

Purpose : Search for a table in Sources and Targets :
Query : 
select SUB.subj_name, decode(WIDG.widget_type,1,'Source',2,'Target'),
MAP.mapping_name,
WIDG.instance_name
from  opb_widget_inst WIDG,  opb_mapping MAP, opb_subject SUB
where SUB.subj_id = MAP.subject_id
and WIDG.mapping_id = MAP.mapping_id
and WIDG.widget_type in (1,2)
and WIDG.instance_name like '%TNAME_%'
and SUB.subJ_NAME='YOUR_FOLDER_NAME'

Description : This query will give list of all folders,mappings where a particular table is being used as source or target instance.

Purpose : Query to give lookup information
Query :
Select distinct wid.WIDGET_ID, all_map.mapping_name, wid.INSTANCE_NAME Lkp_name, Decode(widat.attr_id,2,widat.attr_value) Table_name,
decode (widat.attr_id,6,widat.attr_value) src_tgt
FROM  rep_all_mappings ALL_MAP, rep_widget_inst wid,  OPB_WIDGET_ATTR widat
where all_map.mapping_id=wid.mapping_id
and wid.WIDGET_ID=widat.WIDGET_ID
and all_map.subject_area='DCM_SPP_UPL_DEVT'
and wid.WIDGET_TYPE=11
and widat.WIDGET_TYPE=11
and widat.ATTR_ID in (2,6)

Description : This query will give information about lookup transformations like lookup name,Tablename ,Mapping name etc. 

Purpose : Query to give Invalid workflows
Query :
select opb_subject.subj_name, opb_task.task_name
from  opb_task,   opb_subject
where task_type = 71 
and is_valid = 0 
and opb_subject.subj_id = opb_task.subject_id
and UPPER(opb_subject.SUBJ_NAME) like UPPER('YOUR_FOLDER_NAME')

Description : This query will list of all invalid workflows

Read more