[Architecture] WSO2 Product Installation Resources Released!!!

[Vimukthi Perera]

WSO2 Installation Experience team is pleased to announce the release of
Ansible, AWS, Docker, Kubernetes, Puppet and Vagrant resources for WSO2
products.
Ansible

Related artifacts:

   -

   WSO2 Identity Server v5.8.0 -
   https://github.com/wso2/ansible-is/releases/tag/v5.8.0.1
   -

   WSO2 Stream Processor v4.4.0 -
   https://github.com/wso2/ansible-sp/releases/tag/v4.4.0.1
   -

   WSO2 Enterprise Integrator v6.5.0 -
   https://github.com/wso2/ansible-ei/releases/tag/v6.5.0.1


Issues:

   -

   WSO2 Identity Server - https://github.com/wso2/ansible-is/issues
   -

   WSO2 Stream Processor - https://github.com/wso2/ansible-sp/issues
   -

   WSO2 Enterprise Integrator - https://github.com/wso2/ansible-ei/issues

AWS

Related artifacts:

   -

   WSO2 Identity Server v5.8.0 -
   https://github.com/wso2/aws-is/releases/tag/v5.8.0.2
   -

   WSO2 Stream Processor v4.4.0 -
   https://github.com/wso2/aws-sp/releases/tag/v4.4.0.2
   -

   WSO2 Enterprise Integrator v6.5.0 -
   https://github.com/wso2/aws-ei/releases/tag/v6.5.0.2


Issues:

   -

   WSO2 Identity Server - https://github.com/wso2/aws-is/issues
   -

   WSO2 Stream Processor - https://github.com/wso2/aws-sp/issues
   -

   WSO2 Enterprise Integrator - https://github.com/wso2/aws-ei/issues

Docker

Related artifacts:

   -

   WSO2 API Manager v2.6.0 -
   https://github.com/wso2/docker-apim/releases/tag/v2.6.0.5
   -

   WSO2 Identity Server v5.8.0 -
   https://github.com/wso2/docker-is/releases/tag/v5.8.0.1
   -

   WSO2 Stream Processor v4.4.0 -
   https://github.com/wso2/docker-sp/releases/tag/v4.4.0.1
   -

   WSO2 Enterprise Integrator v6.5.0 -
   https://github.com/wso2/docker-ei/releases/tag/v6.5.0.1


Issues:

   -

   WSO2 Identity Server - https://github.com/wso2/docker-is/issues
   -

   WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues
   -

   WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/issues

Kubernetes

Related artifacts:

   -

   WSO2 Identity Server v5.8.0 -
   https://github.com/wso2/kubernetes-is/releases/tag/v5.8.0.1
   -

   WSO2 Stream Processor v4.4.0 -
   https://github.com/wso2/kubernetes-sp/releases/tag/v4.4.0.1
   -

   WSO2 Enterprise Integrator v6.5.0 -
   https://github.com/wso2/kubernetes-ei/releases/tag/v6.5.0.1


Issues:

   -

   WSO2 Identity Server - https://github.com/wso2/kubernetes-is/issues
   -

   WSO2 Stream Processor - https://github.com/wso2/kubernetes-sp/issues
   -

   WSO2 Enterprise Integrator - https://github.com/wso2/kubernetes-ei/issues

Puppet

Related artifacts:

   -

   WSO2 Identity Server v5.8.0 -
   https://github.com/wso2/puppet-is/releases/tag/v5.8.0.2
   -

   WSO2 Stream Processor v4.4.0 -
   https://github.com/wso2/puppet-sp/releases/tag/v4.4.0.2
   -

   WSO2 Enterprise Integrator v6.5.0 -
   https://github.com/wso2/puppet-ei/releases/tag/v6.5.0.2
   -

   WSO2 Micro Integrator v1.0.0 -
   https://github.com/wso2/puppet-micro-integrator/releases/tag/v1.0.0.2


