The recommendation is to use a name that clearly identifies the customer,
version, and type of installation. This name should include a short form of the
customer name, the Microsoft Dynamics AX 2012 version, the service pack
version, and a code for the installation type, such as Live, Test, or Dev.
Example
The CON_AX2012_Live name signifies that this is a live, or production
installation of Microsoft Dynamics AX 2012 without any service packs for the
Contoso Entertainment customer. If the administrator wanted to track service
packs, the name could be changed to CON_AX2012_SPxx_Live. where xx
would be the number of the service pack installed.
One reason for having a clear naming convention is that the Microsoft Dynamics
AX client or AOS configuration links the application object together with the
database. If the names are not clear, it is easy to accidentally set up a client to use
development application objects and connect to a production database. This
could result in lost or corrupted data.
NOTE: Always use alphanumeric characters meaning a-z and 1-0. Do not use
special characters such as # & ( ) and so on. Do not use blank spaces in names
or directories, use - (dash) or _ (underscore) instead.The following table shows clear naming conventions for the database,
application, client, and instance names:
Install Type | Base Role | Good Naming Convention |
Live Environment | Database Name Application Name AOS Name Client Name | CON_AX2012_DB_Live CON_AX2012_APP_Live CON_AX2012_AOS_Live CON_AX2012_Client_Live |
Test Environment | Database Name Application Name AOS Name Client Name | CON_AX2012_DB_Test CON_AX2012_APP_Test CON_AX2012_AOS_Test CON_AX2012_Client_Test |
Development Environment | Database Name Application Name AOS Name Client Name | CON_AX2012_DB_Dev CON_AX2012_APP_Dev CON_AX2012_AOS_Dev CON_AX2012_Client_Dev |
NOTE: Be aware of possible customer sensitivity with regard to using the
company name as part of the naming convention. Be certain that the naming
convention is decided together with company executives.
Regards,
Hossein Karimi
No comments:
Post a Comment