Although at the end of the year WSO2, released its version 7.0.0. Where it gives a turn to the Enterprise Integrator, prioritizing the deployment approach in the cloud and with microservices. Very close to the end of 2019, it has launched version 6.6.0, continuing and improving its current legacy product based on systems integration.
In this new version we’ll have new improvements that we’ll talk about below in more detail, but we’ve also added a large number of patches that fix existing bugs in previous versions and also a significant list of components that are no longer available and that it’s important for us to know about.
What’s new in Enterprise Integrator 6.6.0
JDK 11 support has been added
The version of the trace software has been updated from Log4j to Log4j2. So now we can make use of all the improvements included in this second version of the famous software, such as hiding sensitive information in the log files.
3.Parameterization of components
One problem when deploying integration across different production environments is the management of information associated with those environments. That is, how we manage endpoint URLs or service passwords, which are different in every environment.
In this new version, WSO2 provides the possibility to declare these endpoints by referring to variables in the environment itself or to values in a file (by default file.properties that is stored inside the conf folder). This parameterization can be done both to the endpoint URIs, the pinned serves attribute of the scheduled tasks, connection parameters in inbound endpoints, message stores and proxy services, and connection parameters of a datasource in a dataservice (but the latter only for the injection through environment variables). Here’s an example:
|<data name=“DataServiceSample” serviceGroup=“” serviceNamespace=“”>
As we see in the example, for the use of environment variables we will use $SYSTEM followed by a colon and the name of the variable. And for the files we will use the same syntax but with the reserved variable $FILE.
Until now, we could analyze the statistics and traces of the Enterprise Integrator with the help of the Analytics module integrated in the same product. But from now on we can also do it with Jaeger. Jaeger is an open source, distributed trace monitoring system based on Dapper and Zipkin.
Through the synapse.properties file we can configure the connection with Jaeger and what information we want to monitor (payloads, message properties or everything). Besides, we can also go one by one configuring the artifacts of our integration so that their traces are also monitored. Example:
|<proxy name=“ProxyServiceSample” statistics=“enable” trace=“enable” transports=“https http” xmlns=“http://ws.apache.org/ns/synapse“>
5.Graphic support in the design of APIs
When we access the API list next to the add new API button we’ll now have a button to generate a new API. From this option the already known editor will be opened, which will allow us to create from scratch an API or import an existing one through its swagger file.
We can also edit the APIs with this new graphical interface. And even try them with the also known Try out option.
6.Integration Studio enhancements
WSO2 continues to increase its platform for development, this time enabling the possibility of creating test suites.
With this new feature, we will be able to create our own JUnit tests associated to the artifacts of our application, indicating which will be the input parameters and which will be the expected output or mocking services unrelated to the integration. In addition to running the tests with a simple click.
As we have mentioned, there is also a list of components that are no longer available in this version. Some of them because they have become obsolete, like the Spring Mediator, and others because their use has ceased to be good practice, like the In or Out Mediators. The complete list is as follows:
- Priority Executors and Enqueue Mediator. Both associated with message prioritization.
- Bean, POJO Command and Spring Mediators. Which allowed us to interact in different ways with Java classes, accessible by the application.
- Conditional Router Mediator. It allowed us to perform switch-like logic.
- In, Out Mediators. They allowed to control the input or output flow within a sequence but are no longer useful with the call/response mediator.
- Event Mediator and In memory Topics. We were allowed to send messages to Topic.
- ESB artifacts option in the administration console.
All of them had already been deprecated in version 6.5.0, basically because they are very little used features.
As you can see, the WSO2 has very active its development in the Enterprise Integrator improving it and adding new and interesting features in each new version.
So it is essential if we want to improve our developments and integrations and be aware of everything that happens in the world WSO2, be aware of our blog not to miss anything.