WSO2 – GenySoft

26 Jun 2020

WSO2 vs MuleSoft AMAZON Connectors List

genysoft_admin
Integration Technology
Amazon, Connectors, List, Mulesoft, WSO2

WSO2 EI – AMAZON CONNECTORS

EI Connectors	Summary
Amazon Lamda Version 1.0.0 by WSO2 Category: Developer Tools Supported Product Version: EI 7.0.x EI 6.4.0 EI 6.4.0	The Amazon Lambda Connector allows you to access the REST API of Amazon Web Service Lambda (AWS Lambda), which lets you run code without provisioning or managing servers. Lambda takes care of everything required to run and scale your code with high availability.
Amazon DynamoDB Version 1.0.1 by WSO2 Category: Other Supported Product Version: EI 7.0.x EI 6.6.0 EI 6.5.0	The Amazon DynamoDB connector allows you to access the Amazon DynamoDB REST API through the WSO2 ESB and perform CRUD operations.
Amazon S3 Version 1.0.10 by WSO2 Category: Developer Tools Supported Product Version: EI 7.0.x EI 6.6.0 EI 6.5.0	The Amazon S3 connector allows you to access the REST API of Amazon Simple Storage Service (Amazon S3), which provides a simple web services interface that can be used to store and retrieve any amount of data, at any time, from anywhere on the web. The connector with WSO2 EI enables you to publish and manage your enterprise data at Amazon S3 service.
Amazon Simple Notification Version 1.0.1 by WSO2 Category: Productivity Tools Supported Product Version: ESB 4.9.0 EI 6.1.1 EI 6.4.0	The Amazon SNS connector allows you to access the exposed API through the WSO2 ESB. Amazon Simple Notification Service (Amazon SNS) is a Web service that enables you to build distributed Web-enabled applications. The connector uses the Amazon SNS REST API reference.
Amazon Simple DB Version 1.0.0 by WSO2 Category: Developer Tools Supported Product Version: ESB 4.8.0 ESB 4.8.1 ESB 4.9.0 ESB 5.0.0	The Amazon SimpleDB connector allows you to access the Amazon SimpleDB API through WSO2 ESB. This service works in close conjunction with Amazon Simple Storage Service (Amazon S3) and Amazon Elastic Compute Cloud (Amazon EC2), collectively providing the ability to store, process, and query data sets in the cloud.
Amazon SES Version 1.0.0 by WSO2 Category: Communication Supported Product Version: ESB 5.0.0 ESB 4.9.0	The Amazon SES connector allows you to access the Amazon SES API through WSO2 ESB. Amazon SES is a highly scalable and cost-effective email solution for businesses and developers.
Amazon Simple Queue Services Version 1.0.8 by WSO2 Category: Developer Tools Supported Product Version: EI 7.0.x EI 6.6.0 EI 6.5.0	Amazon SQS offers reliable and scalable hosted queues for storing messages as they travel between computers. By using Amazon SQS, you can move data between distributed components of your applications that perform different tasks without losing messages or requiring each component to be always available. The Amazon SQS connector for WSO2 EI uses the Amazon SQS API and allows you to send and receive messages, facilitating asynchronous messaging between integrated systems.

MULESOFT- AMAZON CONNECTORS

Amazon S3 Connector Version 5.6.x Mule 4	Amazon S3 is a web storage service that allows organizations to store data in the cloud. You can interface Amazon S3 to store objects. Instant access to the Amazon S3 API enables businesses to create seamless integrations between Amazon S3 and other databases
Amazon EC2 Connector Version 2.3.x Mule 4	Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides secure, resizable compute capacity in the cloud. It is designed to make web-scale cloud computing easier for developers.
Amazon SNS Connector Version 4.4X Mule 4	Amazon SNS is a web service that you can use to publish messages from applications and deliver them to other services, applications, subscribers, internet, and mobile devices, immediately and cost-effectively. Quickly and easily manage to push messaging services with the Amazon Simple Notification Service (SNS) and simplify the process of setting up, operating, and sending notifications from the cloud with the Anypoint Amazon SNS connector from Mulesoft.
Amazon SQS Connector Version 5.5X Mule 4	Amazon Simple Queue Service (Amazon SQS) supports programmatic sending of messages via web service applications as a way to communicate over the Internet.
Amazon S3 Glacier Connector Version 1.0X Mule 4	The Amazon S3 Glacier connector provides connectivity to the Amazon S3 Glacier API, enabling you to interface with Amazon S3 to store objects, archive, download and use data with other AWS services, and build applications that call for internet storage.
Amazon RDS Connector Version 1.3X Mule 4	Amazon RDS provides connectivity to the Amazon Relational Database Service (Amazon RDS) API, enabling you to interface with Amazon RDS to provide resizable capacity while automating hardware provisioning, database setup, patching, and backups.
Amazon DynamoDB Connector Version 1.4X Mule 4	Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability.

26 Jun 2020

Secure Vault Implementation for WSO2 EI

One simple mechanism that comes with all the WSO2 products to overcome this vulnerability is called Secure Vault implementation. It’s an extended version of synapse Secure Vault and hence it has been inherited to WSO2 Carbon platform. This particular feature simply allows us to replace the real password with an alias and then this alias will be mapped with the encrypted version of the real password inside the Secure Vault.

The user-mgt.xml which resides at <EI_HOME>/conf folder contains the password of the Admin User which is ‘admin’. Using the secure vault, this can be replaced by an alias such as UserManager.AdminUser. Password and the encrypted version of the real password will go to Secure Vault. During the runtime, the WSO2 product will check this alias in Secure Vault and decrypt the corresponding password.

The entire Secure Vault implementation mainly based on three files.

cipher-tool.properties
cipher-text.properties
cipher-tool.sh

Following are the summarized steps to make it work.

Step 1: Open the cipher-tool.properties file resides in the <EI_HOME>/conf/security folder and adds the file name and the XPath of the password which you wants to be encrypted in the following format.

<alias>: The value which is going to replace the hard-coded password.
ex: UserManager.AdminUser.Password
<file_name>: The file name of the configuration file where the password resides.
ex: repository/conf/user-mgt.xml
<xpath>: XPath to the password in the configuration file
ex: UserManager/Realm/Configuration/AdminUser/Password
<true, false>: Use value ‘false’ if you are encrypting the value of an XML element, or the value of an XML attribute’s tag. Use the value ‘true’ if you are encrypting the tag of an XML attribute.

ex:
UserManager.AdminUser.Password=repository/conf/user-mgt.xml//UserManager/Realm/Configuration/AdminUser/Password,false

Step2: Open the cipher-text. properties file (<EI_HOME>/conf/security) and adds the alias and the corresponding plaintext password.

<alias>=[plain_text_password] ex: UserManager.AdminUser.Password=[admin]

Step 3. Run the cipher-tool.sh file (<EI_HOME>/bin) by using the ‘./ciphertool.bat -Dconfigure’ command.

That’s it!!! You will see the original password has been replaced by an alias in the configuration file and the encrypted password appearing in the cipher-text. properties file with the corresponding alias.

Observe the changes in below screenshots

Decrypt Encrypted text with the WSO2 Cipher tool:

1. Download the pre-built client jar file and put this jar file in libraries from https://github.com/ashok1995-b/decryptedJarfile/blob/master/org.wso2.samples.decrypt-1.0-jar-with-dependencies.jar

Jar file = org.wso2.samples.decrypt-1.0-jar-with-dependencies.jar

1. Execute as interactive command-line inputs at YOUR_EI_HOME/6.6.0/lib
The command for this is (Inputs will be asked one by one);
java -jar org.wso2.samples.decrypt-1.0-jar-with-dependencies.jar
2. Encrypted Text from (\YOUR_EI_HOME\6.6.0\conf\security\cipher-text.properties)

For Example for UserManager.AdminUser.Password = “admin”

bBa173t6ThRLQOt6Z5BztDC56MXLAwb9cr6gHRJhWSbAGbIG7KaFxNjAuh9pVt/74tY06yKEt/SIgL42QDMQMmMjMgmd9KP9VMtVTMw2EMdW55VETgwHmPzfAiL242M77bpZW/Y9/YTanPQk8KStOxIUI4iAM42lm2z3imbHVh0=

3. KeyStore file path : /YOUR_EI_HOME/6.6.0/repository/resources/security/wso2carbon.jks
4. KeyStore alias : wso2carbon
5. KeyStore password : wso2carbon

Result in Plain Text:

At last, If you are looking for consultants and systems integration experts who understand all these with a strong play in a variety of Integrations products, Genysoft is to consider for all your needs of middleware integration needs.

We are an Integration Experts and Implementation partners of Fiorano, WSO2, JitterBit, MuleSoft, Talend, SnapLogic, Dell Boomi, Apigee from Offshore Hyderabad, India with offices in Johannesburg, South Africa, Texas, USA. We have been working with large scale integration projects Hybrid, Cloud, OnPremise since 2008. We have vast experience working on multiple middleware integration products, which is a very unique combination of skills that we proud of. Be it is On-premise or Cloud, Proprietary or Open source, Frameworks, or Integration Suites we have expertise.

Our integration experts have experience in various integration products such as Fiorano, WSO2, JitterBit, MuleSoft, Talend, SnapLogic, Dell Boomi, Apigee and we are active contributors to the community where we learn and share the experiences. We recognize that each customer integration project is unique and we understand your integration puzzles and we apply our expertise to solve them. Our delivery methodology ensures scalable, cost-effective integration solutions to your problems.

We’ve gathered our knowledge over the decade; a knowledge that we are happy to now place at your service. Please Write to Us your needs for middleware to info@genysoft.com.

15 Jan 2017

Choosing The Right Integration Product – Oracle SOA | MuleSoft | WSO2

genysoft_admin
Integration Technology
ESB, Hyderabad, India., integration, middleware, Mulesoft, Open Source, OSB, SOA, WSO2

Middleware

Integration Suite

An Integration suite offers a complete components and all the features of middleware including an ESB. In addition, many other features such as Business Process Management (BPM), Business Activity Monitoring, Master Data Management, or a Repository and Rules are included. If some of these additional features are required in addition to pure integration, then the use of a suite is advisable.

Enterprise Service Bus

What is “Enterprise Service Bus”
ESB is the modern world application integration platform which completely supports and enables message oriented middleware. It can transform and route the messages in different ways based on contents of the message and routing logic. ESB provides flexible and loosely coupled integration solution for the applications to post messages to the ESB and the ESB will handle the rest.

The great advantage of ESBs over the use of pure frameworks or Integrations Suite is therefore to reduce the cost and complexity significantly. Integration problems are solved at a higher abstraction level.

Integration Framework with EIP

A framework helps implementing Enterprise Integration Patterns(EIP) faster by reusing/building the same integration solution/requirement and keeps applications in a standardized way. Using EIP’s to integrate applications, lowers the implementation efforts and makes solutions robust. A framework helps to integrate different applications using different protocols, technologies, interfaces, endpoints, producer, consumer and EIPs are used to create the integration logic.

With frameworks the development team is more or less solely responsible for the project’s success.
Commercial support is generally not available.
Tooling is also only partly available, and not necessarily suitable for “mission-critical” deployments.

Isn’t ESB it sounding so simple to you? in fact it is.

Basically ESB falls between a framework and an Integration suite. unless you understand what are different products and vendors available in the market to implement “Enterprise Service Bus”. Almost every vendor of proprietary integration products, such as IBM and Oracle, offers middleware integration suites and tools. Perhaps the most important open-source offerings are Mule ESB and WSO2 ESB.

Let’s use below table to compare and choose the right ESB or suite.

Comparing different ESB products together

OSB (Oracle SOA Suite)	Mule ESB	WSO2 ESB
It is a component of Oracle Fusion Middleware (OFM) stack	Mulesoft is pure ESB.	A full suite that is based on a single code base Apache Synapse (lightweight ESB), Axis (Web Service Implementation) into its component and a single development environment
Many other companion products are available in it, for example, the BPEL, Coherence, Complex Event Processing, Business Rules, Enterprise Messaging Service, Service Registry, and many more.	Mule ESB has to be combined with products from other vendors for additional features.	WSO2 provides the entire range of companion products of a suite including Business Process Server, Business Rules Server, Business Activity Monitor, Governance Registry, API Manager.
The tools are very powerful and stable over years. Eclipse and Jdeveloper based development.	Mulesoft ESB development is through Anypoint Studio (Proprietary). With Inbuilt Server, Debugger, Monitoring Capabilities. One Click propagation to dev-prod servers	The entire WSO2 platform can be installed very easily and offers a lightweight, Eclipse-based development studio
Graphical editors exist for most products for easy drag and drop job.	Graphical editors for an efficient implementation of integration scenarios.	A weakness is the graphical tooling. It supports all components of the platform, but it is not as intuitive to use as the tooling of its competitors.
Connectors and Adapters Available, supports most of application integration needs. Custom connector development possible.	Mostly all the standard connectors for B2B products such as SAP or Salesforce are available. Provides on Anypoint Connector (Out-of-the-box Devkit) for custom connector development.	Numerous SOAP, REST, Java API based connectors. All most all the standard connectors Amazon, Twilio, Twitter, Salesforce, JIRA etc. are available. Fully supports to develop custom Connectors.
Support is available at different service level agreements.	Apart from the free open-source version, a commercial enterprise version is available. This offers additional functionality and support for the product.	Apart from the free open-source version, product support available through Change Request or tickets. For that matter can work with implementation partners.
High complexity of the products should not be underestimated. Besides, you should be aware of high licensing and support costs plus a non-transparent pricing model.	Prices are customer friendly Nevertheless, the open-source version can be used (even in production) without any licensing costs. the open-source version simply serves for playing around or doing a proof of concept to later upgrade to the enterprise version with additional features and support.	Prices are customer friendly, open-source version fully support s all your production needs, however you only pay for upgrades and additional support for risk free Prod and all other non-prod are totally cost free.
The installation is tedious and can occasionally take more time to build (several days) for simple Development platform installation.	No Installations required, Works as it is through Download and Extract. Quick and easy.	No Installations required, Works as it is through Download and Extract. All the WSO2 products are built on same carbon platform so makes the installations and maintenance very easy.
The products are proprietary and come from multiple acquisitions made by Oracle over time. Which makes it complex.	Built on Proprietary Mule ESB framework.	Products are built on same carbon platform makes it less complex.
The products are rather heavy. Resource consumption at run-time is very high.	Open source ESBs are very lightweight and provides extensible solutions to your middleware needs.	Open source ESBs are very lightweight and provides extensible solutions to your middleware needs.

Decision:

Therefore, it is wise and advisable to pre-define your integration needs and then to evaluate each of these products to better suit your needs. It is strongly recommended to perform a proof of concept with a use-case. At times you may need to work with an experienced implementation partner to help you make a final decision.

The challenge is every vendor and partners greatly support and admire their products but nobody would agree to say what lack in their products, and less knowledge about other products, finally you end up working with multiple partners and burn your budgets just to in evaluation phase itself. So you need an Implementation partner who knows all middleware products better and help you optimize your cost and time with their expertise.

At last, If you are looking for consultants and systems integration experts who understands all these with a strong play in a variety of Integrations products, Genysoft is to consider for all your needs of middleware.

We are integration experts from Offshore Hyderabad, India and have been working with large scale integration projects since 2008. We have vast experience working on multiple middleware integration products, which is a very unique combination of skills that we proud of. Be it is On-premise or Cloud, Proprietary or Open source, Frameworks or Integration Suites we have expertise.

