This chapter describes how you can add supplementary data sources along with the existing oracle data source.

Development DS

You can define as many additional datasources as you wish by adding template files to your module's datasource folder. You can create a datasource folder if it doesn't exist in your module already.

You may also define datasource property values to be de-templated in your module's build.properties file. Datasources will be de-templated to the Platform Server deployment directory as part of the regular module build. Alternately, you can invoke the "ant deploy-ds" target to deploy the same to Platform Server.

Sample data source template file:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
 
    <bean id="TESTMARIADS" class="org.apache.commons.dbcp2.BasicDataSource" destroy-method="close">
        <property name="url" value="<%maria.connection.url%>" />
        <property name="driverClassName" value="org.mariadb.jdbc.Driver" />
        <property name="username" value="<%maria.username%>" />
        <property name="password" value="<%maria.password%>" />
        <!-- do not remove accessToUnderlyingConnectionAllowed property this must be always true, this property is required to get MariaDB Connection-->
        <property name="accessToUnderlyingConnectionAllowed" value="true" />
        <property name="initialSize" value="<%maria.connectionPool.minSize%>" />
        <property name="maxTotal" value="<%maria.connectionPool.maxSize%>" />
        <property name="validationQuery" value="select 1 from dual" />
    </bean>
</beans>

Deployment DS

For installers, you can put datasource files into the /one/PLT/datasource directory and they will be deployed to Platform Server as part of the installation.

In this case, the files should not be template files. Instead, they should have all values pre-populated.

Please note, you must place these files before running the installer, i.e. before invoking install.sh