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. Hierarchies Upgrade
  13. ActiveVOS Post-Installation Tasks for the Application Server
  14. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  15. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  16. Appendix A: Troubleshooting the Upgrade Process
  17. Appendix B: Frequently Asked Questions
  18. Appendix C: Processing Existing ActiveVOS Tasks
  19. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading Elasticsearch Indexes

Upgrading Elasticsearch Indexes

Upgrade the existing Elasticsearch version 6.2.3 index properties to Elasticsearch version 6.8.6 index properties. To upgrade the indexes, edit the Elasticsearch configuration properties file.
  1. Go to the following directory:
    <elasticsearch 6.2.3 installation directory>/config
  2. Copy the
    analysis
    folder.
  3. Paste the
    analysis
    folder in the following directory:
    <elasticsearch 6.8.6 installation directory>/config
  4. In the Elasticsearch version 6.8.6 configuration directory, edit the following properties in the
    elasticsearch.yml
    file:
  5. Use a text editor to open the file, and edit the following properties:
    Property
    Description
    xpack.security.transport.ssl.enabled
    Specifies whether you want to enable transport layer security (TLS) on the REST layer. Set to
    true
    . Default is
    true
    .
    xpack.security.transport.ssl.verification_mode
    Mode to verify the certificate. The supported mode is certificate. Enter the value
    certificate
    .
    xpack.security.transport.ssl.keystore.path
    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
    .
    xpack.security.transport.ssl.truststore.path
    Relative path to the truststore file. If you used the
    sip_ant
    script to create the truststore, use the default path. Default is
    MDM_TRUST_JKS.keystore
    .
    xpack.security.transport.ssl.keystore.password
    Password for keystore. Default is
    infa@es
    .
    xpack.security.transport.ssl.truststore.password
    Password for truststore. Default is
    infa@es
    .
    xpack.security.http.ssl.enabled
    Specifies whether you want to enable X-Pack. Set to
    true
    .
    xpack.security.http.ssl.verification_mode
    Mode to verify the certificate. The supported mode is certificate. Enter the value
    certificate
    .
    xpack.security.http.ssl.client_authentication
    Specifies whether you want to use the TLS client authentication mode on the REST layer. Set to
    REQUIRED
    .
    xpack.security.http.ssl.keystore.path
    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
    .
    xpack.security.http.ssl.truststore.path
    Relative path to the truststore file. If you used the
    sip_ant
    script to create the truststore, use the default path. Default is
    MDM_TRUST_JKS.keystore
    .
    xpack.security.http.ssl.truststore.password
    Password for truststore. Default is
    infa@es
    .
    xpack.security.http.ssl.keystore.password
    Password for keystore. Default is
    infa@es
    .
    xpack.security.authc.token.enabled
    Specifies whether you want to enable authentication token. Ensure that the value is always set to
    false
    xpack.security.authc.api_key.enabled
    Specifies whether you want to enable API key token. Ensure that the value is always set to
    false
  6. In the Elasticsearch version 6.8.6 configuration directory, open the
    roles.yml
    file and enter the following code to define the user role:
    user: cluster: [ 'monitoring_user','transport_client','kibana_user','snapshot_user' ] indices: - names: [ '*' ] privileges: [ 'all' ]
  7. In the Elasticsearch version 6.8.6 configuration directory, open the
    elasticsearch.yml
    file and enter the following code:
    xpack.security.authc: anonymous: username: roles: authz_exception:
  8. Start Elasticsearch. For more information about how to start Elasticsearch, see the Start Elasticsearch topic.
  9. Run the Elasticsearch health APIs to ensure that the Elasticsearch server uses the HTTPS protocol. For more information about how to test the Elasticsearch APIs, see the Elasticsearch documentation.
  10. Stop the existing Elasticsearch version 6.2.3 and version 6.8.6 environments, the MDM Hub server and Cleanse server services.
  11. Go to the following directory:
    <elasticsearch 6.8.6 installation directory>/config
  12. Configure the following properties in the
    elasticsearch.yml
    file:
    Property
    Description
    path.data
    Point to the Elasticsearch 6.2.3 data directory if you want to migrate existing indexes. You can configure multiple data directories. For more information about configuring multiple data directories, see the Elasticsearch documentation.
    To migrate to Elasticsearch version 6.8.6, your existing Elasticsearch configuration properties must contain the
    cluster.name
    and
    node.name
    properties. If these properties do not exist, you cannot migrate your existing indexes.
    path.logs
    Path to the log files.
    http.port
    Port for the HTTP requests. Enter the same port number that you set in the Elasticsearch 6.2.3 environment.
    transport.tcp.port
    The TCP bind port. Enter the same TCP bind port number that you set in the Elasticsearch 6.2.3 environment.
  13. Start the Elasticsearch version 6.8.6 environment.
  14. Test the Elasticsearch APIs to ensure the indexes are open and do not display any errors. For more information about how to test Elasticsearch APIs, see the Elasticsearch documentation.
  15. Start the Hub Server, the Process Server and the Elasticsearch services.
    Your existing MDM environment is configured with Elasticsearch 6.8.6

0 COMMENTS

We’d like to hear from you!