Dev --> Test --> AQ --> Live
Dev : Use for development as you would guess.
Test : Once the modification is done it is moved to Test by XPO export file. Unit testing of the modification is done on Test instance. When the testing of a couple of modification is done, a full sychro and compile is done. Then the layer USR is moved to AQ.
AQ : Our AQ is build by copying the layer we work on (USR) from Test and the layer that our consultant works on (VAR). Here we do a full sychro and compile to check if both layers are ok together. When everything is ok, we stop the live env, move the layers from AQ to Live and put it back online.
If you're the only one doing the modifications you could forget about the AQ part.
Steeve...
-----Message d'origine-----
De�: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoy�: 20 ao�t 2004 09:58
��: [EMAIL PROTECTED]
Objet�: Re: [development-axapta] Isolating Axapta Modifications until Tested
Hi All,
Does anyone have a scheme for modifying and testing Axapta so that the
modifications are kept out of the ?live? Axapta system until they are
fully tested? Or could you point me to the Axapta manual(s) or another
resource where this is covered best covered?
Thank You,
Bob
Bob Brinker
Oakdene Group, Inc.
2625 Butterfield Rd. (Suite 212E)
Oak Brook, IL 60523-1261
[EMAIL PROTECTED]
[Non-text portions of this message have been removed]
Yahoo! Groups Links
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
