WSO2 Enterprise Integrator 6.6.0 is a comprehensive integration solution that includes the functionality that was previously encapsulated in WSO2 ESB, WSO2 DSS, WSO2 MB, and WSO2 BPS. Therefore, you can upgrade to WSO2 EI 6.6.0 from each of those products.
- See REMOVE-Upgrading from WSO2 Enterprise Service Bus for instructions on upgrading to WSO2 EI 6.6.0 from WSO2 ESB.
- See REMOVE-Upgrading from WSO2 Business Process Server for instructions on upgrading to WSO2 EI 6.6.0 from WSO2 BPS.
- See REMOVE-Upgrading from WSO2 Data Services Server for instructions on upgrading to WSO2 EI 6.6.0 from WSO2 DSS.
- See REMOVE-Upgrading from WSO2 Message Broker for instructions on upgrading to WSO2 EI 6.6.0 from WSO2 MB.
- See REMOVE-Upgrading from WSO2 EI 6.5.0 for instructions on upgrading to WSO2 EI 6.6.0 from the previous WSO2 EI version.
The transport level security protocol of the Tomcat server is configured in the
WSO2 servers use asymmetric encryption by default for the purposes of authentication and data encryption. In asymmetric encryption, keystores (with key pairs and certificates) are created and stored for the product. It is possible to have multiple keystores so that the keys used for different use cases are kept unique.
|You also have the option of switching to symmetric encryption for the EI profile. Using symmetric encryption means that a single key will be shared for encryption and decryption of information.|
|The Java Security Manager is used to define various security policies that prevent untrusted code from manipulating your system. Enabling the Java Security Manager for WSO2 products activates the Java permissions that are in the |
All WSO2 servers contain some configuration files with sensitive information such as passwords. Let's take a look at how such plain text passwords in configuration files can be secured using the Secure Vault implementation that is built into each server.
The following topics will be covered under this section:
When you use the ESB profile of WSO2 EI, it is also possible to encrypt passwords and other sensitive information in synapse configurations. See Working with Passwords in the ESB Profile for instructions.
|Hostname verification is enabled in WSO2 servers by default, which means that when a hostname is being accessed by a particular client, it will be verified against the hostname specified in the product's SSL certificate.|
Configuring custom headers to responses in tomcat server
Navigate to the <EI