complete reference to informatica_ informatica power center testing
Post on 02-Jan-2016
40 Views
Preview:
TRANSCRIPT
1/21/13 Complete reference to Informatica: Informatica Power Center Testing
informaticatutorials-naveen.blogspot.in/2011/04/informatica-power-center-testing.html#axzz2IbCIeQAT 1/2
Home Informatica Data WareHousing Unix-Shell Scripts PL SQL Contact Us
Complete reference to Informatica
Sharing
Discussion Forum
Discussion Forum
Introduction
ETL Life Cycle
What Is Informatica
Client Components
Services Behind Scene
Try U R Hand's on
Admin-Console
Difference Between 7.1
and 8.6
Informatica 8.6
Installation
Interview Zone
Informatica Real Time
Interview Questions
Informatica Experienced
Interview Questions -
part1
Informatica Experienced
Interview Questions -
part2
Informatica Experienced
Interview Questions -
part3
Informatica Experienced
Interview Questions -
part4
Data Warehousing
concept Based Interview
Questions
Transformation
Filter
Expression
Router
Sorter
Rank
Transaction Control
Source Qualifier
Stored Procedure
SQL Transformation
Normalizer
Sequence Generator
Aggregator
Union
Joiner
Update Strategy
Look Up
Subscribe toLearn Informatica
Like 203 people like this.
Sign Up to see w hat
your friends like.
Enter your emailaddress:
Subscribe
Delivered by FeedBurner
Informatica Power Center TestingNaveen
17Apr 2011
Debugger: Very useful tool for debugging a valid mapping to gain
troubleshooting information about data and error conditions. Refer
Informatica documentation to know more about debugger tool.
Test Load Options – Relational Targets.
Running the Integration Service in Safe Mode
Test a development environment. Run the Integration Service in
safe mode to test a development environment before migrating to
production
Troubleshoot the Integration Service. Configure the Integration
Service to fail over in safe mode and troubleshoot errors when
you migrate or test a production environment configured for high
availability. After the Integration Service fails over in safe mode,
you can correct the error that caused the Integration Service to
fail over.
Syntax Testing: Test your customized queries using your source
qualifier before executing the session. Performance Testing for
identifying the following bottlenecks:
Target
Source
Mapping
Session
System
Use the following methods to identify performance bottlenecks:
Run test sessions. You can configure a test session to read from a
flat file source or to write to a flat file target to identify source and
target bottlenecks.
Analyze performance details. Analyze performance details, such
as performance counters, to determine where session
performance decreases.
Analyze thread statistics. Analyze thread statistics to determine
0
Share
1/21/13 Complete reference to Informatica: Informatica Power Center Testing
informaticatutorials-naveen.blogspot.in/2011/04/informatica-power-center-testing.html#axzz2IbCIeQAT 2/2
Next Entries »« Previous Entries
You can follow any responses to this entry through the RSS 2.0 feed. You canleave a response.
0 Responses
Leave a Reply
Enter your comment...
Comment as: Google Account
Publish Preview
Links to this post
Create a Link
Recent Comments
Testing
Unit TestingIntegration TestingUATInformatica TestingDebuggerConstraint Based loadingTarget Load Plan
AdvancedConcepts
Mapping Parameter's &
Variable
Mapplets
Partitioning
Working with links
Scheduler
Types of Task's- 1
Types of Task's- 2
Indirect Method for
Loading
SCD - Type 1
SCD - Type 2
SCD - Type 3
Incremental Aggregation
Mapping Templates
Grid Processing
Work Flow Variables
Performance-Tuning
Necessity Of
Performance-tuning
Identification Of bottle
Necks
Optimization of Bottle
necks
Performance tuning of
Lookup
Push Down
Optimization
Chat with Me
Chat with Me Offline
Visitor's
the optimal number of partition points.
Monitor system performance. You can use system monitoring
tools to view the percentage of CPU use, I/O waits, and paging to
identify system bottlenecks. You can also use the Workflow
Monitor to view system resource usage. Use Power Center
conditional filter in the Source Qualifier to improve performance.
Share metadata. You can share metadata with a third party. For
example, you want to send a mapping to someone else for testing
or analysis, but you do not want to disclose repository connection
information for security reasons. You can export the mapping to
an XML file and edit the repository connection information before
sending the XML file. The third party can import the mapping from
the XML file and analyze the metadata.
Reactions: Excellent (2) Good (4) Useful (2)
© 2009 - Complete reference to Informatica is proudly brought to you by Naveen
top related