Re: [Dev] APIM CLI simplify endpoint url configs

[Rukshan Premathunga]

>
> I guess you are referring to the Microgateway CLI and not the APIM CLI.

Yes. It should be Microgateway CLI


On Mon, Jun 18, 2018 at 11:15 AM, Nuwan Dias  wrote:

> I guess you are referring to the Microgateway CLI and not the APIM CLI.
>
> On Mon, Jun 18, 2018 at 11:11 AM, Rukshan Premathunga 
> wrote:
>
>> Hi All,
>>
>> Currently CLI auto generate endpoints from defautl values and user have
>> to edit it in order to work if endpoints are diffrent. As a solution we
>> thought to provide urls as arguments for setup command.
>> But here we have 4 endpoints(store, publisher, admin and token) to get as
>> arguments. But making all of them as  mandatory, user experience may get
>> reduce, So we need to have a mechanism to derive them.
>>
>> One option is to use one host for apps in same node(store, pub, admin).
>> If it is changed, provide the optional arguments to override them.
>>
>> So can you also share some idea please.
>>
>> Thanks and Regards
>> --
>>
>> Rukshan Chathuranga.
>> WSO2, Inc.
>> +94711822074
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIM CLI simplify endpoint url configs

[Nuwan Dias]

I guess you are referring to the Microgateway CLI and not the APIM CLI.

On Mon, Jun 18, 2018 at 11:11 AM, Rukshan Premathunga 
wrote:

> Hi All,
>
> Currently CLI auto generate endpoints from defautl values and user have to
> edit it in order to work if endpoints are diffrent. As a solution we
> thought to provide urls as arguments for setup command.
> But here we have 4 endpoints(store, publisher, admin and token) to get as
> arguments. But making all of them as  mandatory, user experience may get
> reduce, So we need to have a mechanism to derive them.
>
> One option is to use one host for apps in same node(store, pub, admin). If
> it is changed, provide the optional arguments to override them.
>
> So can you also share some idea please.
>
> Thanks and Regards
> --
>
> Rukshan Chathuranga.
> WSO2, Inc.
> +94711822074
>



-- 
Nuwan Dias

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

[Dev] APIM CLI simplify endpoint url configs

[Rukshan Premathunga]

Hi All,

Currently CLI auto generate endpoints from defautl values and user have to
edit it in order to work if endpoints are diffrent. As a solution we
thought to provide urls as arguments for setup command.
But here we have 4 endpoints(store, publisher, admin and token) to get as
arguments. But making all of them as  mandatory, user experience may get
reduce, So we need to have a mechanism to derive them.

One option is to use one host for apps in same node(store, pub, admin). If
it is changed, provide the optional arguments to override them.

So can you also share some idea please.

Thanks and Regards
-- 

Rukshan Chathuranga.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release of WSO2 Stream Processor 4.2.0 RC1

[Nisala Nanayakkara]

Hi all,

We are calling off this vote as we found some issues with the rc1. We will
do a rc2 and call the vote.

Thanks,
Nisala

On Sat, Jun 16, 2018 at 12:24 PM Nisala Nanayakkara  wrote:

> Hi all,
>
> WSO2 Stream Processor team is pleased to announce the first release
> candidate of WSO2 Stream Processor 4.2.0.
>
> *WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
> platform, of which the real-time, incremental & intelligent data processing
> capabilities let digital businesses create actionable business insights and
> data products.*
>
> Please find the improvements and fixes related to this release here
> 
> .
>
> You can find the source and distribution here
> 
>
> The tag to be voted upon:
> https://github.com/wso2/product-sp/tree/v4.2.0-rc1
> 
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> *- WSO2 Stream Processor Team -*
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Senior Software Engineer
> Mobile | +94 717600022
> WSO2 Inc | http://wso2.com/
>


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CORS Error

[Prakhash Sivakumar]

On Fri, Jun 15, 2018 at 5:21 PM Farasath Ahamed  wrote:

