AX7 production and development

(0) Share

Report

Posted on by Community Member

Hi Guys,

I am a little bit lost here, so will appreciate any help here. There are two option how we can develop: deploy to Azure VM and get VHD on local machine. I am currently using local machine. There are couple issues, but generally it is all good.

Now, when I start thinking on how the production will look like, (in 2012 you don't have much difference between your dev and prod), I am a bit confused. If you look at this picture: http://msdynamics.blob.core.windows.net/media/2015/08/ArchitectureDrawing1.png

, it shows you two data bases: master and read only. Everywhere it says that AX7 will use the SAAS as much as it can. So, for production, will we have VM with SQL Server on it? with all reporting services etc? Where would be that read only and master dbs? Different SQL Servers? Should we do it by our self on configuring log shipping etc?

I understand, that Dynamics 365, this is something that will be closed and you only will have access through the front end, like office365.

Another thing is, when deploying environment through LCS, if we are using Azure after I can see my environment listed, but with local VHD, there is no connection between LCS and my local AX?

Please help to clarify

Thanks

Nick

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (2)

Suggested answer

Mea_ 60,284 on at

Like (0)

Report

Hi Nick Savenko,

You won't have any access to PROD at all. It would be build and managed by MS. All deployments would be done by MS through LCS. The only source of info about it for customers and partners is diagnostic tool on LCS where you an track hard drive usage, CPU, batch job errors and other stuff related to AX and environments.

Prod and sandbox (UAT) use Azure SQL and SSRS instead of SQL server you have on dev and test.

I think that read only DB is entity store. blogs.msdn.microsoft.com/.../power-bi-integration-with-entity-store-in-dynamics-ax-7-may-update

It is read only and you will have access to it to do your BI.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Ievgen

Thank you for your reply.

So, is there any way to try the prod AX? I need to make sure that my solution will work...

Also, how would we know the SQL server which is read only? On that article it says, that you will need to put your SQL server and name of AX db... Is it available through LCS as well?

Thanks

Nick

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

What do you mean under "try PROD" ? You have to have customer going live for that.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,130 Super User 2025 Season 2 on at

Like (0)

Report

Hi Nick,

You.cannot tryout a production environment. It would be available for customers.

Database information and login details are visible on LCS.

When using a local VM there is indeed no link to LCS. This because the monitoring tools does not know when and where this VM will be run. The local VM would be used as development box. Then you can connect via Visual studio online to check in modified objects.

The Production and accepance environments are MS managed and using SQL services etc. Acceptance is production like. A Dev/Test deployed on LCS has its local SQL server.

Was this reply helpful? Yes No
lally 8 on at

Like (0)

Report

Interesting topic.

From the above posts what i understood is AX 7 production environment will be managed by MS .

What about Dev/Test/UAT environments of AX 7 ? Does it also managed by MS ? or Can be accessed by partners/Customers in-house team ?

How to send the customized builds to MS to deploy in production environments for AX 7 ?

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (1)

Report

Hey lally,

Please create new thread for new questions, otherwise it's hard to follow thread with multiple questions.

Talking about AX environment customers and partners have full access to all environments except prod.

You are not sending "builds" you are asking MS to deploy package from LCS, so you need to create package, deploy it to asset library in LCS and create incident for deployment.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you guys for your answers.

So, if AX will be managed by MSFT and administrators wont be able to connect to VMs, I understand there will be no hybrid environments?

Guys, this is from this link: ax.help.dynamics.com/.../architecture-changes-in-ax-7

The cloud architecture consists of three main conceptual areas:

Microsoft Dynamics AX – Dynamics AX VM instances are deployed through LCS to your Azure subscription. Various typologies are available: demo, development/test, and high-availability production typologies.

This is what is confusing me. If they will deploy it through my subscription, I should be able to access my VMs...? no?

Why I actually need to try a production, because of the BLOB storage. Local Emulator doesn't support HTTPS, and AX perevents to display anything from HTTP due to the security issues. So, I don't know how to make sure my solution will work 100%.

Anyway, thank you for help

Nick

Was this reply helpful? Yes No
lally 8 on at

Like (0)

Report

As the questions related to the same post ..so i am asking questions in same post ...believe this will be last conversation in this post.

[quote user="ievgen Miroshnikov"]You are not sending "builds" you are asking MS to deploy package from LCS, so you need to create package, deploy it to asset library in LCS and create incident for deployment.[/quote]

As you highlighted above, does the process applicable to only Prod environment or for Dev/ Test/UAT /.. environments also follow the same process or partners/customers can directly deploy the builds in this environments. ?

Assume that client has some performance issues in production only but not in Dev/ Test/UAT /, being a developer if i do not have the access , then how to access production environment and how to resolve ?

Or MS team can resolve such issues on paid services ....How does it work ?

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

@lally

Partner has full access to dev\test\build and sandbox, all except prod.

Developers use VSO to synch changes between dev boxes.

You are using build box to build changes from VSO and deploy them to test. But you can use VSO, manual package transfer everything you would like.

Than you deploy your package to LCS and from LCS your deploy it to sandbox. Sandbox has same topology as Prod but probably less resources. As you have full access to sandbox you theoretically can install VS and do debugging or synch changes from VSO and build there.

If change was accepted your are asking MS to deploy it to Prod.

Now, you have diagnostic tool in LCS to monitor Prod performance like CPU, long running queries and so on. You can restore a backup of prod to sandbox to try repro you issues on same data, that's literally all.

MS have different service plans for AX with different level of service www.microsoft.com/.../service-plans.aspx some of them include proactive support so MS will look at performance other not so you need to open incidences by yourself.

Was this reply helpful? Yes No
Verified answer

Mea_ 60,284 on at

Like (0)

Report

@Nick

You probably need to talk to MS if it is possible to get Sandbox deployed for you, however it won't be free anyway.

There is a hybrid cloud support in MS road map but no real dates, something like end of 2017 or 2018 and no details about architecture.

Was this reply helpful? Yes No