The WSO2 API Manager 1.2.0 Released!

The WSO2 API Manager team is pleased to announce the release of version
1.2.0 of the Open Source API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API management challenges such as API provisioning, API governance, API
security and API monitoring. It combines some of the most powerful and
mature components of the WSO2's state-of-the-art Carbon platform to deliver
a smooth and end-to-end API management experience while catering to both
API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

   - *API provider:* Define new APIs and manage them
   - *API store:* Browse published APIs and subscribe to them
   - *API gateway:* The underlying API runtime based on WSO2 ESB

WSO2 API Manager is developed on top of the revolutionary WSO2 Carbon
platform <http://wso2.org/projects/carbon> (Middleware a' la carte), an
OSGi based framework that provides seamless modularity to your SOA via
componentization. This release also contains many new features and a range
of optional components (add-ons) that can be installed to customize the
behavior of the API Manager. Further, any existing features of the product
which are not required in your environment can be easily removed using the
underlying provisioning framework of Carbon. In brief, WSO2 API Manager can
be fully customized and tailored to meet your exact API management needs.

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also take a look at the online
product 
documentation<http://docs.wso2.org/wiki/display/AM120/WSO2+API+Manager+Documentation>
.
How to Run

   1. Extract the downloaded zip
   2. Go to the bin directory in the extracted folder
   3. Run the wso2server.sh or wso2server.bat as appropriate
   4. Launch a web browser and navigate to
http://localhost:9763/publisherto access the API provider webapp
   5. Navigate to http://localhost:9763/store to access the API store
   6. Use "admin", "admin" as the username and password to login as an admin
   7. If you need to start the OSGi console with the server use the
   property -DosgiConsole when starting the server. The INSTALL.txt file found
   on the installation directory will give you a comprehensive set of options
   and properties that can be passed into the startup script

New Features of WSO2 API Manager 1.2.0

