(Linux)

Deploy a WebSphere Commerce environment locally

We can deploy a WebSphere Commerce environment locally for developing, testing, or debugging a local runtime environment. Build a more complex system for the production environment.


Before beginning


Procedure

  1. Install Docker.

    1. Install Docker Version 17.06 or later.

    2. Install Docker Compose Version 1.10 or later.

    3. Consider creating a Docker Unix group.

      Note: Prefix sudo to Docker commands if you do not create a Docker Unix group.

  2. Download the following sample file and update fields to suit the environment.

    Note: If the link does not prompt us to save, right-click and save the file. Open the file in a source code editor to view and edit in the proper YAML format.

    The YAML samples assume we are using a Db2 Docker image. Update all the parameters that are in angle brackets <>. The sample files are commented with descriptions of the parameters.

  3. In a command line, go to where you downloaded the docker-compose.yml file.

  4. Download the Docker images and deploy the Docker containers.

      docker-compose -f docker-compose.yml up -d

    Note:

    • If the images are not already on your machine, the command downloads Docker images from our registry. The images are approximately 10 GB in total so the duration of this command depends on your Internet connection.

    • Whenever our Docker virtual machine is restarted, restart the Docker containers by rerunning the docker-compose -f <file> up -d command.

  5. If you loaded sample data in the database, then build the search index.

    1. Send the following REST request (POST) and add basic authentication with login as spiuser and the password for the spiuser. We can build the search index using one of the following methods:

      • By using cURL if you have cURL installed. Use the following cURL command with the spiuser plain text password. 

          curl -k -u spiuser:spiuserPassword-X POST https://<transaction_server_hostname>:5443/wcs/resources/admin/index/dataImport/build?masterCatalogId=10001

      • By using a browser plug-in such as HttpRequester (for Mozilla Firefox) or Postman (for Google Chrome). Use the following URL and authenticate with user spiuser and the spiuser plain text password. 

          https://<transaction_server_hostname>:5443/wcs/resources/admin/index/dataImport/build?masterCatalogId=10001

      Note the jobstatusId that we get in the response, for example, {"jobstatusId":"xxxxx"}.

    2. Use the jobstatusId and send the following REST request (GET) to check the request execution status. Again, use basic authentication with spiuser and the spiuser password. 

        https://<search_server_hostname>:3738/search/admin/resources/index/build/status?jobStatusId={jobstatusId}

      When successful, you will get a Status: 200 OK and response similar to the following example: 

        response content: {
"finishTime":"2017-08-01 06:49:31.395759",
"lastUpdate":"2017-08-01 06:49:31.395759",
"progress":"100%",
"jobStatusId":"14003",
"startTime":"2017-08-01 06:48:17.369909",
"message":"Indexing job started for masterCatalogId:10,001. Indexing job finished successfully for masterCatalogId:10001.",
"jobType":"SearchIndex",
"properties":"[]",
"status":"0"}

  6. Ensure that we can log in to Management Center.

    • https://<transaction_server_hostname>:8000/lobtools/cmc/ManagementCenter

  7. Ensure that we can visit the Aurora starter store.

    • https://<store_server_hostname>:8443/wcs/shop/en/auroraesite


What to do next


Related concepts
Extract and load data
Run Engine commands


Related tasks
Building the WebSphere Commerce Search index
Building custom Docker images based on customization packages
Use the Management Center
Running utilities from the Utility server Docker container