This documentation is for WSO2 Enterprise Integrator version 6.3.0 . View documentation for the latest release.
WSO2 Enterprise Integrator Documentation - Enterprise Integrator Documentation - WSO2 Documentation

All docs This doc
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Welcome to the WSO2 Enterprise Integrator (WSO2 EI) 6.x.x documentation!

Product scenarios

If you want to learn how to implement the fundamental scenarios of WSO2 EI, click the links below:

ESB pattern for a connected enterprise

WSO2 EI will act as an ESB to connect miscellaneous applications and services of your organization. It provides flexible infrastrcuture to support agile enterprises. This involves cross connecting services and IT assets by bridging between different transport protocols and supporting data transformations between different formats to route messages among them.


Gateway


WSO2 EI acts as a Gateway for you to extend the reach for existing or legacy applications within your overall integration solution. This allows you to connect remote systems and devices together.

Security gateway


WSO2 EI can be the Policy Enforcement Point (PEP) for security, which provides secure access to applications and services as well as to external partners.

Connecting systems


WSO2 EI can connect packaged applications (e.g., SAP) via connectors to move information to and from those. Also, it can connect on-premise and cloud-based systems (e.g., Sales Force) in any combination with ease.

Development experience


WSO2 EI brings you an Eclipse-based Tooling experience for you to develop connectivity solutions that conform to best practices, in a quick and easy manner. It allows you to use its built-in patterns and templates to kick start development and then to create your own patterns to suit your business needs.

Data integration


WSO2 EI enables you to extract, transform, store and process data residing in different storage sources to bring them to a unified view on your screen easily with WSO2 EI. Furthermore, it gives access to data on demand for you to operate on data using service semantics.

File processing


WSO2 can connect file systems for you to unlock the valuable business data stored in files by performing online processting tasks such as a simple file movement between two systems with message queuing and transformation.


Message queues and topics


WSO2 EI allows you to decouple the interacting parties across time, space, and synchronization. This includes asynchronous request processing for long running operations and mitigating the timing requirements between two systems. Also, you can use WSO2 EI to bridge different messaging protocols such as AMQP and MQTT to integrate devices seamlessly using different messaging protocols and to articulate varying delivery guarantees to provide stability over unreliable networks.

Monitoring and analytics


WSO2 EI Analytics facilitate you to understand what is going on in your business, the service usage trends and the health of the system by detecting system performance and identofying bottlenecks via capabilities such as tracing messages and analysing staistics graphically.

Microservices


WSO2 EI brings you a separate profile to deploy your microservices. This allows you to quickly get started with developing and running Java microservices. You simply need to annotate your service and deploy it using a single line of code.

Workflows and human interactions


The ability to model, execute and integratr comprehensive user/role-based human interactions into processes enables you to automate long-running business interactions within the business to reduce the workload, resource requirements, and errors, to achieve proper rule enforcement and to improve efficiency. Therefore, WSO2 EI empowers you to monitor the business using dashboards, generate reports and statistics on the preformance of the processes and instances, for you to continuously identify and improve business processes, and also to achieve proper rule enforcement using business processes.


  • No labels