1 Reply Latest reply on Aug 18, 2014 6:06 AM by Wolf-Dieter Fink

    Datasource configuration in domain mode

    xxxxx roque Newbie

      I successfully configured a datasource in my standalone.xml file,but I can´t get the same configuration to work in domain mode.Are there some change I need to apply?

       

      My config looks as follows:

       

      <datasource jndi-name="java:/datasources/OracleDs" pool-name="OracleDs" enabled="true" use-java-context="true">

                              <connection-url>jdbc:oracle:thin:@xxxx:1521:xxxx</connection-url>

                              <driver-class>oracle.jdbc.OracleDriver</driver-class>

                              <driver>oracle</driver>

                              <security>

                                  <user-name>xxx</user-name>

                                  <password>xxxxx</password>

                              </security>

                              <validation>

                                  <validate-on-match>false</validate-on-match>

                                  <background-validation>false</background-validation>

                              </validation>

                              <statement>

                                  <share-prepared-statements>false</share-prepared-statements>

                              </statement>

                          </datasource>

                          <drivers>

                               <driver name="oracle" module="com.oracle">

                                  <xa-datasource-class>oracle.jdbc.driver.OracleDriver</xa-datasource-class>

                              </driver>

                          </drivers>

        • 1. Re: Datasource configuration in domain mode
          Wolf-Dieter Fink Master

          The datasource configuration is the same for both modes.

          Difference is that the domain.xml contain more than one profiles (as standalone*.xml does).

           

          You need to check whether you use the correct profile. The server is part of a server-group and this group use a specific configuration profile.

          This profile need to have the datasource. Also you need to add the driver as a module (manually) for all instances if you use more than one.

           

          If that did not help you should provide more details.