Page Comparison

...

Open the <MB_HOME>/repository/conf/datasources/master-datasources.xml file. This is where datasources are configured to point to the databases used by the Message Broker. This file consists of commented out configurations for datasources. The datasource configuration for MySQL is among these. The changes made to this file must be done in both broker nodes.

Uncomment or add the following configuration into the master-datasources.xml file. Update the JDBC URL to correctly point to your database and enter the username and password for the MySQL database user with the proper permissions.You simply have to update the url pointing to your MySQL database, the username and password required to access the database and the MySQL driver details as shown below. Further, be sure to set the <defaultAutoCommit> element to false for the MB database.

Code Block

language	xml

<datasource>
  <name>WSO2_MB_STORE_DB</name>
  <jndiConfig>
     <name>WSO2MBStoreDB</name>
  </jndiConfig>
     <definition type="RDBMS">
         <configuration>
            <driverClassName>com.mysql.jdbc.Driver</driverClassName>
            <url>jdbc:mysql://localhost:3306/wso2_mb</url>
            <username>root</username>
            <password>root</password>
            <maxActive>50</maxActive>
            <maxWait>60000</maxWait>
            <minIdle>5</minIdle>
            <testOnBorrow>true</testOnBorrow>
            <validationQuery>SELECT 1</validationQuery>
            <validationInterval>30000</validationInterval>
            <defaultAutoCommit>false</defaultAutoCommit>
         </configuration>
      </definition>
</datasource>

The elements in the above configuration are described below:

Element Description

url The URL of the database. The default port for a DB2 instance is 50000.

username and password The name and password of the database user

driverClassName The class name of the database driver

maxActive The maximum number of active connections that can be allocated at the same time from this pool. Enter any negative value to denote an unlimited number of active connections.

maxWait The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception. You can enter zero or a negative value to wait indefinitely.

minIdle The minimum number of active connections that can remain idle in the pool without extra ones being created, or enter zero to create none.

testOnBorrow

The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and another attempt will be made to borrow another.

validationQuery The SQL query that will be used to validate connections from this pool before returning them to the caller.

validationInterval The indication to avoid excess validation, and only run validation at the most, at this frequency (time in milliseconds). If a connection is due for validation, but has been validated previously within this interval, it will not be validated again.

defaultAutoCommit

Specifies whether each SQL statement should be automatically committed when it is completed. It is recommended Anchor
default_auto_commit
default_auto_commit
defaultAutoCommit

It is required to disable auto committing by setting this property to false for the MB database. This means that multiple SQL statements will be committed to the database as one transaction, as opposed to committing each SQL statement as an individual transaction.

Info
For more information on other parameters that can be defined in the `<MB_HOME>/repository/conf/`datasources/ `master-datasources.xml` file, see Tomcat JDBC Connection Pool.

Open the <MB_HOME>/repository/conf/broker.xml file. This is the root configuration file of WSO2 MB. The changes made to this file must be done in all the MB nodes.

In the broker.xml file we need to use the MySQL message store and Andes context store. To do this, uncomment or add the following configuration.

Code Block

language	xml

...
<persistence>
  <messageStore class="org.wso2.andes.store.rdbms.RDBMSMessageStoreImpl">
        <property name="dataSource">jdbc/MySQLMessageStore</property>
  </messageStore>

  <andesContextStore    class="org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl">
        <property name="dataSource">jdbc/MySQLMessageStore</property>
  </andesContextStore>
...
</persistence>

The elements in the above configuration are described below.

The fully qualified name of the respective implementation class should be defined under the class attributes of messageStore and andesContextStore elements. This implementation class will be used by MB to persist relevant information.
The <property> elements are used to define different properties for each store. The minimal property for starting each store is the dataSource property. Depending on the implementation, the required properties may differ.

...

Versions Compared

Old Version 6

New Version Current

Key