You can share an API to application developers who are subscribed to the API Stores of other tenants. This allows you to advertize your APIs to a wider community. Subscribers of other tenant stores can view and browse your APIs but to subscribe to them, the users must visit your (the original publisher's) store.
The capability to publish to external API Stores is not configured by default. Follow the steps below to configure it. In this guide, we use two separate instances of the API Manager and we publish from one instance to the Store of the other instance.
- Copy the API Manager product pack to two different locations.
Go to the
<APIM_HOME>/repository/conf/carbon.xmlfile of the second instance and change its port by an offset of 1. You do this to avoid the port conflicts that occur when you run more than one WSO2 product on the same host.
Tip: Please check whether the Thrift port under the
<ThriftServerPort>elements are changed according to the port offset in the
<APIM_HOME>/repository/conf/api-manager.xmlfile. The default Thrift port is 10397.
- Start both servers. Let's publish from the first instance of the API Manager to the Store of the second instance.
- Log in to APIM admin console of the first instance (
https://<Server Host>:9443/carbon) as admin. In a multitenant environment, you must log in using the tenant's credentials.
- Click Main> Resources > Browse.
The Registry opens. Go to the
Click the Edit as Text link, uncomment the
<StoreURL>element under the
<ExternalAPIStores>element and add details of each external API store that you need to publish APIs to. In this example,
http://localhost:9764/storeis the API Store of the second API Manager instance.
- You publish to its super tenant's Store (admin/admin).
- The port is 9764 as you incremented it by 1 earlier.
- If the second API Manager instance has multiple tenants and you want to publish to a tenant's Store, the tenant's Store URL and credentials must be given here.
- Click Save Content.
If you want to cofigure more than one external store, change the configuration in <ExternalAPIStore> and add it to the external-api-stores.xml.
For example if we have three API Stores one is super tenant and other two are tenant stores, we can configure these three external stores as below.
In a multitenant environment, each tenant can publish to different external Stores by changing the above file in their tenant space. For more information on how APIs appear and are available for subscription in a multitenant environment, see API visibility and subscription. Note that publishing to an external Store only means that the API is advertised there. To subscribe, you must always register and log in to the original publisher's tenant Store.
Note the following in the configuration above:
<ExternalAPIStore id="" type="" className="">
id: The external store identifier, which is a unique value.
type: The type of the Store. This can be a WSO2-specific API Store or an external one.
className: The implementation class inside the API Manager distribution.
The URL of the API store of the current APIM deployment. This is the URL to the API in the original publisher's store. APIs that are published to external stores are redirected to this URL.
The name of the Store that is displayed in the publisher UI.
The URL of the API Store.
The credentials of a user who has permissions to create and publish APIs.
Registry changes are applied dynamically. You do not need to restart the server.
Log in to the API Publisher of the first instance as admin/admin and create an API. In a multitenant environment, log in to the API Publisher using your tenant's credentials.
Click on the newly created API to see a new tab called External API Stores added to the API Publisher console. Select the Store that you want to publish to (in this case, Store1) and click Save.
Note the following:
- You can select multiple external API stores and click Save to publish your API to them.
- If the API creator updates the API after publication to external stores, either the creator or a publisher can simply push those changes to the published stores by selecting the stores and clicking Save again.
- If the API creator deletes the API, each external store that it is published to receives a request to delete the API.
Log in to an external API Store (in this case,
A link appears as Visit Publisher Store, which directs you to the original publisher’s store (in this case,
http://localhost:9763/store) through which you can subscribe to the API.
You have added multiple external stores to your registry and published your APIs to them.