emeadaxsupport: How to install AX 2012 Enterprise Portal in a multi-server web farm

[Blog bot]

Источник: http://blogs.msdn.com/b/axsupport/ar...-web-farm.aspx
==============

This blog post is written to clarify some steps in the installation guide https://technet.microsoft.com/en-us/.../dd309729.aspx when you install AX 2012 Enterprise Portal (EP) in a multi-server web farm.
It is important to follow the installation guide and use this post as additional info.

Under section “Before you begin”:

Host header

When installing EP in a multi-server web farm then you need to use host header. Review the SharePoint documentation about host headers and Web farms before you install Enterprise Portal.
Here are links to articles:
Install and configure SharePoint 2013: https://technet.microsoft.com/en-us/.../cc262957.aspx
Install SharePoint 2013 across multiple servers for a three-tier farm: https://technet.microsoft.com/en-us/.../ee805948.aspx
SharePoint IT Pro Blog: http://blogs.technet.com/b/tothesharepoint/
Office blogs: https://blogs.office.com/?filter=tru...uct=sharepoint
Host-named site collection architecture and deployment (SharePoint 2013):
https://technet.microsoft.com/en-us/.../cc424952.aspx

Good non MS SharePoint blog: https://stevegoodyear.wordpress.com/

Here is a couple of blog post how to set up Network Load Balancing in SharePoint farm: http://community.bamboosolutions.com...rver-farm.aspx

http://community.bamboosolutions.com...rver-farm.aspx



BackConnectionHostNames

You need to add BackConnectionHostNames in Windows registry on each of the web servers in the farm.
Ref: https://msdn.microsoft.com/en-us/library/cc982052.aspx and https://support.microsoft.com/en-us/kb/896861

Example:
You are using the host header “EP” and your domain is contoso.com
Open Registry editor (regedit) and create a Multi-String registry key with name BackConnectionHostNames under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 with following values



Quit Registry Editor, and then restart the IISAdmin service and run IISReset for the changes to take effect.

If you use the FQDN (fully qualified domain name) as the load balanced host header then you add only the FQDN in BackConnectionHostNames, e.g. only EP.contoso.com



Under section “Before you install Enterprise Portal”:

Web application

If you intend to deploy Enterprise Portal in a load balanced multi server web farm, then you must use SharePoint Central Administration to create a new Web application using the host header before you install Enterprise Portal.

In “Install and configure SharePoint” point 1 it is stated: “If you are using a load balancer, specify a site name in the Load Balanced URL field on the Web application that will host the Enterprise Portal site”.
This means that you should specify the load balanced site name in the Host Header field.

Example:
You plan to use http://EP.contoso.com as the load balanced URL to access Enterprise Portal. In this case you need to specify the host header “EP.contoso.com” when creating the web application.

Create a new Web Application.
1. Log on to the server hosting the Central Administration Service as the SharePoint Farm Administrator account.
2. Open the SharePoint 2013 Central Administration site and under System Settings > Manage services on server, ensure that the Claims to Windows Token Service and Microsoft SharePoint Foundation Web application service is started.
3. In Application Management > Manage web applications, create a new web application on port 80 and set the host header name to “EP.contoso.com”.





Note: Set the application pool identity under Configurable to be the same as your Business Connector Proxy User account defined in AX (Administration > Setup > Security > System Service accounts).



4. Once your web application has been created, create a TEST SharePoint Team site and validate you are able to browse to it from both the Central Admin server, WFE servers and clients.


Hosts file

If you already have configured the load balancer for the farm, then you need to edit the hosts file on each server in the farm before you install Enterprise Portal. When you browse to the load balanced URL it will be resolved to the IP address of the load balancer which will route the request to a Web Frontend Server (WFE). If you try to install EP without editing the hosts file, then the web application URL will be resolved to the load balancer instead of the local machine and the installation will fail.
The hosts file is located under C:\windows\system32\drivers\etc
Add a line with local IP address mapped to host header on each server.

Example:
The web farm consists of 3 servers and load balanced URL is EP.contoso.com:
Central Admin server with IP 10.10.50.101
WFE1 with IP 10.10.50.102
WFE2 with IP 10.10.50.103

On Central admin server add this line in hosts file:
10.10.50.101 EP.contoso.com
On WFE1 server add this line in hosts file:
10.10.50.102 EP.contoso.com
On WFE2 server add this line in hosts file:
10.10.50.103 EP.contoso.com



See this blog post for how to update AX 2012 Enterprise Portal in a multi-server web farm: http://blogs.msdn.com/b/axsupport/ar...-web-farm.aspx






Источник: http://blogs.msdn.com/b/axsupport/ar...-web-farm.aspx