Live/Production server preparation

(0) Share

Report

Posted on by Community Member

Hi All,

Currently we have imported all masters and configured everything in AX R3 server and we named it as TEST server. Now we are going to preparing LIVE/Production server by following one of below processes.

Can you please suggest which one is the best process? Also, guide me if you have any other better way.

1) After completions of user testing on TEST server, delete all transaction by using “SysDatabaseTransDelete” class. Make a new server for Live by restoring TEST server backup. I believe this class is updated in R3 and will delete all transactions. I knew that, in earlier version of R3 there were issues and are rectified in R3.

2) After user tests all masters and before doing any posting, we will take back of TEST server and will prepare Pre Go-Live server. During or after postings, if user wanted to modify the data or any customization, We will make same changes on both the servers. Once we got the confirmation from users that TEST is working fine, we will make Pre Go-Live server as live server.

3) Re-importing all masters in Live server and ask user to cross the data.

I don’t think 3 one is best one. Please suggest.

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Denis Macchinetti 16,444 on at

Like (0)

Report

Hi

In my opinion the best one is the second option.

Usually I have an AX configuration environment without any transactions where done ONLY setup, so Number sequence, Finance setup, etc.

Only in the Test env, functional guys will test the AX Setup ( coming from the Config Env) and the personalizations coming from DEV.

About customizations, I use TFS and with a Build Server ( TFS Build ), only the customizations verified by the developers ( made the check-in ) will be transfer to the target envs.

About AX Setup, we will move the AX configuration from Config env to the Target envs, using DAT\DEF framework.

Was this reply helpful? Yes No
Suggested answer

Guy Terry 28,924 Moderator on at

Like (0)

Report

Hi DaxMohan,

So right now, Test is configured and contains all master data, but no transactions?

1) I don't like. You would have to test that using SysDatabaseTransDelete created a system that you could go live on. And during user testing, I assume users would be creating dummy customers, items etc, which you don't want in Live.

2) Is a better solution. But is your master data now really how it will be at go live? For example, you might create new items, customers, whatever in your legacy application between the time you loaded master data in to the test environment and the time you go live.

3) Is the solution I would look at if the required master data could be different between start of testing and go live. Use the same imports you built to import the data into test, so that you can verify during test that they are good. Then, build a plan to import the data to live in the run up to go live (remembering to factor how long the imports take).

The downside is you have to configure live from scratch, since you already loaded data into your only environment that contains your best configuration :-(

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Thank you guys. Your suggestions are valuable.

Was this reply helpful? Yes No