i got 10 IIS Server Farm and total 5 server on my configuration same machine. Each server farm has different arr configuration with different domains. What is the best aproch to configure application provisioning. Now i use one provision farm to sync all 5 servers and other farms for load balancing. Should i set all 10 farms with application provisioning or not ?
Related
So I am a bit confused about SharePoint server deployment. Let me give a run down of how I want the installation to be.
We have about 6 servers with shared minroles and below is the plan on how we want it to be setup.
2 web front-end/distributed cache server
2 Application/search servers
2 db servers.
1 custom server
Also looking at setting up a load balancer for the 2 front-end servers.
My question is this, do I have to install SharePoint server software in all the servers in other to select their roles? I'm confused about that part.
If thats the case how do i go about the deployment really. Confusing
Yes, you have to install SharePoint SharePoint server software in all the servers.
First, you need to Create and configure the farm on the application servers. After creating the farm, you can add the servers to the farm. The below article would help you:
https://learn.microsoft.com/en-us/sharepoint/install/multiple-servers-for-a-three-tier-farm
https://learn.microsoft.com/en-us/sharepoint/install/add-web-or-application-server-to-the-farm
https://learn.microsoft.com/en-us/sharepoint/install/add-a-database-server-to-an-existing-farm
We have 2 Azure VMs running IIS and hosting 50+ .Net web applications (Webforms, MVC, WCF & ASMX). Both of the 2 VMs are identical and all sites are configured using a hostname ([subdomain].domain.com) on port 443 and requiring SSL.
11 of these sites are legacy and require afinity because of session state, all other sites don't and can be randomly loadbalanced.
All of the sites run perfectly on each of the 2 servers.
Now we would like to put an Application Gateway in front of the 2 VMs to provide loadbalancing, https redirect, WAF, ...
Can we configure 1 Application Gateway to do all this and make sure the affinity is only valid for those 11 sites and not for all of them and also do the https redirect?
Or do we need to configure 2 Application Gateways, 1 for the 11 affinity-dependent sites and 1 for the remaining and then have dns point to 1 of the Gateways?
In Application gateway you can create 100 Listeners (For WAF enabled
SKUs). So you should be able to accommodate your setup with one
Application gateway.
When you are creating HTTP settings, you can choose whether to
enable Cookie based affinity or not.
Application gateway has all the feature you requested, like HTTP to
HTTPS redirection, WAF protection.
So you should be able to deploy an Application Gateway and configure to make your setup work.
I'm in the process of migrating an existing website into Azure for a client. The current architecture is 4 web vm's mated to 4 sql server vms. One web vm per sql server vm. Complexity and cost is prohibiting us from migrating the sql server vm's into azure sql servers. These are read only databases and use log shipping to keep them synced.
I have easily published the asp.net application to an azure web app. My question is, how do I evenly distribute the web app instances to the 4 sql server vm's?
Depending on hourly traffic, I can see anywhere from 2 to 8 web app instances running at any given time. How can I evenly distribute the load to the 4 database vm's?
Depending on how you setup your environment you could put an Azure Internal Load Balancer (ILB) in place to load balance TCP 1433 across the four back-end SQL Database Servers.
You might need to tweak the distribution mode, but I'd run it first to see what the performance is like. If the Database is relatively static perhaps you could even consider using a VM Scale Set to scale out SQL based on load.
I have a SharePoint web application that has some custom web parts that consume an asmx web service. This service talks to an Oracle 10g database. Currently, the service is hosted on the application server in its separate web site (and port). I think I should host it on the front end servers under the _vti_bin folder to automatically achieve high availability and load balancing of the service calls. Would you recommend this "enhancement"?
Please notice that the asmx service is configured to run in a 32 bit app pool since oracle client, which it uses, is 32 bit software. I think then I can’t just have it under _vti_bin, I may need to have it in its own virtual directory under the SharePoint application’s IIS web site and configure that VD to run in a separate 32 bit app pool. Will that work out? Will I still achieve the HA and LB benefits knowing that Windows NLB is used?
Another related question; should the service be hosted on the WFE in the first place? It hits an external database which I could think of as a middle tier service that can be kept on the application server(s); one more server to be added soon
I have two computers - Computer1 and Computer2. I deployed my web application on IIS 7 in Computer1. I have access to it from browser in Computer1 by http://localhost/home.aspx, but I don't have access to this web application from Computer2 by http://computer1/home.aspx. What should I do to have access to it from Computer2?
Maybe firewall creates problems.