[Dev] WSO2 API Manager 2.1.0-update2 Released!

[Ishara Cooray]

The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update2 of 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
   -

   API Key Manager: Performs Key Generation and Key Validation
   functionalities
   -

   API Traffic Manager: Performs Rate Limiting of API Requests

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also take a look at the online
product documentation
.

Distributions

WSO2 APIM 2.1.0-update2.zip


WSO2 APIM Analytics 2.1.0-update2.zip

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 https://localhost:9443/publisher to
   access the API publisher webapp
   5.

   Navigate to https://localhost:9443/store to access the API store
   6.

   Navigate to https://localhost:9443/admin to access Admin Portal
   7.

   Use "admin", "admin" as the username and password to login as an admin

Bug Fixes And Improvements in 2.1.0-update2

Please refer [1] and [2] for WSO2 API Manager 2.1.0-update2 Bug fixes and
Improvements

[1]  JIRA 

[2]  GitHub 

Known Issues

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

 [1]   JIRA 

 [2]   GitHub

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

   Developer List : dev@wso2.org | Subscribe | Mail Archive
   
   -

   User List : u...@wso2.org | Subscribe | Mail Archive
   
   -

   User Forum : Stack Overflow
   

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 API Manager through the public API Manager JIRA
. You can use the Carbon JIRA
 to report any issues related to
the Carbon base framework or associated Carbon components.

-- The WSO2 API Manager Team --



Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512 <+94%2077%20262%209512>
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stream Processor Editor - Removing .siddhi file extension from showing on the ui

[Damith Wickramasinghe]

Hi All,

Yes +1 . I will inc-operate the changes .

Regards,
Damith

On Fri, Dec 8, 2017 at 6:57 PM, Ramindu De Silva  wrote:

> Hi all,
>
> +1 for Erangas suggestion.
> We may need to remove the ".siddhi" postfix from ".siddhi" in save to
> file placeholder as well. Currently, we, either way, add .siddhi extension
> when saving the file.
>
> Best Regards,
> Ramindu.
>
> On Fri, Dec 8, 2017 at 11:16 AM, Eranga Liyanage  wrote:
>
>> Hi All,
>>
>> Yes, we can show the .siddhi extension on workspace tree.
>>
>> Users first interaction with the file is either Save, Open, or Import. On
>> those interfaces also we show that it's a .siddhi extension file, so users
>> won't get confused by removing it from the tab.
>>
>> Best regards.
>> Eranga
>>
>> On Fri, Dec 8, 2017 at 7:18 AM, Jason De Silva  wrote:
>>
>>> Hi Damith / Eranga,
>>>
>>> If I am the user I would like to know the extension of the file. So +1
>>> to at least show the .siddhi extension in workspace tree/dropdown if we are
>>> removing it from the tabs.
>>>
>>> Regards,
>>> Jason
>>>
>>> Jason De Silva
>>> *Software Engineer - QA*
>>> Mobile: +94 (0) 772 097 678
>>> Email: jas...@wso2.com
>>> WSO2 Inc. www.wso2.com
>>> 
>>>
>>> On Fri, Dec 8, 2017 at 6:19 AM, Damith Wickramasinghe 
>>> wrote:
>>>
 Hi Eranga,

 I understand your point but my only issue is not conveying user that
 these files use .siddhi extension. So shall we at least keep the .siddhi
 extension in workspace dropdown as we are showing the actual files there.
 So that user knows it. And we can remove the .siddhi extensions in tabs.
 WDYT ?

 Regards,
 Damith

 On Thu, Dec 7, 2017 at 11:42 AM, Eranga Liyanage 
 wrote:

