Page Comparison

...

The connection between physical databases and the server is established through datasources. The master-datasources.xml file (stored in the <MB_HOME>/repository/conf/datasources directory) is the default datasource configuration file that is shipped with WSO2 products. In the case of WSO2 MB, since we use two databases (Carbon database for registry/user management data and the MB-specific database for storing MB data), the master-datasources.xml file should contain two separate datasource configurations corresponding to the two databases.

If you check the default master-datasources.xml file in the product, you will see that the configurations point to the embedded H2 databases. The following instructions given below explain how you can divert the default configurations to point to the external MySQL database you created in step 1.

Follow the steps given below to replace the MB-specific datasource configuration with a new connection to a the MSSQL database:

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 BrokerWSO2 MB. This file consists of commented out configurations for datasources. The datasource configuration for MSSQL 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 a the MSSQL database user with the proper permissions.

Code Block

language	xml

<datasource>
    <name>WSO2_MB_STORE_DB</name>
    <jndiConfig>
        <name>jdbc<name>WSO2MBStoreDB</MSSQLWSO2MBStoreDB</name>
    </jndiConfig>
    <definition type="RDBMS">
         <configuration>
                    <url>jdbc:jtds:sqlserver://localhost:1433/wso2_mb</url>
                    <username>sa</username>
             <dataSourceClassName>com.microsoft.sqlserver       <password>sa</password>
                    <driverClassName>net.sourceforge.jtds.jdbc.SQLServerXADataSource</dataSourceClassName>Driver</driverClassName>
                    <maxActive>200</maxActive>
 <dataSourceProps>                		<property name = "URL">jdbc:sqlserver://127.0.0.1\SQLExpress</property>
		<property name="databaseName">wso2mb</property> <maxWait>60000</maxWait>
                    <minIdle>5</minIdle>
                    <testOnBorrow>true</testOnBorrow>
                    <property name="user">sa</property><validationQuery>SELECT 1</validationQuery>
                   <property name="password">mssql</property> <validationInterval>30000</validationInterval>
                    <<defaultAutoCommit>false</dataSourceProps>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.

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 Message BrokerWSO2 MB. The changes made to this file must be done in all the WSO2 Message Broker MB nodes.

In the broker.xml file we need to use the MSSQL 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/MSSQLWSO2MBStoreDB</property>
  </messageStore>

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

The elements in the above configuration are described below.

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

...

Versions Compared

Old Version 5

New Version 6

Key