Table of Contents

Search

  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

Configure the Process Server Properties

Configure the Process Server Properties

Configure all the Process Server instances to enable search. Use the Process Server tool in the Hub Console and the
cmxcleanse.properties
file to configure the Process Server properties for search.
  1. In the Hub Console of a node, start the Process Server tool.
  2. Click
    Write Lock
    Acquire Lock
    .
  3. In the right pane of the Process Server tool, click the
    Add Process Server
    button.
    The
    Add/Edit Process Server
    dialog box appears.
  4. Set the following properties of a Process Server for search:
    Property
    Description
    Server
    IP address or the fully qualified host name of the application server on which you want to deploy the Process Server. The name is case sensitive.
    Do not use
    localhost
    as the host name.
    Port
    Port of the application server on which you want to deploy the Process Server.
    If you want to use the HTTPS protocol to communicate with the Process Server, specify the HTTPS port of the application server.
    Enable Search Processing
    For a search configuration based on Elasticsearch, this property indicates whether the Process Server is enabled to run an Initially Index Smart Search Data job. This batch job creates indexes for all the values of the searchable fields in a business entity.
    Select the check box to enable the option for your search configuration, or clear the check box to disable the option.
    Enable Secured Connection (HTTPS)
    Indicates whether to use the HTTPS protocol to communicate with the Process Server.
    Select the check box to use the HTTPS protocol, or clear the check box to use the HTTP protocol.
    If you select to use the HTTPS protocol, you must specify the HTTPS port of the application server.
  5. Click
    OK
    , and then click
    Save
    .
  6. Use a text editor to open the
    cmxcleanse.properties
    file in the following location:
    <MDM Hub Installation Directory>\hub\cleanse\resources
  7. Configure the following properties for search:
    cmx.ss.enabled
    Indicates whether to use the Process Server to perform smart search. Default is false. Set to true if you want to use the Process Server to perform smart search.
    cmx.ss.enabled
    Indicates whether to enable search. In a new installation, the default is
    true
    . When upgrading, if this property is set, the value remains set to the pre-upgrade value. If this property is not set, the default is
    false
    .
    JBoss 6.4.0 only. When you enable search in an environment that uses JBoss 6.4.0, you must set
    cmx.server.match.file_load
    to
    false
    . This setting forces the Process Server to use the JDBC uploader instead of native database utilities for matches.
    ex.max.conn.per.host
    Sets the maximum number of Elasticsearch nodes that you want to connect to the host. Set to the number of Elasticsearch cluster nodes on the host.
    ex.max.threads
    Sets the maximum number of threads that you want the Apache asynchronous non-blocking receiver to use for each node in the Elasticsearch cluster. Default is
    1
    .
    Change the value only when suggested by Informatica Global Customer Support.
    search.provisioning.numreplicas
    Optional. Number of copies of the search engine (Solr or Elasticsearch) documents that you want to create on different nodes. Use the replication factor to create multiple copies of the documents in the shards of different nodes. You require multiple copies of the documents to achieve high availability if one or more nodes shut down unexpectedly. For example, if the replication factor is 2, you get two copies of the documents in two nodes. For Solr, the default is 1. For Elasticsearch, the default is 0.
    MAX_INITIAL_RESULT_SIZE_TO_CONSIDER
    Optional. Manually add the property. Total number of search results to display in the
    Data Director
    application. The recommended maximum value is 250. Default is 130. Any value higher than 130 affects the performance of the
    Data Director
    application.
    ssl.keyStore
    Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Absolute path and file name of the keystore file.
    ssl.keyStore.password
    Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Plain text password for the keystore file.
    ssl.trustStore
    Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Absolute path and file name of the truststore file.
    ssl.trustStore.password
    Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Plain text password for the truststore file.
    cmx.websphere.security.ssl.config.url
    Required if you use the HTTPS port of the application server to configure the Process Server. For WebSphere only. Manually add the property. Absolute path of the
    ssl.client.props
    file with the file name.
  8. Save the
    cmxcleanse.properties
    file.
  9. Restart the application server.

0 COMMENTS

We’d like to hear from you!