This release of API Manager comes with a horde of new features and bug
fixes.
Bug Fixes

   - [APIMANAGER-342 <https://wso2.org/jira/browse/APIMANAGER-342>] -
   Cannot login to API-Publisher/Store when context root is present
   - [APIMANAGER-711 <https://wso2.org/jira/browse/APIMANAGER-711>] - Error
   while starting the server : after install API manager features to carbon
   - [APIMANAGER-724 <https://wso2.org/jira/browse/APIMANAGER-724>] -
   Refresh token should not re-generate new tokens for tokens marked in-active
   - [APIMANAGER-730 <https://wso2.org/jira/browse/APIMANAGER-730>] - Login
   API not stable, sometimes 60s timeout,sometimes 500 Internal Error
   - [APIMANAGER-766 <https://wso2.org/jira/browse/APIMANAGER-766>] -
   Statistics publishing database hardcoded in hive scripts
   - [APIMANAGER-770 <https://wso2.org/jira/browse/APIMANAGER-770>] -
   Default database for BAM configuration is wrong
   - [APIMANAGER-778 <https://wso2.org/jira/browse/APIMANAGER-778>] -
   Displays an error log,when trying to invoke a publsihed API through
   curl/restClient
   - [APIMANAGER-780 <https://wso2.org/jira/browse/APIMANAGER-780>] -
   Remove hard-coded user-credentials defined in site.json
   - [APIMANAGER-784 <https://wso2.org/jira/browse/APIMANAGER-784>] - Users
   are not allowed to add documents for APIs if special characters are
   included in document name
   - [APIMANAGER-786 <https://wso2.org/jira/browse/APIMANAGER-786>] - When
   we use a Hostname to bind ,APi manager throws exception
   - [APIMANAGER-790 <https://wso2.org/jira/browse/APIMANAGER-790>] - UI
   Issue of changing the label 'Sandbox' as 'Production' when generating the
   sandbox key
   - [APIMANAGER-791 <https://wso2.org/jira/browse/APIMANAGER-791>] -
   Trying to access a published API gives a blank page in Store
   - [APIMANAGER-792 <https://wso2.org/jira/browse/APIMANAGER-792>] -
   Cannot login to API Publisher webapp when the server runs with a
   WebContextRoot "Unable to log you in! Transport error: 404 Error: Not Found"
   - [APIMANAGER-797 <https://wso2.org/jira/browse/APIMANAGER-797>] - API
   MANAGER 1.1.0: NullPointerException when listing Metadata
   - [APIMANAGER-798 <https://wso2.org/jira/browse/APIMANAGER-798>] - Need
   to update apimgt server feature to enable create APIM database while
   installing APIMgt features from p2-repo
   - [APIMANAGER-799 <https://wso2.org/jira/browse/APIMANAGER-799>] -
   Duplicate module.xml
   - [APIMANAGER-800 <https://wso2.org/jira/browse/APIMANAGER-800>] - Add
   <Property name="DomainName">domain.com</Property> to the user-mgt.xml
   - [APIMANAGER-803 <https://wso2.org/jira/browse/APIMANAGER-803>] - get a
   NPE very often when logging in to AM store, when having multiple userstores
   - [APIMANAGER-805 <https://wso2.org/jira/browse/APIMANAGER-805>] -
   Cannot sign up the subscribers with same name but to different user-stores
   - [APIMANAGER-807 <https://wso2.org/jira/browse/APIMANAGER-807>] - After
   publishing an API, if we edit the api conf @ gateway..getting "Sandbox key
   offered to the API with no sandbox endpoint" error
   - [APIMANAGER-808 <https://wso2.org/jira/browse/APIMANAGER-808>] - Error
   page when viewing system logs from the wizard
   - [APIMANAGER-809 <https://wso2.org/jira/browse/APIMANAGER-809>] -
   logging in with 'userdomain/username' fails when there is only one user
   store
   - [APIMANAGER-811 <https://wso2.org/jira/browse/APIMANAGER-811>] - NPE
   when listing Metadata > APIs
   - [APIMANAGER-812 <https://wso2.org/jira/browse/APIMANAGER-812>] - NPE
   when viewing Application logs page
   - [APIMANAGER-813 <https://wso2.org/jira/browse/APIMANAGER-813>] - Users
   of the secondary user store can log in when username is given with
   <primary-user-domain>/username
   - [APIMANAGER-815 <https://wso2.org/jira/browse/APIMANAGER-815>] - Fix
   the test case for APIMgtDaoTest testGetAllAPIUsageByProvider() test case
   - [APIMANAGER-817 <https://wso2.org/jira/browse/APIMANAGER-817>] -
   Errors thrown from BAM side due to 'EVENT_KS' keyspace has not created at
   the APIM toolbox deploying time
   - [APIMANAGER-820 <https://wso2.org/jira/browse/APIMANAGER-820>] - Newly
   added permissions for 'subscriber' role getting droped after restarting the
   server

Improvements

   - [APIMANAGER-651 <https://wso2.org/jira/browse/APIMANAGER-651>] - Print
   the publisher & store URLs on console at startup
   - [APIMANAGER-690 <https://wso2.org/jira/browse/APIMANAGER-690>] -
   Provide a mechanism to upload doc content from existing files
   - [APIMANAGER-698 <https://wso2.org/jira/browse/APIMANAGER-698>] - API
   name is shown wrong in API gateway.
   - [APIMANAGER-723 <https://wso2.org/jira/browse/APIMANAGER-723>] -
   Showing multiple/older versions in the Store APIs UI
   - [APIMANAGER-745 <https://wso2.org/jira/browse/APIMANAGER-745>] -
   Ability to turn off commenting on API
   - [APIMANAGER-746 <https://wso2.org/jira/browse/APIMANAGER-746>] -
   Ability to turn off rating on API
   - [APIMANAGER-748 <https://wso2.org/jira/browse/APIMANAGER-748>] -
   Performance Improvement Fix - Thrift call between Gateway & KeyMgt nodes
   for token validation
   - [APIMANAGER-775 <https://wso2.org/jira/browse/APIMANAGER-775>] - Add
   configuration options for database ports, names, passwords in API Mgr
   Toolbox scripts
   - [APIMANAGER-787 <https://wso2.org/jira/browse/APIMANAGER-787>] - Make
   thrift server startup configurable.
   - [APIMANAGER-788 <https://wso2.org/jira/browse/APIMANAGER-788>] -
   Enable showing multiple versions and deprecated APIs in APIStore as a
   configurable option in api-manager.xml
   - [APIMANAGER-801 <https://wso2.org/jira/browse/APIMANAGER-801>] -
   Enable users from multiple user store to create, publish, subscribe and
   invoke APIs.
   - [APIMANAGER-819 <https://wso2.org/jira/browse/APIMANAGER-819>] -
   Update the UI page Users/Keys in publisher app to display access
   token/token status with subscriptions

New Features

   - [APIMANAGER-531 <https://wso2.org/jira/browse/APIMANAGER-531>] -
   Provide a means of viewing all versions of a given API
   - [APIMANAGER-769 <https://wso2.org/jira/browse/APIMANAGER-769>] -
   uri-template definition should allow to include query string
   - [APIMANAGER-818 <https://wso2.org/jira/browse/APIMANAGER-818>] - Add
   Revoke Access Token UI to publisher app

Task

   - [APIMANAGER-739 <https://wso2.org/jira/browse/APIMANAGER-739>] -
   Re-factor JWTGenerator -> generateToken

Wish

   - [APIMANAGER-774 <https://wso2.org/jira/browse/APIMANAGER-774>] -
   Support PostgreSQL deployment


   - List of resolved
issues<https://wso2.org/jira/secure/IssueNavigator.jspa?requestId=10848>

Key Features of WSO2 API Manager

Following is a categorization of the core features supported by WSO2 API
Manager based on the target user group.

   - API Publisher:
      - Publish APIs to external consumers and partners, as well as
      internal users; SOAP and REST services are supported
      - Manage API versions (several versions can be deployed in parallel)
      - Govern the API lifecycle (publish, deprecate, retire)
      - Attach documentation (files, external URLs) to APIs
      - Apply Security policies to APIs (authentication, authorization)
      - Attach SLAs
      - Provision and Manage API keys
      - Track consumers per API
      - Monitor API usage and performance, SLA compliance
      - Gather consumers requirements
   - API Consumers:
      - Find useful APIs by browsing or searching through the API Store:
      view top rated, top used and featured APIs
      - Explore API documentation and ask questions to publisher
      - Register applications and obtain API keys
      - Subscribe to API changes and receive news
      - Evaluate APIs, rate APIs, and share comments
      - Request features and improvements from publishers
      - Participate in online forums
      - OAuth2 support for API access

Known Issues

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

   - WSO2 API Manager open
issues<https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10810>

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   - Developer List : dev@wso2.org |
Subscribe<dev-requ...@wso2.org?subject=subscribe>
    | Mail Archive <http://wso2.org/mailarchive/dev/>
   - User List : u...@wso2.org |
Subscribe<user-requ...@wso2.org?subject=subscribe>
    | Mail Archive <http://wso2.org/mailarchive/user/>

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 API Manager through the publicAPI Manager
JIRA<https://wso2.org/jira/browse/APIMANAGER>.
You can use the Carbon JIRA <http://www.wso2.org/jira/browse/CARBON> to
report any issues related to the Carbon base framework or associated Carbon
components.
Support

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visithttp://wso2.com/support.

To learn more about WSO2 API Manager and WSO2 support offerings please
visit http://wso2.com/products/api-manager.

*-- The WSO2 API Manager Team --*
Thanks.
-- 
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +14084122175 | +94713068779

 <http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to