Page Comparison

WSO2 API Manager is a complete solution for publishing APIs, creating and managing a developer community and for routing API traffic in a scalable manner. It leverages the integration, security and governance components from the WSO2 Enterprise Service Bus, WSO2 Identity Server, and WSO2 Governance Registry. In addition, as it is powered by the WSO2 Business Activity Monitor (BAM), the WSO2 API Manager is ready for massively scalable deployments immediately.

...

1. Open the API Publisher (https://<hostname>:9443/publisher) and log in as apicreator.

2. Click the Add link and provide the information given in the table below. Click Implement once you are done.
   

   Field		Sample value
   Name		PhoneVerification
   Context		/phoneverify
   Version		1.0.0
   Visibility		Public
   Resources	URL pattern	CheckPhoneNumber
   	Request types	GET, POST, OPTIONS

   

3. Give the following information in the Implement tab that opens and click Manage once you are done.

   Field	Sample value
   Implementation method	Backend
   Endpoint type	HTTP
   Production endpoint	In this guide, we work with a service exposed by the Cdyne services provider. We use their phone validation service, which has SOAP and REST interfaces. Endpoint is http://ws.cdyne.com/phoneverify/phoneverify.asmx.  This sample service has two operations as CheckPhoneNumber and CheckPhoneNumbers. Let's use CheckPhoneNumber here.
   Endpoint security scheme	Non Secured (If secured, user is asked for credentials of the backend service)

   

4. Click Manage to go to the Manage tab and provide the following information. 

   Field	Value	Description
   Tier Availability	Bronze/Gold/Silver/Unlimited	The API can be available at different level of service; you can select multiple entries from the list. At subscription time, the consumer chooses which tier they are interested in.

   

   Tip
   Tip: For resources that have methods requiring authentication (i.e., Auth Type is not NONE), you set  None  as the Auth type of OPTIONS to support CORS (Cross Origin Resource Sharing) between the API Store and Gateway.

5. Once you are done, click Save and Publish. 

6. Go to the API Store (https://<hostname>:9443/store) and note that the API you just published is listed there.
   

...

1. Log in to the API Publisher as apicreator if you are not logged in already.
2. Click on the PhoneVerification API and then the Copy button that appears in its Overview tab.
   

3. Give a new version number (e.g., 2.0.0) and click Done.
   

   Tip

   Tip: The Default Version option means that you make this version the default in a group of different versions of the API. A default API can be invoked without specifying the version number in the URL. For example, if you mark http://host:port/youtube/2.0 as the default version when the API has 1.0 and 3.0 versions as well, requests made to http://host:port/youtube/ get automatically routed to version 2.0.  If you mark any version of an API as the default, you get two API URLs in its Overview page in the API Store. One URL is with the version and the other is without. You can invoke a default version using both URLs. If you mark an unpublished API as the default, the previous default, published API will still be used as the default until the new default API is published (or prototyped).

...

1. Log in to the API Publisher as apipublisher that you created earlier in this guide.
2. Click on the PhoneVerification API version 2.0.0. Note that you now see a tab by the name API life cyclelifecycle in the API Publisher UI.
3. Go to the life cycle Lifecycle tab and select the state as PUBLISHED from the drop-down list.
   
   The three checkboxes mean the following:
   
   • Propagate Changes to API Gateway: Used  Used to define an API proxy in the API Gateway runtime component, allowing the API to be exposed to the consumers via the API Gateway. If this option is left unselected, the API metadata will not change and you will have to manually configure the API Gateway according to the information published in the API the API Store.
   • Deprecate Old Versions: If  If selected, any prior versions of the API will be set to the DEPRECATED state automatically.
   • Require Re-Subscription: Invalidates  Invalidates current user subscriptions, forcing users to subscribe again.
4. 
   
   
   

...