Home > Ax 2012, Ax2012R2 Conference Updates > ALM (Deployment) with Dynamics Ax 2012 R2

ALM (Deployment) with Dynamics Ax 2012 R2

October 24, 2012 Leave a comment Go to comments

Metadata db and the datadb can now be separate 🙂

Single user Topology for development: Microsoft recomments the Single user topology when using sourcecontrol and to manage multiparty development

– Shared application topology is not recommened for the following reasons
– To debug a Pcode the visual studio needs to be used. During the attach process the AOS is paused for all user
– Server restarts for a single user stops the entire application

– Visual Studio Projects – Apart from the Synchornize to the AOT, we must right scripts to run MSbuild for these projects. This
ensures a proper VS project import

Deploying to the Production

– Element id’s as we all know is generated during the import of models, so it is recommended not to import models in to Production
system to avoid id conflicts

– Maintain a seperate staging setup where the metadatastore of the production and staging are maintained commonly. Import models to
the staging and then move the metadata

– Model store import is quicker, will bring the down time and speed up import.

 

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: