...
WSO2 Enterprise Integrator 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.01.0 from each of those products.
- See Upgrading from WSO2 Enterprise Service Bus/wiki/spaces/EI610/pages/5866054 for instructions on upgrading to WSO2 EI 6.01.0 from WSO2 ESB.
- See Upgrading from WSO2 Business Process Server/wiki/spaces/EI610/pages/5866056 for instructions on upgrading to WSO2 EI 6.01.0 from WSO2 BPS.
- See Upgrading from WSO2 Data Services Server/wiki/spaces/EI610/pages/5866057 for instructions on upgrading to WSO2 EI 6.01.0 from WSO2 DSS.
- See Upgrading from WSO2 Message Broker for /wiki/spaces/EI610/pages/5866058 for instructions on upgrading to WSO2 EI 6.1.0 from WSO2 MB.
- See /wiki/spaces/EI610/pages/5869205 for instructions on upgrading to WSO2 EI 6.01.0 from the previous WSO2 MBEI version.
...
Clustering
When you cluster WSO2 EI, the three separate profiles (runtimes) included in WSO2 EI should be separately clustered according to your requirement. See the following topics for instructions on clustering each profile in WSO2 EI:
...
See the following topics in the WSO2 Administration Guide for instructions on configuring users, roles and defining permissions for each user.
| Configuring the System Administrator | The admin user is the super tenant that will be able to manage all other users, roles and permissions in the system by using the management console of the product. Therefore, the user that should have admin permissions is required to be stored in the primary user store when you start the system for the first time. The documentation on setting up primary user stores will explain how to configure the administrator while configuring the user store. The information under this topic will explain the main configurations that are relevant to setting up the system administrator. |
|---|---|
| Configuring the Authorization Manager | According to the default configuration in WSO2 products, the users, roles and permissions are stored in the same repository (i.e., the default, embedded H2 database). However, you can change this configuration in such a way that the users and roles are stored in one repository (user store) and the permissions are stored in a separate repository. A user store can be a typical RDBMS, an LDAP or an external Active Directory. The repository that stores permissions should always be an RDBMS. The Authorization Manager configuration in the user-mgt.xml file connects the system to this RDBMS. The information under this topic will instruct you through setting up and configuring the Authorization Manager. |
| Configuring User Stores | The user management feature allows you to maintain multiple user stores for storing users and their roles. See the following topics for instructions: |
| Managing Users, Roles and Permissions | Create new users, roles and assign permissions using the management console. |
...
...
Configuring security
It is recommended to change the default security settings in each profile of WSO2 EI according to the requirements of your production environment. As all profiles in WSO2 EI are WSO2 servers built on top of the WSO2 Carbon Kernel, the main security configurations are inherited from the Carbon kernel. For instructions on configuring these main security settings, see the following topics in the WSO2 Product Administration Guide:
| Note |
|---|
Important! If you are configuring your production environment, be sure to check the Security Guidelines for Production Deployment before applying any security configurations. |
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 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 sec.policy file. You modify this file to change the Java security permissions as required. | |
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: | |
| 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 multitenancy
You can create multiple tenants in your EI profile so that you can maintain tenant isolation in a single server/cluster. For information on configuring multiple tenants for the profile, see Working with Multiple Tenants in the WSO2 Administration Guide.
...
A registry is a content store and a metadata repository for various artifacts such as services, WSDLs, and configuration files. In WSO2 servers, all configurations pertaining to modules, logging, security, data sources and other service groups are stored in the registry by default. For information on setting up and configuring the registry for your server, see Working with the Registry in the WSO2 Administration Guide.
...
- The ports used by all the profiles of WSO2 EI are listed here. For the list of ports in all WSO2 products, see Default Ports of WSO2 Products in the WSO2 Administration Guide.
- For instructions on configuring ports, see Changing the Default Ports in the WSO2 Administration Guide.
Managing product features
Each WSO2 product is a collection of reusable software units called features where a single feature is a list of components and/or other feature. By default, each profile of WSO2 EI is shipped with the features that are required for your main use cases of the profile.
...
...
Configuring custom proxy paths
...
The following topics describe how to monitor the separate runtimes (profiles) in WSO2 EI:
A properly configured logging system is vital for identifying errors, security threats and usage patterns in your product server. For instructions on monitoring the server logs, see Monitoring Logs in the WSO2 Administration Guide. | |
HTTP Requests/Responses are logged in the access log(s) and are helpful to monitor your application's usage activities, such as the persons who access it, how many hits it receives, what the errors are etc. For more information on access logs, go to HTTP Access Logging in the WSO2 Administration Guide. | |
| Monitoring using WSO2 metrics | JVM Metrics allow you to monitor statistics of your server using Java Metrics. For instructions on setting up and using Carbon metrics for monitoring, see Using WSO2 Metrics in the WSO2 Administration Guide. |
| JMX-based monitoring | For information on monitoring your server using JMX, see JMX-based monitoring in the WSO2 Administration Guide. For information on the various MBeans available for monitoring, see JMX Monitoring. |
| Monitoring TCP-based messages | You can view and monitor the messages passed along a TCP-based conversation using the TCPMon. For information on setting up and using TCPMon in your server, see Monitoring TCP-Based Messages in WSO2 Administration Guide. |
| Viewing handlers in message flows | Message flows provide graphical and textual views of the globally engaged handlers of the system at any point of time. The modules use the handlers to engage in different message flows at defined phases. You can observe the handlers invoked in each phase of each flow in real time. |
...
...
Applying patches
For information on updating WSO2 EI with the latest available patches (issued by WSO2) using the WSO2 Update Manager (WUM), see Updating WSO2 Products Getting Started with WUM in the WSO2 Administration Guide.
...