• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

migrate from tomcat 5 to websphere 5.1

 
Ranch Hand
Posts: 164
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi ,
i am new to websphere 5.1.
I want to deploy my web application (war) in websphere. what changes should i need to run application in websphere as in tomcat?.
another question is ...i am using commons dbcp factory for connection pooling in tomcat. what should i do to achieve connection pooling in websphere 5.1?? . i am using ms sql server 2000 database.

waiting for your kind replies.
 
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Milan,

If you are accessing your database only through datasource definitions (lookup a datasource via jndi and get connections from it) then you don't have to change anything in your application. The war file will deploy to WebSphere as well.

You must first define a JDBC provider with suitable driver (I think WebSphere alreay has an embedded driver for SQLServer). During this operation you should have an option to select "connection pool datasource" as the driver implementation type (I am using v6.0 now and cannot remember exactly). Then you define your datasource using this provider with your database settings. What is left is to map map the datasource you created to the one you defined in your application during deployment (application assemmbly phase).

Regards
Kurtcebe Eroglu
 
Milan Jagatiya
Ranch Hand
Posts: 164
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi kurt,
thanks for reply...
i already done this...not succeed..
i am using ms sql server 2000. to set the datasaurce i following below steps...

1) resaurces -> JDBC Providers -> new ->
2) selected " Microsoft JDBC driver for MSSQLServer 2000 "
3) set classpath for sqljdbc.jar
4) Implementation Classname :
com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource

5) in Additional Properties -> datasaurces -> created datasaurce name "mydb"
6) set all the properties for datasaurce.

still getting error :


JVM logs :


what it says??..

thanks...
 
Kurtcebe Eroglu
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Do we have something more at SysErr.log? Log above seems to belong to server startup only (with some JMS configuration errors raised). The lines that are added to the logs just at the time you test the connection would be more informative...

I would also suggest checking your settings against Vendor-specific data sources minimum required settings SQLServer section.

Regards
Kurtcebe Eroglu
 
Milan Jagatiya
Ranch Hand
Posts: 164
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


Do we have something more at SysErr.log?



System.err





I would also suggest checking your settings against Vendor-specific data sources minimum required settings SQLServer section.


yeah..i already refered that link...but not works..
 
Kurtcebe Eroglu
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Milan, there seems to be two different problems; first one is datasource configuration, and second is that something seems to be wrong in your deployment descriptor.

You are testing connection just after you define it, using admin console (not from within your application), right? So to test whether JDBC provider and data source definitions are working, you do not have to deploy any applications. My suggestion is, then, to undeploy your application and focus on datasource definition first; clear all logs, without any applications deployed, simply create and successfully test a connection to your database using admin console (test connection button in datasources page). This way we may avoid different problems getting in each other's way, because, as you can also see, there is nothing related to the error on datasource definition in the logs...

Kurtcebe
 
Milan Jagatiya
Ranch Hand
Posts: 164
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks kurt...I really appreciate your help....
I solved it...It was a versioning problem actually...
thanks again...
 
reply
    Bookmark Topic Watch Topic
  • New Topic