Install the B2B for Adobe Commerce extension

1. Change to your Adobe Commerce installation directory and enter the following command to update your composer.json file and install the B2B for Adobe Commerce extension:

   composer require magento/extension-b2b:<version>
   

   NOTE

   The Compatible B2B extension version must be specified in the command, which can be found in the left column of the compatibility table.

   If you get an error when trying to install the B2B extension for a local instance of Adobe Commerce for example:

   [InvalidArgumentException] Could not find a matching version of package magento/extension-b2b.
   

   Check the package spelling, your version constraint, and that the package is available and matches your minimum-stability (stable).

   If not already defined globally in your COMPOSER_HOME, you must create an auth.json file in the root directory and add the following code, using the actual values of your public_key and private_key for username and password:

   {
      "http-basic": {
         "repo.magento.com": {
            "username": "<public_key>",
            "password": "<private_key>"
         }
      }
   }
   

2. When prompted, enter your authentication keys.

   Your public key is your username; your private key is your password. If you have stored your public and private keys in auth.json, you aren’t asked to enter them here.

3. Run the following commands after Composer finishes updating modules:

   bin/magento setup:upgrade
   

   bin/magento setup:di:compile
   

   bin/magento setup:static-content:deploy -f
   

   bin/magento cache:clean
   

Message consumers

The B2B for Adobe Commerce extension uses MySQL for message queue management. Start the corresponding message consumers for the needed B2B features after installation.

Start message consumers

1. List the available message consumers:

   bin/magento queue:consumers:list
   

   You should see the following consumers:

   sharedCatalogUpdatePrice
   sharedCatalogUpdateCategoryPermissions
   quoteItemCleaner
   inventoryQtyCounter
   async.operations.all
   

2. Start each consumer separately:

   bin/magento queue:consumers:start <consumer_name>
   

   For example:

   bin/magento queue:consumers:start sharedCatalogUpdatePrice
   

Refer to Manage message queues in the Configuration Guide for more information.

Add message consumers to cron

You can also add these two message consumers to the cron job (optional) by adding the following lines in your crontab:

* * * * * ps ax | grep [s]haredCatalogUpdateCategoryPermissions >>/dev/null 2>&1 || nohup php /var/www/html/magento2/bin/magento queue:consumers:start sharedCatalogUpdateCategoryPermissions &
* * * * * ps ax | grep [s]haredCatalogUpdatePrice >>/dev/null 2>&1 || nohup php /var/www/html/magento2/bin/magento queue:consumers:start sharedCatalogUpdatePrice &

Specify parameters for message consumers

Depending on your system configuration, to prevent possible issues, specify the following parameters when starting the services:

• --max-messages: manages the consumer’s lifetime and allows you to specify the maximum number of messages processed by the consumer. The best practice for a PHP application is to restart long-running processes to prevent possible memory leaks.

• --batch-size: allows you to limit the system resources consumed by the consumers (CPU, memory). Using smaller batches reduces resource usage and, thus, leads to slower processing.

Enable B2B features in the Admin

After installing the B2B for Adobe Commerce extension and starting message consumers (if you want to enable the Shared Catalog feature), you must also enable B2B features in the Admin.

Business.Adobe.com resources