Re: [Architecture] [APIM][C5] New API version creation notification email feature - C5 - APIM

[Sam Sivayogam]

Hi Pubudu,

There is a Notifier interface so if anyone needs a different type of
notification then they can extend that interface and write their own
Notifier class and there should be a configuration to set the Notifier
class.

Thanks,
Sam

On Fri, Jul 21, 2017 at 1:07 AM, Pubudu Gunatilaka  wrote:

> Hi Krishan,
>
> Is this notification mechanism restricted to email? Have we considered
> other notification mechanism? If we can integrate a generic CEP output
> adapter module which supports email, sms, etc, users will be able to plug
> any notification mechanism based on their preference. Email notification
> mechanism is more suitable for new API creation use case. But in the
> future, there can be other use cases and we would need other notification
> mechanisms other than email.
>
> Thank you!
>
> On Fri, Jul 21, 2017 at 12:21 AM, Jochen Traunecker <
> jochen.traunec...@googlemail.com> wrote:
>
>> Hi,
>>
>> what about supporting webhooks in addition or is this already available?
>>
>> Thanks,
>> Jochen
>>
>> 2017-07-20 9:37 GMT+02:00 Nuwan Dias :
>>
>>> We will need to template the email content and stuff. So we'll need some
>>> sort of a configuration to store the default template and allow users to
>>> change it as needed.
>>>
>>> On Thu, Jul 20, 2017 at 12:53 PM, Krishan Wijesena 
>>> wrote:
>>>
 Hi All,

 An earlier version of APIM had enabled notifications process at the
 creation of new API versions in order to notify existing subscribers (via
 email) that a new version of the API is available.now need to implement
 this feature according to C5 APIM.


 [image: ]

 1.Check whether user enabled notification if yes I need to create
 NotificationDTO object and store data to object.

 2.Send NotificationDTO object to notifier (separate thread) through
 executor.

 3.Notifier extended NewAPIVersionEmailNotifier send emails to existing
 subscribers.

 This is the main design of the operation.This Operation can implement
 through any API.but now I call this operation from API called "create new
 version" in APIServiceImpl and using JavaMail.


 Please provide suggestions for improvements.

 Thanks & Regards.

 --

 *Krishan Wijesena*
 Software Engineer | WSO2

 Email : krish...@wso2.com
 Mobile : +94776219923 <+94%2077%20621%209923>
 WSO2 Inc : http://wso2.com
 [image: http://wso2.com/signature] 

>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Architect - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Gruss / regards
>>
>> Jochen Traunecker
>> mailto: jochen.traunec...@gmail.com
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
*Sam Sivayogam*

Senior Software Engineer
Mobile  : +94 772 906 439
Office   : +94 112 145 345
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] New API version creation notification email feature - C5 - APIM

[Pubudu Gunatilaka]

Hi Krishan,

Is this notification mechanism restricted to email? Have we considered
other notification mechanism? If we can integrate a generic CEP output
adapter module which supports email, sms, etc, users will be able to plug
any notification mechanism based on their preference. Email notification
mechanism is more suitable for new API creation use case. But in the
future, there can be other use cases and we would need other notification
mechanisms other than email.

Thank you!

On Fri, Jul 21, 2017 at 12:21 AM, Jochen Traunecker <
jochen.traunec...@googlemail.com> wrote:

> Hi,
>
> what about supporting webhooks in addition or is this already available?
>
> Thanks,
> Jochen
>
> 2017-07-20 9:37 GMT+02:00 Nuwan Dias :
>
>> We will need to template the email content and stuff. So we'll need some
>> sort of a configuration to store the default template and allow users to
>> change it as needed.
>>
>> On Thu, Jul 20, 2017 at 12:53 PM, Krishan Wijesena 
>> wrote:
>>
>>> Hi All,
>>>
>>> An earlier version of APIM had enabled notifications process at the
>>> creation of new API versions in order to notify existing subscribers (via
>>> email) that a new version of the API is available.now need to implement
>>> this feature according to C5 APIM.
>>>
>>>
>>> [image: ]
>>>
>>> 1.Check whether user enabled notification if yes I need to create
>>> NotificationDTO object and store data to object.
>>>
>>> 2.Send NotificationDTO object to notifier (separate thread) through
>>> executor.
>>>
>>> 3.Notifier extended NewAPIVersionEmailNotifier send emails to existing
>>> subscribers.
>>>
>>> This is the main design of the operation.This Operation can implement
>>> through any API.but now I call this operation from API called "create new
>>> version" in APIServiceImpl and using JavaMail.
>>>
>>>
>>> Please provide suggestions for improvements.
>>>
>>> Thanks & Regards.
>>>
>>> --
>>>
>>> *Krishan Wijesena*
>>> Software Engineer | WSO2
>>>
>>> Email : krish...@wso2.com
>>> Mobile : +94776219923 <+94%2077%20621%209923>
>>> WSO2 Inc : http://wso2.com
>>> [image: http://wso2.com/signature] 
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Gruss / regards
>
> Jochen Traunecker
> mailto: jochen.traunec...@gmail.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] New API version creation notification email feature - C5 - APIM

