Installing HCL Commerce Developer Update Packages (interactive method)

• Open the IBM Installation Manager application.

• Navigate to File > Preferences and then click Repositories.

• On the Repositories page, click Add Repository.
• In the Add Repository dialog box, click Browse.
• Locate the update package folder, select the repository.config file, and click OK.
• Click Test Connections to ensure the repository is accessible.
• Enable Rollback Support
  • On the Start page of Installation Manager, click File > >Preferences > Files for Rollback.
  • Select Save files for rollback to enable rollback capability.

• From the Start page, click Update.
• Select the HCL Commerce Developer package and click Next. The update packages wizard detects all of the applicable fixes. Recommended features are automatically selected.
• Select the updates that you want to apply and click Next. The update is automatically preselected.
• Click Next.
• Review the summary information and click Update to install the updates.
• Review Installation History: Review the installation history by selecting File > Installation History.

• Check the update log file located at WCDE_installdir\UpdateDelta\9.1.x.0\applyUpdate.log.
  • The x values represent the update package level.

• Review the merges.log file located at WCDE_installdir\UpdateDelta\9.1.x.0\backup\merges.log.

  This log lists files that were modified by both the update and your environment.

• Files modified by both the update and your changes are backed up at WCDE_installdir\UpdateDelta\9.1.x.0\backup.
• Use a text comparison tool to compare the original and updated versions of each file listed in merges.log.
• For any deleted files, determine if they are still needed and take appropriate action.
• If a compressed archive (for example, .zip, .jar, .war) was deleted and previously modified, the update may be incomplete. In such cases: Roll back the update, restore the archive file and reapply the update.

• Back up the database before proceeding. This is essential for rollback purposes. For more information about how to back up, see BACKUP DATABASE COMMAND.
• Run the updatedb utility to update your database.
• Configure the development database using the setdbtype utility. This step is mandatory for existing environments. For more information, see Changing the development database type by using the setdbtype command.

• Use the setSpiuserPassword utility if you are changing the spiuser password or you are upgrading from a version earlier than 9.1.9.0 to 9.1.9.0 or later.

  For more information, see Setting the spiuser password in HCL Commerce Developer.

• If you are using Elasticsearch, configure the HCL Commerce Developer Search environment.

  For more information, see Setting up the HCL Commerce Developer Search environment.

For Apache Solr:

• Open HCL Commerce Developer in the RAD environment.
• Expand WebSphere Application Server Liberty Profile > Servers > searchServer > resources > search > index, and delete managed-solr and solr folders.
• Start the Transaction server, Search server, and Store server, then build the Solr search index.
  • Update CRS and Transaction Server JNDI Settings.
    Modify the following file to configure the JNDI settings for both the CRS and Transaction Server to point to Solr:

    C:\IBM\WebSphere\Liberty\usr\servers\crsServer\configDropins\overrides\jndi.xml
    

    Add or update the necessary Solr JNDI configuration entries.
  • Update Name Bindings Configuration.
    Update the following file to reflect the Solr configuration:

    C:\WCDE_V9\wasprofile\config\cells\localhost\nodes\localhost\servers\server1\namebindings.xml
    

    Make sure all relevant references to Solr are correctly set.

  For more information about building the Solr index, see Building the HCL Commerce Search index.

For Elasticsearch:

• Issue the following command from within a REST client. POST https://ingestServerHostname:ingestServerPort/connectors/auth.reindex/run?storeId=11 .
• Authenticate with username spiuser and the correct password:
  • HCL Commerce versions 9.1.0.0 through 9.1.8.0: spiuser / passw0rd.
  • HCL Commerceversion 9.1.9.0 and greater: spiuser / QxV7uCk6RRiwvPVaa4wdD78jaHi2za8ssjneNMdu3vgqi.
• Replace storeId=11 with your store’s actual ID:
  • AuroraESite: storeId=1
  • AuroraB2BSite: storeId=2
  • Emerald storeId=11
  • Sapphire storeId=12

  OR

  From a command prompt, issue the following command:

  curl --user spiuser:spi_plain_text_password --insecure -X POST "https://ingestServerHostname:ingestServerPort/connectors/auth.reindex/run?storeId=11"

  This call will return a runID value. For example:

  { "runId": "i-26144b4d-cd1c-4679-b2c2-870fc27e6095" }

• Monitor the indexing progress using.

  GET

  GET https://ingestServerHostname:ingestServerPort/connectors/auth.reindex/runs/[runId]/status 

  OR

  via curl

  curl --user spiuser:spi_plain_text_password --insecure -X GET \
  "https://ingestServerHostname:ingestServerPort/connectors/auth.reindex/runs/[runId]/status"
  

• Wait until the process is complete.

  The progress percentage is approximate. To view detailed logs, remove /status from the URL in the GET request if issues occur.