Onboarding and Installation
Install the Catalog Service to request and receive product data from a Commerce instance using the Catalog Service GraphQL API.
Prerequisites
The onboarding process for Catalog Service requires access to the command line of the server. If you are not familiar with working from the command line, ask a developer or system integrator to help.
Software requirements
- Adobe Commerce 2.4.4+
- PHP 8.1, 8.2
- Composer: 2.x
Supported platforms
- Adobe Commerce on cloud infrastructure: 2.4.4+
- Adobe Commerce on premises: 2.4.4+
Endpoints
Catalog Service has two endpoints available for onboarding:
- Sandbox (
https://catalog-service-sandbox.adobe.io/graphql
)—used for testing and validation before going live - Production (
https://catalog-service.adobe.io/graphql
)—used for live traffic for Commerce merchants and websites
All Commerce test instances use the Sandbox endpoint.
Perform all Load testing on the Sandbox endpoint. Before you begin load testing, submit a Support ticket so that the Services team can anticipate the additional server traffic.
Installation and configuration
To get started with Catalog Service for Adobe Commerce, the following steps are required:
- Install the data export extensions
- Configure the service and data export
- Access the service
Install the data export extensions
You must have access to the command line of the server to complete the Catalog Service onboarding process.
The Catalog Service is installed with Composer keys, which are linked to the Commerce account mageid
provided during the signup process. Composer uses these keys during the initial installation of Adobe Commerce, or in situations in which the Composer keys were not previously saved to an external auth.json
file.
See Get your authentication keys for more information about obtaining Composer keys.
The Catalog Service extension can be installed on both Adobe Commerce cloud infrastructure and on-premises instances.
Use this method to install the Catalog Service extension for a Commerce Cloud instance.
-
On your local workstation, change to the project directory for your Adobe Commerce on cloud infrastructure project.
note note NOTE For information about managing Commerce project environments locally, see Managing branches with the CLI in the Adobe Commerce on Cloud Infrastructure User Guide. -
Check out the environment branch to update using the Adobe Commerce Cloud CLI.
code language-shell magento-cloud environment:checkout <environment-id>
-
Add the Catalog Service module.
code language-bash composer require "magento/catalog-service" "^3.0.1" --no-update
-
Update package dependencies.
code language-bash composer update "magento/catalog-service"
-
Commit and push code changes for the
composer.json
andcomposer.lock
files. -
Add, commit, and push the code changes for the
composer.json
andcomposer.lock
files to the cloud environment.code language-shell git add -A git commit -m "Add catalog service module" git push origin <branch-name>
Pushing the updates initiates the Commerce cloud deployment process to apply the changes. Check the deployment status from the deploy log.
Use this method to install the Catalog Service extension for an on-premises instance.
-
Use Composer to add the Catalog Service module to your project:
code language-bash composer require "magento/catalog-service" "^3.0.1" --no-update
-
Update dependencies and install the extension:
code language-bash composer update "magento/catalog-service"
-
Upgrade Adobe Commerce:
code language-bash bin/magento setup:upgrade
-
Clear the cache:
code language-bash bin/magento cache:clean
note tip TIP In some cases, particularly when deploying to production, you might wish to avoid clearing compiled code because it can take some time. Ensure that you back up your system before making any changes.
Configure the service and data export
After you install the Catalog Service, complete the following tasks to integrate the Catalog service with your Adobe Commerce instance. This integration enables data synchronization and communication between the Commerce instance, the Catalog Service, and other supporting services.
-
Set up the Commerce Services Connector by specifying the API keys and selecting a SaaS Data Space.
Commerce Services Connector setup is a one-time process required to use Adobe Commerce services like the Catalog Service, Live Search, and Product Recommendations. If you have already configured the connector for another service, skip this step.
-
Perform an initial data sync from the Data Management Dashboard.
The initial sync could take from a few minutes to hours depending on the catalog size. You can monitor the synchronization status from the Data Management dashboard. After the initial sync, the Catalog exports product data on an ongoing basis to keep the services up to date.
To ensure that the catalog export is running correctly:
- Confirm that cron jobs are running.
- Verify that the indexers are running from the Admin or by using the Commerce CLI command
bin/magento indexer:info
. - Verify that the
Catalog Attributes Feed, Product Feed, Product Overrides Feed
, andProduct Variant Feed
indexers are set toUpdate by Schedule
.
Access the service
The Catalog Service GraphQL API is accessible from the https://catalog-service.adobe.io/graphql
endpoint using POST commands over HTTPS.
In your GraphQL queries, you must specify multiple HTTP headers including the public API key you added to the Adobe Commerce Services Connector configuration in the Admin. For details, see the Storefront Services GraphQL documentation.
Firewall configuration
To allow Catalog Service through a firewall, add commerce.adobe.io
to the allowlist.
Catalog Service and API Mesh
The API Mesh for Adobe Developer App Builder enables developers to integrate private or third-party APIs and other interfaces with Adobe products using Adobe IO.
See the Catalog Service and API Mesh topic for installation and configuration details.
Data Management Dashboard
For more information about Catalog Service data synchronization, see the Data Management Dashboard.