[Jochen Traunecker]

Hi,

what about supporting webhooks in addition or is this already available?

Thanks,
Jochen

2017-07-20 9:37 GMT+02:00 Nuwan Dias :

> We will need to template the email content and stuff. So we'll need some
> sort of a configuration to store the default template and allow users to
> change it as needed.
>
> On Thu, Jul 20, 2017 at 12:53 PM, Krishan Wijesena 
> wrote:
>
>> Hi All,
>>
>> An earlier version of APIM had enabled notifications process at the
>> creation of new API versions in order to notify existing subscribers (via
>> email) that a new version of the API is available.now need to implement
>> this feature according to C5 APIM.
>>
>>
>> [image: ]
>>
>> 1.Check whether user enabled notification if yes I need to create
>> NotificationDTO object and store data to object.
>>
>> 2.Send NotificationDTO object to notifier (separate thread) through
>> executor.
>>
>> 3.Notifier extended NewAPIVersionEmailNotifier send emails to existing
>> subscribers.
>>
>> This is the main design of the operation.This Operation can implement
>> through any API.but now I call this operation from API called "create new
>> version" in APIServiceImpl and using JavaMail.
>>
>>
>> Please provide suggestions for improvements.
>>
>> Thanks & Regards.
>>
>> --
>>
>> *Krishan Wijesena*
>> Software Engineer | WSO2
>>
>> Email : krish...@wso2.com
>> Mobile : +94776219923 <+94%2077%20621%209923>
>> WSO2 Inc : http://wso2.com
>> [image: http://wso2.com/signature] 
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <+94%2077%20777%205729>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Gruss / regards

Jochen Traunecker
mailto: jochen.traunec...@gmail.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 Stream Processor 4.0.0-M7 Released !

[Yasara Dissanayake]

Hi All,

The WSO2 Analytics team is pleased to announce the release of WSO2 Stream
Processor Version 4.0.0 Milestone 7.

WSO2 Smart Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by
WSO2 Stream
Processor's real-time, incremental & intelligent data processing
capabilities.

WSO2 Stream Processor can:

   - Receive events from various data sources
   - Process & correlate them in real-time with the sate of the art
   high-performance real-time Siddhi Complex Event Processing Engine that
   works with easy to learn the SQL-Like query language.
   - Process analysis that spans for longer time duration with its
   incremental processing capability by achieving high performance with low
   infrastructure cost.
   - Uses Machine Learning and other models to drive intelligent insights
   from the data
   - Notifications interesting event occurrences as alerts via multiple
   types of transport & let users visualize the results via customizable
   dashboards.
   - WSO2 SP is released under Apache Software License Version 2.0, one of
   the most business-friendly licenses available today.


You can find the product at
https://github.com/wso2/product-sp/releases/download/v4.0.0-M7/wso2sp-4.0.0-M7.zip

Documentation at https://docs.wso2.com/display/SP400/
Source code at https://github.com/wso2/product-sp/releases/tag/v4.0.0-M7

*WSO2 SP 4.0.0-M7 includes following*

*New Features*

   - File IO
   - Text Source/Sink Mappers.

*Improvements*

   - WSO2 Custom Maping
   - Authentication Interceptor for Siddhi-Apps API


*Reporting Issues*

Issues can be reported using the public JIRA available at https://wso2
.org/jira/browse/DAS

*Contact us*

WSO2 Stream Processor developers can be contacted via the mailing lists:

Developer List : d...@wso2.org | Subscribe
 | Mail Archive


Alternatively, questions can also be raised in the stackoverflow:

Forum http://stackoverflow.com/questions/tagged/wso2/


*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
visit http://wso2.com/support/.

For more information on WSO2 Smart Analytics and Smart Analytics Solutions,
visit the WSO2 Smart Analytics Page .

*~ The WSO2 Analytics Team ~*

-- 


*Yasara Dissanayake*
*Software Engineer*
*WSO2 Lanka (pvt) Ltd.*

*Web : http://wso2.com/ *

*Email   : yas...@gmail.com Mobile : +94702107422
<+94%2070%20210%207422>*

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Kubernetes] Improving Kubernetes Deployment Support for WSO2 Products

[Imesh Gunaratne]

On Thu, Jul 20, 2017 at 6:06 AM, Isuru Haththotuwa  wrote:

> [ += Architecture ]
>
> On Thu, Jul 20, 2017 at 2:57 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Dilan,
>>
>> Apologies for the delayed response.
>>
>> A couple of changes that I can think of:
>>
>>- Rather than using Puppet to build the Docker images, use a simple
>>copy based approach.
>>   - IMHO using puppet to build docker images is an overkill. We can
>>   have one product base images, and build the images relevant to product
>>   specific deployment patterns extending from the base image.
>>
>>
​+1 Isuru! We also had an offline discussion on this with Lakmal. Better to
make usage of Puppet optional for K8S based deployments.

Thanks
Imesh​

