This documentation is work in progress and will be released with the next WSO2 EI version.
Page Comparison - Administration - Micro Integrator Profile (v.6 vs v.7) - WSO2 Enterprise Integrator 6.x.x - WSO2 Documentation

All docs This doc

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Micro Integrator profile of WSO2 Enterprise Integrator (WSO2 EI) 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.

Table of Contents

...

Setting up

...

the Micro Integrator

Listed below are the administration tasks that are required for settting up the Micro Integrator in our environment.

...

  • The ports used by all the profiles of WSO2 EI 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.

Performance

...

tunning

.................

Configuring users, roles, and permissions

...

The following topics describe how to monitor the separate runtimes (profiles) in WSO2 EI:

Monitoring logs

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. 

Monitoring HTTP Access Logs

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 all the profiles of WSO2 EI 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.