>
>
> On Thu, Jun 14, 2018 at 3:32 PM, shibsankar  wrote:
>
>> *grant_type=password.*
>>
>>
>>
>> For your convenience, I  am providing the Angular JS relevant code
>>
>>
>> *// from Angular Controller js*
>>
>> var dataObj="
>> grant_type=password=x=x=openid";
>>
>>  Service.callTokenAPI(dataObj)
>> .then(function onSuccess(response) {
>> console.log("Success");
>> console.log("result  = " + JSON.stringify(response));
>> }, function onFailure(error) {
>> console.log("failure");
>> });
>>
>>
>>
>> *//from Service.js*
>>
>> var callTokenAPI = function (dataObj) {
>> console.log("Call server dataObj =" + angular.toJson(dataObj));
>> var secret=clientKey+":"+clientPass;
>> var base64Encoded= btoa(secret);
>> console.log("base64Encoded="+base64Encoded);
>> return $http({
>> url: tokenAPI,
>> method: 'POST',
>> data: dataObj,
>> headers: { "Content-Type": "application/json;charset=utf-8"
>> ,"Authorization":base64Encoded}
>> });
>> };
>>
>>
> Can you try setting the 'content-type' header to
> 'application/x-www-form-urlencoded'? (Check [1])
>
> [1]
> https://security.stackexchange.com/questions/187311/why-cors-preflight-is-not-available-for-post-requests-when-content-type-is-appli/187312#187312
>

This should work. Also I think the reason for your observation is when
adding CORS related configs in tokenapi.xml and revokeapi.xml files, the
CORS allowing is not getting applied for the inbound and outbound requests
which uses 8280 and 8243 ports, just to confirm can you please try allowing
9443 for this and make this call ?

