Overview

CONNECT can facilitate a database-less deployment for environments and/or clients that do not want to use databases. With CONNECT 5.1, there is no need to have data-sources already defined on the server in order to deploy CONNECT successfully. This is achieved by defining the database beans on as required basis (lazy-init= true) and removing the unnecessary resource-refs in the web.xml files.  Additionally, we need to configure following files:

1. Comment out the databaseEventLogger from the loggersList bean in EventLoggerFactoryConfig.xml. Your EventLoggerFactoryConfig.xml should look like this:

   EventLoggerFactoryConfig.xml

       <bean id="loggersList" class="java.util.ArrayList">
           <constructor-arg>
               <list>
                   <ref bean="log4jEventLogger"/>
                   <!--ref bean="databaseEventLogger" /-->
               </list>
           </constructor-arg>
       </bean>

2. Provide a No-Op implementation for transactionstore  in TransactionLoggingProxyConfig.xml
   TransactionLoggingProxyConfig.xml

       <!--   Beans defined for transactionstore    -->
       <alias alias="transactionstore" name="transactionstorenoop" />
   

3. Set LogToDatabase=false in audit.properties

Note: CONNECT can be deployed in fully functional pass-through modes without data sources defined on the server. Although CONNECT can be deployed without databases in standard mode, customers need to override the PD, PD Deferred Request, QD and RD reference adapters to not use databases.