Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.7.1

Upgrading from Version 9.7.1

Configure the Elasticsearch Properties File

Configure the Elasticsearch Properties File

Informatica provides a sample Elasticsearch properties file. To configure Elasticsearch, edit the properties file.
  1. Find the
    elasticsearch.yml
    file in the following directory:
    <elasticsearch installation directory>/config
  2. Use a text editor to open the file, and edit the following properties:
    Property
    Description
    bootstrap.memory_lock
    Sets up memory locking. To prevent any Elasticsearch memory from being swapped out, set to
    true
    . Default is
    true
    .
    cluster.name
    Specify a unique name for the Elasticsearch cluster. If you have multiple clusters, ensure that the name of each cluster is unique. If a cluster has multiple nodes, ensure that on each node of the cluster, the same cluster name is specified.
    discovery.zen.minimum_master_nodes
    Required for a multi-node cluster to prevent data loss and maintain cluster stability. Set to the following value:
    (number of master-eligible nodes / 2) + 1
    For example, if a cluster has three nodes, all of which are master-eligible nodes and can contain data, then set the property to
    (3 / 2) + 1
    , which is rounded to
    2
    .
    discovery.zen.ping.unicast.hosts
    Required for a multi-node cluster. This property is used to specify the discovery setting, which is a list of IP addresses and transport ports of the nodes in the cluster. Use the following format to set the property:
    ["host1:port1","host2:port2","host3:port3"]
    http.port
    Port for the HTTP requests. Default is
    9200
    .
    network.host
    The IP address of the host to use as the bind address.
    node.data
    Enables a node as a data node that performs data related operations, such as CRUD and search. Default is
    true
    .
    node.ingest
    Enables a node as an ingest node that transforms and enriches the data before indexing. Default is
    true
    .
    node.master
    Enables a node as a master node that controls the cluster. If a cluster has multiple nodes, enable at least one of the nodes as a master node. For high availability, set multiple nodes as master nodes. Default is
    true
    .
    node.name
    Specify a unique name for the node.
    path.data
    Path to the directory where you want to store the data. You can configure multiple data directories. For more information about configuring multiple data directories, see the Elasticsearch documentation.
    path.logs
    Path to the log files.
    transport.tcp.port
    The TCP bind port. Default is
    9300
    .
    searchguard.enterprise_modules_enabled
    Specifies whether you want to enable Search Guard Enterprise Edition. To avoid license violation, always set the property to
    false
    .
    The MDM Hub installer includes Search Guard Community Edition, which is free. Informatica does not include a license for Search Guard Enterprise Edition.
    searchguard.ssl.transport.keystore_type
    The type of keystore file. Set to
    JKS
    . Default is
    JKS
    .
    searchguard.ssl.transport.keystore_filepath
    Relative path to the keystore file. If you used the
    sip_ant
    script to create the keystore, use the default path. Default is
    MDM_ESKEYSTORE_FILE_JKS.keystore
    .
    searchguard.ssl.transport.keystore_password
    The keystore password. Default is
    infa@1234
    .
    searchguard.ssl.transport.truststore_type
    The type of truststore file. Set to
    JKS
    . Default is
    JKS
    .
    searchguard.ssl.transport.truststore_filepath
    Relative path to the truststore file. If you used the
    sip_ant
    script to create the truststore, use the default path. Default is
    MDM_ESTRUSTSTORE_FILE_JKS.keystore
    .
    searchguard.ssl.transport.truststore_password
    The truststore password. Default is
    infa@1234
    .
    searchguard.ssl.http.enabled
    Specifies whether you want to enable transport layer security (TLS) on the REST layer. Set to
    true
    . Default is
    true
    .
    searchguard.ssl.http.clientauth_mode
    Specifies whether you want to use the TLS client authentication mode on the REST layer. Set to
    REQUIRE
    . Default is
    REQUIRE
    .
    searchguard.ssl.http.keystore_type
    The type of keystore file. Set to
    JKS
    . Default is
    JKS
    .
    searchguard.ssl.http.keystore_filepath
    Relative path to the keystore file. If you used the
    sip_ant
    script to create the keystore, use the default path. Default is
    MDM_ESCLIENT_FILE_JKS.keystore
    .
    searchguard.ssl.http.keystore_password
    The keystore password. Default is
    infa@1234
    .
    searchguard.ssl.http.truststore_type
    The type of truststore file. Set to
    JKS
    . Default is
    JKS
    .
    searchguard.ssl.http.truststore_filepath
    Relative path to the truststore file. If you used the
    sip_ant
    script to create the truststore, use the default path. Default is
    MDM_ESTRUSTSTORE_FILE_JKS.keystore
    .
    searchguard.ssl.http.truststore_password
    The truststore password. Default is
    infa@1234
    .
    searchguard.cert.oid
    The object identifier (OID) of the client certificate. Default is
    1.2.3.4.5.5
    .
    If you used the
    sip_ant
    script to create the certificates, use the default OID.
    If you did not use the
    sip_ant
    script to create the security certificates, you might need to set this property.
    searchguard.ssl.transport.enforce_hostname_verification
    Specifies whether you want to verify host names on the transport layer. If the certificates are not created by using the
    sip_ant
    script, set to
    true
    . Default is
    false
    .
    searchguard.nodes_dn
    The DNs of the node certificates to identify requests between the nodes in the Elasticsearch cluster. If you used the
    sip_ant
    script to create the certificates, use the default value. Default is
    - CN=EsNode
    .
    searchguard.authcz.admin_dn
    The DN of the client certificate that is also an administrative certificate. If you used the
    sip_ant
    script to create the certificates, use the default value. Default is
    - CN=EsClient
    .
  3. Save the properties file with the same name,
    elasticsearch.yml
    .

0 COMMENTS

We’d like to hear from you!