Installing SAP Commerce Cloud 2005 for use with Spartacus

The following instructions describe how to install and configure SAP Commerce Cloud release 2005 for use with a Spartacus storefront. In these instructions, SAP Commerce Cloud is installed to your local computer, so localhost is used in the browser URLs.


Table of Contents


Important Disclaimers

  • Starting with release 2005, SAP Commerce Cloud ships with all users inactive and without passwords. These users may need to be restored for certain backend functionality to work. For example, although you will be able to add products to cart and check out, certain users are required to fulfill orders with Order Management as used in the default cx recipe. See this help topic for more information and for a sample ImpEx that enables such users.

  • Starting with release 1905, SAP Commerce Cloud releases ships without a default admin password. You must specify a password when running recipe commands, or you can specify a password in a file named custom.properties stored in CXCOMM*\installer\customconfig. The sample custom.properties file included in these instructions contain the default password nimba; we strongly recommend you change this password to suit your requirements, as it should not be used for production servers.

  • The sample custom properties file and OCC credentials supplied here are for evaluation purposes only. Aside from a default password, for example, the CORS settings are permissive to prevent access issues. We strongly recommend that a professional SAP Commerce Cloud administrator review these settings to suit your requirements, as they should not be used for production servers.

Installation and Configuration Instructions

Summary:

  • Step 1: Download, unzip, and create the new recipe
  • Step 2: Build and initialize the recipe
  • Step 3: Import OCC credentials
  • Step 4: Update system and user credentials (2005 only) (optional)

Step 1: Download, unzip, and create the new recipe

  1. Download and unzip the following files:
  2. Move the file custom.properties from spartacussampledata/resources/installer/customconfig to installer/customconfig.

    It is strongly recommend that you inspect this file’s settings using a text editor (see the notes below for more information). The contents of this file are listed at the end of this document for reference.

  3. In hybris/bin:
    • Create the folder custom.
    • Move the entire spartacussampledata folder to hybris/bin/custom.
  4. In the installer/recipes folder:
    • Duplicate the cx folder.
    • Change the name of the duplicate folder to cx-for-spa.
  5. In the new cx-for-spa folder:
    • Open build.gradle with a text editor.
    • Uncomment // extName 'spartacussampledata' in the list of extensions.
    • Save and close the file.

Step 2: Build and initialize the new recipe

  1. Open a terminal or command prompt window inside the installer folder.

  2. Set up the recipe using the following command:

    ./install.sh -r cx-for-spa

    If you are using Windows, change ./install.sh to install.bat.

  3. Initialize the system using the following command:

    ./install.sh -r cx-for-spa initialize

  4. Start SAP Commerce Cloud using the following command:

    ./install.sh -r cx-for-spa start

    (Using spartacussampledata and the full cx recipe, startup may take approximately 30 minutes, depending on your system.)

  5. Verify that SAP Commerce Cloud is working. To do this, you can:
    • Display the Admin Console: https://localhost:9002
    • Display Backoffice: https://localhost:9002/backoffice (can take 15-20 seconds to start the first time)
    • Display the Accelerator Electronics storefront: https://localhost:9002/yacceleratorstorefront/?site=electronics
  6. Verify that the Spartacus versions of the sample stores were created.
    • Display Backoffice.
    • Go to WCMS > Website. You should see “-spa” versions of the sample stores.

Step 3: Import OCC credentials

Spartacus uses OCC REST API calls to get information from and make changes to the backend. To do this, the backend must be configured with certain credentials.

  1. Open the Hybris Administration Console for your local SAP Commerce Cloud, in a web browser at the following address:

    https://localhost:9002

  2. Point to the Console tab, then click Impex Import.

  3. Copy-paste the following code into the Import content field.

    INSERT_UPDATE OAuthClientDetails;clientId[unique=true]    ;resourceIds       ;scope        ;authorizedGrantTypes                                            ;authorities             ;clientSecret    ;registeredRedirectUri
                                    ;client-side              ;hybris            ;basic        ;implicit,client_credentials                                     ;ROLE_CLIENT             ;secret          ;http://localhost:9001/authorizationserver/oauth2_implicit_callback;
                                    ;mobile_android           ;hybris            ;basic        ;authorization_code,refresh_token,password,client_credentials    ;ROLE_CLIENT             ;secret          ;http://localhost:9001/authorizationserver/oauth2_callback;
    
  4. Click the Import content button

