Managing APIs Sample¶
This sample scenario elaborates as to how you can manage public vs. partner vs. private APIs with WSO2 API Manager.
The following are the use cases with regard to managing public vs. partner vs. private APIs.
Ability to use some of the APIs internally.
Ability to share a subset of the internal APIs with partners.
As a result of the latter mentioned use case, it should facilitate the development of an API ecosystems with partners across industries (e.g., ability to book a hotel and a car as well at the time of booking a flight).
Connect with APIs that are owned by your partner
Enable partners to connect with your APIs
Expose some of the APIs as public APIs to expand the business operations . Maintain a further subset of the APIs so that it can be exposed as public APIs. Many of the APIs that are used internally and with partners can be used as public APIs in order to drive additional business and help obtain new customers.
- ABC organization is an organization that has separate departments for finance and operations other than their core business department which is mobile phone manufacturing.
- The core business, finance, and operations departments are named
- The finance department handles the salaries of employees. The core department is responsible for maintaining the mobile phone manufacturing stock. The operations department handles maintenance work of the organization.
Description of each API is as follows:
Employee_info_API - Used by the core and finance departments.
Mobile_stock_API - This API is used to get details of the current mobile stock details, and is used by the core department.
Salary_details_API - This API is used to get details with regard to the salary of the employees, and is used by the finance department.
Maintenance_Task_API - An API used to get maintenance tasks required for the day.
The following user cases are related to the above mentioned sample business scenario.
The finance department (
deparment_finance)needs to get the salary of each and every employee. This data is private to the finance department.
The core department (
department_core)needs to know the details about the stocks (e.g., the current stock price). This is private to the core department.
The finance and core departments both need to know the details of the employees who are working in Core department. This data is only provided to the core and finance departments. The operations department should not be able to access the latter mentioned data.
The core department (
department_core)and the public need to know the current prices of the mobile phones.
The operations department (
department_operations) needs to know the maintenance tasks required for the day.
When a public user gets the details with regard to the price of a phone, which belongs to brand “A” and model “B”, that same user should automatically shown the prices of the phone pouches that correspond to that relevant phone model.
Running the sample¶
Run the sample as follows to populate the sample data:
Download the WSO2 API Manager sample scenarios.
Unzip the sample-scenarios ZIP file and rename the unzipped folder to
- Copy the sample-scenarios folder to the
Start the WSO2 API Manager Server.
<API-M_HOME>/sample-scenariosdirectory and execute the
Enter the scenario number as 1, when prompted.
The following are the user credentials that you need to use when signing in to the WSO2 API Manager instance that has the sample data populated.
|Finance department firstname.lastname@example.org||123123|
|Manufacturing department email@example.com||123123|
|Maintenance department firstname.lastname@example.org||123123|
Implementing the scenario¶
You need to do the following in WSO2 API Manager.
- Create three different tenants for the three departments with users that can create APIs. The screen shot below illustrates the tenants in the system. The following screen shot depicts the created APIs.
Create an API that is visible only to the tenant who is part of the finance department, in order to get the employee salary details.
The screen shot below illustrates that John can subscribe to the
Salary_details_APIas John belongs to the finance department.
The screen shot below illustrates that John can not subscribe to the
Mobile_stock_API,because John does not belong to the core manufacturing department.
3. Create an API that is visible only to the tenant who is part of the core department, in order to get the current mobile stock details. The screen shot below illustrates that Tom can subscribe to the
Mobile_stock_APIas Tom belongs to the core manufacturing department.
4. Create an API that is visible only to the tenant who is part of the operations department, in order to get the maintenance tasks that are required for the day.
Create an API subscription that is visible only to the finance and core departments, but restricted to the operations departments, in order to get the details of employees who are working in the core departments.
The screen shots below illustrates that both John and Tom can subscribe to
Employee_info_APIas they have permission to access the
6. Create an API that is publicly visible, to get mobile phone prices by exposing the API to the mobile phone prices. This API should be tagged as “mobile”.
Depending on the situation, you can specify the "Visibility on the Developer Portal " as Public, which means that the API is accessible to everyone, or you can restrict by roles, whereby the API is visible only to specific user roles in the tenant store that you specified).
Create an API to get the prices of the mobile pouches. This should also have the tag “mobile”. In this scenario, when an application client sends a request for the mobile phone prices it will also send a request to another API that has the same tag and get the relevant results. (When a user buys a mobile, it should predict the available matching mobile pouches that are for sale.)
You can invoke and check the API’s after subscribing to the relevant API’s and generating the keys.Top