Issues:

   -

   WSO2 Identity Server - https://github.com/wso2/puppet-is/issues
   -

   WSO2 Stream Processor - https://github.com/wso2/puppet-sp/issues
   -

   WSO2 Enterprise Integrator - https://github.com/wso2/puppet-ei/issues
   -

   WSO2 Micro Integrator -
   https://github.com/wso2/puppet-micro-integrator/issues

Vagrant

Related artifacts:

   -

   WSO2 API Manager v2.6.0 -
   https://github.com/wso2/vagrant-apim/releases/tag/v2.6.0.3
   -

   WSO2 Identity Server v5.8.0 -
   https://github.com/wso2/vagrant-is/releases/tag/v5.8.0.1
   -

   WSO2 Stream Processor v4.4.0 -
   https://github.com/wso2/vagrant-sp/releases/tag/v4.4.0.1
   -

   WSO2 Enterprise Integrator v6.5.0 -
   https://github.com/wso2/vagrant-ei/releases/tag/v6.5.0.1


Issues:

   -

   WSO2 API Manager - https://github.com/wso2/vagrant-apim/issues
   -

   WSO2 Identity Server - https://github.com/wso2/vagrant-is/issues
   -

   WSO2 Stream Processor - https://github.com/wso2/vagrant-sp/issues
   -

   WSO2 Enterprise Integrator - https://github.com/wso2/vagrant-ei/issues


How You Can Contribute

Join our mailing list and correspond with the developers directly.

Developer List: d...@wso2.org

User List: u...@wso2.org

Reporting Issues

We encourage you to report issues and documentation faults regarding
WSO2 Ansible,
AWS, Docker, Kubernetes, Puppet and Vagrant resource through respective
repositories by creating issues.

Thank you!

WSO2 Installation Experience Team


Vimukthi Perera | Software Engineer | WSO2 Inc.
(m) +94771153999 | (e) vimuk...@wso2.com



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

Re: [Architecture] Implementing native JSON support for Synapse mediators

[Arunan Sugunakumar]

Hi Chathura,

On Thu, Jun 13, 2019 at 10:10 AM Chathura Ekanayake 
wrote:

> Hi Arunan,
>
> Enhancing EI JSON support is very useful. Does this change the syntax or
> introduce new syntax? If so, could you give some samples.
>

Yes, It introduces new syntax. But it will not effect existing users or the
configurations. To use the native JSON support, instead of giving XPath
expressions we need to give JSONPath expressions within "json-eval()". A
sample configuration for Iterate mediator is given below.


   
  
   


All the JSONPath supported mediators currently have a similar syntax.


> Regarding the JSON schema based transformation, how does the transform
> mediator determine mappings. Do we have to specify mappings as a part of
> the config?
>

Yes, we need to give the schema to transform the payload. Currently the
user have limited control over how the XML converts to JSON. By defining a
schema (either a partial or a complete one), the user can correct the
payload as he wants. This will be highly useful when you are using XML only
mediators (like XSLT) to manipulate a JSON payload. I will elaborate more
and share some samples once we have finalised the implementation details.

Thanks & Regards,
Arunan

