forked from wso2/product-apim
-
Notifications
You must be signed in to change notification settings - Fork 0
/
release-notes.html
373 lines (344 loc) · 18 KB
/
release-notes.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
~
~ WSO2 Inc. licenses this file to you under the Apache License,
~ Version 2.0 (the "License"); you may not use this file except
~ in compliance with the License.
~ You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~ KIND, either express or implied. See the License for the
~ specific language governing permissions and limitations
~ under the License.
-->
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta content="text/html; charset=iso-8859-1" http-equiv="content-type"/>
<title>WSO2 API Manager v1.10.0 - 7th January 2016</title>
</head>
<body>
<div id="main-content">
<h1>The WSO2 API Manager 1.10.0 Released!</h1>
<p>
The WSO2 API Manager team is pleased to announce the release of version 1.10.0 of
the Open Source API Manager.
</p>
<p>
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.
</p>
<p>
WSO2 API Manager is comprised of several modules.
</p>
<ul>
<li><b>API Provider:</b> Define new APIs and manage them</li>
<li><b>API Store:</b> Browse published APIs and subscribe to them</li>
<li><b>API Gateway:</b> The underlying API runtime based on WSO2 ESB</li>
<li><b>API Key Manager:</b> Performs Key Generation and Key Validation functionalities</li>
</ul>
<p>
WSO2 API Manager is developed on top of the revolutionary
<a href="http://wso2.org/projects/carbon">WSO2 Carbon platform</a>
(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.
</p>
<p>
For more information on WSO2 API Manager please visit <a href="http://wso2.com/products/api-manager">
http://wso2.com/products/api-manager</a>. Also take a look at the online product
<a href="https://docs.wso2.com/display/AM1100/WSO2+API+Manager+Documentation">documentation</a>.
</p>
<h2>How to Run</h2>
<ol>
<li>Extract the downloaded zip</li>
<li>Go to the bin directory in the extracted folder</li>
<li>Run the wso2server.sh or wso2server.bat as appropriate</li>
<li>Launch a web browser and navigate to <a href="https://localhost:9443/publisher">https://localhost:9443/publisher</a>
to access the API provider webapp
</li>
<li>Navigate to <a href="https://localhost:9443/store">https://localhost:9443/store</a> to access the API store</li>
<li>Navigate to <a href="https://localhost:9443/admin-dashboard">https://localhost:9443/admin-dashboard</a> to access Admin dashboard</li>
<li>Use "admin", "admin" as the username and password to login as an admin</li>
</ol>
<h2>New Features in 1.10.0</h2>
<ul>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-509'>APIMANAGER-509</a>] - Provide means to search tags
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-647'>APIMANAGER-647</a>] - Provide a better UI than selecting from a drop down list to deal with lifecycle states of an API with publisher UI
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3705'>APIMANAGER-3705</a>] - Add HTTP method "PATCH" support to API-M
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3979'>APIMANAGER-3979</a>] - Support Digest auth protected enpoint as a back end URL.
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4027'>APIMANAGER-4027</a>] - Enabling users to invoke APIs when the throttle limit has exceeded
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4034'>APIMANAGER-4034</a>] - Making the backend endpoint/url optional
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4179'>APIMANAGER-4179</a>] - Support reverse proxy for API manager admin-dashboard application
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4192'>APIMANAGER-4192</a>] - Set a throttling hard limit per API
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4262'>APIMANAGER-4262</a>] - REST API for publisher and there we are exposing a resource "/tiers"
</li>
</ul>
<h2>Improvements in 1.10.0</h2>
<ul>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-2166'>APIMANAGER-2166</a>] - DB2 Support
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-2514'>APIMANAGER-2514</a>] - [APIM Migration] Improve instructions in README.txt for default embedded h2 db
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-2553'>APIMANAGER-2553</a>] - Review the REST API
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-2661'>APIMANAGER-2661</a>] - uri templates are allowed to be saved with invalid characters
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-2687'>APIMANAGER-2687</a>] - Forum content and reply editting
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3364'>APIMANAGER-3364</a>] - Set correct registry permissions when the Publisher/Subscriber roles have been created by an external Identity Server
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3591'>APIMANAGER-3591</a>] - Throttle Policy management Enhacements
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3638'>APIMANAGER-3638</a>] - Make order of execution of APIManagerExtensionHandler and APIAuthenticationHandler configurable at each tenant
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3951'>APIMANAGER-3951</a>] - Store and return audit meta data for artifacts that are created or modified via published API calls
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3958'>APIMANAGER-3958</a>] - OAuth2 SCOPE value is not available in message path. It is better to set it as property?
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-3978'>APIMANAGER-3978</a>] - /userinfo end point can be deployed as default API in the Gateway.
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4112'>APIMANAGER-4112</a>] - [Store REST API] New API to return APIs by tag
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4114'>APIMANAGER-4114</a>] - Renaming locations to which the store/publisher apps are being copied at build time
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4124'>APIMANAGER-4124</a>] - High number of DB calls going from Gateway to the database if default api is selected.
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4144'>APIMANAGER-4144</a>] - Fix the issue in API Migration client when we have blocked APIs
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4146'>APIMANAGER-4146</a>] - Integrate registry lifecycle with APIM 1.10.0
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4189'>APIMANAGER-4189</a>] - Introduce IDs for fields to enable EnjoyHint capabilities for the cloud tutorial
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4217'>APIMANAGER-4217</a>] - Sufficient Audit logs should be included for main activities in publisher, store
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4383'>APIMANAGER-4383</a>] - Change the error message into a meaningful one that get after exceeding the hard throttling limit in APIM logs.
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4392'>APIMANAGER-4392</a>] - Its better to make the wildcard charater mandatory for the publisher REST API query
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4393'>APIMANAGER-4393</a>] - APIM is not sending "Access-Control-Allow-Credentials" header in response.
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4413'>APIMANAGER-4413</a>] - Include different error codes when throttling out in different throttling levels
</li>
<li>[<a href='https://wso2.org/jira/browse/APIMANAGER-4414'>APIMANAGER-4414</a>] - Add log messages to indicate when DAS reconnected with APIM and when DAS disconnected with APIM
</li>
</ul>
<h2>Resolved Issues</h2>
<ul>
<li>
<a href="https://wso2.org/jira/issues/?filter=12597">WSO2 API Manager V1.10.0 resolved issues</a>
</li>
</ul>
<h2>Key Features of WSO2 API Manager</h2>
<p>
Following is a categorization of the core features supported by WSO2 API Manager
based on the target user group.
</p>
<ul>
<li>Create a Store of all Available APIs:
<ul>
<li>Graphical experience similar to Android Marketplace or Apple App Store.</li>
<li>Browse APIs by provider, tags or name.</li>
<li>Self-registration to developer community to subscribe to APIs.</li>
<li>Subscribe to APIs and manage subscriptions on per-application basis.</li>
<li>Subscriptions can be at different service tiers based on expected usage levels.</li>
<li>Role based access to API Store; manage public and private APIs.</li>
<li>Manage subscriptions at a per-developer level.</li>
<li>Browse API documentation, download helpers for easy consumption.</li>
<li>Comment on and rate APIs.</li>
<li>Forum for discussing API usage issues (Available soon in future version).</li>
<li>Try APIs directly on the store front.</li>
<li>Internationalization (i18n) support.</li>
</ul>
</li>
<li>Publishing and Governing API Use:
<ul>
<li>Publish APIs to external consumers and partners, as well as internal users.</li>
<li>Supports publishing multiple protocols including SOAP, REST, JSON and XML style services as APIs.</li>
<li>Manage API versions and deployment status by version.</li>
<li>Govern the API lifecycle (publish, deprecate, retire).</li>
<li>Attach documentation (files, external URLs) to APIs.</li>
<li>Apply Security policies to APIs (authentication, authorization).</li>
<li>Associate API available to system defined service tiers.</li>
<li>Provision and Manage API keys.</li>
<li>Track consumers per API.</li>
<li>One-click deployment to API Gateway for immediate publishing.</li>
</ul>
</li>
<li>Route API Traffic:
<ul>
<li>Supports API authentication with OAuth2.</li>
<li>Extremely high performance pass-through message routing with sub-millisecond latency.</li>
<li>Enforce rate limiting and throttling policies for APIs by consumer.</li>
<li>Horizontally scalable with easy deployment into cluster using proven routing infrastructure.</li>
<li>Scales to millions of developers/users.</li>
<li>Capture all statistics and push to pluggable analytics system.</li>
<li>Configure API routing policies with capabilities of WSO2 Enterprise Service Bus.</li>
<li>Powered by WSO2 Enterprise Service Bus.</li>
</ul>
</li>
<li>Manage Developer Community:
<ul>
<li>Self-sign up for API consumption.</li>
<li>Manage user account including password reset.</li>
<li>Developer interaction with APIs via comments and ratings.</li>
<li>Support for developer communication via forums (Available soon in future version).</li>
<li>Powered by WSO2 Identity Server.</li>
</ul>
</li>
<li>Govern Complete API Lifecycle:
<ul>
<li>Manage API lifecycle from cradle to grave: create, publish, block, deprecate and retire.</li>
<li>Publish both production and sandbox keys for APIs to enable easy developer testing.</li>
<li>Publish APIs to partner networks such as ProgrammableWeb (Available soon in future version).</li>
<li>Powered by WSO2 Governance Registry.</li>
</ul>
</li>
<li>Monitor API Usage and Performance:
<ul>
<li>All API usage published to pluggable analytics framework.</li>
<li>Out of the box support for WSO2 Business Activity Monitor and Google Analytics.</li>
<li>View metrics by user, API and more.</li>
<li>Customized reporting via plugging reporting engines.</li>
<li>Monitor SLA compliance.</li>
<li>Powered by WSO2 Business Activity Monitor.</li>
</ul>
</li>
<li>Pluggable, Extensible and Themeable:
<ul>
<li>All components are highly customizable thru styling, theming and open source code.</li>
<li>Storefront implemented with Jaggery (jaggeryjs.org) for easy customization.</li>
<li>Pluggable to third party analytics systems and billing systems (Available soon in future version).</li>
<li>Pluggable to existing user stores including via JDBC and LDAP.</li>
<li>Components usable separately - storefront can be used to front APIs gatewayed via third party gateways such as Intel Expressway Service Gateway.</li>
<li>Support for Single Sign On (SSO) using SAML 2.0 for easy integration with existing web apps</li>
</ul>
</li>
<li>Easily Deployable in Enterprise Setting:
<ul>
<li>Role based access control for managing users and their authorization levels.</li>
<li>Store front can be deployed in DMZ for external access with Publisher inside the firewall for private control.</li>
<li>Different user stores for developer focused store-front and internal operations in publisher.</li>
<li>Integrates with enterprise identity systems including LDAP and Microsoft Active Directory.</li>
<li>Gateway can be deployed in DMZ with controlled access to WSO2 Identity Server (for authentication/authorization) and governance database behind firewall.</li>
</ul>
</li>
<li>Support for creating multi-tenanted APIs
<ul>
<li>Run a single instance and provide API Management to multiple customers</li>
<li>Share APIs between different departments in a large enterprise</li>
</ul>
</li>
<li>Publishing and Governing API Use
<ul>
<li>Document an API using Swagger</li>
<li>Restrict API Access tokens to domains/IPs</li>
<li>Ability to block a subscription and restricting a complete application</li>
<li>Ability to revoke access tokens</li>
<li>Separate validity period configuration for Application Access Token</li>
<li>OAuth2 Authorization Code Grant Type Support</li>
<li>Configuring execution point of mediation extensions</li>
</ul>
</li>
<li>Monitor API Usage and Performance
<ul>
<li>Improved dashboard for monitoring usage statistics (Filtering data for a date range, More visually appealing widgets)</li>
</ul>
</li>
</ul>
<h2>Known Issues</h2>
<p>
All the open issues pertaining to WSO2 API Manager are reported at the following
location:
</p>
<ul>
<li>
<a href="https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10810">
Known Issues
</a>
</li>
</ul>
<h2>How You Can Contribute</h2>
<h3>
Mailing Lists
</h3>
<p>
Join our mailing list and correspond with the developers directly.
</p>
<ul>
<li>
Developer List :
<a href="mailto:dev@wso2.org">dev@wso2.org</a>
|
<a href="mailto:dev-request@wso2.org?subject=subscribe">Subscribe</a>
|
<a href="http://wso2.org/mailarchive/dev/">Mail Archive</a>
</li>
<li>
User List :
<a href="mailto:user@wso2.org">user@wso2.org</a>
|
<a href="mailto:user-request@wso2.org?subject=subscribe">Subscribe</a>
|
<a href="http://wso2.org/mailarchive/user/">Mail Archive</a>
</li>
</ul>
<h3>
Reporting Issues
</h3>
<p>
We encourage you to report issues, documentation faults and feature requests
regarding
WSO2 API Manager through the public <a href="https://wso2.org/jira/browse/APIMANAGER">API Manager
JIRA</a>. You
can use the
<a href="http://www.wso2.org/jira/browse/CARBON">Carbon JIRA</a>
to report any
issues related to the Carbon base framework or associated Carbon components.
</p>
<h2>Support</h2>
<p>
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.
</p>
<p>
For more details and to take advantage of this unique opportunity please
visit <a href="http://wso2.com/support">http://wso2.com/support</a>.
</p>
<p>
To learn more about WSO2 API Manager and WSO2 support offerings please visit
<a href="http://wso2.com/products/api-manager/">http://wso2.com/products/api-manager</a>.
</p>
<p>
<i>-- The WSO2 API Manager Team --</i>
</p>
</div>
</body>
</html>