>
>>-
>>- Without using an intermediate set of scripts do build docker images
>>(currently we have our own docker build, run scripts), let the user
>>directly use Docker API for building images, running them, etc.
>>   - For a Docker user its more natural to use the Docker API.
>>   Additionally, there would be no need to maintain our own build scripts.
>>
>> Please share your thoughts.
>> I have started this effort for APIM the new deployment patterns discussed
>> in thread [1] in APIM group, and the WIP artifacts can be found at [2] and
>> [3]. Note that these artifacts are not finalized.
>>
>> [1]. API-M perf results to share with a customer
>> [2]. https://github.com/isurulucky/docker-apim/tree/new-deploymen
>> t-patterns
>> [3]. https://github.com/isurulucky/kubernetes-apim/tree/new-deplo
>> yment-patterns
>>
>> On Thu, Jul 13, 2017 at 7:56 PM, Dilan Udara Ariyaratne 
>> wrote:
>>
>>>
>>> -- Forwarded message --
>>> From: Dilan Udara Ariyaratne 
>>> Date: Thu, Jul 13, 2017 at 7:48 PM
>>> Subject: [Architecture] [Kubernetes] Improving Kubernetes Deployment
>>> Support for WSO2 Products
>>> To: architecture 
>>>
>>>
>>> Hi All,
>>>
>>> I am currently working on $subject. Initial idea is to deliver a fully
>>> automated, stable Kubernetes deployment experience for the end users of
>>> both WSO2 EI and APIM products
>>> such that during the process, we can understand how we can improve
>>> Kubernetes-common, the base Kubernetes deployment enabling layer as its
>>> platform.
>>>
>>> Earlier with our old product strategy, we did maintain a repository
>>> called, kubernetes-artifacts
>>>  where all the product
>>> specific artifacts were also kept.
>>>
>>> Now, we have split this out in to two levels, namely
>>> [1] kubernetes-common  -
>>> base Kubernetes deployment enabling layer
>>> [2] kubernetes-, i.e. for example, kubernetes-ei -
>>> Product specific kubernetes artifacts that integrates with kubernetes-common
>>>
>>> However, with our new product strategy and architectural changes, most
>>> of the product-specific kubernetes artifacts are not yet done and WSO2 EI,
>>> WSO2 APIM are two such products.
>>>
>>> While there is an on-going effort by Isuru (Isuruh) on finalizing
>>> kubernetes-apim related deployment artifacts, I will be working on
>>> kubernetes-ei related artifacts
>>> as an effort to improve Kubernetes Deployment Support for WSO2 Products.
>>>
>>> As mentioned above, during this process, we will be also accessing ways
>>> of improving Kubernetes-common layer for a much-developer friendly
>>> framework in building
>>> more customer centric production ready kubernetes deployment artifacts
>>> with very minimum effort.
>>>
>>> Thanks,
>>> Dilan.
>>>
>>> *Dilan U. Ariyaratne*
>>> Senior Software Engineer
>>> WSO2 Inc. 
>>> Mobile: +94766405580 <%2B94766405580>
>>> lean . enterprise . middleware
>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048 <071%20635%208048>* *
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048 <+94%2071%20635%208048>* *
>
>
>


-- 
*Imesh Gunaratne*
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IS] SCIM Support for Admin Users

[Bhathiya Jayasekara]

Hi Ishara,

On Thu, Jul 20, 2017 at 4:57 PM, Ishara Karunarathna 
wrote:

> HI Bhathiya,
>
> On Thu, Jul 20, 2017 at 4:50 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi Sathya,
>>
>> On Thu, Jul 20, 2017 at 2:34 PM, Sathya Bandara  wrote:
>>
>>> Hi all,
>>>
>>> With the current user core implementation we do not include a SCIM
>>> user_id for admin users (Since SCIM is not used in all products) which
>>> prevents SCIM based CRUD operations on admin users. In order to implement
>>> this we have identified the following two approaches.
>>>
>>> *#option 1*
>>>
>>> Generate admin users' SCIM userId in SCIM component activator at server
>>> start up (for admin users in super tenant domain). For tenant admins we can
>>> configure a listener on tenant admin creation in TenantMgtService[2] to
>>> generate user_id if SCIM is enabled.
>>>
>>
>> The super tenant case is fine, but when you use a listener for tenants,
>> if someone enable SCIM later, existing tenant admins will not be SCIM
>> compatible. To avoid that, can't we skip the "if SCIM is enabled" part of
>> your suggestion? Will that be a problem?
>>
> To support SCIM user store should support to store scim_id attribute and
> other attributes. So If they enable it later they should explicitly
> configure the IDs, Whether to support SCIM or not is a organization
> decision which should take before you setup the environments.
> And primary user store for tenants also get the configuration of supper
> tenant primary store (apart from tenant partitioning) so this should be
> fine.
>

I missed the fact that we have enabled SCIM by default in primary user
store. With that, this is fine.

Thanks,
Bhathiya


