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 HotFix 3
  • All Products

Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Server Installation
  6. Hub Server Post-Installation Tasks
  7. Process Server Installation
  8. Process Server Post-Installation Tasks
  9. ActiveVOS Post-Installation Tasks for the Application Server
  10. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  11. Resource Kit Installation
  12. Resource Kit Post-Installation Tasks
  13. Troubleshooting the MDM Hub
  14. Uninstallation

Installation Guide for IBM DB2 with Red Hat JBoss

Installation Guide for IBM DB2 with Red Hat JBoss

Back Next

Configuring Metadata Caching (Optional)

Configuring Metadata Caching (Optional)

Metadata caches manage items such as data objects, repository objects, and search tokens. The MDM Hub uses Infinispan for metadata caching. Infinispan is installed with the Hub Server. For the caches that the Hub Server uses, the Infinispan configuration file contains default attribute values.
Run the MDM Hub with the default attribute values for the caches. If you experience performance issues, you can fine-tune the attribute values to better suit your environment.
The following table summarizes the default attribute values:
Infinispan Element and Attribute
Default Value
Description
locking acquire-timeout
60000
Maximum time during which the Hub Server can try to acquire a lock.
transaction stop-timeout
30000
When a cache stops, this attribute sets the maximum time that Infinispan waits while the Hub Server finishes remote and local transactions.
transport cluster
infinispan-cluster
Name for the underlying group communication cluster.
transport stack
UDP
Type of configuration: UDP or TCP. The configurations are defined in the
jgroups-udp.xml
 file and the
jgroups-tcp.xml
 file.
transport node-name
$node$
Name of the current node. The Hub Server sets this attribute.
The node-name defaults to a combination of the host name and a random number. The number differentiates multiple nodes on the same host.
transport machine
$machine$
ID of the machine where the node runs. The Hub Server sets this attribute.
expiration lifespan
--
Maximum lifespan of a cache entry in milliseconds. When a cache entry exceeds its lifespan, the entry expires within the cluster. If you need to optimize performance, increase the lifespan for the following caches: DISABLE_WHEN_LOCK, DATA_OBJECTS, and REPOS_OBJECTS.
For example, you can increase the lifespan from one hour (3600000) to one day (86400000).
Each cache has its own default value for this attribute. To find the default values, open the
inifinspanConfig.xml
 file.
expiration interval
--
Maximum interval for checking the lifespan. If you need to optimize performance, increase the interval for the following caches: DISABLE_WHEN_LOCK, DATA_OBJECTS, and REPOS_OBJECTS.
For example, you can increase the interval from five seconds (5000) to five minutes (300000).
Each cache has its own default value for this attribute. To find the default values, open the
inifinspanConfig.xml
 file.
0 COMMENTS
We’d like to hear from you!