Installing HCL Commerce Developer Update Packages (silent method)

1. In a command prompt, go to the eclipse subdirectory in the directory where you installed IBM Installation Manager.
2. Run the IBM Installation Manager by using the following commands to create a response file:
   Important: Ensure that you enter a file path that exists. Installation Manager does not create directories for the response file and the log file.
   • To create the response file and install the product:

     IBMIM –record response_file_path

     For example, IBMIM –record C:\WCDE_v9\installresponse.txt.
   The Installation Manager starts.
3. Complete the installation steps interactively, pointing the repository to the extracted update package.
   The options that you choose while you use the interactive method are recorded in the response file. For more information about using the interactive method, see Installing Update Packages (interactive method).

   Remember: Ensure that you set the repository preferences to the location of the HCL Commerce Developer installation image during the recording of the response file.
4. Click Finish, then close Installation Manager to save and finalize the response file.
   Note: The response file is generated only after you click Finish and exit Installation Manager.
5. Revert your system back to the state it was in before you created the response file.

• Navigate to the eclipse\tools directory of Installation Manager on the target machine:cd C:\Program Files\IBM\Installation Manager\eclipse\tools.
• Run the silent installation: imcl.exe -input C:\WCDE_v9\installresponse.txt -log C:\logs\maintenance_install.log -acceptLicense.

  Ensure that the log directory exists beforehand. For detailed progress, add the -sP flag.

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

After the update is applied, review any file conflicts.

• Open the merges.log file located at:

  luaCopyEditWCDE_installdir\UpdateDelta\9.1.x.0\backup\merges.log

• This file lists any files that were modified both by the update and by your customizations.

• Use a file comparison tool to review and merge differences between the original and updated files.
• For deleted files, determine whether they are still needed and restore them if necessary.
• If a compressed archive file (such as a ZIP, JAR, or WAR) was both modified and deleted during the update, it may be incomplete. In such cases, roll back the update, restore the archive, and reapply the update.

• Back up your database before running any update utilities. A backup is required if you plan to uninstall updates later. For more information about how to back up, see BACKUP DATABASE COMMAND.
• Run the updatedb utility to update your database.
• If you are upgrading from a version earlier than 9.1, run the setdbtype utility to configure the development database. For more information, see Changing the development database type by using the setdbtype command

Use the setSpiuserPassword utility to set the spiuser password.

This step is required if you intend to update the spiuser password, or if you use the default spiuser password when updating HCL Commerce Developer from a version prior to 9.1.9.0, to a version that is 9.1.9.0 or greater.

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

If you are planning on developing for the Elasticsearch-based search solution, set up your 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.