>
> -Ishara
>
>>
>> Another option is to use the same approach as super tenant. Get all
>> active tenants at component activation and set them SCIM ids. But I don't
>> think that's a good idea as it can slow down the server startup (unless you
>> do that in a seperate thread).
>>
>> Thanks,
>> Bhathiya
>>
>>
>>>
>>> *#option 2*
>>>
>>> In AbstractUserStoreManager [1] modify addInitialAdminData() operation
>>> to apply SCIM user_id claim when adding a new admin user. For the default
>>> LDAP admin we can check the already existing claims for the user_id claim
>>> and generate a random id if it doesn't exist. For tenant admins this can be
>>> done via the above mentioned listener. In this approach we expose SCIM on
>>> all the other products which do not support SCIM since we implement this at
>>> kernel level.
>>>
>>> In my opinion, option 1 would be more suitable since in this approach we
>>> do not need to additionally provide this feature on products that do not
>>> support SCIM.
>>>
>>> Highly appreciate your suggestions on this.
>>>
>>> [1] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.ws
>>> o2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/
>>> common/AbstractUserStoreManager.java#L3835
>>> [2] https://github.com/wso2/carbon-multitenancy/blob/master/comp
>>> onents/tenant-mgt/org.wso2.carbon.tenant.mgt/src/main/java/
>>> org/wso2/carbon/tenant/mgt/services/TenantMgtAdminService.java#L57
>>>
>>>
>>> Thanks,
>>> Sathya
>>> --
>>> Sathya Bandara
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com
>>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>>>
>>> <+94%2071%20411%205032>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <+94%2071%20547%208185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <071%20799%206791>
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Architecture mailing list

Re: [Architecture] [IS] SCIM Support for Admin Users

[Ishara Karunarathna]

HI Bhathiya,

On Thu, Jul 20, 2017 at 4:50 PM, Bhathiya Jayasekara 
wrote:

> Hi Sathya,
>
> On Thu, Jul 20, 2017 at 2:34 PM, Sathya Bandara  wrote:
>
>> Hi all,
>>
>> With the current user core implementation we do not include a SCIM
>> user_id for admin users (Since SCIM is not used in all products) which
>> prevents SCIM based CRUD operations on admin users. In order to implement
>> this we have identified the following two approaches.
>>
>> *#option 1*
>>
>> Generate admin users' SCIM userId in SCIM component activator at server
>> start up (for admin users in super tenant domain). For tenant admins we can
>> configure a listener on tenant admin creation in TenantMgtService[2] to
>> generate user_id if SCIM is enabled.
>>
>
> The super tenant case is fine, but when you use a listener for tenants, if
> someone enable SCIM later, existing tenant admins will not be SCIM
> compatible. To avoid that, can't we skip the "if SCIM is enabled" part of
> your suggestion? Will that be a problem?
>
To support SCIM user store should support to store scim_id attribute and
other attributes. So If they enable it later they should explicitly
configure the IDs, Whether to support SCIM or not is a organization
decision which should take before you setup the environments.
And primary user store for tenants also get the configuration of supper
tenant primary store (apart from tenant partitioning) so this should be
fine.

-Ishara

>
> Another option is to use the same approach as super tenant. Get all active
> tenants at component activation and set them SCIM ids. But I don't think
> that's a good idea as it can slow down the server startup (unless you do
> that in a seperate thread).
>
> Thanks,
> Bhathiya
>
>
>>
>> *#option 2*
>>
>> In AbstractUserStoreManager [1] modify addInitialAdminData() operation
>> to apply SCIM user_id claim when adding a new admin user. For the default
>> LDAP admin we can check the already existing claims for the user_id claim
>> and generate a random id if it doesn't exist. For tenant admins this can be
>> done via the above mentioned listener. In this approach we expose SCIM on
>> all the other products which do not support SCIM since we implement this at
>> kernel level.
>>
>> In my opinion, option 1 would be more suitable since in this approach we
>> do not need to additionally provide this feature on products that do not
>> support SCIM.
>>
>> Highly appreciate your suggestions on this.
>>
>> [1] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.ws
>> o2.carbon.user.core/src/main/java/org/wso2/carbon/user/core
>> /common/AbstractUserStoreManager.java#L3835
>> [2] https://github.com/wso2/carbon-multitenancy/blob/master/comp
>> onents/tenant-mgt/org.wso2.carbon.tenant.mgt/src/main/
>> java/org/wso2/carbon/tenant/mgt/services/TenantMgtAdminService.java#L57
>>
>>
>> Thanks,
>> Sathya
>> --
>> Sathya Bandara
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>>
>> <+94%2071%20411%205032>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <+94%2071%20547%208185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Ishara Karunarathna
Associate Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IS] SCIM Support for Admin Users

[Bhathiya Jayasekara]

Hi Sathya,

On Thu, Jul 20, 2017 at 2:34 PM, Sathya Bandara  wrote:

> Hi all,
>
> With the current user core implementation we do not include a SCIM user_id
> for admin users (Since SCIM is not used in all products) which prevents
> SCIM based CRUD operations on admin users. In order to implement this we
> have identified the following two approaches.
>
> *#option 1*
>
> Generate admin users' SCIM userId in SCIM component activator at server
> start up (for admin users in super tenant domain). For tenant admins we can
> configure a listener on tenant admin creation in TenantMgtService[2] to
> generate user_id if SCIM is enabled.
>

