web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Synchronization of multiple AOS instances

(0) ShareShare
ReportReport
Posted on by

Hello

We are using AX 2012 CU5. Is it possible to synchronize multiple AOS instances without restarting the AOS service? I've heard that there is something like compiling CIL to do the job but I'm not sure. Can somebody tell me what the possibilities are without restarting?

Problem is that from now when I make menu-items or reports/forms on one AOS, I always have to wait untille restart of AOS before it is also available on the other AOS instance (we have 2 instances balancing). Currently we are in the middle of a dataconversion phase for some Finance modules. Due to this, we cannot restart AOS instances for 2 weeks.

Regards

Luk

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    You really shouldn't develop in production environment, much less in a clustered one. Create a separate AX environment for development.

    By the way, how does a data conversion prevent AOS services from being restarted?

  • Community Member Profile Picture
    on at

    I never develop in production environment. I develop in Test and export all objects. Then I import them in production. From then I have the problem because I only import on one AOS.

    Data conversion is beiing done by a specific module in AX. Closing AX during the process is no option.

  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    Aha, all right.

    I suspect there is no way to be sure that new DLLs etc. are loaded without restarting the process. You could restart AOSes one by one, as you do.

    Nevertheless I would strongly suggest following the recommended procedure, i.e. stopping AOS services, importing updated model store and starting AOSes. That ensures that you get exactly the same version you tested, you don't have to compile anything in production, new versions of DLLs are loaded and so on.

    I understand that there may be cases when you really can't do that, but I would still rather use my time to remove the impediments than finding ways how to avoid supported procedures.

  • 1807Beers Profile Picture
    160 on at

    Hi,

    When doing modelstore deployment (from test to production environment for example), advice we have been given is to stop all production aos instances, import modelstore, start one aos instance, full cil generation, start all other aos instances.

    How does the CIL actually get refreshed on all other aos instances and is it possible to check they have been refreshed successfully?

      

  • Suggested answer
    Umesh Pandit Profile Picture
    9,315 User Group Leader on at

    Hi Luk,

    Best practice for synchronize multiple AOS instances is to stop all instances,except one on which you will be doing the sync.

  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    It shouldn't be necessary to even recompile CIL. The model store already contains CIL code and DLL files are deployed when the AOS starts.

    About validation, you can review DLL files in XppIL folder.

  • 1807Beers Profile Picture
    160 on at

    Thanks for reply.

    So does Full CIL Generation store CIL in modelstore, then start of aos extract latest CIL from modelstore?

    I've done Full CIL Generation on one aos (with all the others stopped) and can see dlls dated as expected in XppIL folder on that aos, but in other aos started after Full CIL Generation the dlls show older dates as if they've not been refreshed?

  • Community Member Profile Picture
    on at

    Hi ...

    I don't mean to take us off topic or hijack the thread but I've read one option for code promotion is to use a temporary schema. On the surface it seems like it would be the option with the shortest down time required but counter to what I've read in terms of actual adoption; meaning most seems to prefer the modelstore import versus a schema swap. Can anyone explain the pitfalls of using a temporary schema?

    Thanks in advance.

  • AXT Profile Picture
    1,699 on at

    Hi, i'm wondering if and how you solved this issue. We are phasing exactly the same issue since we have more than 2 AOS instances. We are following the same procedure as described in the last response from 1807Beers. We are on AX 2012 CU5  and currently have 5 AOS Instances, one dedicated for Batch and not in the cluster. Is the a known issue/bug with AX2012 RTM or anybody has the same with R2/R3?

  • Dilliraj Pudi Dasarathan Profile Picture
    86 on at

    Generally all the other AOS the DLL's should generate automatically which is picked from SYSXPPAssembly from DB. 

    However, the .xpp files under source folder doesn't get refreshed automatically unless you generate a incremental one. in each of the AOS.  When the AOT is edited for any purpose. 

    When you debug through Visual Studio, you can observe the .xpp files missing in the other AOS other than the primary AOS where it is deployed. 

    It is recommended to Generate Inc CIL to be on Safe Side, which doesn't take time. 

    Regards

    Dilliraj 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans