Install an AOS instance on multiple computers
Hossein.K
6,642
Like
Share
Report
For most production environments, you will install multiple AOS instances, each
on a different server. You can use multiple AOS instances to support batch
processing and load balancing. If you plan to install multiple application object
servers on the same computer, you must specify a unique port for each AOS
otherwise port conflicts will cause one or more application object servers to stop.
Install each AOS instance as described in the "Procedure: Install an AOS
Instance", but be certain to point all the AOS instances to the same database. You
can use a single domain account for all instances of the AOS service or you can
specify a different account for each instance. It is recommended that you use a
separate domain account for each AOS instance.
If you use multiple accounts, you can create a group in Active Directory to more
easily manage AOS account permissions. Use the following procedure to set up
permissions for the Active Directory group.
1. Create a group in Active Directory.
2. Add the AOS accounts to the group you created.
3. Make the Active Directory group a login on the database server.
4. Make the login a user in the Microsoft Dynamics AX database, and
add the user to the following database roles: db_ddladmin,db_datareader, and db_datawriter, and grant access to the
following objects.
5. Grant the Active Directory group full permissions to the folder that contains the application files.
Regards,
Hossein Karimi
on a different server. You can use multiple AOS instances to support batch
processing and load balancing. If you plan to install multiple application object
servers on the same computer, you must specify a unique port for each AOS
otherwise port conflicts will cause one or more application object servers to stop.
Install each AOS instance as described in the "Procedure: Install an AOS
Instance", but be certain to point all the AOS instances to the same database. You
can use a single domain account for all instances of the AOS service or you can
specify a different account for each instance. It is recommended that you use a
separate domain account for each AOS instance.
If you use multiple accounts, you can create a group in Active Directory to more
easily manage AOS account permissions. Use the following procedure to set up
permissions for the Active Directory group.
1. Create a group in Active Directory.
2. Add the AOS accounts to the group you created.
3. Make the Active Directory group a login on the database server.
4. Make the login a user in the Microsoft Dynamics AX database, and
add the user to the following database roles: db_ddladmin,db_datareader, and db_datawriter, and grant access to the
following objects.
| Type | Permission | Objects | ||
| Schema | Control | DBO | ||
| Table | Select | SchemaVersion | ||
| View | Select | UTILELEMENTS, UTILIDELEMENTS, UTILMODELS | ||
| Stored Procedure | Execute | CREATESERVERSESSIONS, CREATEUSERSESSIONS, getNumInternal, XU_AllocateHandle, XU_AppendMerge, XU_AppendMergeSecurityMetadata, XU_AssignAxId, XU_BuildElementList, XU_BuildElementListByParentHandle, XU_BuildElementListByParentName, XU_BuildHandleOrderList, XU_BuildNameOrderList, XU_BulkReadHdlElements, XU_ConflictDetectPreProcess, XU_ConflictDetectRedo, XU_ConflictResolve, XU_ConflictResolveReplace, XU_ConflictResolveToNewModel, XU_ConflictResolveToNewModels, XU_CreateModel, XU_CreateVirtualModel, XU_Delete, XU_DeleteElements, XU_DeleteExt, XU_DeleteLabelTextByHandle, XU_DeleteModelOnly, XU_DeleteModelsInLayerOnly, XU_DeleteMovedElements, XU_DeleteReferencedModelElements, XU_DeleteTopElements, XU_DeleteVirtualParentsMerge, XU_DirtyLayers, XU_DirtyModel, XU_DisableEnableNonClusteredIndexes, XU_Find, XU_FindByNames, XU_FindByParentHandle, XU_Fixup,
|
Regards,
Hossein Karimi
*This post is locked for comments