Our integration engineers have experience in various integration products such as Oracle SOA, WSO2, Mulesoft and we are active contributors to the community where we learn and share the experiences. We recognize that each customer integration project is unique and we understand your integration puzzles and we apply our expertise to solve them. Our delivery methodology ensures scalable, cost effective integration solutions to your problems.

We’ve gathered our knowledge over decade; a knowledge that we are happy to now place at your service. Please Write to Us your needs of middleware.

12 Jan 2017

What Makes Integration Difficult?

genysoft_admin
Integration Technology
Hyderabad, India., integration, middleware, Mulesoft, Oracle, SOA, WSO2

For organizations looking to integrate applications on ever-more-complex environments, often as cloud, on-premises and hybrids, integration has become an essential IT component, and a preferred method to keep applications connected everywhere.

The major analyst firms are predicting a great future for middleware.

Gartner forecasts that middleware software will account for potential growth rate of IT expenditure year by year. Integration costs have been a significant overhead in large IT projects for some time, but costs only includes the software, not the internal IT effort of making it work. That being said integration solutions already accounts for 30% to 40% of the total project cost, and often as much as 70%. What Makes Integration Difficult?

Choosing The Right Integration Product

Primary difficulty is choosing a right product for integration needs and it is also essential to choose between Proprietary or Open Source tools for that matter.
Proprietary software provides all possible features and strong support. However, there is also higher costs and a perceived higher complexity in usage and maintenance. Where as open source middleware products are less costly as low as 10% of Proprietary Software, ease of use and flexible.
All most all Proprietary Integrations provide similar features and solutions, and also the most of the leading open source products offer similar capabilities and limitations. Comparing different ESB products.

Therefore, it is advisable to pre-define your own needs, and then to evaluate the product which suite best for your needs.

Criteria	Proprietary	Open Source	Winner
Ease of use	Very complex installation (Product expert consultants needed)	One Click Installer	Open Source
Monitoring	Inbuilt into the product (e.g. for administration and monitoring), Analysis of source code not necessary, refactoring via GUI	Third Party tools needed (e.g. for administration and monitoring), Analysis of source code necessary, refactoring via GUI	Proprietary
Community	Buy support, forums, Product experts blogs.	Based on open source projects, plus own community, implementation experts.	Open Source
Support	24/7 enterprise support, SLAs as you wish, deployments with thousands of servers	24/7 enterprise support, less guarantees than proprietary support, check for local consulting and support	Proprietary
Features	All Integration features and many more (BPEL, BAM, CEP, EDA, etc., etc., etc.)	All Integration features and some more	Proprietary
Flexibility	(Make a change request and wait is long; Not free) OR (Pay to get dedicated support)	Open source, change what you want	Open Source
Custom Solutions	Do it yourself Or Pay	Standards-based, lack of standards	Both
Adapters and Connectors	Connectors and Adapters available for all most all for technologies and business applications	Connectors and Adapters available for all most all for technologies and business applications	Both
Costs	MUCH Expensive	LESS Expensive	Open Source
Licensing	Complex price list, pay for upgrades, migrations.	Subscription model, upgrades are inclusive, predictive costs, downgrades possible	Open Source

Architecture

1-Copy-Copy_edited
Architecting integration solutions for project is a complex task. There are many conflicting drivers and even more possible and proven solutions. Many times the architecture phase takes more time and include current and future needs for businesses and inevitable changes and additions put the original architecture at challenge. Most integration vendors provide methodologies and best practices, but these instructions cost you more and typically drive you towards the vendor-provided tool sets and often require extra efforts to create a custom solution as patches.

Enterprise Integration Patterns

A pattern makes a solution reusable due to its independence from a specific implementation. As a result of using design patterns, software developers might have a common understanding of a problem and this leads to an effective way for easier communication.

The “patterns” are not copy-paste code samples or shrink-wrap components, but rather nuggets of advice that describe solutions to frequently recurring problems. Used properly, the integration patterns can help fill the wide gap between the high-level vision of integration and the actual system implementation.