?Uploading Data Driven Websites to your ISP's Server??

[Guest_imported]

I have created fairly basic/static websites in the past and now would like to upload my first data driven website (developed by Macromedia UltraDev.)
I have yet to select my domain name and select the isp to purchase this from .... but my big question is... As the database is part of the site, do I have to load my database up to the isp's server with the html files? Is this the procedure, if not please advise. I have asked 4 ISP's and unbelievably No Joy as yet... any advise would be appreciated. THANK YOU

 

[GiaBetiu]

Hi,
Just few things.
First you need a webserver to host your site(s).
The webserver should have on it the entire site. The database it is part of your site. You need to access it. So it must be where your server is (maybe different server), but you will have an ODBC connection with it, and as you see it is a NetBIOS based mapping.
And, actually I don't understand what you really want. To have that server at home? Then, you have to ask your provider for a permanent public address for your system, and then to ask them about a domain name assignment. AFter this you will have a webserver at home, with the name that you want. Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5

 

[Guest_imported]

thanks very much... however this little project is for my employers who want to purchase a domain name and then be able to have a data driven website on that domain on the internet. The already have the data warehouse housing all the data.

Have I started to make any sense yet?

thank you for your time

 

[GiaBetiu]

In this case, what can I say, usually a professional webserver configuration it is built in 2 parts: frontend and backend.
Shortly is like this:
Frontend should have the public access, backend is the stage server (where you have to design the site) and the database server for example.

They should be in a private network. And the reasons are:
- if you are using ASP (ADO) then you have to use a NetBIOS mapping
- if you use PHP you are lucky, because the connection command is like:
mysql_connect(hostname, user, password)
Being in this way you must be able to specify any host reacheable by TCP/IP.
The main reason to not have this (a remote backend sevrer) I think that is the speed. You can have surprises when your page will not be loaded because there not enough bandwith. And there is some traffic...

So, if you think that is not a problem the above issue, you can try the idea with PHP.
But my strong recomandation is to have an internal connection between the two servers (frontend and backend).
And, in this case these servers should have the same location. You can have them in your company network, assuring that your frontend server has a public address and a corrected associated DNS record. Or asking a provider o host them.
The third possibilty is maybe to ask your provider to keep them, and to update your remote database periodically. But, it depends on your needs.

I hope that these will help you. Success! Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5