Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Sample Process Server Properties File

Sample Process Server Properties File

Process Server
properties file is called
The following example shows the contents of a typical file:
# Cleanse properties # cmx.server.datalayer.cleanse.working_files.location=C:/infamdm/Hub_971_DB2/cleanse/tmp cmx.server.datalayer.cleanse.working_files=KEEP cmx.server.datalayer.cleanse.execution=LOCAL # Server settings # Installation directory cmx.home=C:/infamdm/Hub_971_DB2/cleanse # Application server type: jboss, tomcat, websphere or weblogic cmx.appserver.type=jboss cmx.appserver.version=7 # default setting: 8880 for websphere only (this is not being used in jboss and weblogic cmx.appserver.soap.connector.port= # Match Properties cmx.server.match.server_encoding=0 # limit memory usage by managing the number of records per match ranger node cmx.server.match.max_records_per_ranger_node=3000 # Cleanse Properties #
Informatica Address Verification
Properties # Trillium Director Properties # Trillium Director 11+ Properties # Group1Software Enterprise Server Properties # Group1Software CDQ Server Properties #FirstLogicDirect Properties encryption.plugin.jar=C:\Temp\informatica_dataencryption.jar


We’d like to hear from you!