I'll look into this thing of setting it up with a script. I did something like that in the past when I was programming PERL. But that was yet another platform dependent application, (Windows) so I didn't gain any experience of doing it for other platforms.

Thanks a lot for all the time you've spent on explaining this stuff, Harish! I really appreciate it!! I'll most likely go for Marco's solution if it's a stable product, but I think I'll try out your solution too, just to see if I made the right choice.

THANKS!!

Best regards,
Gert
----- Original Message -----
Sent: Monday, February 04, 2002 3:25 AM
Subject: Re: Deployment of servlets & database

You need not bundle DB s/w along with ur app. U can write scripts which will create ur DB schema on client's m/c. Only thing the client should do is to select their DB s/w installation home/install dir etc. Your script should create the schema/tables etc for ur app in their DB. Then ur app will become platform independent, regardless of the underlying DB.
 
All the best
 
 
:-) Harish
 
 
----- Original Message -----
Sent: Monday, February 04, 2002 1:23 PM
Subject: Re: Deployment of servlets & database

You've answered the most critical question... I can't use MS Access for cross platform deployment. Having them on separate machines (if it works) could be one way of doing it, but in my eyes it's not a good solution. (too many "links" that can be broken)

Ideally, I would like to deliver the application + DB as one package, and the only thing the customer has to do is to install the software, set up the DSN (I guess they don't have that on Unix...) and then run it... voila... up and running. I guess this is my picture of a perfect world. :)

Thanks Harish for spending your time to give me an answer on this issue!

Regards,
Gert

Reply via email to