Introduction to Informatica Power Center - Quontra Solutions

Information about Introduction to Informatica Power Center - Quontra Solutions

Published on September 8, 2014

Author: quontra123



Introduction to Informatica PowerCenter : Introduction to Informatica PowerCenter IT Courses Online Training and Placements: IT Courses Online Training and Placements Quontra Solutions View Larger Map For Free Demo Contact US: 3427 Vintage cir , SE Smyrna, GA-30080 Phone :  (404)-900-9988                 (404)-990-3007 Email: [email protected] Visit Us : Data Warehousing : Data Warehousing Data warehousing is the entire process of data extraction, transformation, and loading of data to the warehouse and the access of the data by end users and applications Data Mart: Data Mart A data mart stores data for a limited number of subject areas, such as marketing and sales data. It is used to support specific applications. An independent data mart is created directly from source systems. A dependent data mart is populated from a data warehouse. Need For ETL Tool: Need For ETL Tool Data Extraction Often performed by COBOL routines (not recommended because of high program maintenance and no automatically generated meta data) Sometimes source data is copied to the target database using the replication capabilities of standard RDBMS (not recommended because of “dirty data” in the source systems) Increasing performed by specialized ETL software Sample ETL Tools: Sample ETL Tools DataStage from Ascential Software SAS System from SAS Institute Informatica Data Integrator From BO Hummingbird Genio Suite from Hummingbird Communications Oracle Express Abinito Decision Stream From Cognos MS-DTS from Microsoft Components Of Informatica: Components Of Informatica Repository Manager Designer Workflow Manager Informatica provides the following integrated components:: Informatica provides the following integrated components: Informatica repository . The Informatica repository is at the center of the Informatica suite. You create a set of metadata tables within the repository database that the Informatica applications and tools access. The Informatica Client and Server access the repository to save and retrieve metadata. Informatica Client . Use the Informatica Client to manage users, define sources and targets, build mappings and mapplets with the transformation logic, and create sessions to run the mapping logic. The Informatica Client has three client applications: Repository Manager, Designer, and Workflow Manager. Informatica Server . The Informatica Server extracts the source data, performs the data transformation, and loads the transformed data into the targets. Architecture: Architecture Process Flow: Process Flow Informatica Server moves the data from source to target based on the workflow and metadata stored in the repository. A workflow is a set of instructions how and when to run the task related to ETL. Informatica server runs workflow according to the conditional links connecting tasks. Session is type of workflow task which describes how to move the data between source and target using a mapping. Mapping is a set of source and target definitions linked by transformation objects that define the rules for data transformation. Sources: Sources Power Mart and Power Center access the following sources: Relational. Oracle, Sybase, Informix, IBM DB2, Microsoft SQL Server, and Teradata. File . Fixed and delimited flat file, COBOL file, and XML. Extended . If you use Power Center, you can purchase additional Power Connect products to access business sources such as PeopleSoft, SAP R/3, Siebel, and IBM MQSeries. Mainframe . If you use Power Center, you can purchase Power Connect for IBM DB2 for faster access to IBM DB2 on MVS. Other . Microsoft Excel and Access . Targets: Targets Power Mart and Power Center can load data into the following targets: Relational . Oracle, Sybase, Sybase IQ, Informix, IBM DB2, Microsoft SQL Server, and Teradata. File . Fixed and delimited flat files and XML. Extended . If you use Power Center, you can purchase an integration server to load data into SAP BW. You can also purchase Power Connect for IBM MQSeries to load data into IBM MQSeries message queues. Other . Microsoft Access . You can load data into targets using ODBC or native drivers, FTP, or external loaders. General Flow of Informatica: General Flow of Informatica Step 1: Creating Repository ,creating folders ,Creating users and assign permission in Repository Manager, so as to work in the client tools . Step 2:Connecting to the repository from the designer. importing source and target tables , creation of mappings . Step 3 : Creation of Workflow through workflow Manager which has different tasks connected between them. In that ,session is the task which is pointing to a mapping created in the designer. Repository: Repository The Informatica repository is a set of tables that stores the metadata you create using the Informatica Client tools. You create a database for the repository, and then use the Repository Manager to create the metadata tables in the database. You add metadata to the repository tables when you perform tasks in the Informatica Client application such as creating users, analyzing sources, developing mappings or mapplets, or creating sessions. The Informatica Server reads metadata created in the Client application when you run a session. The Informatica Server also creates metadata such as start and finish times of a session or session status. Contd :- Repository Contd..: Repository Contd.. When you use Power Center, you can develop global and local repository to share metadata: Global repository . The global repository is the hub of the domain. Use the global repository to store common objects that multiple developers can use through shortcuts. These objects may include operational or application source definitions, reusable transformations, mapplets, and mappings. Local repositories. A local repository is within a domain that is not the global repository. Use local repositories for development. From a local repository, you can create shortcuts to objects in shared folders in the global repository. These objects typically include source definitions, common dimensions and lookups, and enterprise standard transformations. You can also create copies of objects in non-shared folders. Repository Architecture: Repository Architecture Repository Client Repository Server ---------------------------- Repository Agent Repository Database Creating a Repository: Creating a Repository To create Repository 1. Launch the Repository Manager by choosing Programs-Power Center (or Power Mart) Client-Repository Manager from the Start Menu. 2. In the Repository Manager, choose Repository-Create Repository. Note: You must be running the Repository Manager in Administrator mode to see the Create Repository option on the menu. Administrator mode is the default when you install the program. 3. In the Create Repository dialog box, specify the name of the new repository, as well as the parameters needed to connect to the repository database through ODBC. Working with Repository.. : Working with Repository.. By default 2 users will be created in the repository . Database user used to connect to the repository. Administrator User. By default 2 Groups will be created Public Administrators. These groups and users cannot be deleted from the repository . The administrator group has only read privilege for other user groups. Working with Repository contd..: Working with Repository contd.. Informatica tools include two basic types of security: Privileges . Repository-wide security that controls which task or set of tasks a single user or group of users can access. Examples of these are Use Designer, Browse repository , Session operator etc. Permissions . Security assigned to individual folders within the repository. You can perform various tasks for each privilege. Ex :- Read , Write and Execute. Folders: Folders Folders provide a way to organize and store all metadata in the repository, including mappings, schemas, and sessions. Folders are designed to be flexible, to help you organize your data warehouse logically. Each folder has a set of properties you can configure to define how users access the folder. For example, you can create a folder that allows all repository users to see objects within the folder, but not to edit them. Or you can create a folder that allows users to share objects within the folder. Shared Folders When you create a folder, you can configure it as a shared folder. Shared folders allow users to create shortcuts to objects in the folder. If you have reusable transformation that you want to use in several mappings or across multiple folders, you can place the object in a shared folder. For example, you may have a reusable Expression transformation that calculates sales commissions. You can then use the object in other folders by creating a shortcut to the object. Folder Permissions: Folder Permissions Permissions allow repository users to perform tasks within a folder. With folder permissions, you can control user access to the folder, and the tasks you permit them to perform. Folder permissions work closely with repository privileges. Privileges grant access to specific tasks while permissions grant access to specific folders with read, write, and execute qualifiers. However, any user with the Super User privilege can perform all tasks across all folders in the repository. Folders have the following types of permissions: Read permission . Allows you to view the folder as well as objects in the folder. Write permission . Allows you to create or edit objects in the folder. Execute permission . Allows you to execute or schedule a session or batch in the folder. Creating Folders: Creating Folders Other Features of Repository Manager: Other Features of Repository Manager Viewing , removing Locks Adding Repository Backup and Recovery of Repository Taking Metadata reports like Completed Sessions details , List of reports on Jobs , session , workflow etc PowerPoint Presentation: Questions/Comments ? PowerPoint Presentation: Designer Working with Designer: Working with Designer Connecting to the repository using User id and password. Accessing the folder Importing the source and target tables required for mapping. Creation of mapping Tools provided by Designer: Tools provided by Designer Source Analyzer: Importing Source definitions for Flat file, XML, COBOL and relational Sources. Warehouse Designer: Use to Import or create target definitions. Transformation Developer: Used to create reusable transformations Mapplet Designer: Used to create mapplets Mapping Designer: Used to create mappings Importing Sources: Importing Sources Import from Database: Import from Database Use ODBC connection for importing from database Import from File: Import from File Creating Targets: Creating Targets You can create target definitions in the Warehouse Designer for file and relational sources. Create definitions in the following ways: Import the definition for an existing target. Import the target definition from a relational target. Create a target definition based on a source definition . Drag one of the following existing source definitions into the Warehouse Designer to make a target definition: Relational source definition Flat file source definition COBOL source definition Manually create a target definition. Create and design a target definition in the Warehouse Designer . Creating targets: Creating targets Creation of simple mapping: Creation of simple mapping Creation of simple mapping: Creation of simple mapping Switch to the Mapping Designer. Choose Mappings-Create. While the workspace may appear blank, in fact it contains a new mapping without any sources, targets, or transformations. In the Mapping Name dialog box, enter <Mapping Name> as the name of the new mapping and click OK. The naming convention for mappings is m_ MappingName . In the Navigator, under the <Repository Name> repository and <Folder Name> folder, click the Sources node to view source definitions added to the repository . Contd.. Mapping creation Contd.. : Mapping creation Contd.. Click the icon representing the EMPLOYEES source and drag it into the workbook. Mapping creation Contd..: Mapping creation Contd.. The source definition appears in the workspace. The Designer automatically connects a Source Qualifier transformation to the source definition. After you add the target definition, you connect the Source Qualifier to the target. Click the Targets icon in the Navigator to open the list of all target definitions. Click and drag the icon for the T_EMPLOYEES target into the workspace. The target definition appears. The final step is connecting the Source Qualifier to this target definition. Mapping creation Contd..: Mapping creation Contd.. To Connect the Source Qualifier to Target Definition: Click once in the middle of the <Column Name> in the Source Qualifier. Hold down the mouse button, and drag the cursor to the <Column Name> in the target. Then release the mouse button. An arrow (called a connector) now appears between the row columns PowerPoint Presentation: Thank you

Related presentations

Other presentations created by quontra123