Professional Documents
Culture Documents
REVIEW V1.1
Larry Reski
Bio:
Table of Contents
Moving between Microsoft Dynamics AX 2012 Environments ................................................................. 1
SUMMARY...................................................................................................................................................... 1
Restore the database and set proper SQL permissions ........................................................................................ 3
Verify the Kernel and Application versions in the Database ............................................................................. 3
Setting Database Permissions for the AOS service account.............................................................................. 3
Provide Microsoft Dynamics AX user credentials ................................................................................................. 5
Changing the Microsoft Dynamics AX users account to new Domain Account information .............................. 5
Configure Base System functionality ................................................................................................................... 7
Changing the System Service Accounts ........................................................................................................... 7
AOS Services .................................................................................................................................................. 9
Install or configure additional components ....................................................................................................... 12
Non-interactive Business Connector Configuration ....................................................................................... 12
Workflow ..................................................................................................................................................... 13
BI Components ............................................................................................................................................. 14
OLAP database ............................................................................................................................................. 14
List of Connection strings that reference server and database names............................................................ 14
Help Server .................................................................................................................................................. 15
Enterprise Portal and Role Centers ............................................................................................................... 16
Enterprise Search ......................................................................................................................................... 18
Project Server Integration............................................................................................................................. 19
Web Service on IIS ........................................................................................................................................ 19
Customized Business Connector integrations ................................................................................................ 20
Appendix.......................................................................................................................................................... 21
Unique GUID per Microsoft Dynamics AX environment ................................................................................. 21
REVIEW V1.1
There are special circumstances where there are AOT based metadata and matching SQL
database records that need to be moved together, such as customized security or workflow
objects. The topic of moving code will not be covered here, but you can refer to Microsoft
Dynamics AX 2012 White Paper: Deploying Customizations Across Microsoft Dynamics AX
2012 Environments.
Consider the following scenarios where users may need to restore a Microsoft Dynamics AX
database to a different environment:
1. Testing a Microsoft Dynamics AX service pack, rollup, or full version upgrade.
2. Bringing Microsoft Dynamics AX 2012 data in house for testing or development.
3. Restoring a copy of the production database into a test or development environment to
work with the most recent changes.
4. Moving a production database from one Active Directory domain to different
production Active Directory domain environment.
In most scenarios, users should have the base Microsoft Dynamics AX 2012 software installed
in the new environment and running at the same service pack and rollup version as the
environment where the database was backed up. This would not apply to scenarios where
users are testing a service pack, rollup or full version upgrade.
At a high level, the process for moving the database from one environment to another will
follow these steps:
1. Restore the database and set proper SQL permissions.
REVIEW V1.1
2. Provide correct Microsoft Dynamics AX user credentials to allow users to connect and
login with a client.
3. Configure the base system functionality for those setting which may have changed.
4. Install or configure additional components such as Business Intelligence and Enterprise
Portal.
The specific requirements of a user's particular scenario may include additional steps or
steps in a different order. This document is designed outline common considerations.
Having a good understanding of the installation process and all the integrations and touch
points will aid users in adapting the process to their needs.
REVIEW V1.1
The record returned at the top of the list indicates the last time the setup or upgrade checklist
was run, note the APPBUILD and KERNELBUILD versions. This may not always give you the
most recent build depending if you are working with a database that is not fully upgraded
and you can use this query to get the highest build used in this environment by running the
following.
select distinct(KERNELBUILD) from SYSSETUPLOG
In the new environment, you will install the same version of Microsoft Dynamics AX kernel to
match these builds. If you setup the new environment with the correct kernel and application
build versions, the Upgrade Checklist does not appear when opening a client using an AOS
instance connected to the restored database.
In Microsoft Dynamics AX 2012, the application layer files are stored in the Microsoft
Dynamics AX database instead of on an application file share in previous versions.
Implications will be discussed later in this section, when users consider coding related
scenarios.
Refer to the Microsoft Dynamics AX 2012 Installation Guide in the section on Create a
SQL Server database manually or see the MSDN topic AOS Security.
REVIEW V1.1
Make sure the database name has been set correctly in the Microsoft Dynamics AX 2012
Server Configuration tool on the Database connection tab
For both Dynamics AX 2012 RTM and Dynamics AX 2012 R2 only one database name is
specified in the configuration tool, but for Dynamics AX 2012 R2 where there is the additional
model database the naming convention is used of adding the suffix of _model to the database
that is used here. So in this example for Dynamics AX 2012 R2 the AXDB is the business
database and the model database will need to be called AXDB_model, to match the naming
convention.
Next, start the Microsoft Dynamics AX Object Server in the Services management tool. If the
AOS fails to start, check the application event log for the specific errors and take appropriate
corrective actions.
Whenever an AOS starts against a database environment a record will be added or updated in the
sysserversessions table. In addition, the AOS service account name is also in the AOSaccount field.
Table Name
Column in Table
sysServerSessions
AOSAccount
Since the existing records in this table may not be valid in the new environment, these records
may need to be removed or updated. The recommended approach would be to remove all records
from the sysserversessions table, while all AOS instances are stopped and have the record
recreated as the new AOS service starts against the database.
REVIEW V1.1
The <user_alias> placeholder represents the actual alias of the Microsoft Dynamics AX
user account that you want to make the Microsoft Dynamics AX administrator in the
restored environment.
The script returns the values for the following user information:
Security identifier (SID)
Network domain name
Network alias
Users can obtain the SID using other tools such as Active Directory users, and
computers management console or PowerShell scripts. If you are logged into, a
machine and you want to make your own the Dynamics AX admin you can open a
command prompt and run:
Whoami /user
REVIEW V1.1
For Microsoft Dynamics AX 2012 RTM there is normally only one record updated, but
for Microsoft Dynamics AX 2012 R2, there may be, multiple records for the admin
account each having a different partition column value.
At this point, the AOS is started against the newly restored database; ensure the
Microsoft Dynamics AX 2012 Configuration tool is set correctly to connect to that new
AOS instance. Then start the Microsoft Dynamics AX 2012 client and login as the
Microsoft Dynamics AX administrator account you just updated.
REVIEW V1.1
Table Name
Columns in Table
SysBCProxyUserAccount
SysWorkflowParameters
SiteURL, ExecutionUserID,
workitememailid
Use the table above to help you develop SQL update scripts.
REVIEW V1.1
Table Name
Columns in Table
Server
Configuration
SysServerConfig,
BatchServerConfig
ServerID
Cluster
Configuration
SysClusterConfig
ClusterName
Batch Groups
BatchServerGroup
ServerID
Batch
ServerID
The following SQL scripts are examples of how users can change the records to use the new
AOS instance in the restored environment without making the changes through the client.
update batch set SERVERID = '<01@NewAOS>' where serverid = '<02@OldAOS>'
update sysserverconfig set enablebatch = 1 where serverid = '<01@NewAOS>'
update BATCHSERVERCONFIG set SERVERID = '<01@NewAOS>' where serverid =
'<02@OldAOS>'
REVIEW V1.1
Make sure to change the <01@NewAOS> and <02@OldAOS> placeholders with the actual AOS
instance name. Depending on user testing requirements, they may need to make other
changes to the AOS cluster setup for specific load balancing scenarios. The steps related to
batch jobs and workflow may be different. Refer to workflow section of this document to
learn the importance of running the workflow wizard.
After the changes are made, restart the AOS instances, in case they are caching any of the
settings.
AOS Services
AOS services are used by the client and the installer and should be verified and working in
the new environment before users install other Microsoft Dynamics AX components such as
Enterprise Portal.
Open the Microsoft Dynamics AX 2012 client, click System Administration, click Setup, click
Services and Application Integration Framework, and then click Inbound ports. Users
should see several WCF services with a category of basic that are installed with the AOS.
Make sure they all have a green checkbox next to them. If they do not, users can delete the
service and then click Register basic ports to have them regenerated on this server. If you
still get errors, try to activate the port and troubleshoot any errors written to the info log.
Resolve all the errors, close the client, and restart the AOS. If users have registered other
services besides the basic ports, they will need to handle any domain or server machine name
parameters.
REVIEW V1.1
Email Parameters
Email Parameters are used for email alerts and sending server side email using an SMTP
server. This requires some server specific values that may change when users install
Microsoft Dynamics AX in the new environment. Check with the user's network and IT
department on security specific setup required to send SMTP email in the user's organization.
There is no Microsoft Dynamics AX installation required, but it may be necessary to change
these parameters for SMTP email to function after restoring the database in a new
environment.
To open SMTP email, click System Administration, click Setup, click System, and then click
email parameters.
The following table lists the form name, tables and columns involved in email setup related to
environment specific settings.
Form Name
Table Name
SysEmailParameters SYSEMAILPARAMETERS
Columns in Table
AttachmentPath,
SMTPRelayServerName,
SMTPPortNumber,
SMTPServerIPAddress,
SMTPUserName,
DNSServerName
10
REVIEW V1.1
Document Management
Document management can store information to the database or to the file system. For those
deployments that use the file system, this can be changed by navigating to System
Administration| Setup | System Parameters once the form opens choose File store and
browse to the correct path.
The following table lists the form name, tables and columns involved in Document Handling
setup.
Form Name
Table Name
Columns in Table
11
REVIEW V1.1
12
REVIEW V1.1
In the new environment, if users are setting up the SSRS, SSAS and Enterprise Portal for the
first time, doing the BI Components and Enterprise Portal and Role Center installation will set
the correct values in the database.
If users restore the Microsoft Dynamics AX database to an environment where they have
already installed and deployed BI Components and Enterprise Portal, then they can change
the server names and URL references in the database. They can do this by using the client
forms or running SQL update statements. The following section discusses the database forms
and tables involved with the different Microsoft Dynamics AX components.
Workflow
For a new workflow deployment, the AOS installation will cover the workflow code that
Microsoft Dynamics AX 2012 runs under the AOS process. Setting the System service
accounts discussed about will set the Workflow Execution account, and the AOS server and
batch setup already discussed handles the batch jobs that are used with workflow. The
additional step that will need to be completed is to run the workflow infrastructure
configuration.
1. Click System Administration, click Setup, click Workflow, and then click Workflow
infrastructure configuration. To enable workflow in an existing environment with a
restored database for a different environment, open the Batch Job form. Click System
administration, click Inquiries, click Batch Jobs, and then click Batch Jobs.
2. The workflow batch jobs could be actively running. First, change the status to withhold
by highlighting the Workflow message processing job and from the top of the form click
Functions, click Change status, and then click Withhold. Do the same steps for the
Workflow due date expirations and Workflow line item notifications batch jobs.
3. Once all three workflow batch jobs are in a Withhold status, highlight the Workflow
message processing job and from the top of the form, click Functions, and then click
Delete, which will bring up a query window. Remove all columns except one, and
choose a field of Job Description.
4. In the Criteria, type *Workflow*. Due to the fact that there are no other jobs with
workflow in the job description, and click OK to delete the records.
5. Now that the workflow batch jobs are removed along with the records from the related
tables, correct all the AOS and batch group settings discussed above and run the
Workflow infrastructure configuration again. This will create the workflow batch
jobs with the correct settings for this environment.
6. Since this problem is likely to happen again the next time users restore the production
database to the test environment, create SQL update scripts to correct the problem in
the database directly.
7. Open SQL manager and run select statements on the following tables:
Global Technical Readiness
Microsoft Confidential - For Internal Use Only
13
REVIEW V1.1
8. By looking at the columns in each table, users find that the SERVERID is available in the
Batch table and would be the column to update in the environment when the database
is restored. An example of the update statement would look like the following:
update BATCH set SERVERID = '<new AOS instance name>' where SERVERID =
'<old AOS instance name>'
9. Make sure to change the placeholders for the actual AOS instance name and update
both the batch and batchjob tables.
BI Components
OLAP database
If needed, restore the OLAP database, which should already contain reduced cubes to match
the customer license keys and configuration.
Dynamics Database for OLTP connection string, is held in the OLAP database by using SQL
management tools and connect to Analysis Services. Under the Dynamics AX database
choose the Data Sources folder and adjust the properties on the Dynamics Database data
source.
It is recommended to redeploy new ODC files after the above forms have been updated
to the test or development Enterprise Portal.
Redeploy any Enterprise Portal changes that exist in the AOT to the test EP website.
Dynamics AX (4.0
Perspectives)
SharePoint
Document Library
SQL Manager
(Analysis Services)
Depending on the method, users should ensure all connections strings have correct server
names and databases. The list above outlines the connections strings.
In the SSRS reports manager site edit the SharedLibrary.DynamicsAXOLAP datasource.
14
REVIEW V1.1
To change this setup in the client click System Administration, click Setup, click Business
Intelligence, click Analysis Services, and then click Analysis Servers.
To change this setup in the client click System Administration, click Setup, click Business
Intelligence, click Reporting Services, and then click Reporting Servers.
The following table lists the form name, tables and columns involved in OLAP and SSRS setup
related to environment specific settings.
Form Name
Table Name
Columns in Table
SRSServersForm
BICONFIGURATION
PROJECTPATH, DATASOURCENAME,
CONNECTIONSTRING, LOGFILEPATH,
PROJECTFILENAME
SRSSERVERS
SERVERID, SERVERURL,
AXAPTAREPORTFOLDER,
REPORTMANAGERURL, SERVERINSTANCE,
AOSID, CONFIGURATIONID
Help Server
The Help Server may not be required in most testing and development environments, unless
users are doing Help Server specific customizations or want to provide help in a separate
training environment. For a new deployment of the Help Server, refer to the Installation
Guide. Once the Help Server is installed, it will update the existing value in the restored
database. If the Help Server is already deployed in the development or test environment, the
Help Server URL can be changed through the client or in SQL server.
1. To change this setup in the client click System Administration, click Setup, click
System, and then click Help system parameters.
2. For the SQL server tables refer to the table below:
Form Name
Table Name
Columns in
Table
4. To change the value, users would create a SQL update statement with the same
where clause. After making the changes to the help sever URL a client and possibly
AOS, restart is required depending on cache settings. See the Help topics are not
15
REVIEW V1.1
displayed in the help viewer section of the installation Guide if you need to setup
the search server to be indexed again in the new environment.
5. All clients deployed in the Development or test environment would need to access
the Help Server URL.
16
REVIEW V1.1
3. To change this web site URL in the client click System Administration, click
Setup, click Enterprise Portal, and then click Web Sites.
4. In the web sites form, delete the old or incorrect web site URL from the other
environment. Click Register site and enter the Internal URL and the External
URL of Enterprise Portal in the new environment. This will use a web service
to get the SiteID GUID from the WSS databases and update the values in the
Microsoft Dynamics AX database.
5. If users get errors or want to use SQL update statements, use the following
steps to update the URLs manually. Users can get the correct SiteID GUID from
the WSS database to update the EPWEBSITEPARAMETERS and
EPGLOBALPARAMETERS tables with by using the same Web Service call that
Enterprise Portal calls. Before making any changes, ensure that the user has a
working Enterprise Portal Web site in the new environment.
6. To do get the SiteID GUID, open Internet Explorer from the IIS server and go to
the website URL for the Enterprise Portal web site and use the following
relative path: /_layouts/ep/WSSAdmin.asmx.
7. By default the full URL would be
http://localhost/_layouts/ep/WSSAdmin.asmx. Users can also replace
localhost in the URL with the machine name of the IIS server. Once the web
page opens, users will click the GetEPWebInfo link.
Figure 2: WSSAdmin
8. A new web page will open, enter the siteURL of the Enterprise Portal web site
and click Invoke.
9. This will return the GUID id of the Enterprise Portal web site to be used with
method 3 above to create SQL update statements.
10. The following table lists the form name, tables and columns involved in
Enterprise Portal setup related to environment specific settings.
Global Technical Readiness
Microsoft Confidential - For Internal Use Only
17
REVIEW V1.1
Form Name
Table Name
Columns in Table
EPParameters
EPGLOBALPARAMETERS
HOMEPAGESITEID,
DEVELOPMENTSITEID,
SEARCHSERVERURL
EPUpdate
EPWebSiteParameters EPWEBSITEPARAMETERS
CollabSiteParameters
INTERNALURL, SITEID,
EXTERNALURL
COLLABSITEPARAMETERS ROOTURL
Enterprise Search
Enterprise Search uses SharePoint 2010 and may not be required in most testing and
development environments, unless users are doing Enterprise Search specific
customizations.
Enterprise Search integrates SharePoint 2010 Central Administration and the configuration
of the Business Data Connectivity and Search Application services.
The approach to take for deployment in a new environment is to have either SharePoint 2010
Server or SharePoint 2010 Foundation installed and the services configured in SharePoint
Central Administration. Next, install Enterprise Search from the Microsoft Dynamics AX 2012
installation media. See the installation Guide for details.
Once the Business Data Connectivity and Search Application services are installed and
running in the new environment, click System Administration, click Setup, click Search,
and then click Search Configuration in the Microsoft Dynamics AX client.
The Search Configuration will connect to the service applications configured in SharePoint
Central Administration. Users will select them from the dropdown list and mark the
checkbox to crawl the content, create the index, tables and columns you define.
In an existing deployment, where the Enterprise Search was working with a previous
database users could take three different approaches.
18
The first method is to bring over the new Microsoft Dynamics AX database along with
SharePoint database and restore all of them in the new environment. This would
require the user to follow the recommended methods of moving the SharePoint
database and best practices outlined for that product.
The second method would be to create a new Business Data Connectivity, Search
Application services and databases and have the newly restored Microsoft Dynamics AX
database content indexed.
The third method and possibly the easiest would be to use the existing Business Data
Connectivity and Search Application services and re build the indexes with the newly
restored Dynamics AX database content.
REVIEW V1.1
Table Name
Columns in Table
SyncParameters
SYNCPARAMETERS
Table Name
Columns in Table
AifWebsites
AIFWEBSITES
VirtualDirectoryShare,
URL
If there is more than one record in the form and the other reference is no longer valid in this
environment, delete the record from the other environment to eliminate the confusion.
If the AOS instance is on a separate server or does not have rights to the Web site where the
user installed Web Services on IIS, they will need to grant the rights manually.
For both new and existing installations of Web Services on IIS see the section in the
Installation Guide After you install the web services on IIS for the steps to create an
enhanced port. Users may be required to delete the existing inbound port and create a new
one with the restored database.
19
REVIEW V1.1
20
REVIEW V1.1
Appendix
Unique GUID per Microsoft Dynamics AX environment
If users experience incorrect caching information or strange form behavior, they may be
using the same Client Cache file when switching between database environments.
In order to ensure that a unique AUC file is created per instance for the Microsoft Dynamics
AX client to use, and to ensure that the Microsoft Dynamics AX instances have a unique Global
GUID, update the GlobalGUID in the SysSQMSettings table with an empty GUID (000000000000-0000-0000-000000000000).
After making this change, restart the AOS service and it will then generate a new GUID that
allows a new AUC file to be created for the Microsoft Dynamics AX client to use.
PURPOSE:
Deploy the enterprise portal and each individual component of SharePoint site.
USAGE:
AxUpdatePortal -listvirtualservers
Listvirtualservers: List of all virtual servers, SharePoint Web applications and IIS Web
sites, on this computer.
Deploy: Deploy a new virtual server, SharePoint web application, to an IIS web server,
which already has Enterprise Portal installed on it. If the createsite parameter is
21
REVIEW V1.1
omitted then only the virtual server is created and the user will need to later create the
web site. Users can run this from any computer. Connects to IIS via a web service.
Createsite: Create an Enterprise Portal web site within an existing Enterprise Portal
virtual server. Users can run this from any computer. Connects to IIS via a web service.
Updateall: Update all web components on an Enterprise Portal web site, SharePoint
site collection. Users can run this from any computer. Connects to IIS via a web service.
Proxies: Update all proxies on an Enterprise Portal web site, SharePoint site
collection. Users can run this from any computer. Connects to IIS via a web service.
Images: Update all images on an Enterprise Portal web site, SharePoint site collection.
Users can run this from any computer. Connects to IIS via a web service.
ADDITIONAL PARAMETERS:
virtualserver <value>
Virtual server name, (SharePoint web application). Example: ServerName
virtualserverurl <value>
Virtual server URL, (SharePoint Web application). Example: http://ServerName[:port].
websiteurl <value>
Web site url (SharePoint Site Collection). Example:
http://SeverName[:port]/Sites/DynamicsAx.
treenodepath <value>
Deploy web component tree node path. Example: /web/Web Files/Page
Definitions/ActivityEdit
Updatewebsites
Update all enterprise portal web sites during the redeploy. You can run this from any
computer. Connects to IIS via a web service.
Iisreset
Stop and restart the IIS web server after completing the deploy operation.
Verbose
Log the exception and error message handling to the console. Applies only to this
command: -redeploy
22