Anypoint API Experience Hub Unmanaged Package Post Installation Instructions
After installing the Revenium Anypoint API Experience Hub (AEH) Package, some configuration is needed before you can use it in your organization.
Last updated
After installing the Revenium Anypoint API Experience Hub (AEH) Package, some configuration is needed before you can use it in your organization.
Last updated
Make sure that .
First of all, you need to make sure your users in AEH are assigned to a in Anypoint Platform with the following permissions:
Exchange
Exchange Viewer
API Manager
Manage Contracts View Contracts
Table 1. Anypoint's Team configuration.
If you would not like to receive the default Anypoint email notifications .
Go to Setup > Tabs, and under Custom Object Tabs, click on New (Figure 1).
In the Custom Object Tab form (Figure 2) select Revenium URL in the object field.
Select a Tab style, add a meaningful description, and click on Next.
Restrict the access to this tab to meet your Customer's needs and click on Save.
In the Custom Object Tab form (Figure 2) select Revenium API Key in the object field.
Select a Tab style, add a meaningful description, and click on Next.
Restrict the access to this tab to meet your Customer's needs and click on Save.
Navigate to the Revenium URL Custom Tab you created in Step 2 and click on New (Figure 3).
Create a Revenium URL, as described in Table 2.
Revenium API URL
Yes
API
Table 2. Revenium URL configuration.
Navigate to the Revenium API Keys Custom Tab you created in Step 2 and click on New (Figure 4).
Create a Revenium API Key, as described in Table 3.
Revenium API Key
User who will use the API Key
Table 3. Revenium API Key configuration.
Go to Setup > Security > Trusted URLs and click on New Trusted URL (Figure 5).
Create the required Trusted Sites as described in Table 4.
Revenium_API_URL
Yes
All
Allow site for connect-src, Allow site for frame-src
Stripe_API
Yes
All
Allow site for connect-src, Allow site for frame-src
Google_Pay
Yes
All
Allow site for connect-src, Allow site for frame-src
Raygun_API
Yes
All
Allow site for connect-src
Revenium_CDN
Yes
All
Allow site for img-src
Salesforce_Maps
Yes
All
Allow site for connect-src, Allow site for frame-src
Table 4. Revenium API Key configuration.
Go to Setup > Security > Remote Site Settings and click on New Remote Site (Figure 8).
Create the required Remote Sites as described in Table 5.
Revenium_API_URL
Yes
Yes
Table 5. Revenium API Key configuration.
When using the Revenium Anypoint API Experience Hub Package with a Salesforce Profile different from System Administrator or API Experience Hub Member User, you need to assign the Permission Set Revenium Subscriber to the Subscribers under that profile in order to make it work. To do this, go to Setup > Permission Sets > Revenium Subscriber > Manage Assignments (Figure 9). After that, assign the corresponding Subscribers to it and click Next (Figure 10). Finally, select an expiration date if appropriate and click Assign (Figure 11).
In Salesforce Setup, enter sites in the Quick Find box and select All Sites.
Next to the site that you want to access, click Builder.
In Experience Builder, click the Settings icon and select General.
Under Guest Subscriber Profile, click the guest Subscriber profile link (Figure 11).
In the Field-Level Security section you can set the Read/Edit access for the Current RM Org field from the Subscriber object (Figure 12). Moreover, in this profile menu you will see the options to enable access to Apex Classes, Custom Objects and Named Credentials listed in Table 5 (Figure 13).
In order to access products or APIs from Revenium's components in your site you need to add them from AEH's API manager. To do that, click on API Experience Hub in your Anypoint account and then add the products/APIs you want from Exchange, as shown in Figures 14 and 15.
To ensure a smooth workflow for Subscribers requesting access to your API bundles, it's essential to include the "View Available Products" button directly on your Community Source detail page (Figure 18).
By placing this component on an sources details page, a button will appear that will do two things, 1) return the Subscriber to the catalog page including the “Drop-In Storefront” component, 2) filter the list of displayed products in the displayed storefront to show only products that contain the source on the original page that the user was browsing.
This allows Subscribers who are interested in using a particular API to understand which products they can purchase that include that API. By having the button readily available, Subscribers can efficiently access the storefront and request access to the desired API bundles within a single, streamlined experience.
Resources
URL provided by Revenium staff. Default is:
.
Finally, .
You will also need to create a Sharing Rule to grant access to the Custom Objects to a certain group of Subscribers. To do this, you should navigate to Setup > Sharing Settings > Revenium API Key Sharing Rules (and Revenium URL Sharing Rules). You can see the following link to learn more about. For example, if you want to share the records owned by a certain role with all the Subscribers in the portal with a particular role assigned, you would need to define it in this way (Figure 13):
If you allowed Guest Subscribers in your organization (and have followed the instructions in #7), you need to add Sharing Rules for the Experience Site Guest subscriber as outlined .
Check that the visibility of your APIs is set to Everyone, otherwise your portal member will not be able to access your APIs. You can do this from the APIs in the portal tab. .
You also need to provide the API name of the page your storefront is located . By default, the API Access Requester button redirects you to the Home page of your Experience Cloud site.