>
> On Fri, Jun 7, 2019 at 12:27 PM Arunan Sugunakumar 
> wrote:
>
>>
>> Hi all,
>>
>>
>> I am working on implementing native JSON support for Synapse mediators.
>> As part of the effort, we have to implement JSON support in all the
>> relevant mediators and currently we have implemented native JSON support to
>> Iterate, Aggregate and Enrich mediators. We have to implement it for
>> ForEach, Header, Publish Event, Rule and Call Template mediator. Other
>> mediators either already have JSON support or not relevant to handling JSON
>> payloads (eg XSLT mediator). Please see the attachment for a complete
>> analysis.
>>
>> Initially all the JSON payloads sent to the Synapse got transformed into
>> XML and all the mediators manipulated the payload as XML using XPath. This
>> approach led to some issues such as some of the original information in the
>> JSON payload was lost during the conversion. As a remedy, it was decided to
>> implement native JSON support to the mediators. The original payload exists
>> as a stream in the Message Context and the JSON supported mediators use
>> that stream to do the data manipulation and after the manipulation, the
>> stream and the SOAP envelope are updated. Currently the problem is that, to
>> handle JSON payloads natively, we can only use JSON supported mediators in
>> the mediation. If we use a non JSON supported mediator, the JSON payload in
>> the JSON stream becomes obsolete and we have to use XPath to manipulate the
>> JSON payload in the remaining mediators.
>>
>> As a solution, we can implement JSON support for all the relevant
>> mediators and minimize this problem. This solution is totally backward
>> compatible and existing users can continue to manipulate JSON payload via
>> XPath if they want. To give users more control over the payload, we are
>> also planning to introduce a new Transform mediator which will take a
>> payload and a schema as input, and it will give out a modified payload
>> according to the schema as output.
>>
>>
>> [image: Transform mediator (2).png]
>> Any suggestions or concerns are highly appreciated.
>>
>> Thanks & Regards,
>> Arunan
>>
>> --
>> *Sugunakumar Arunan*
>> Software Engineer | WSO2
>>
>> Email : aru...@wso2.com
>> Mobile : +94766016272
>> Web : http://wso2.com
>> 
>>
>

-- 
*Sugunakumar Arunan*
Software Engineer | WSO2

Email : aru...@wso2.com
Mobile : +94766016272
Web : http://wso2.com

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

Re: [Architecture] [Intern Project] Salsforce Wave Analytics Connector for WSO2 EI

[Keerthika Mahendralingam]

Hi All,

This connector is released in the store [1].

[1].
https://store.wso2.com/store/assets/esbconnector/details/31ee2da6-921a-47a9-8fe6-88306c19397e

Thanks,
Keerthika.

On Thu, Jan 31, 2019 at 12:52 PM Nirubikaa Ravikumar 
wrote:

>
> Hi all,
>
> As an intern project, I am going to develop Salesforce Wave Analytics
> Connector for WSO2 EI.
>
> *API: Salesforce Wave Analytics REST API*
> *Authentication mechanism: Oauth 2.0 Authentication.*
>
> Salesforce Wave Analytics is a business intelligence platform from
> Salesforce.com that is optimized for mobile access and data visualization.
> And Wave analytics is an analytic tool that helps to create powerful
> reports and dashboards from a large amount of enterprise data
>
> For the initial version of the connector, I am going to implement the
> following 13 methods:
>
> 1.  ListTopLevelResources: Lists the top-level resources available for
> Analytics.
> 2.  ListAnnotations: Lists the collection of annotations
> 3.  ListDatasets: Returns the collection of the dataset.
> 4.  UpdateDatasets: Updates a dataset for a specified ID.
> 5. Query: Executes a query written in Salesforce Analytics Query Language
> 6.  ListDashboards: Returns a list of Analytics dashboards.
> 7.  CreateDashboard: Creates the dashboard.
> 8.  UpdateDashboard: Updates the dashboard with the specified ID.
> 9.  ListTemplate: Returns a list of Analytics templates
> 10.ListFolder: Lists the collection of the folder.
> 11.ListFolderByID: Returns the representation for an Analytics
> application or folder.
> 12.ReplaceFolder: Replaces folder.
> 13.ListLenses: Returns a list of Analytics lenses.
>
> I have attached a user story for 'Salesforce Wave Analytics for WSO2 EI'.
> Please let me know if you have any concerns.
>
> --
> R.Nirubikaa
> Software Engineering Intern | WSO2
> M: O779108852
>
>
>


-- 

Keerthika Mahendralingam
Senior Software Engineer
Mobile :+94 (0) 776 121144
keerth...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture