a 8 SOA Architecture
4
Service Oriented Architecture is similar to the distributed processing. Let us say, earlier you have one PM Server that used to execute workflows. let us say, you have 10 sessions that should run concurrently, the PM Server (a computer program) resides only in one machine and so one machine will run only one session at any point of time, t hough they look to be running concurrently. If you have attached 10 other systems to that machine, even then PM Server is only on one machine, so it can only execute jobs on that machine. But with service oriented architecture, there will one main machine/node (gate way node) which has Domain service and the other 10 machines (worker nodes) just have integration services (s imilar to PM Server in 713 ). So if you have 10 ses sions to be run concurrently, then these 10 machines will r un each session giving very good performance. So this is called Service Oriented Architecture. Earlier ar chitecture was client server. Informatica Architecture --Integration Service vs Power center Server The differences between 7.x and 8.x is on architecture as well as The architecture of PowerCenter 8.x primarily differs from that of PowerCenter 7.x in the administration of the product. PowerCenter has now adopted a Service Oriented Architecture (SOA).The SOA architecture has replaced several servers that were used within the PowerCenter 7.x installer. A Tomcat web server is used to run an Informatica 'domain' comprising of several repositories or integration 'services'. An integration service is responsible for data movement. SOA allows a single console tool to be used to administer the PowerCenter installer. This tool is web based and can be a ccessed from anywhere in your network. SOA supports several integration or repository services to run concurrently. This allows high availability to be implemented (if a server hosting an integration service fails these tasks can be 'failed over' onto another node in the domain). Additionally PowerCenter 8.x supports the use of Java in mappings, the ability to 'push down' processing into the database and other similar improvements. There is nosignificant change in the client interface. Additional Information: Several terms have acquired a new meaning with the change in product architecture. PowerCenter 7.x PowerCenter 8.x R epository server and repository R epository service PowerCenter Server I ntegration service Some other enchancements like push down processing, more flexible java transformations, SQL transformations, string parsing functions are newly added to 8.x. Only change we can see in it is a single place where we do all administration stuff. Repository server is renamed as repository service and informatica pc server renamed as integration service. Not much change in client interface as we still have Repository Manager,Designer,Workflow Manag er and Workflow Monitor. Also on 8.5 and 8.6, security, user and group administration has been moved to t he administration console. When comparing to the architecture 7.1 n 8.1,DOMAIN,NO DE,INTEGRATIO N SERVICES added to the 8.1 architectutre.DOMAIN is a web based admin console.NODE is like INF server or power centre server.INTEGRATION SERVI CES is li ke repository server.
Transcript of a 8 SOA Architecture
5/16/2018 a 8 SOA Architecture - slidepdf.com
http://slidepdf.com/reader/full/a-8-soa-architecture 1/3
Service Oriented Architecture is similar to the distributed processing. Let us say, earlier you have one
PM Server that used to execute workflows. let us say, you have 10 sessions that should run
concurrently, the PM Server (a computer program) resides only in one machine and so one machine
will run only one session at any point of time, though they look to be running concurrently. If you
have attached 10 other systems to that machine, even then PM Server is only on one machine, so it
can only execute jobs on that machine. But with service oriented architecture, there will one mainmachine/node (gate way node) which has Domain service and the other 10 machines (worker nodes)
just have integration services (similar to PM Server in 713). So if you have 10 sessions to be run
concurrently, then these 10 machines will run each session giving very good performance. So this is
called Service Oriented Architecture. Earlier architecture was client server.
Informatica Architecture --Integration Service vs Power center Server
The differences between 7.x and 8.x is on architecture as well as The architecture of PowerCenter 8.x
primarily differs from that of PowerCenter 7.x in the administration of the product. PowerCenter has
now adopted a Service Oriented Architecture (SOA).The SOA architecture has replaced several
servers that were used within the PowerCenter 7.x installer. A Tomcat web server is used to run an
Informatica 'domain' comprising of several repositories or integration 'services'. An integration service
is responsible for data movement.
SOA allows a single console tool to be used to administer the PowerCenter installer. This tool is web
based and can be accessed from anywhere in your network. SOA supports several integration or
repository services to run concurrently. This allows high availability to be implemented (if a server
hosting an integration service fails these tasks can be 'failed over' onto another node in the domain).
Additionally PowerCenter 8.x supports the use of Java in mappings, the ability to 'push down'
processing into the database and other similar improvements. There is nosignificant change in the
client interface.
Additional Information: Several terms have acquired a new meaning with the change in product
architecture.
PowerCenter 7.x PowerCenter 8.x R epository server and repository R epository service PowerCenter
Server I ntegration service Some other enchancements like push down processing, more flexible java
transformations, SQL transformations, string parsing functions are newly added to 8.x. Only change
we can see in it is a single place where we do all administration stuff. Repository server is renamed as
repository service and informatica pc server renamed as integration service. Not much change in
client interface as we still have Repository Manager,Designer,Workflow Manager and Workflow
Monitor.
Also on 8.5 and 8.6, security, user and group administration has been moved to the administration
console.
When comparing to the architecture 7.1 n 8.1,DOMAIN,NODE,INTEGRATION SERVICES added
to the 8.1 architectutre.DOMAIN is a web based admin console.NODE is like INF server or powercentre server.INTEGRATION SERVICES is like repository server.
5/16/2018 a 8 SOA Architecture - slidepdf.com
http://slidepdf.com/reader/full/a-8-soa-architecture 2/3
DOMAIN,NODE,INTEGRATION SERVICES are at one place that is DOMAIN DATABASE.In 8.1
we don't have admin console n repository agent.and also you can install multiple NODES in a single
machine.and you can intiate multiple processes simultaneously. In INF 8.1 has more security you can
not create repository with out previliges.you no need to start the services in control panel everytime.and also some of the transformations added in 8.1.They are SQL,JAVA transformations.It
supports unstructured data like emails,word,pdfs.concept of flatfile updation is introduced.
Effective in PowerCenter 8.0, you might notice an increase in memory and CPU resource usage on
machines running PowerCenter Services. The following factors can increase memory and CPU
resource usage:
Updates to Integration Service and Repository Service processes. The pmserver and pmdtm process
for the Integration Service and the pmrepagent process for the Repository Service include updated
functionality that requires more memory and CPU resource usage.
High availability. You configure a domain for high availability, service restart, failover, and recovery
operations.
Java Runtime Environment (JRE). The PowerCenter service-oriented architecture uses JRE to run the
PowerCenter domains and nodes. Domains and nodes require more memory and CPU resources than
when you run a PowerCenter Server or Repository Server in PowerCenter 7.x.
Log Manager. The Log Manager requires additional memory and CPU resources when it collects and
processes a large number of log events.
Informatica Repository:
The informatica repository is at the center of the informatica suite.
· The Informatica repository is a relational database that stores information, or metadata,used by the Informatica Server and Client tools.
· Metadata is data about data which include information such as source definitions ,target definitions, mappings describing how to transform source data, sessions indicatingwhen you want the Informatica Server to perform the transformations, and connect strings forsources and targets.
· The repository also stores administrative information such as usernames and passwords,permissions and privileges, and product version.
· Use repository manager to create the repository. The Repository Manager connects tothe repository database and runs the code needed to create the repository tables. These
tables stores metadata in specific format the informatica server, client tools use.
5/16/2018 a 8 SOA Architecture - slidepdf.com
http://slidepdf.com/reader/full/a-8-soa-architecture 3/3
Informatica Components:
Server Components:
1. Repository Service
2.
Integration Service
Client Components:
1. Repository Manager2. Designer3. Workflow Manager4. Workflow Monitor
Server Components
1. Repository Service:
Ø The Repository Server manages the metadata in the repository database.
Ø The Repository Server manages connections to the repository from client applications.
Ø The Repository Service is a separate, multi-threaded process that retrieves, inserts, andupdates metadata in the repository database tables. The Repository Service ensures the
consistency of metadata in the repository.
2. Integration Service:
Ø The Integration Server reads mapping and session information from the repository. Itextracts data from the mapping sources and stores the data in memory while it applies thetransformation rules that you configure in the mapping. The Integration Server loads thetransformed data into the mapping targets.
Ø Manages the scheduling and execution of workflows
Ø The Integration Server can start and run multiple workflows concurrently. It can alsoconcurrently process partitions within a single session.
![Service Oriented Architecture (SOA) [1/5] : Introduction to SOA](https://static.fdocuments.us/doc/165x107/54b75eeb4a7959f9168b4652/service-oriented-architecture-soa-15-introduction-to-soa.jpg)
