Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Monday, January 02, 2006

Single Node vs. Shared for AOS

Someone asked me on tech-unity.com the difference between a Single Node vs. Shared for setting up an AOS. I found the below to be very helpful:

Single Node Object Server

(Exclusive mode/Advanced Object Server)
The Exclusive Mode of the AOS applies to systems where one AOS services an application exclusively to all clients. In such an environment, only one AOS operates for each application running. This gives wider possibilities for exploiting caching mechanisms to obtain better basic throughput. It also provides efficient means for obtaining One-system Awareness (the situation where all clients are known and controlled by one central instance capable of dispatching messages, reporting on complete system condition, and managing all sessions).

Load Sharing Object Server

(Shared mode/Parallel Object Server)
The Shared mode of AOS is used in situations where AOS, for any reason, must coexist with other AOS (or during migration to the AOS environment, to coexist with standard 2-tier Axapta clients accessing the same application and data resources). In the Shared mode, the AOS allows others to access the application object database (AOD). This allows starting multiple AOSes (at different Windows NT Servers) servicing the same network-shared application, and accessing the same data at the SQL server. This mode gives a reduced basic throughput (compared to the Exclusive mode AOS) due to the reduced possibilities with respect to caching, but it provides a wider specter of scalability by allowing a number of Object Servers to run in parallel. Using the Load Balanced Client Connect feature of Axapta, the client sessions are distributed over the servers available when a client logs in. In such an installation, even servers of different capacity can cooperate on servicing clients in the load-distributed AOS environment.

There is some more great information where I found this at: CenterLineERP

Find a job at: www.DynamicsAXJobs.com


Post a Comment

<< Home

Copyright 2005-2011, J. Brandon George - All rights Reserved