You can verify that the OAuth client has been successfully defined by entering the following curl command in a terminal or command prompt window:

curl -k -d "client_id=mobile_android&client_secret=secret&grant_type=client_credentials" -X POST https://localhost:9002/authorizationserver/oauth/token

The curl command sends a POST request for an access token, using the client ID and password that you added to the back end. The command should return something similar to the following:

{
  "access_token" : "550d9a25-87c8-4e76-af21-6174a1e56d5c",
  "token_type" : "bearer",
  "expires_in" : 41809,
  "scope" : "basic openid"
}

Step 4: Update system and user credentials (2005 only) (optional)

If you are using SAP Commerce Cloud 2005, you may need to enable users and passwords for certain functionality to work.

See this help topic for more information.

All Done

You can now start Spartacus. After you have configured SAP Commerce Cloud to accept OCC REST API calls, you can set up and start your storefront. See Building the Spartacus Storefront From Libraries for more information.

Notes

General

  • Some of the steps in this procedure are derived from the documentation for installing SAP Commerce Cloud using recipes. For more information, see Installing SAP Commerce Using Installer Recipes in the SAP Help Portal.
  • The default cx recipe is used to create the recipe for Spartacus. Among other extensions, the cx recipe uses the Order Management Services feature (OMS). If you make an order, OMS doesn’t ship the order, so orders remain in processing. To ship the order, a Warehouse Agent must confirm order shipment. For more information, see the OMS documentation.

Spartacus Sample Data Extension

  • The Spartacus Sample Data extension contains both sample data modifications used by Spartacus. The extension makes a copy of the Electronics and Apparel sample stores, if present (and Powertools in a future release). If you are trying out Spartacus for the first time and intend to use the default sample data, using the Spartacus Sample Data extension is strongly recommended. However, you can use you own sample data or recipe as long as it includes extensions that support OCC APIs like commercewebservices.
  • The Spartacus Sample Data extension copies data from other storefronts, so at minimum, electronicsstore extension is required. You can also use apparelstore, and when supported in the future, powertoolstore. Note that the time to initialize is longer because SAP Commerce Cloud builds the standard stores first, then the stores for Spartacus. If you do not need all these sample stores, you can comment them out in your recipe’s build.gradle file.
  • Previous versions of the Spartacus Sample Data extension are available. Prior to Spartacus 3.0, this extension was called the Spartacus Sample Data Addon. To download the Spartacus Sample Data AddOn for the 2.0.0-next.3 release, for example, you can access the Assets section of the @spartacus/storefront@2.0.0-next.3 library here.
  • For more information about the changes that are implemented with the Spartacus Sample Data extension, see Spartacus Sample Data Extension.

Sample configuration properties

The sample custom properties file is meant for development and evaluation purposes only. Please be careful to at least review the following properties:

  • The admin password (initialpassword.admin) (default is nimda).
  • CORS settings as described further in this document, and in the Spartacus documentation.

The following table summarizes the settings included in this file:

Setting Description
initialpassword.admin Admin password so you can access the console and Backoffice
occ.rewrite.overlapping.paths.enabled Defines if certain B2B OCC calls are prefixed with ‘org’ to avoid endpoint conflicts
sop.post.url Defines where to send mock payment creation requests, so you can check out
corsfilter* Defines various CORS settings required for Spartacus functionality to work (see more information below) - note that the settings are permissive and should be changed to match your site configuration
mockup.payment.label.billTo* Defines extra state and phone number fields for payment, used by Spartacus
yacceleratorordermanagement.fraud* Increases the fraud score limits so you mock purchases are not cancelled
task.polling.interval.min Defines how long the system waits to kick off a new task - smaller values speed up order processing
build.parallel Speeds up initialization if your system has multiple cores