>
>
>>
>> When I  run this I am getting CORS error screenshot shared earlier.
>>
>> Regards
>> Shib
>>
>>
>> On Thu, Jun 14, 2018 at 3:00 PM, Rushmin Fernando 
>> wrote:
>>
>>> Could you please let us know the grant type you are using here. I would
>>> like to know whether this is a valid use case.
>>>
>>> On Thu, Jun 14, 2018 at 2:54 PM shibsankar  wrote:
>>>
 Yes.  I get  same CORS error with the correct endpoint, which is */*
 *token*

 screenshot attached.

 Regards
 Shib

 On Thu, Jun 14, 2018 at 2:42 PM, Rushmin Fernando 
 wrote:

> In the console logs, it says */toekn, *which is wrong spellings.
>
> Do you get the same CORS error with the correct endpoint, which is 
> */**token
> *?
>
> On Thu, Jun 14, 2018 at 2:26 PM shibsankar  wrote:
>
>> I am receiving CORS Error when I call the WSO2 token API  from
>> Angular JS application.
>>
>> How do you fix this?
>>
>> Regards
>> Shib(9831418066)
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>

>>>
>>> --
>>> *Best Regards*
>>>
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> mobile : +94775615183
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Farasath Ahamed
> Senior Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Prakhash Sivakumar
Senior Software Engineer | WSO2 Inc
Platform Security Team
Mobile : +94771510080
Blog : https://medium.com/@PrakhashS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

[Heshitha Hettihewa]

Hi All,

I've tested the following,

   - JMS Inbound endpoint
   - ESB Analytics component Data publishing and Dashboard improvements
   - Business process profile basic functionalities with BPMN Explorer
   - Devstudio tooling BPMN Editor
   - Devstudio tooling Humantask Editor
   - Devstudio tooling EI 630 server feature and artifact deployment
   through dev studio
   - Basic Devstudio tooling ESB functionalities
   - Management console basic UI functionalities

No blockers found.

[+] Stable - go ahead and release

Thanks,
Heshitha.


On Sun, Jun 17, 2018 at 10:18 PM, Nandika Jayawardana 
wrote:

> Hi All,
>
> Tested the following.
>
> Tested the sample deployment, execution and un deployment of business
> process profile BPEL, BPMN and HumanTasks.
>
> Tested micro integrator profile vfs and jms functionality.
>
> Also tested developer studio for ESB solution project, inbound endpoints.
>
> [+] Stable - go ahead and release
>
> Regards
> Nandika
>
> On Sun, Jun 17, 2018 at 3:03 PM, Maryam Ziyad  wrote:
>
>> Hi All,
>>
>> Tested the following:
>>
>>- ESB profile as JMS queue sender/receiver, topic
>>publisher/subscriber (proxy services), with the Broker profile
>>- JMS producer caching with and without specifying a destination in
>>axis2.xml, for the ESB profile
>>- Simple secured proxy services
>>- Response on requests to non-existent services
>>
>> [+] Stable - go ahead and release
>>
>> Thank you,
>> Maryam
>>
>> On Sun, Jun 17, 2018 at 11:04 AM, Chanika Geeganage 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the following scenarios
>>>
>>>- Basic tests on dataservices samples
>>>- Dataservices REST requests including batch requests with JSON
>>>- Dataservices tasks
>>>- JSON path eval in EI profile
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks
>>>
>>> On Sat, Jun 16, 2018 at 3:09 PM, Nirothipan Mehalingam <
>>> nirothi...@wso2.com> wrote:
>>>
 Hi all,

 I have tested the following,

- Adding a new user and log in using newly created user.
- Deploying a simple custom class mediator as an OSGi bundle and
validating the flow.
- Enabling debug logs via the management console.
- Adding scheduled task via management console and via carbon apps.
- Deploying carbon apps in micro-integrator profile and
validating the deployments and the artifacts.
- Adding inline throttle policy and validating the flow.


 [+] Stable - go ahead and release

 Thanks.
 Nirothipan


 On Sat, Jun 16, 2018 at 12:57 PM, Isuru Udana  wrote:

> Hi All,
>
> Did basic tests of all artifact types in both Integrator and Micro
> Integrator profiles using artifacts created from EI Tooling.
>
> [+] Stable - go ahead and release
>
> Thanks.
>
>
> On Sat, Jun 16, 2018 at 12:07 PM Thishani Lucas 
> wrote:
>
>> Hi All,
>>
>> Tested the following in both ESB profile and Micro Integrator profile.
>>
>>- Store and forward with scheduled forwarding processor and JMS
>>message store in the Broker profile.
>>- Sampling message processor.
>>- JMS inbound endpoint.
>>- File inbound endpoint (vfs).
>>- Mail-To transport using a listener proxy.
>>- Constructing and sending multipart form data.
>>- Publishing stats to the Analytics profile.
>>- Basic functionalities of some mediators and endpoints.
>>
>> [+] Stable - Go ahead and release.
>>
>> Thanks,
>> Thishani
>>
>> On Sat, Jun 16, 2018 at 11:46 AM Lahiru Madushanka <
>> lahirum...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> Tested the following
>>>
>>> Ubuntu Windows
>>> Test EI micro-integrator EI + MI
>>> JMS inbound endpoint ✓ ✓ ✓
>>> JMS listener proxy ✓ ✓ ✓
>>> JMS publisher proxy ✓ ✓ ✓
>>> JMS message Store ✓ ✓ ✓
>>> JMS transaction and rollback ✓ ✓
>>> Message sampling processor ✓ ✓ ✓
>>> Class mediator ✓ ✓ ✓
>>> Data Mapper mediator (using CAPP) ✓ ✓
>>>
>>> Smoke test management console of all profiles in windows
>>> ✓
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> Lahiru
>>>
>>> On Sat, Jun 16, 2018 at 1:11 AM Malaka Gangananda 
>>> wrote:
>>>
 Hi All,

 We are pleased to announce the second release candidate of WSO2
 Enterprise Integrator 6.3.0.

 Known issues: https://github.com/wso2/product-ei/issues

 Source and binary distribution files:
 https://github.com/wso2/product-ei/releases/tag/v6.3.0-rc2

 The tag to be voted upon: https://github.com/wso2/produc
 t-ei/tree/v6.3.0-rc2

 Please vote as follows:
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 ~The WSO2 

Re: [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC1

[Chamin Dias]

Hi,

We are closing the vote due to the blocker.

On Sun, Jun 17, 2018 at 7:43 PM, Prasanna Dangalla 
wrote:

> Hi All,
>
> [-] Broken - do not release
>
> We found a blocker[1] in RC1 distribution. Hence -1 for the RC1.
>
> [1] - https://github.com/wso2/carbon-apimgt/issues/5493
>
> Thanks
> *Prasanna Dangalla*
> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> We will fix the issue and release another release candidate as soon as
possible.

Thanks

>
> *cell: +94 718 11 27 51*
> *twitter: @prasa77*
>
>
> On Sat, Jun 16, 2018 at 2:05 AM Chamin Dias  wrote:
>
>> Hi all,
>>
>> We are pleased to announce the first release candidate of WSO2 API
>> Manager 2.5.0.
>>
>> This release fixes the following issues.
>>
>>- Fixes : carbon-apimgt
>>
>> 
>>- Fixes : product-apim
>>
>> 
>>- Fixes : analytics-apim
>>
>> 
>>
>> Source and distribution,
>> Runtime : https://github.com/wso2/product-apim/releases/tag/v2.5.0-
>> rc1
>> Analytics : https://github.com/wso2/analytics-apim/releases/tag/v2.5.
>> 0-rc1
>>
>> Please download, test the product and vote.
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> WSO2 API Manager Team
>>
>> --
>> Chamin Dias
>> Mobile : 0716097455
>> Email : cham...@wso2.com
>> LinkedIn : https://www.linkedin.com/in/chamindias
>>
>>


-- 
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

[Nandika Jayawardana]

Hi All,

Tested the following.

Tested the sample deployment, execution and un deployment of business
process profile BPEL, BPMN and HumanTasks.

Tested micro integrator profile vfs and jms functionality.

Also tested developer studio for ESB solution project, inbound endpoints.

[+] Stable - go ahead and release

Regards
Nandika

On Sun, Jun 17, 2018 at 3:03 PM, Maryam Ziyad  wrote:

> Hi All,
>
> Tested the following:
>
>- ESB profile as JMS queue sender/receiver, topic publisher/subscriber
>(proxy services), with the Broker profile
>- JMS producer caching with and without specifying a destination in
>axis2.xml, for the ESB profile
>- Simple secured proxy services
>- Response on requests to non-existent services
>
> [+] Stable - go ahead and release
>
> Thank you,
> Maryam
>
> On Sun, Jun 17, 2018 at 11:04 AM, Chanika Geeganage 
> wrote:
>
>> Hi All,
>>
>> I have tested the following scenarios
>>
>>- Basic tests on dataservices samples
>>- Dataservices REST requests including batch requests with JSON
>>- Dataservices tasks
>>- JSON path eval in EI profile
>>
>> [+] Stable - go ahead and release
>>
>> Thanks
>>
>> On Sat, Jun 16, 2018 at 3:09 PM, Nirothipan Mehalingam <
>> nirothi...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the following,
>>>
>>>- Adding a new user and log in using newly created user.
>>>- Deploying a simple custom class mediator as an OSGi bundle and
>>>validating the flow.
>>>- Enabling debug logs via the management console.
>>>- Adding scheduled task via management console and via carbon apps.
>>>- Deploying carbon apps in micro-integrator profile and
>>>validating the deployments and the artifacts.
>>>- Adding inline throttle policy and validating the flow.
>>>
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks.
>>> Nirothipan
>>>
>>>
>>> On Sat, Jun 16, 2018 at 12:57 PM, Isuru Udana  wrote:
>>>
 Hi All,

 Did basic tests of all artifact types in both Integrator and Micro
 Integrator profiles using artifacts created from EI Tooling.

 [+] Stable - go ahead and release

 Thanks.


 On Sat, Jun 16, 2018 at 12:07 PM Thishani Lucas 
 wrote:

> Hi All,
>
> Tested the following in both ESB profile and Micro Integrator profile.
>
>- Store and forward with scheduled forwarding processor and JMS
>message store in the Broker profile.
>- Sampling message processor.
>- JMS inbound endpoint.
>- File inbound endpoint (vfs).
>- Mail-To transport using a listener proxy.
>- Constructing and sending multipart form data.
>- Publishing stats to the Analytics profile.
>- Basic functionalities of some mediators and endpoints.
>
> [+] Stable - Go ahead and release.
>
> Thanks,
> Thishani
>
> On Sat, Jun 16, 2018 at 11:46 AM Lahiru Madushanka <
> lahirum...@wso2.com> wrote:
>
>> Hi all,
>>
>> Tested the following
>>
>> Ubuntu Windows
>> Test EI micro-integrator EI + MI
>> JMS inbound endpoint ✓ ✓ ✓
>> JMS listener proxy ✓ ✓ ✓
>> JMS publisher proxy ✓ ✓ ✓
>> JMS message Store ✓ ✓ ✓
>> JMS transaction and rollback ✓ ✓
>> Message sampling processor ✓ ✓ ✓
>> Class mediator ✓ ✓ ✓
>> Data Mapper mediator (using CAPP) ✓ ✓
>>
>> Smoke test management console of all profiles in windows
>> ✓
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Lahiru
>>
>> On Sat, Jun 16, 2018 at 1:11 AM Malaka Gangananda 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are pleased to announce the second release candidate of WSO2
>>> Enterprise Integrator 6.3.0.
>>>
>>> Known issues: https://github.com/wso2/product-ei/issues
>>>
>>> Source and binary distribution files: https://github.com/wso2/produc
>>> t-ei/releases/tag/v6.3.0-rc2
>>>
>>> The tag to be voted upon: https://github.com/wso2/produc
>>> t-ei/tree/v6.3.0-rc2
>>>
>>> Please vote as follows:
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> ~The WSO2 Integration Team~
>>>
>>> Thanks,
>>>
>>>
>>> --
>>> Malaka.
>>> --
>>> Malaka Gangananda - Software Engineer | WSO2
>>> Email : mala...@wso2.com
>>> Mobile : +94713564340
>>> Web : http://wso2.com
>>>   
>>> ___
>>> 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
>>
>
>
> --
> *Thishani Lucas*
> *Software Engineer*
> *WSO2 Lanka (Private) Limited**: http://wso2.com *
> 

Re: [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC1

[Prasanna Dangalla]

Hi All,

[-] Broken - do not release

We found a blocker[1] in RC1 distribution. Hence -1 for the RC1.

[1] - https://github.com/wso2/carbon-apimgt/issues/5493

Thanks
*Prasanna Dangalla*
Senior Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware


*cell: +94 718 11 27 51*
*twitter: @prasa77*


On Sat, Jun 16, 2018 at 2:05 AM Chamin Dias  wrote:

> Hi all,
>
> We are pleased to announce the first release candidate of WSO2 API Manager
> 2.5.0.
>
> This release fixes the following issues.
>
>- Fixes : carbon-apimgt
>
> 
>- Fixes : product-apim
>
> 
>- Fixes : analytics-apim
>
> 
>
> Source and distribution,
> Runtime : https://github.com/wso2/product-apim/releases/tag/v2.5.0-rc1
> Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.5.0-rc1
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 API Manager Team
>
> --
> Chamin Dias
> Mobile : 0716097455
> Email : cham...@wso2.com
> LinkedIn : https://www.linkedin.com/in/chamindias
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

[Maryam Ziyad]

Hi All,

Tested the following:

   - ESB profile as JMS queue sender/receiver, topic publisher/subscriber
   (proxy services), with the Broker profile
   - JMS producer caching with and without specifying a destination in
   axis2.xml, for the ESB profile
   - Simple secured proxy services
   - Response on requests to non-existent services

[+] Stable - go ahead and release

Thank you,
Maryam

On Sun, Jun 17, 2018 at 11:04 AM, Chanika Geeganage 
wrote:

> Hi All,
>
> I have tested the following scenarios
>
>- Basic tests on dataservices samples
>- Dataservices REST requests including batch requests with JSON
>- Dataservices tasks
>- JSON path eval in EI profile
>
> [+] Stable - go ahead and release
>
> Thanks
>
> On Sat, Jun 16, 2018 at 3:09 PM, Nirothipan Mehalingam <
> nirothi...@wso2.com> wrote:
>
>> Hi all,
>>
>> I have tested the following,
>>
>>- Adding a new user and log in using newly created user.
>>- Deploying a simple custom class mediator as an OSGi bundle and
>>validating the flow.
>>- Enabling debug logs via the management console.
>>- Adding scheduled task via management console and via carbon apps.
>>- Deploying carbon apps in micro-integrator profile and
>>validating the deployments and the artifacts.
>>- Adding inline throttle policy and validating the flow.
>>
>>
>> [+] Stable - go ahead and release
>>
>> Thanks.
>> Nirothipan
>>
>>
>> On Sat, Jun 16, 2018 at 12:57 PM, Isuru Udana  wrote:
>>
>>> Hi All,
>>>
>>> Did basic tests of all artifact types in both Integrator and Micro
>>> Integrator profiles using artifacts created from EI Tooling.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks.
>>>
>>>
>>> On Sat, Jun 16, 2018 at 12:07 PM Thishani Lucas 
>>> wrote:
>>>
 Hi All,

 Tested the following in both ESB profile and Micro Integrator profile.

- Store and forward with scheduled forwarding processor and JMS
message store in the Broker profile.
- Sampling message processor.
- JMS inbound endpoint.
- File inbound endpoint (vfs).
- Mail-To transport using a listener proxy.
- Constructing and sending multipart form data.
- Publishing stats to the Analytics profile.
- Basic functionalities of some mediators and endpoints.

 [+] Stable - Go ahead and release.

 Thanks,
 Thishani

 On Sat, Jun 16, 2018 at 11:46 AM Lahiru Madushanka 
 wrote:

> Hi all,
>
> Tested the following
>
> Ubuntu Windows
> Test EI micro-integrator EI + MI
> JMS inbound endpoint ✓ ✓ ✓
> JMS listener proxy ✓ ✓ ✓
> JMS publisher proxy ✓ ✓ ✓
> JMS message Store ✓ ✓ ✓
> JMS transaction and rollback ✓ ✓
> Message sampling processor ✓ ✓ ✓
> Class mediator ✓ ✓ ✓
> Data Mapper mediator (using CAPP) ✓ ✓
>
> Smoke test management console of all profiles in windows
> ✓
> [+] Stable - go ahead and release
>
> Thanks,
> Lahiru
>
> On Sat, Jun 16, 2018 at 1:11 AM Malaka Gangananda 
> wrote:
>
>> Hi All,
>>
>> We are pleased to announce the second release candidate of WSO2
>> Enterprise Integrator 6.3.0.
>>
>> Known issues: https://github.com/wso2/product-ei/issues
>>
>> Source and binary distribution files: https://github.com/wso2/produc
>> t-ei/releases/tag/v6.3.0-rc2
>>
>> The tag to be voted upon: https://github.com/wso2/produc
>> t-ei/tree/v6.3.0-rc2
>>
>> Please vote as follows:
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> ~The WSO2 Integration Team~
>>
>> Thanks,
>>
>>
>> --
>> Malaka.
>> --
>> Malaka Gangananda - Software Engineer | WSO2
>> Email : mala...@wso2.com
>> Mobile : +94713564340
>> Web : http://wso2.com
>>   
>> ___
>> 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
>


 --
 *Thishani Lucas*
 *Software Engineer*
 *WSO2 Lanka (Private) Limited**: http://wso2.com *
 *lean.enterprise.middle-ware*

 *Tel: +94 77 2556931 *

 *LinkedIn: https://www.linkedin.com/in/thishani-lucas/
 *


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

>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>>
>>>