Wednesday, June 29, 2016

Install AX Enterprise Portal on SharePoint 2013 Multi Server Farm

How I Installed Enterprise Portal on a SharePoint 2013 Multi Server  Farm

Brief overview of SharePoint 2013 farm.

  • 1 Application server on Windows 2012 R2
  • 1 WFE server on Windows 2012 R2
  • 1 Index server on Windows 2012 R2
  • 1 SQL Server 2014 on Windows 2012 R2


Permissions:
          After fighting with permissions for a while I finally resolved my permissions issues.  Now this was my first successful install and it is a Dev environment so I’m was not really worried about giving too many permissions.  There are 2 accounts AX uses that I had to grant permissions to in my SharePoint Environment and on my servers.  AXBCProxy account and the AX_Install account.  I entered both of these accounts in the Server Admins group on all the SharePoint Servers in the farm.  I also made them Farm Administrators and Assigned them full control in the Web Application.  In SQL I gave them Db Creator role and in the SharePoint _Config and SharePoint_AdminContent DB’s I gave them WSS_Content_Application_Pools Role.

Note: My normal SharePoint configuration I would be running Microsoft SharePoint Foundation Web Application only on the WFE server but for the install of EP I will run it on the Application server as well while I set this up.

We are running AX 2012 CU 9. The AX environment was already configured. I then built a SharePoint 2013 Farm pathed to May 2016 CU.

Now I tried installing the AX software just on the WFE server initially, howerver this did not work. The EP portal template option never appeared when selecting SharePoint 2010 Custom Template while creating the EP Site Collection.  Some of the documentation I’ve read said to install EP on a multi-server farm you had to create a DNS record and point it to the WFE. That did not work for me so I came up with this alternative.

SharePoint Instructions:
         Log on to the App Server with your SP_Farm admin account. Create a new Web Application.  I called mine http://WFEMachineName:Port but I used the WFE’s Machine Name and not the App Servers. I then created a root site collection. This allows you to see that SharePoint is working correctly before installing Enterprise Portal (EP).  I always temporarily turn off Anti-Virus on the App\WFE servers before starting the install. 

AX Instructions:
              Now logon to the App Server and WFE Server with your AX_Install account and run the Prerequisites checker for all the pieces of AX you wish to install.  After the prerequisites have been installed.

I deployed the following AX components on the App Server and the Web Server. I started the Dynamics AX wizard and installed Client Components> Client & Remote Desktop Services integration Note: I did not install Office add-ins

Next I installed  Management Utilities and finally I installed EP on both the WFE and App servers. The EP install is pretty straight forward until you get to the Configure a Web Site for Enterprise Portal page.  Select the Web Application that you recently created. Then uncheck all of the check boxes and Click Next> Click Install>

I tried the install with the boxes checked and it was never successful. It cost me a lot of time troubleshooting and I never got it to complete successfully.  I found this blog helpful but it did not answer all my questions: https://blogs.msdn.microsoft.com/


After successfully installing EP on both servers.  I edited the Hosts file on the App server.  I entered the IP address for the App Server and the name of the WFE server.

Example: 10.1.1.2    WFEServerName

Create the EP Site Collection:
      Login to Central Admin with the AX Install
             Create Site Collection>
                      Select the Web Application you created for EP: Fill in the required fields.
Example:
     Title:  EP AX Dev
     URL: http://MachineName:Port/sites/DynamicsAX
     Select Experience Version> 2010>
     Click on Custom Tab>




    Select Microsoft Dynamics Enterprise Portal>
    Add Site Collection Administrators
    Click OK>

Almost done:
          After the site is created test it from the Application Server.  If it works, and it should, double check that the site was also deployed to the WFE server. Test to make sure the site works from the WFE Server as well.  Now delete the entry put in the HOSTS file on the App Server. Back in Central Admin go to Manage Services on Server > Select the App Server > Click Stop Microsoft SharePoint Foundation Web Application This can take a minute or two.  After it has stopped go to IIS on the App Server and check to see that the site has been removed. Now test to make sure you can still get to the EP website. This worked for me and I hope it helps you. 

Regards,
Scott Davis


0 comments:

Post a Comment