![]() |
VOOZH | about |
The CData API Server enables you to access Adobe Commerce data from cloud-based applications like the Salesforce console and mobile applications like the Salesforce1 Mobile App. In this article, you will use the API Server and Salesforce Connect to access Adobe Commerce external objects alongside standard Salesforce objects.
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Adobe Commerce OData services:
To work with Adobe Commerce data from Salesforce Connect, we start by creating and configuring a Adobe Commerce connection. Follow the steps below to configure the API Server to connect to Adobe Commerce data:
Adobe Commerce uses the OAuth 1 authentication standard. To connect to the Adobe Commerce REST API, obtain values for the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties by registering an app with your Adobe Commerce system. See the "Getting Started" section in the help documentation for a guide to obtaining the OAuth values and connecting.
You will also need to provide the URL to your Adobe Commerce system. The URL depends on whether you are using the Adobe Commerce REST API as a customer or administrator.
Customer: To use Adobe Commerce as a customer, make sure you have created a customer account in the Adobe Commerce homepage. To do so, click Account -> Register. You can then set the URL connection property to the endpoint of your Adobe Commerce system.
Administrator: To access Adobe Commerce as an administrator, set CustomAdminPath instead. This value can be obtained in the Advanced settings in the Admin menu, which can be accessed by selecting System -> Configuration -> Advanced -> Admin -> Admin Base URL.
If the Use Custom Admin Path setting on this page is set to YES, the value is inside the Custom Admin Path text box; otherwise, set the CustomAdminPath connection property to the default value, which is "admin".
Next, create a user to access your Adobe Commerce data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the Adobe Commerce tables:
Having configured a connection to Adobe Commerce data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsFollow the steps below to connect to the feed produced by the API Server.
URL: Enter the URL to the OData endpoint of the API Server. The format of the OData URL is https://your-server:your-port/api.rsc.
Note that plain-text is suitable for only testing; for production, use TLS.
Select JSON in the Format menu.
After you have created the external data source, follow the steps below to create Adobe Commerce external objects that reflect any changes in the data source. You will synchronize the definitions for the Adobe Commerce external objects with the definitions for Adobe Commerce tables.
After adding Adobe Commerce data as an external data source and syncing Adobe Commerce tables with Adobe Commerce external objects, you can use the external objects just as you would standard Salesforce objects.
Create a new tab with a filter list view:
π A filtered list view shown on a custom tab. (NetSuite Invoices are shown.)Display related lists of Adobe Commerce external objects alongside standard Salesforce objects:
π A related list that shows an indirect lookup relationship, which links a child external object to a parent standard object. (Salesforce accounts and associated NetSuite invoices are shown.)You can use the following checklist to avoid typical connection problems:
Ensure that the server you are hosting the API Server on is using TLS 1.1 or above. If you are using the .NET API Server, you can accomplish this by using the .NET API Server's embedded server.
If you are using IIS, TLS 1.1 and 1.2 are supported but not enabled by default. To enable these protocols, refer to the how-to on MSDN and the Microsoft technical reference.
If you are using the Java edition, note that TLS 1.2 is enabled by default in Java 8 but not in Java 6 or 7. If you are using these earlier versions, you can refer to this this Oracle how-to.
Learn more or sign up for a free trial:
CData API Server