DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Objective: To have two EP Sites that are connected to two different AOS's, configured on a single server machine.

Current Software & Hardware Environment

  • Server runs on a 64Bit Processor
  • Windows 2003 R2 Enterprise 64 bit with SP2
  • SQL Server 2005 SP2
  • Sharepoint Server 2007
  • Dynamics Ax 2009

Current Configuration

  • Sharepoint is installed to run on a website “Sharepoint – DEV” (on port 80) and uses an application pool with the same name. The app pool uses a Ax admin account for its identity, the account will be referred to as “AxAdmin” in this blog entry.
  • The Dynamics Ax 2009 Client Configuration is configured to use the “Development” AOS referred to in this blog entry as “DevAOS” and so is the Business Connector.
  • The “AxAdmin” account is configured to be the Proxy account for accessing Dynamics Ax through the Business Connector.

 Configuring two EP Sites linked to different AOS’s coexist on a single server

  1. Run the “Ax 2009” installation.
  2. Select “Add Remove” (or Repair) option from the installer screen.
  3. Select “Role Centers and Enterprise Portal” as the component to be installed.
  4. Enter the password for the “AxAdmin” account which is also the Proxy account
  5. Select  the website “Sharepoint –Dev” , Check “Configure for Windows Sharepoint Services” and check create web site – the site url is “http://myserver/sites/DevSite” – referred to as “DevSite” in this blog entry
  6. Complete the installation. After which the development site is up and running. The “DevSite” connects to “DevAOS” and works fine.
  7. Create a new “Application Pool” using the existing “DevSite” application pool “Sharepoint – Dev” as the template, this application pool will be referred to as “Sharepoint-Test” in this blog entry.
  8. Create a new website “TestSite” and use “Sharepoint – Test” as the application pool. Set the port to “90” (any port that is not is use already)
  9. Open the “Dynamics Ax Client Configuration” and change the AOS referred to by the Local Client and the Business Connector to the “TestAOS”
  10. Open the AOT of “TestAOS” and select Web > Web Files > Static Files > EPSetupParam and edit it – Change the URL to “TestSite”.
  11. Repeat steps 1 to 6 on the new website.
  12. Add the following Web.config entries based on the blog entry from Solutions Monkey

https://blogs.msdn.com/solutions/archive/2006/09/11/ep-configuration-single-web-server-multiple-aos-installations.aspx

On the Web server, make the following edits to the Web.config file in the wwwroot folder (for example, C:\inetpub\wwwroot where the Second Web server is installed in the C: drive):

 1) Add the Microsoft.Dynamics section group under <configSections>. Add the following text:

<sectionGroup name="Microsoft.Dynamics">
<section name="Session" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral,PublicKeyToken=b77a5c561934e089" />
</sectionGroup>

2. Add the following Microsoft.Dynamics element under </system.web>. Add the following text to the file:

 <Microsoft.Dynamics>
     <Session Timeout="15" Configuration="C:\Inetpub\wwwroot\axapta.axc" />
 </Microsoft.Dynamics>

You can export the AX configuration pointing to the second AOS to a file  and refer it in the second step.

 

 

NOTE: The installation creates a new application pool and a new website virtual directory with the same name but prefixed with a GUID.

NOW how two versions of the product being developed should be deployed on the same sharepoint server is still a QUESTION Hmmm will get back to this blog after I have an answer from the Microsoft guys :)
Workaround: Create a new Layout and ControlTemplate folder and change the web folders in the new website to refer to the new folders and copy the controls to the new folder. This is a clumpsy fix but it works !!

Possible errors

The installation might rollback if there are users connected to the AOS - and the DAX dlls might be locked. There is another error which was encountered saying "Sharepoint port" is already in use dont know the reason for this error but try stopping the other website during the installation

posted @ Tuesday, August 12, 2008 7:37 PM
Print

Comments on this entry:

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Joern Krebs at 10/1/2008 12:28 PM
Gravatar
Do you have found a solution for this problem? We are facing the same problem, but with at least 30 customers. If we are havin an error, it will be a very "detroying" one. ;-)

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Prabhat Samuel at 10/12/2008 6:47 PM
Gravatar
As mentioned in the blog we have a very rough work-around, but havent got a straight-forward solution to creating multiples.

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Shereen at 6/30/2009 5:19 AM
Gravatar
How do i link to a specific AOT in visual studio 2008 when using multiples EP

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Shereen at 6/30/2009 8:53 AM
Gravatar
Hi Prabhat,

Thank You so much for your reply.
I really appreciate it.

We have 3 enviroments a dev, test and Production Enviroment for Ax.

Questions:
1. How do you link a specific environment(AOT e.g. test or dev) to a Enterprise Portal site.
2. When I am Visual studio 2008, and a create a project specific for an environment-
How do know which environment I am linking to viz “Add to AOT”
3. When I open Visual Studio 2008, create a new User control, then the button for add to AOT is absent.


Thank you

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Tomas at 9/10/2009 12:16 AM
Gravatar
Hello!
I followed your instructions and got i to work om my local VPC image.
However in out rest-environment when installing the Role Center/EP I get the same error as described below:
http://geekswithblogs.net/ssmantha/archive/2009/05/12/axwebpart.cab-deployment-failed-while-doing-dynamics-ax-2009-enterprise-portal.aspx

The files mensioned for deletion does not exist om my web-server so nothing to delete...

This has the effect that the existing Ax-solution in SharePoint is retracted.
Any suggestions?

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Trung at 9/24/2009 2:34 PM
Gravatar
Thank you,

I have problem when create website for second EP. Sharepoint cannot create website successful with this error "The remote server returned an error: (500) Internal Server Error"
Anybody have idea about this?

# re: DAX 2009 - Single Server Multiple EPSites (BC.NET - AOS)

Left by Migliori casino at 1/6/2011 7:36 PM
Gravatar
I feel strongly about it and love learning more on this topic. If possible, as you gain expertise, would you mind updating your blog with more information?...

#  ram van pcm

Left by Austin Steven at 10/7/2012 8:57 PM
Gravatar
Your blog to write very inspiration, very philosophy, write very close to the life. This is the perfect blog for anyone who wants to know about this topic.

# Indian roommate classifieds

Left by Parol Pedazo at 2/18/2013 11:47 PM
Gravatar
Nice, hard coded cookie in program! Please send me sites which generate one session key per user. I mean thats this methods is a bug.

Your comment:



(not displayed)

 
 
 
 

Live Comment Preview:

 
«January»
SunMonTueWedThuFriSat
272829303112
3456789
10111213141516
17181920212223
24252627282930
31123456