Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
we're currently customising AX to meet our business requirements. We're implementing a single instance of AX which is to be accessed by multiple countries. For each country we're working with a different partner (local to that country) to complete the development work for their requirements. In order to work in this way, we need to give all developers access to a single instance of TFS, and to a single AX Team Server.
As we have different partners developing the code for us, and each partner/company's developers develop on their local machines, the development machines are on a different domain to TFS (in fact, they're in a completely different AD forest). This means that when AX communicates with TFS, the credentials AX sends will not be the ones required by the TFS server.
Were we to give all developers a machine on our network, we'd need to provision for 37 developers, meaning 37 machines capable of supporting an AOS and database, as well as sufferring potential network issues between the developer and their machine - so this feels like a worst case solution.
FYI: We're hoping to use a hosted instance of TFS, but regardless of whether this is hosted or on our company's network, it's still not on a different domain to the developers' machines.
Info on TFS2010 with AX2009 available here: http://daxmusings.blogspot.com/2010/08/dynamics-ax-2009-and-team-foundation.html
Thanks in advance,
The quick solution to all these issues is to use terminal services. Any developer can log into a remote desktop that is hosted in any domain, and log on. You would still need an account in your AD for every developer, but at least not a machine for every developer.
Remember the issue with AX and TFS is that it does not support multiple developers on one AOS out of the box, so using a terminal services scenario brings up that problem again. There are ways around that but it requires customizing the TFS integration in AX.
I've personally not used a hosted TFS, but I've talked with one of the hosting companies and they say that AX will "prompt" you for credentials to log into TFS. I have not tested or verified this at all, but there are multiple companies offering hosted TFS for AX so I assume this somehow works, whether it's with a credentials prompt or otherwise.
As far as the "team server" for AX IDs, that is just a database (no service), and TFS does not need access to that, so you should host that internally. One of the requirements though is that it is NOT hosted on the same database as your AX database (authentication issues otherwise).
Dynamics AX MVP | My Blog | Sikich | Twitter @JorisdG
That's great - thanks Joris. We'll test AX 2009 with a hosted TFS and feed back on how we get on.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13