Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Infrastructure Planning
  3. Business and Technical Requirements
  4. Installation and Deployment Considerations
  5. Sample Installation Topologies

Infrastructure Planning Guide

Infrastructure Planning Guide

Back Next

Multiple Application Server Instances Topology

Multiple Application Server Instances Topology

In a multiple application server instances topology, you distribute the installation of the MDM Hub components across multiple application server instances.
To set up a multiple application server instances topology, you need multiple machines with application server instances. The topology provides scalability. To scale the processing capability of the MDM Hub implementation, deploy additional Process Server instances on additional application server instances.
If a Process Server fails, batch jobs running on the Process Server fail. The batch jobs do not fail over and complete on Process Server instances that are online. You must start the batch jobs again. The internal load-balancing mechanism of the MDM Hub distributes the batch job requests between the Process Server instances that are online.
You can use the multiple application server instances topology for high data volumes. The topology supports high volume batch jobs by distributing the load across the Process Servers that you configure.
If the MDM Hub implementation contains multiple Hub Server instances and you use JMS message queues, to consume outbound JMS messages, deploy the Hub Server instances in a cluster. Otherwise, each application server instance will have a different outbound JMS destination.
The sample installation topology contains four machines. An application server instance is installed on three of the four machines. The Hub Server is deployed on the application server instance on one of the machines. The Process Server instances are deployed on the application server instances on the other two machines. The Hub Server distributes the processing load for batch jobs between the two Process Server instances. If one of the Process Server instances fail or is offline, the Hub Server sends the processing request to the other Process Server that is online. The Hub Store is configured on the fourth machine on which a database server is installed.
The following image shows a sample multiple application server instances installation topology that is not highly available:
The installation topology contains four machines. An application server instance is installed on Machine 1, Machine 2, and Machine 3. The Hub Server is deployed on the application server instance on Machine 1. The Process Server instances are deployed on the application server instances on Machine 2, and Machine 3. The database is configured on Machine 4.
If you need high availability, you can configure additional Hub Server instances and configure external load balancers between the Hub Server instances.
The following image shows a sample multiple application server instances installation topology that is highly available:
The installation topology contains five machines. An application server instance is installed on Machine 1, Machine 2, Machine 3, and Machine 4. The Hub Server is deployed on the application server instance on Machine 1 and Machine 2. The Process Server instances are deployed on the application server instances on Machine 3, and Machine 4. The database is configured on Machine 5.
The following table describes the capabilities of the multiple application server instances topology:
Capability
Availability
High availability
None.
If you need high availability, you can configure additional Hub Server instances and configure external load balancers between the Hub Server instances.
Scalability
Yes.
To scale the MDM Hub to support large data volumes, add more MDM Hub components. Also, to process multiple requests concurrently, configure multiple threads for the Process Server.
The MDM Hub supports multithreading for the following operations and components:
  • Hub Console operations
  • Batch jobs
  • Services Integration Framework (SIF)
Load balancing
Yes. The MDM Hub distributes the load between the available Process Server instances by using an internal load balancing mechanism.
The MDM Hub supports load balancing for the following operations:
  • Hub Console operations
  • All batch jobs except the Generate Match Tokens job
    The MDM Hub supports load balancing for the fuzzy matching portion of the Match jobs and for the cleanse process portion of the Stage jobs.
The MDM Hub does not support load balancing for the following components:
  • Informatica Data Director
  • Services Integration Framework (SIF)
  • Outbound JMS message queues
Maintainability
Difficult to maintain because the MDM Hub components are deployed on multiple machines. In environments where frequent changes are required, deployments and configurations need to be performed on each machine.
0 COMMENTS
We’d like to hear from you!