WSO2 Micro Integrator is a container-friendly ESB to build your integrated enterprise. Before you start building your integration scenarios and running them on the Micro Integrator, you need to set up and configure the Micro Integrator according to your enterprise requirements. Once your system is up and running, you need to monitor its performance. See the following topics for more details.
Securing WSO2 Micro Integrator
It is recommended to change the default security settings to the requirements of your production environment. The main security configurations of WSO2 Micro Integrator are inherited from the Carbon kernel.
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. The following topics explain more details on keystores.
|You also have the option of switching to symmetric encryption. Using symmetric encryption means that a single key will be shared for encryption and decryption of information.|
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 the server.
The following topics will be covered under this section:
|Securing Passwords in Synapse Configurations|
When you use WSO2 Micro Integrator or the ESB profile of WSO2 EI, it is also possible to encrypt passwords and other sensitive information in synapse configurations.
|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 the file-based registry
The H2 database-based registry is not available in the Micro Integrator profile. Instead, it has a file-system-based registry, which provides the same functionality. Thus, by default, the
<EI_HOME>/wso2/micro-integrator/registry directory will act as the registry to store registry artifacts etc. This main registry directory will consist of the following sub registry directories.
- Local: To store local artifacts of the product server that are not shared with the other products in the deployment.
- Config: To store all product-specific artifacts that are shared between similar product instances.
- Governance: To store all artifacts that re relevant to the governance of the product.
If you want to change the default locations of the Registry directories, uncomment and change the following configuration in the
Changing the default ports
When you run multiple instances of the same profile or multiple clusters on the same server or virtual machines (VMs), you must change the default ports with an offset value to avoid port conflicts.
- The ports used by WSO2 Micro Integrator are listed here, along with the complete list of ports in all WSO2 products.
- For instructions on configuring ports, see Changing the Default Ports in the WSO2 Administration Guide.
For information on updating WSO2 Micro Integrator with the latest available patches (issued by WSO2) using the WSO2 Update Manager (WUM), see WSO2 Updates.
Configuring custom proxy paths
This feature is particularly useful when multiple WSO2 products (fronted by a proxy server) are hosted under the same domain name. By adding a custom proxy path you can host all products under a single domain and assign proxy paths for each product separately. For instructions on configuring custom proxy paths, see Adding a Custom Proxy Path in the WSO2 Administration Guide.
Customizing error pages
You can make sure that sensitive information about the server is not revealed in error messages by customizing the error pages in the servers. For instructions, see Customizing Error Pages in the WSO2 Administration Guide.