> Hi Damith,
>
> In editors usually, we can edit multiple file types. So when the
> respective file is opened it shows the file type with it for easy
> identification.
>
> But in our case, we support only .siddhi files and we open files from
> our own workspace which contains only siddhi files. Many single file type
> applications usually do not show its file type on UI.
>
> In the Stream Processor Editor, we usually open multiple siddhi files
> and in the tab area, it takes unnecessary space to show the .siddhi
> extension. IMHO it's better to hide it from tab section.
>
> [image: Inline image 1]
>
> We can show the .siddhi extension on workspace tree and other file
> open/import etc. modals.
>
> WDYT?
>
> Best regards,
> Eranga
>
>
> On Thu, Dec 7, 2017 at 8:48 AM, Damith Wickramasinghe <
> dami...@wso2.com> wrote:
>
>> Hi Eranga/ All,
>>
>> In stream processor we support only files with .siddhi extension.
>> Even though it is the case IMO user needs to know that the file should 
>> have
>> .siddhi extension. Because one can just copy paste a file to workspace
>> directory of editor without adding the .siddhi extension when he see only
>> files without extension created. And having it there also will not make 
>> any
>> UX issues as I see it. Please raise any concerns if we need to 
>> accommodate
>> this requirement.
>>
>> Regards,
>> Damith
>>
>> --
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315 <+94%2072%20867%201315>*
>>
>>
>
>
> --
> *Eranga Liyanage*
> Senior UX Engineer | WSO2
> Mob : +94 77 395 
> Blog : https://medium.com/@erangatl
> Linkedin : https://www.linkedin.com/in/erangaliyanage
>
>


 --
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 
 lean.enterprise.middleware

 mobile: *+94728671315 <+94%2072%20867%201315>*


>>>
>>
>>
>> --
>> *Eranga Liyanage*
>> Senior UX Engineer | WSO2
>> Mob : +94 77 395 
>> Blog : https://medium.com/@erangatl
>> Linkedin : https://www.linkedin.com/in/erangaliyanage
>>
>>
>
>
> --
> *Ramindu De Silva*
> Software Engineer
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> email: ramin...@wso2.com 
> mob: +94 719678895
>



-- 
Senior Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

mobile: *+94728671315*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Add asset information with multivalue attributes using Governance REST API

[Chandana Napagoda]

Hi,

It seems that the code is written in a way that, adding and retrieval of
the unbounded tables fields are not supported.  So we might have to change
some codes to support this requirement.

Regards,
Chandana

Blog: http://blog.napagoda.com
Linkedin: https://www.linkedin.com/in/chandananapagoda/

On 7 December 2017 at 18:56, Saneth Dharmakeerthi  wrote:

> Hi Prasanna,
>
> Thanks for the investigation help. I tried to GET request in GREG 530 it
> also not returning the unbounded table values (multivalue tables). it
> seems this issue is there in both GET and POST in GREG 530
>
>
> Thanks and Best Regards,
>
> Saneth Dharmakeerthi
> *Associate Technical Lead*
> WSO2, Inc.
> Mobile: +94772325511 <+94%2077%20232%205511>
>
> 
>
> On Thu, Dec 7, 2017 at 12:32 PM, Prasanna Dangalla 
> wrote:
>
>> HI All,
>>
>> Saneth and I Investigated this issue and it seems to be the POST request
>> cannot send unbounded table field values. But I remember fixing this in GET
>> requests. [1,2].
>>
>> [1] - https://github.com/wso2/carbon-governance/pull/103/
>> 
>> [2] - https://github.com/wso2/carbon-governance/pull/242/files
>>
>> Thanks
>>
>> *Prasanna Dangalla*
>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>>
>> *cell: +94 718 11 27 51*
>> *twitter: @prasa77*
>>
>> On Wed, Dec 6, 2017 at 2:54 PM, Saneth Dharmakeerthi 
>> wrote:
>>
>>> Hi,
>>>
>>> I am writing a client to import asset information to GREG using
>>> Governance REST API [1].
>>> If assert has multivalue tables I wonder how we can include them in the
>>> POST request.
>>>
>>> Appreciate your feedback on how can I accomplish this task.
>>>
>>>
>>>
>>> [1] https://docs.wso2.com/display/Governance500/Governance+REST+API
>>>
>>>
>>> Thanks and Best Regards,
>>>
>>> Saneth Dharmakeerthi
>>> *Associate Technical Lead*
>>> WSO2, Inc.
>>> Mobile: +94772325511 <+94%2077%20232%205511>
>>>
>>> 
>>>
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev