How can you install the BizTalk application onto the BizTalk DR servers?
I can see how if we have the SQL log shipping to the DR SQL Server, we have DR at the database level ...
But how does this work for the BizTalk application server level?
So what about the installation of the BizTalk application onto the DR BizTalk server, so the assemblies are in the GAC, when the DR database isn't available because of the log shipping?
And ditto any IIS web directories?
The simple answer is, you just do. Perhaps you're overthinking this.
You install the applications on the DR servers just as you would the 'main' servers. In fact, if you talking about Log Shipping DR, they are part of the same Group so you must deploy to DR same time, same process you use to on main servers.
Basically, there's no difference application wise.
Related
I am buiding an internet web application using c# ASP.NET. I am using my own computer to develop the application. I've installed the oracle database on my computer. In order to deploy this application on the server, does the server have to install oracle client? I already included Oracle.DataAccess.dll in the bin folder.
Yes it does, assuming you're connecting to the database on the same server!
For example, you can connect to remote databases, but the point is where ever the database lives (server or PC), it will need Oracle installed.
The web server you will deploy your application to does not need to have Oracle server but it must have the Oracle client installed (Instant client for instance) + you will have to deploy your database to the Oracle server
I developed a web application for some small company. It connects to an SQL database created in Microsoft SQL server Managment studio 2008. Now they would like to test this app on a local computer before they put it on a server.
My question is, what are all the things I need to make this app work on a random computer running Win with no Visual Studio or SQL server installed?
Thanks for your help.
EDIT: They want to run it on a local computer only.
maybe Microsoft Web Platform Installer 3.0 can help you out.
http://www.microsoft.com/web/downloads/platform.aspx
Install .Net version you are using. It might already be there.
Install/configure IIS
Install SQL Server Express
Your db connection string obviously need to be changed to the local
sql server connection in web.config
Because it is a simple app, just copy the entire app (except proj
files, .cs, .vb files) to that computer
For one, point the connection string at SQL Server on a staging server. The whole idea of testing is to have the same environment as the production server.
We need to deploy our asp.net web site in web farm which consists of 16 web servers. Whenever we need to roll out a new release it is very time consuming and tedious as we need to deploy it first on the DR environment (16 web servers) and then on to Live environment (16 web servers).
Currently we prepare the msi on our build server and copy it on all the front end web servers which involves first FTPing the msi to a common location on hosting network and then copying from the common location to each server.
After thet we backup the existing website and then run the installer one by one on each machine.
After installing the new version we replace the web.config file with the older one as it is encrypted and hardly contains any new thing in it as part of new release. This saves us from encrypting the web.config file again.
Could somebody please suggest a better way of doing this deployement as it is really turning out to be time consuming. Previously this model was ok for us as we had only 4 web servers but not it is no longer a sutable option.
Thanks..
Take a look at the Web Farm Framework. It will handle the replication of your application across your entire farm.
Another option is to use the "Shared Configuration" option in IIS7 as well as a DFS share to replicate all of your files and metabase configuration. This just won't handle registry changes or the GAC.
I wanted to run a .net application on a laptop. I created the application(aspx pages and SQL database) on a computer that has VS 08 installed. Now i wanted to run this application on a laptop that does not have SQL sever 2005 installed.
As far as the aspx pages if i publish them to a zip drive copy it to my laptop and go into IIS and define a new virtual directory to point where my pages are that should work RIGHT??
Now for the database i don't know what i need to do
any ideas???
Publish the web app to a folder on the laptop and create an IIS Virtual directory pointing to that folder.
As for the DB, install an express version of SQL Server (http://www.microsoft.com/express/Database/) and
point you web app at them.
Have you considered using SQL Server Compact Edition? This will allow you to move the db around with the application.
You need to install sql server on the client(laptop) so you can run the application properly
As far as the aspx pages if i publish
them to a zip drive copy it to my
laptop and go into IIS and define a
new virtual directory to point where
my pages are that should work RIGHT??
Yes this should work.
As for the database, you'll need to install it on the computer you are running IIS on and copy the schema and data over or (I would recommend this way) have your code connect to a server which has the database on it.
You need to install at a minimum SQL Server 2005 express edition. You may also need to change the connection settings for your application, which may be in your .config file(depending on how you did your conneciton in your application) and depending on whether the server instance and database name you choose are different from what you used on your development computer.
Should the ASPNETDB be left in default app folder created by Visual Studio when deploying on webserver? I have another DB that is in the mssql data folder, should that be placed in same directory as well? Im not clear on whether it matters one way or the other.
It depends what environment you are deploying your application to. Specifically, what database servers are available to you or what you are able to deploy.
If you have, or can install, SQL Server and have full administration rights over the instance then the easiest option is to attach both databases to that instance and change your connection strings appropriately. In this case both files should reside outside wwwroot, in a SQL Server specific directory.
I presume this is how the database in your 'mssql' data folder is being accessed. The connection string SHOULD NOT contain 'AttachDbFilename'.
The other option involves SQL Server Express Edition and User Instances. User Instances are created on demand to host a database when the application user does not have the right to attach it to a setup created instance. User Instances run in the context of the application user, ASPNET in your case, and lack advanced security features.
Visual Studio uses this same setup. ASPNETDB is likely using this method. The connection string SHOULD contain 'AttachDbFilename'.
A database that has been created in a user instance can be migrated to a setup instance. However, a database from a setup instance cannot be attached to a user instance because the security information is unavailable.
See Configuring ASP.NET 2.0 Application Services to use SQL Server 2000 or SQL Server 2005 and SQL Server 2005 Express Edition User Instances for further information.