Вы находитесь на странице: 1из 32

] 

 


| | |  |


| | 
]

ë¸  
ë
 
ë]   


| | |  |


| | 
µ 
 



 ]


ã PowerCenter introduces a service-oriented architecture

ã PowerCenter introduces a domain, which serves as the primary unit of


administration for the PowerCenter environment.

ã A domain is a collection of nodes and services in the PowerCenter environment.

ã The first time you install Informatica Services, you create a domain and add a
node to the domain.

| | |  |


| | 
Ï 


É 

         



   

   
        

 
 

É  
   
  
   


É        




   

É      
  
  

É !  
  
 
"

 #  
  

| | |  |


| | 
Ï 


| | |  |


| | 
Ï 
  

| | |  |


| | 
Ï 
  

| | |  |


| | 
¸  

É $   
 
%  
  
 


    
 
  
%  
  


É $   
  
  
  


É & 

É '   

É &  

| | |  |


| | 
m  

É The Partitioning Option increases PowerCenter¶s performance through parallel data processing
.
É hen the Integration Service runs the session, it can achieve higher performance by
partitioning the pipeline and performing the extract, transformation, and load for each partition
in parallel.

É  m  
É 
 

 
É $  
 
É $    
É ( 
É % 
 
É &  

| | |  |


| | 

 

É  
 
    

É )


  
  
%

   
* 

    
 

É +
+ 


  
 
%

      
 
 

| | |  |


| | 

   

É ou can configure the following information when you edit or add a partition point:
É Specify the partition type at the partition point.
É Add and delete partitions.
É nter a description for each partition.

| | |  |


| | 
¸  

É The Integration Service uses a hash function to group rows of data among partitions .
É Improves the performance of the session , the hash function usually processes
numerical data more quickly than string data.
É Specify a hash key for user hash key.
É e have created a sample mapping when 
 
  
mapping(m_orders_scd3) for Partitioning then the run time comes up to 37 seconds

| | |  |


| | 
¸  
 

É using hash user key partition the run time comes up to 22 seconds to complete the
session as shown in the below figure

| | |  |


| | 
Æ    


É ith key range partitioning, the Integration Service distributes rows of data based on a port.
É you define a range of values.

| | |  |


| | 
Æ    

 

É using key range partition the run time comes up to 33 seconds to complete the
session as shown in the below figure.

| | |  |


| | 
  
 

É „    

| | |  |


| | 
¸ash auto-keys

É 
     
   
     
É        
         
   V

| | |  |


| | 
 
   
 

É In pass-through partitioning, the Integration Service processes data without


redistributing rows among partitions.
É Increases data throughput , without increasing number of partitions.

| | |  |


| | 
<
<
  
 

É In round-robin partitioning, the Integration Service distributes rows of data evenly to all partitions .

É The session based on this mapping reads item information from three flat files of different sizes:
É Source file 1: 80,000 rows
É Source file 2: 5,000 rows
É Source file 3: 15,000 rows
É hen the Integration Service reads the source data, the first partition begins processing 80% of the
data, the second partition processes 5% of the data, and the third partition processes 15% of the
data.
É To distribute the workload more evenly, set a partition point at the Filter transformation and set the
partition type to round-robin. The Integration Service distributes the data so that each partition
processes approximately one-third of the data.

| | |  |


| | 
]   


É If the volume of data grows or you add more CPUs, you might need to adjust
partitioning so the session run time does not increase.

É hen you use dynamic partitioning, you can configure the partition information so
the Integration Service determines the number of partitions to create at run time.

É The Integration Service scales the number of session partitions at run time based on
factors such as source database partitions or the number of nodes in a grid.

| | |  |


| | 

  ]   


| | |  |


| | 

  ]   
 
 

É 
    
  

 

 
!

É ]. Do not use dynamic partitioning. Defines the number of partitions on the
Mapping tab.

É "

  
. Sets the partitions to a number that you define in the
Number of Partitions attribute. Use the $DynamicPartitionCount session parameter,
or enter a number greater than 1.

É "


  Sets the partitions to the number of nodes in the
grid running the session. If you configure this option for sessions that do not run on a
grid, the session runs in one partition and logs a message in the session log.

É "

  
  Determines the number of partitions using database
partition information. The number of partitions is the maximum of the number of
partitions at the source.

| | |  |


| | 
"

  


É dit the task , go to config object tab. Set the dynamic partition as based on number
of partitions, number of partitions 3.

| | |  |


| | 
"

  

 

É Using Dynamic partition the run time comes up to 32 seconds to complete the
session as shown in the below figure.

| | |  |


| | 
  
 

É „    

| | |  |


| | 
"


 

É dit the task , go to config object tab. Set the dynamic partition as based on number
of nodes in grid.

| | |  |


| | 
"


 
 

É Using Dynamic partition the run time comes up to 25 seconds to complete the
session as shown in the below figure.

| | |  |


| | 
"

  


É dit the task , go to config object tab. Set the dynamic partition
as based on source partition

| | |  |


| | 
"

  
 
 

É Using this option Dynamic partition the run time comes up to


20 seconds to complete the session as shown in the below
figure.

| | |  |


| | 
  
]   


V Session run time does not increase with volume of data grows or you add
more CPUs.

V Scales cost-effectively to handle large data volumes.


É nhances developer productivity.
É Optimizes system performance in response to changing business
requirements.

É ven though any system fails , session will be completed. ( grid computing).

| | |  |


| | 
ñµ µ µ#]$ µ < µ µ

É $

   
  % ñ

   

É $

   
   ] 

| | |  |


| | 
m 

| | |  |


| |