Hi Areeg, We don't have the schema for SQLServer. Not sure how you created the ODE schema for SQLServer.
For tomcat one needs to integrate an External Transaction manager. The resource element configuration will not work properly. Would recommend trying the ODE-Tomcat-Bitronix-MYSQL bundle from here. You need to run the package though, to get the archive. https://github.com/vanto/apache-ode-tomcat-bundle regards, sathwik On Wed, Jun 11, 2014 at 1:25 PM, Areeg Samir <[email protected]> wrote: > Hello everyone, > I have a simple process that invoking a web service that is getting > information from SQLServer database. The process takes integer values and > return integer value. But every time I'm trying to call my process, I can't > get my result from database.I searched a lot to connect my SQLServer > database with Apache ODE. > > > After days of trying I created acontext.xml file in the ode\META-INF that > contains the follow: > > <Context path="/ode" docBase="ode" debug="5" reloadable="true" > crossContext="true"> > <Resource name="jdbc/ode" > auth="Container" > type="javax.sql.DataSource" > maxActive="100" > maxIdle="30" > maxWait="10000" > username="xxx" > password="xxx" > driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" > > url="jdbc:sqlserver://localhost:1433;databaseName=ValidatedData;user=xxx;password=xxx"/> > </Context> > > I also configured the web.xml in the ode\WEB-INF with: > <resource-ref> > <res-ref-name>jdbc/ode</res-ref-name> > <res-type>javax.sql.DataSource</res-type> > <res-auth>Container</res-auth> > <res-sharing-scope>Shareable</res-sharing-scope> > </resource-ref> > > > And configured ode-axis2.properties with: > ode-axis2.db.mode=EXTERNAL > ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ode > > ode-axis2.http.connection-manager.max-per-host=100 > ode-axis2.http.connection-manager.max-total=100 > ode-axis2.process.dehydration=true > ode-axis2.cluster.localRoute.targets= > http://myloadbalancer.com:8080/ode/processes/ > ode-axis2.cluster.localRoute.base=http://localhost:8888/ode/processes/ > ode-axis2.db.emb.type=derby > > But when I do the previous configuration, tomcat didn't deploy the process > and I got "SOAP message MUST NOT contain a Document Type Declaration(DTD)" > > If I comment the configuration in the ode-axis2.properties, Tomcat deploy > the process but I when I try to evaluate the process I got > "axis2nsx:SelectionFailure". > > I also tried to change the db.mode in ode-axis2.properties to internal and > embedded but I got database derby error connection. > > I tried a lot to know what cause the previous errors. I do many > configurations in the previous files, searched a lot in the internet, > loaded ODE Schema into SQLServer but I got extra errors.I don't know > whether the error in my connection with SQLServer or in my Process. > Please, if anyone has an idea about what causing these errors I would be > so grateful! > > > > I use: > apache-tomcat-6.0.35. > apache-ode-1.3.6 > axis2-1.6.2 > sqljdbc4.jar in tomcat\lib