The super tenant case is fine, but when you use a listener for tenants, if
someone enable SCIM later, existing tenant admins will not be SCIM
compatible. To avoid that, can't we skip the "if SCIM is enabled" part of
your suggestion? Will that be a problem?

Another option is to use the same approach as super tenant. Get all active
tenants at component activation and set them SCIM ids. But I don't think
that's a good idea as it can slow down the server startup (unless you do
that in a seperate thread).

Thanks,
Bhathiya


>
> *#option 2*
>
> In AbstractUserStoreManager [1] modify addInitialAdminData() operation to
> apply SCIM user_id claim when adding a new admin user. For the default LDAP
> admin we can check the already existing claims for the user_id claim and
> generate a random id if it doesn't exist. For tenant admins this can be
> done via the above mentioned listener. In this approach we expose SCIM on
> all the other products which do not support SCIM since we implement this at
> kernel level.
>
> In my opinion, option 1 would be more suitable since in this approach we
> do not need to additionally provide this feature on products that do not
> support SCIM.
>
> Highly appreciate your suggestions on this.
>
> [1] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.
> wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/
> core/common/AbstractUserStoreManager.java#L3835
> [2] https://github.com/wso2/carbon-multitenancy/blob/master/
> components/tenant-mgt/org.wso2.carbon.tenant.mgt/src/
> main/java/org/wso2/carbon/tenant/mgt/services/TenantMgtAdmin
> Service.java#L57
>
>
> Thanks,
> Sathya
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Kubernetes] Improving Kubernetes Deployment Support for WSO2 Products

[Isuru Haththotuwa]

[ += Architecture ]

On Thu, Jul 20, 2017 at 2:57 PM, Isuru Haththotuwa  wrote:

> Hi Dilan,
>
> Apologies for the delayed response.
>
> A couple of changes that I can think of:
>
>- Rather than using Puppet to build the Docker images, use a simple
>copy based approach.
>   - IMHO using puppet to build docker images is an overkill. We can
>   have one product base images, and build the images relevant to product
>   specific deployment patterns extending from the base image.
>   - Without using an intermediate set of scripts do build docker
>images (currently we have our own docker build, run scripts), let the user
>directly use Docker API for building images, running them, etc.
>   - For a Docker user its more natural to use the Docker API.
>   Additionally, there would be no need to maintain our own build scripts.
>
> Please share your thoughts.
> I have started this effort for APIM the new deployment patterns discussed
> in thread [1] in APIM group, and the WIP artifacts can be found at [2] and
> [3]. Note that these artifacts are not finalized.
>
> [1]. API-M perf results to share with a customer
> [2]. https://github.com/isurulucky/docker-apim/tree/new-deploymen
> t-patterns
> [3]. https://github.com/isurulucky/kubernetes-apim/tree/new-deplo
> yment-patterns
>
> On Thu, Jul 13, 2017 at 7:56 PM, Dilan Udara Ariyaratne 
> wrote:
>
>>
>> -- Forwarded message --
>> From: Dilan Udara Ariyaratne 
>> Date: Thu, Jul 13, 2017 at 7:48 PM
>> Subject: [Architecture] [Kubernetes] Improving Kubernetes Deployment
>> Support for WSO2 Products
>> To: architecture 
>>
>>
>> Hi All,
>>
>> I am currently working on $subject. Initial idea is to deliver a fully
>> automated, stable Kubernetes deployment experience for the end users of
>> both WSO2 EI and APIM products
>> such that during the process, we can understand how we can improve
>> Kubernetes-common, the base Kubernetes deployment enabling layer as its
>> platform.
>>
>> Earlier with our old product strategy, we did maintain a repository
>> called, kubernetes-artifacts
>>  where all the product
>> specific artifacts were also kept.
>>
>> Now, we have split this out in to two levels, namely
>> [1] kubernetes-common  - base
>> Kubernetes deployment enabling layer
>> [2] kubernetes-, i.e. for example, kubernetes-ei -
>> Product specific kubernetes artifacts that integrates with kubernetes-common
>>
>> However, with our new product strategy and architectural changes, most of
>> the product-specific kubernetes artifacts are not yet done and WSO2 EI,
>> WSO2 APIM are two such products.
>>
>> While there is an on-going effort by Isuru (Isuruh) on finalizing
>> kubernetes-apim related deployment artifacts, I will be working on
>> kubernetes-ei related artifacts
>> as an effort to improve Kubernetes Deployment Support for WSO2 Products.
>>
>> As mentioned above, during this process, we will be also accessing ways
>> of improving Kubernetes-common layer for a much-developer friendly
>> framework in building
>> more customer centric production ready kubernetes deployment artifacts
>> with very minimum effort.
>>
>> Thanks,
>> Dilan.
>>
>> *Dilan U. Ariyaratne*
>> Senior Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048 <071%20635%208048>* *
>
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IS] SCIM Support for Admin Users