Sample OCC credentials

  • By default, SAP Commerce Cloud successfully replies to OCC REST API calls that do not require authentication. For example, you can do the following:
    • Display Open API documentation: https://localhost:9002/rest/v2/swagger-ui.html
    • Display information about the Electronics base store: https://localhost:9002/rest/v2/electronics/basestores/electronics

To be able to register users and check out, SAP Commerce Cloud must be configured with a client ID and password. When required, your Spartacus storefront sends this client ID and password when communicating with the back end.

  • When you import the OCC credentials ImpEx, you add the client ID mobile_android and password (or secret): secret. The values for client ID and password are samples. You would use different values for your production environments.
  • For more information on this topic, see this help topic.

CORS Settings

  • CORS settings are very important for security. We strongly recommend that a professional SAP Commerce Cloud administrator review these settings to suit your requirements, as the sample properties should not be used for production servers.
  • CORS (Cross-Origin Resource Sharing) defines a way for a browser and a server to decide which cross-origin requests for restricted resources can or cannot be allowed. Certain Spartacus functionality, such as checkout and consent management, may not work properly if the CORS OCC REST API settings are not configured properly in SAP Commerce Cloud.
  • You can add these settings using the Hybris Administration Console. Hover your mouse over the Platform tab, click Configuration, then update the CORS settings.
  • For information on Spartacus and CORS settings, see Cross-Origin Resource Sharing (CORS).
  • There are a number of other Spartacus features that also require additional CORS settings. For more information about CORS, see ycommercewebservices Extension in the SAP Help Portal.

Troubleshooting

  • If SAP Commerce Cloud installer doesn’t work, make sure there are no spaces in the path to the SAP Commerce Cloud folder.
  • If Spartacus starts or partially starts, check all CORS settings. For more information, see Cross-Origin Resource Sharing (CORS).

config.properties file

To use these settings, create a file named custom.properties inside the spartacussampledata/resources/customconfig folder, and then add the following to the file:

   initialpassword.admin=nimda
   sop.post.url=https://localhost:9002/acceleratorservices/sop-mock/process
   occ.rewrite.overlapping.paths.enabled=true
   corsfilter.default.allowedOrigins=*
   corsfilter.acceleratorservices.allowedOrigins=*
   corsfilter.permissionswebservices.allowedOrigins=*
   corsfilter.ycommercewebservices.allowedOrigins=*
   corsfilter.ycommercewebservices.allowedHeaders=origin content-type accept authorization cache-control x-anonymous-consents x-profile-tag-debug x-consent-reference
   corsfilter.ycommercewebservices.exposedHeaders=x-anonymous-consents
   corsfilter.commercewebservices.allowedOrigins=*
   corsfilter.commercewebservices.allowedHeaders=origin content-type accept authorization cache-control x-anonymous-consents x-profile-tag-debug x-consent-reference
   corsfilter.commercewebservices.exposedHeaders=x-anonymous-consents
   corsfilter.assistedservicewebservices.allowedOrigins=*
   corsfilter.assistedservicewebservices.allowedHeaders=origin content-type accept authorization cache-control x-anonymous-consents x-profile-tag-debug x-consent-reference
   corsfilter.assistedservicewebservices.exposedHeaders=x-anonymous-consents
   mockup.payment.label.billTo.region=billTo_state
   mockup.payment.label.billTo.phoneNumber=billTo_phoneNumber
   yacceleratorordermanagement.fraud.scoreLimit=500000
   yacceleratorordermanagement.fraud.scoreTolerance=500000
   yacceleratorordermanagement.fraud.scoreLimitExternal=500000
   yacceleratorordermanagement.fraud.scoreToleranceExternal=500000
   task.polling.interval.min=0
   smarteditaddon.dynamicattribute.enabled=true
   build.parallel=true