This guide walks you through how to work directly with APIs to set up an ODS with your code and data using sfcc-ci. Use a third-party IDE if preferred, for example: Prophet Debugger.
Specify a sandbox on the abcd realm with an unlimited time to live. sfcc-ci ensures the WebDAV and OCAPI permissions are pre-configured using the client_id from authentication.
sfcc-ci sandbox:create -r abcd --ttl 0
Validate your sandbox is started:
sfcc-ci sandbox:get -s [sandbox_id]
Zip up your cartridges:
Use your preferred tool to create a zip file of your cartridges. The zip should contain a top level folder with the code version name. In this folder should contain the cartridge folders.
Your .zip file name must exactly match the top level folder name inside the .zip file, for example if your code version is version1 the zip should be called version1.zip
Upload and activate your code version. For the .zip file, use the same name that you used for the code version.
Make sure the code version information used in your .zip file name exactly matches the name of the top level folder inside of the .zip file.
When importing your data, make sure your .zip file archive, also known as the “site import archive”, has the required folder structure.
If SLAS hybrid authentication fails with the error Cannot construct SLAS session-bridge URL: no ACTIVE SCAPI short code found for this organization, generate a dedicated SCAPI short code for your sandbox realm in Business Manager. See Base URL and Request Formation and Generate a Short Code and Create an API Client ID.
Next Steps
If you are using SCAPI: see
Quick Start for details on how to set up a demo using the SDK.