[Isura Karunaratne]

Hi Sathya,

On Thu, Jul 20, 2017 at 2:34 PM, Sathya Bandara  wrote:

> Hi all,
>
> With the current user core implementation we do not include a SCIM user_id
> for admin users (Since SCIM is not used in all products) which prevents
> SCIM based CRUD operations on admin users. In order to implement this we
> have identified the following two approaches.
>
> *#option 1*
>
> Generate admin users' SCIM userId in SCIM component activator at server
> start up (for admin users in super tenant domain). For tenant admins we can
> configure a listener on tenant admin creation in TenantMgtService[2] to
> generate user_id if SCIM is enabled.
>

+1 to this approach. For tenant admins, we can create a TenantMgtListener
and use onTenantCreate operation to create SCIM ID.

With the SCIM ID, it is required add following claims as well


   -

   urn:scim:schemas:core:1.0:meta.created

   -

   urn:scim:schemas:core:1.0:meta.lastModified

   -

   urn:scim:schemas:core:1.0:userName



Thanks
Isura.

> *#option 2*
>
> In AbstractUserStoreManager [1] modify addInitialAdminData() operation to
> apply SCIM user_id claim when adding a new admin user. For the default LDAP
> admin we can check the already existing claims for the user_id claim and
> generate a random id if it doesn't exist. For tenant admins this can be
> done via the above mentioned listener. In this approach we expose SCIM on
> all the other products which do not support SCIM since we implement this at
> kernel level.
>
> In my opinion, option 1 would be more suitable since in this approach we
> do not need to additionally provide this feature on products that do not
> support SCIM.
>
> Highly appreciate your suggestions on this.
>
> [1] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.
> wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/
> core/common/AbstractUserStoreManager.java#L3835
> [2] https://github.com/wso2/carbon-multitenancy/blob/master/
> components/tenant-mgt/org.wso2.carbon.tenant.mgt/src/
> main/java/org/wso2/carbon/tenant/mgt/services/TenantMgtAdmin
> Service.java#L57
>
>
> Thanks,
> Sathya
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>



-- 

*Isura Dilhara Karunaratne*
Senior Software Engineer | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : http://isurad.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [IS] SCIM Support for Admin Users

[Sathya Bandara]

Hi all,

With the current user core implementation we do not include a SCIM user_id
for admin users (Since SCIM is not used in all products) which prevents
SCIM based CRUD operations on admin users. In order to implement this we
have identified the following two approaches.

*#option 1*

Generate admin users' SCIM userId in SCIM component activator at server
start up (for admin users in super tenant domain). For tenant admins we can
configure a listener on tenant admin creation in TenantMgtService[2] to
generate user_id if SCIM is enabled.

*#option 2*

In AbstractUserStoreManager [1] modify addInitialAdminData() operation to
apply SCIM user_id claim when adding a new admin user. For the default LDAP
admin we can check the already existing claims for the user_id claim and
generate a random id if it doesn't exist. For tenant admins this can be
done via the above mentioned listener. In this approach we expose SCIM on
all the other products which do not support SCIM since we implement this at
kernel level.

In my opinion, option 1 would be more suitable since in this approach we do
not need to additionally provide this feature on products that do not
support SCIM.

Highly appreciate your suggestions on this.

[1] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/
org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/
AbstractUserStoreManager.java#L3835
[2] https://github.com/wso2/carbon-multitenancy/blob/
master/components/tenant-mgt/org.wso2.carbon.tenant.mgt/
src/main/java/org/wso2/carbon/tenant/mgt/services/
TenantMgtAdminService.java#L57


Thanks,
Sathya
-- 
Sathya Bandara
Software Engineer
WSO2 Inc. http://wso2.com
Mobile: (+94) 715 360 421 <+94%2071%20411%205032>

<+94%2071%20411%205032>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] New API version creation notification email feature - C5 - APIM

[Nuwan Dias]

We will need to template the email content and stuff. So we'll need some
sort of a configuration to store the default template and allow users to
change it as needed.

On Thu, Jul 20, 2017 at 12:53 PM, Krishan Wijesena 
wrote:

> Hi All,
>
> An earlier version of APIM had enabled notifications process at the
> creation of new API versions in order to notify existing subscribers (via
> email) that a new version of the API is available.now need to implement
> this feature according to C5 APIM.
>
>
> [image: ]
>
> 1.Check whether user enabled notification if yes I need to create
> NotificationDTO object and store data to object.
>
> 2.Send NotificationDTO object to notifier (separate thread) through
> executor.
>
> 3.Notifier extended NewAPIVersionEmailNotifier send emails to existing
> subscribers.
>
> This is the main design of the operation.This Operation can implement
> through any API.but now I call this operation from API called "create new
> version" in APIServiceImpl and using JavaMail.
>
>
> Please provide suggestions for improvements.
>
> Thanks & Regards.
>
> --
>
> *Krishan Wijesena*
> Software Engineer | WSO2
>
> Email : krish...@wso2.com
> Mobile : +94776219923 <+94%2077%20621%209923>
> WSO2 Inc : http://wso2.com
> [image: http://wso2.com/signature] 
>



-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [APIM][C5] New API version creation notification email feature - C5 - APIM

[Krishan Wijesena]

Hi All,

An earlier version of APIM had enabled notifications process at the
creation of new API versions in order to notify existing subscribers (via
email) that a new version of the API is available.now need to implement
this feature according to C5 APIM.


[image: ]

1.Check whether user enabled notification if yes I need to create
NotificationDTO object and store data to object.

2.Send NotificationDTO object to notifier (separate thread) through
executor.

3.Notifier extended NewAPIVersionEmailNotifier send emails to existing
subscribers.

This is the main design of the operation.This Operation can implement
through any API.but now I call this operation from API called "create new
version" in APIServiceImpl and using JavaMail.


Please provide suggestions for improvements.

Thanks & Regards.

-- 

*Krishan Wijesena*
Software Engineer | WSO2

Email : krish...@wso2.com
Mobile : +94776219923
WSO2 Inc : http://wso2.com
[image: http://wso2.com/signature] 
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5][APIM] Exposing WSDL based APIs in API Manager 3.0.0

[Shazni Nazeer]

Will uploading multiple wsdl's (unrelated) with its respective dependencies
supported?

I mean when we do that, do we plan to create multiple API's based on it?

In WSO2 Governance Registry, previously we had that support which created
multiple service artifacts.

On Thu, Jul 20, 2017 at 12:29 PM, Malintha Amarasinghe 
wrote:

> Hi,
>
> On Thu, Jul 20, 2017 at 5:36 AM, Ishara Cooray  wrote:
>
>> Hi Malintha,
>>  + for the idea as it makes more sense to the api rather than giving only
>> one POST operation.
>>
>> Currently we can create soap apis only by giving the URl of the wsdl.
>> Are we going to support create soap apis by uploading wsdl as well?
>>
> Yes Ishara. We will support uploading a single wsdl as well as uploading a
> zip archive with dependent wsdls and XSDs.
>
> Thanks!
>
>
>> Thanks & Regards,
>> Ishara Cooray
>> Senior Software Engineer
>> Mobile : +9477 262 9512 <+94%2077%20262%209512>
>> WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> On Mon, Jul 17, 2017 at 11:22 PM, Malintha Amarasinghe <
>> malint...@wso2.com> wrote:
>>
>>> Hi Maninda,
>>>
>>> If there are any POST operations defined as HTTP binding, we will make
>>> them normal HTTP POST operations. Sorry, may be my example is a bit
>>> confusing.
>>>
>>> If we take below set of operations, we will have to include HTTP POST
>>> operations as well.
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> We will be extracting:
>>>
>>>- GET /GetQuickQuote
>>>- GET /GetQuoteDataSet
>>>- POST /GetQuickQuote
>>>- POST /GetQuoteDataSet
>>>
>>>
>>>
>>> I meant to say we would use "POST /" resource only for SOAP binding
>>> operations. For example:
>>>
>>>
>>> 
>>> http://schemas.xmlsoap.org/soap/http"/>
>>> 
>>> http://ws.cdyne.com/GetQuote; style="
>>> document"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> http://ws.cdyne.com/GetQuickQuote; style="
>>> document"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> http://ws.cdyne.com/GetQuoteDataSet; style="
>>> document"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> Thanks!
>>> Malintha
>>>
>>>
>>> On Mon, Jul 17, 2017 at 4:38 PM, Maninda Edirisooriya 
>>> wrote:
>>>
 Hi Malintha,

 Why we are not making POST operations too as HTTP POST operations? As
 POST is also a HTTP verb why make it different as SOAP? Are there any more
 differences between SOAP binding that are not supported in HTTP REST like
 operations? If that is the case is it correct to move other operations
 (like GET etc.) to HTTP operations?
 Thanks.


 *Maninda Edirisooriya*
 Senior Software Engineer

 *WSO2, Inc.*lean.enterprise.middleware.

 *Blog* : http://maninda.blogspot.com/
 *E-mail* : mani...@wso2.com
 *Skype* : @manindae
 *Twitter* : @maninda

 On Thu, Jul 13, 2017 at 7:21 PM, Malintha Amarasinghe <
 malint...@wso2.com> wrote:

> Hi,
>
> In C4 based API Manager, when we create an API using a WSDL, the API
> is created with only one resource which is POST /*. We used this for
> invoking the service with SOAP payloads.
>
> But in a typical WSDL, there are several operations defined which are
> of different bindings such as SOAP and HTTP. When we look at HTTP binding
> based operations, those are a slightly similar to REST operations which
> use HTTP verbs such as GET, DELETE, PUT etc.
>
> For APIM 3.0.0 we are considering parsing those operations as well and
> automatically create resources in the API.
>
> A user can select one of below two options when creating a WSDL-based
> API. This is because it is not good to mix up both SOAP and other 
> REST-like
> (HTTP binding) operations in the same API.
>
> *1. Create a Pass-through SOAP API*
>
> If a user selects this option, an API will be created with "POST /".
> This is similar to an API Manager 2.1.0 SOAP API.
>
> *2. Create an API with HTTP binding operations*
>
> Then, the operations with HTTP binding are extracted from WSDL and
> those are used to create resources in API.
>
> For example, if we take below binding of the WSDL:
>
>    type="tns:WeatherForecastHttpGet">
> 
> 
>   
>   
> 
>   
>   
> 
>   
> 
> 
>   
>   
> 
>   
>   
> 
>   
> 
>   
>
>
> These operations can be generated based on above:
>
> GET /GetWeatherByZipCode
> GET /GetWeatherByPlaceName
>
>
> Appreciate your inputs on this.
>
> Thanks!
>
> --
> Malintha Amarasinghe
> *WSO2, Inc. - lean 

Re: [Architecture] [C5][APIM] Exposing WSDL based APIs in API Manager 3.0.0

[Malintha Amarasinghe]

Hi,

On Thu, Jul 20, 2017 at 5:36 AM, Ishara Cooray  wrote:

> Hi Malintha,
>  + for the idea as it makes more sense to the api rather than giving only
> one POST operation.
>
> Currently we can create soap apis only by giving the URl of the wsdl.
> Are we going to support create soap apis by uploading wsdl as well?
>
Yes Ishara. We will support uploading a single wsdl as well as uploading a
zip archive with dependent wsdls and XSDs.

Thanks!


> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512 <+94%2077%20262%209512>
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Mon, Jul 17, 2017 at 11:22 PM, Malintha Amarasinghe  > wrote:
>
>> Hi Maninda,
>>
>> If there are any POST operations defined as HTTP binding, we will make
>> them normal HTTP POST operations. Sorry, may be my example is a bit
>> confusing.
>>
>> If we take below set of operations, we will have to include HTTP POST
>> operations as well.
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> We will be extracting:
>>
>>- GET /GetQuickQuote
>>- GET /GetQuoteDataSet
>>- POST /GetQuickQuote
>>- POST /GetQuoteDataSet
>>
>>
>>
>> I meant to say we would use "POST /" resource only for SOAP binding
>> operations. For example:
>>
>>
>> 
>> http://schemas.xmlsoap.org/soap/http"/>
>> 
>> http://ws.cdyne.com/GetQuote; style="document
>> "/>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> http://ws.cdyne.com/GetQuickQuote; style="
>> document"/>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> http://ws.cdyne.com/GetQuoteDataSet; style="
>> document"/>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>> Thanks!
>> Malintha
>>
>>
>> On Mon, Jul 17, 2017 at 4:38 PM, Maninda Edirisooriya 
>> wrote:
>>
>>> Hi Malintha,
>>>
>>> Why we are not making POST operations too as HTTP POST operations? As
>>> POST is also a HTTP verb why make it different as SOAP? Are there any more
>>> differences between SOAP binding that are not supported in HTTP REST like
>>> operations? If that is the case is it correct to move other operations
>>> (like GET etc.) to HTTP operations?
>>> Thanks.
>>>
>>>
>>> *Maninda Edirisooriya*
>>> Senior Software Engineer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>
>>> *Blog* : http://maninda.blogspot.com/
>>> *E-mail* : mani...@wso2.com
>>> *Skype* : @manindae
>>> *Twitter* : @maninda
>>>
>>> On Thu, Jul 13, 2017 at 7:21 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Hi,

 In C4 based API Manager, when we create an API using a WSDL, the API is
 created with only one resource which is POST /*. We used this for invoking
 the service with SOAP payloads.

 But in a typical WSDL, there are several operations defined which are
 of different bindings such as SOAP and HTTP. When we look at HTTP binding
 based operations, those are a slightly similar to REST operations which
 use HTTP verbs such as GET, DELETE, PUT etc.

 For APIM 3.0.0 we are considering parsing those operations as well and
 automatically create resources in the API.

 A user can select one of below two options when creating a WSDL-based
 API. This is because it is not good to mix up both SOAP and other REST-like
 (HTTP binding) operations in the same API.

 *1. Create a Pass-through SOAP API*

 If a user selects this option, an API will be created with "POST /".
 This is similar to an API Manager 2.1.0 SOAP API.

 *2. Create an API with HTTP binding operations*

 Then, the operations with HTTP binding are extracted from WSDL and
 those are used to create resources in API.

 For example, if we take below binding of the WSDL:

   >>> type="tns:WeatherForecastHttpGet">
 
 
   
   
 
   
   
 
   
 
 
   
   
 
   
   
 
   
 
   


 These operations can be generated based on above:

 GET /GetWeatherByZipCode
 GET /GetWeatherByPlaceName


 Appreciate your inputs on this.

 Thanks!

 --
 Malintha Amarasinghe
 *WSO2, Inc. - lean | enterprise | middleware*
 http://wso2.com/

 Mobile : +94 712383306 <071%20238%203306>

>>>
>>>
>>
>>
>> --
>> Malintha Amarasinghe
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>


-- 
Malintha Amarasinghe
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

Mobile : +94 712383306