Installing two AOS in the same server

(0) Share

Report

Posted on by Eduard R

I'm new to AX 2102.

Currently we have only one AOS instance installed in PRO.

Most of the time this single AOS instance is running in debug mode so developer can attach, debug and quickly figure out what's wrong when user complains.

I was wondering if it is posible or better to have two AOS instances in the same box one for normal users without debug flag, and another one only for developers with the flag set.

In short which scenario do you prefer?

A) A single instance AOS with debug set to true

B) Two AOS instance pointing to the same BBDD, one no debug for users, and another with debug.

And a side question, having two AOS instances pointing to the same BBDD, how it changes the deployment process? The two AOS can have diferent source code versions? I'm interested on keeping always the two AOS sincronized…

All responses (5)

Answers (2)

Sort by

Verified answer

nmaenpaa 101,172 Moderator on at

Like (1)

Report
Copy link

Link copied!

Normally you should not have debugging enabled in a Prod AOS. It will cause a significant performance loss. Also debugging in a live system can cause freezing of user sessions. However if you do so, it's a good idea to have it enabled only in one AOS, and let users use other AOSes. But please make sure that you have licenses for all your AOSes.

When deploying changes, you should always have only one AOS running. After the deployment is done (including compilations and CIL generation if you didn't use Modelstore delivery), start the second AOS. In startup it will get the latest code from the modelstore. If you do not follow this process, two AOSes might indeed have different code versions and this could cause unpredictable issues in your system.

If you are not familiar with MS whitepaper regarding deployment of customizations, now is a good time to check it: docs.microsoft.com/.../deploying-customizations-across-microsoft-dynamics-ax-2012-environments-white-paper
Suggested answer

guk1964 10,888 on at

Like (0)

Report
Copy link

Link copied!

Absolutely. Code should be debugged before deployment to live and debugging on live should be done rarely and with users out of the system i.e. out of hours.

(What happens if debugging finds a a code fault? Is that then going to be corrected and tested in a live system? Will such a code change be recompiled?)

Other than for very small implementations (which is generally not the case for Enterprise systems), I would also expect at least one more dedicated AOS for batch processes like workflows, mrp, retail sync etc
Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

If you find yourself often in need of debugging with live data, you should have another system - copied from Prod, where you always keep the same codebase than in your prod. If you need to debug something, you need to copy Prod databases in this system, and debug the issue. This way the Prod system is not harmed by debugging, and you can still troubleshoot issues fairly quickly.
Eduard R 5 on at

Like (0)

Report
Copy link

Link copied!

And what about having two AOSes (listening on different ports) in the same server? Could it work? In this way I can stop the secondary AOS if I don't need debugging, keeping a teorical good performance.

Regarding licenses, I would need to check it out… The second instance would only be used by developers, no final users there. Like the second instance would be always stopped, from time to time in emergencies I could start it...
Verified answer

nmaenpaa 101,172 Moderator on at

Like (1)

Report
Copy link

Link copied!

Yes, you can have two AOS instances on the same server, on different ports. You need a license for both. Another good reason to do your debugging in a test / prodcopy system instead.