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.4 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Performance Tuning
  3. Recommendations
  4. Appendix A: Glossary

Performance Tuning Guide

Performance Tuning Guide

Back Next

Recommendations for the Hub Console Optimization

Recommendations for the Hub Console Optimization

The Hub Console parameters can be optimized for better performance.
The following table lists the recommendations for the Hub Console optimization:
Parameter
Recommended Setting
Description
Client Java Version (JRE)
As specified in the
Product Availability Matrix (PAM).
Ensure that the client Java version is as specified in the PAM document for the product.
It is not required for the Hub Console to pick the latest JRE that the client box has. The JRE version selected depends on the PATH variable. To ensure that the Hub Console uses the correct JRE, temporarily enable the console log as listed in the Informatica Knowledge Base article.
When enabled, the next launch of Hub Console opens a Java console window where you can see the used JRE version in the top of the console.
Console log
Disable (Default).
Disable the logging by launching the javaws -viewer option on the client box in the run command.
In the javaws window, go to Java Control Panel in the Advanced tab and perform the following steps:
  • Clear ‘Enable tracing’ and ‘Enable logging’ options in the Debugging section.
  • Check ‘Hide Console’ option in the Java Console section.
High Data Volume
See the parameter "High Volume of Data in
C_REPOS_TABLES
 with historical data" in Database - General Recommendation Section.
Having huge number of records in the tables listed in the referenced section might cause multiple issues on Hub console.
The following lists are the issues that might be include:
  • batch groups screen loads too slowly.
  • base object record is saved too slowly.
  • cleanse function is saved too slowly.
Network latency
Good network connection.
Hub Console communicates with the Hub Server (application server) frequently. Therefore, the Hub Console must process a considerable amount of data to and from the Hub Server. Have good network connection between the client box and the application server.
Disable dirty index notification for Solr search.
cmx.ss.dirtyIndex.disable=true
If you use Solr search, you must set the property in the
cmxserver.properties
 file. When the user clicks on the batch viewer, this property disables the dirty index notification feature and improves the Hub Console performance. See the
Informatica Multidomain MDM Configuration Guide
 for further details.
Console mode
cmx.appserver.console.mode=https (/http)
MDM 10.3 and earlier versions use http(s) instead of the default EJB.
The MDM 10.4 is configured only with http(s).
For more information, search the
Informatica Knowledge Base
 for article numbers 310913 and 139923.
0 COMMENTS
We’d like to hear from you!