You are here

Upgrading from Solr 1.4 to Solr 4 search

Use this information to upgrade from Alfresco Content Services 4.x with the Solr 1.4
 search server to Alfresco Content Services 5.2.6
 with the Solr 4 search server.

To determine the current search server, navigate to the Search Manager
 page at Alfresco Share Admin Console > Repository Services > Search Service. Select
 the search subsystem from the Search Service In Use list.


Follow the steps to migrate from Alfresco Content Services 4.x with Solr 1.4 search service to Alfresco Content Services 5.2.6 with Solr 4 search service.

  1. Upgrade to Alfresco Content Services 5.2.6
 and continue to use the Solr 1.4 search service as before.

    For information on migrating the Solr 1.4 indexes with Alfresco Content Services 4.x to Solr 1.4 with Alfresco Content Services 5.2.6, see Upgrading Solr 1.4 search service.

  2. Configure Solr 4 to track the repository. For details, see Installing and Configuring Solr 4.
  3. While Solr 4 builds its indexes, you can monitor progress using the SUMMARY report.

    http://localhost:8080/solr4/admin/cores?action=SUMMARY&wt=xml 

    For details, see the Unindexed Solr
 Transactions topic.

  4. Optionally, you can use the Solr Admin Web interface to view Solr configuration details, run queries, and analyze document fields.
    1. Open the FireFox Certificate Manager by selecting Firefox > Preferences... > Advanced > Certificates > View Certificates > Your Certificates.
    2. Import the browser keystore browser.p12 that is located in your <ALFRESCO_HOME>/alf_data/keystore directory.
    3. Enter the password alfresco.

      A window displays showing that the keystore has been imported successfully. The Certificate Manager now contains the imported keystore with the repository certificate under the Your Certificates tab.

    4. Close the Certificate Manager by clicking OK.
    5. In the browser, navigate to a Solr URL.

      For example, use http://localhost:8080/solr for Solr and http://localhost:8080/solr4 for Solr 4.

      The browser displays an error message window to indicate that the connection is untrusted. This is due to the Alfresco certificate not being tied to the server IP address. In this case, view the certificate and confirm that it is signed by the Alfresco Certificate Authority.

    6. Expand I understand the risks.
    7. Select Add Exception.
    8. Click View.

      This displays the certificate.

    9. Confirm that the certificate was issued by Alfresco Certificate Authority, and then confirm the Security Exception.

    Access to Solr 1.4/Solr 4 is then granted. The Solr Admin page is displayed. It is divided into two parts.

    The left-side of the screen is a menu under the Solr logo that provides navigation through various screens. The first set of links are for system-level information and configuration and provide access to Logging, Core Admin and Java Properties. At the end of this information is a list of Solr cores configured for this instance of Alfresco Content Services.

    The center of the screen shows the detail of the Solr core selected, such as statistics, summary report, and so on.

  5. Monitor the progress of both the Solr 1.4 and Solr 4.0 subsystems via the JMX client or the SUMMARY report.

    Important: Do not use the Alfresco Share Admin Console tool to monitor the status of the subsystems as it will change the subsystem used for query. Only use the JMX client.
  6. When the index is updated as reported by the SUMMARY report, you can use the REPORT option and check the following:
  7. When the Solr 4 index is updated, you must enable the Solr 4 subsystem and disable the Solr
 1.4 subsystem.
  8. (Optional) To decommission (now redundant) Solr 1.4, follow the steps below:
    1. Stop the Solr 1.4 search service.
    2. Delete the solr directory from <ALFRESCO_HOME>/tomcat/webapps.
    3. Delete the solr.xml file from <ALFRESCO_HOME>tomcat/conf/Catalina/localhost.
    4. Delete the solr directory from <ALFRESCO_HOME>/alf_data.

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.