Changing the default database
By default, WSO2 products are shipped with an embedded H2 WSO2 MB contains two embedded H2 databases: The default Carbon database, which is used for storing user management and registry data. We recommend that you use , and the default broker-specific database.
You can change the default database configurations in WSO2 MB by setting up new physical databases, and updating the relevant configurations. We recommend the use of an industry-standard RDBMS such as Oracle, PostgreSQL, MySQL, MS SQL, etc. when you set up your production environment. You can change the default database configuration by simply setting up a new physical database and updating the configurations in the product server to connect to that database. For instructions on setting up and configuring databases, see Working with Databases in the WSO2 Administration Guide
For information on setting up a new database for your profile, see Setting up the Physical Database in the WSO2 Administration Guide.
Add the database drivers to the
<MB_HOME>/repository/components/lib/directory when setting up the database.
- Once you set up a new Carbon database, see Changing the Carbon Database for instructions on updating the configurations.
- Once you set up a new broker-specific database, see Changing the Default Broker Database for instructions on updating the configurations.
Configuring users, roles and permissions
For instructions on configuring posts, see Changing the Default Ports in the WSO2 Administration Guide.
Installing, uninstalling and 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, WSO2 MB is shipped with the features that are required for your main use cases.
For information on installing new features, or removing/updating an existing feature, see Working with Features in the WSO2 Administration Guide.
Configuring custom proxy paths
- Monitoring server 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.
- Message tracing in WSO2 MB: In WSO2 MB you have the option of tracing messages by enabling a trace log file. See the troubleshooting guide for instructions.
Monitoring using WSO2 metrics: WSO2 MB 3.5.0 is shipped with JVM Metrics, which allows 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 details on how you can troubleshoot and trace errors that occur in your WSO2 MB server, see Troubleshooting WSO2 MB.
In a production environment, WSO2 Message Broker can be clustered and configured with an external Database Management System (DBMS) of your choice. For instructions on the clustered deployment, see Clustered Deployment.