Ax40 Enus Ins 03

8/14/2019 Ax40 Enus Ins 03

1/26

Chapter 4: Installing a Development System

Page 65

CHAPTER 3: INSTALLING A DEVELOPMENTSYSTEM

ObjectivesThe objectives are:

Perform a single computer install of Microsoft Dynamics AX 4.0.

Explain which roles cannot have multiple installs on a singlecomputer.

Install multiple instances of the Application Object Server (AOS).

Manage new Microsoft Dynamics AX 4.0 instances.

Point a client to a new Microsoft Dynamics AX 4.0 instance.

Explain the process of setting up a Version Control Server.

Introduction:

The recommended procedure for Administrators is to maintain separatedevelopment, test, and production environments. While a developmentenvironment can run on different hardware than the intended productionenvironment, the test environment must copy the production environment asclosely as possible.

In a single environment, it is possible to install multiple instances of Microsoft

Dynamics AX 4.0. The primary use for multiple instances is in a developmentenvironment, and users have different ways to set this up in Microsoft DynamicsAX.

This section examines the development environment and how to set it upalongside the live environment, where it may share some of the live installationservers. Additionally, the scenario examines the process of installing thedatabase, application file server, application object server, and client on separatecomputers for the live system:

8/14/2019 Ax40 Enus Ins 03

2/26

Installation & Configuration for Microsoft Dynamics AX 4.0

Page 66

Scenario

GTM is in the process of implementing Microsoft Dynamics AX 4.0. They planto install the database, application file server, application object server, and clienton separate computers for the live system. To complete the implementation, theimplementers will perform system development, testing, and training.

Problem

While GTM is implementing the live system, they will have to be able to testconfiguration settings without altering data. They also must be able to developforms and processes where users will not be able to access them until they arefinished. GTM is also planning to train their users so that they are familiar withthe system when it is implemented.

Goal

The goal for GTM is to be able to develop, test, and train in a system that

duplicates their live system without affecting live data. The test and trainingsystems must be similar enough to the live system so that training and testing iseffective. Implementers can configure the development system differently, ifrequired, because developers will test system changes before moving the changesto the live system.

Solution

To accomplish their goal, GTM requires multiple environments for MicrosoftDynamics AX 4.0. GTM must create a separate environment for development,testing, and training.

Configure a development environment that implementers can use tocreate forms and processes before moving them to the live system.

Configure a test environment where implementers can test objectscreated in development. The test environment must duplicate the liveenvironment as much as possible

Configure a training environment on a single computer that can beused by multiple users.

8/14/2019 Ax40 Enus Ins 03

3/26


Page 67

Install Microsoft Dynamics AX 4.0 on a Single Computer

It is possible to set up the four core Microsoft Dynamics AX 4.0 roles on a singlecomputer to create a development, test, pilot, or trial environment.

Prerequisites

All Microsoft Dynamics AX 4.0 computers that communicate with other

Microsoft Dynamics AX 4.0 computers must be part of the same Microsoft

Active Directory domain, configured in native mode.

Microsoft SQL Server 2000 Enterprise edition, or Microsoft SQL Server 2005,Standard or Enterprise editions must also be running in the environment or on thecomputer.

Verify Rights

The implementer must log into an account that is both a member of:

The Administrators group on the computer that is running the Setup.

The Database Creators server role in the instance of SQL Serverwhere creating the database.

Start Setup

Insert the Microsoft Dynamics AX 4.0 DVD into the DVD drive. If the MicrosoftDynamics AX 4.0 Setup Wizard does not start automatically, double-click theAutorun.hta file in the root directory of the DVD. If installing from a networklocation, the recommendation is to share the installation files on a file server andconnect to the location from the computer where the implementer must install theprogram.

Install on a Single Computer

To install Microsoft Dynamics AX 4.0 on a single computer, the implementercan use the following steps:

1. To start the installation process, clickMicrosoft Dynamics AX 4.0.

On the Prerequisites checkpage, Setup validates that the softwarerequired to install Microsoft Dynamics AX 4.0 is present. If it is not,

clickInstall.

To continue after the update is completed, clickNext.

2. On the Welcome page of the Setup Wizard, clickNext to continue.

8/14/2019 Ax40 Enus Ins 03

4/26


Page 68

3. On the License agreement page, read the license agreement andthen clickI accept the terms in the license agreement to accept thelicense terms and conditions. Accepting the license agreementactivates the Next button. To continue, clickNext.

4. On the Select installation type page, clickSingle computer

installation, and then clickNext.

5. On the Select region page, choose a region to install. Regionsprovide country-specific tax and financial functionality. Thefollowing list includes the countries/regions whose tax and financialinformation is included in all installations.

Australia Austria Belgium Canada Denmark

Finland France Germany Ireland Italy

Malaysia Netherlands NewZealand

Norway Singapore

SouthAfrica

Spain Sweden Switzerland Thailand

UnitedKingdom

UnitedStates

TABLE 3.1:COUNTRIES AND REGIONS

6. On the Install application files page, type the location, or clickBrowse to navigate to the location where the application files will beinstalled.

7. On the Create an instance of Application Object Server page,enter the name for the Application Object Server (AOS) and thenclickNext.

8. On the Select databasepage, select Microsoft SQL Server. ForSQL Server, determine whether to connect to a new database or anexisting database.

To Do this:

Create a new Microsoft SQL

Server database

In the Select databasepage, clickCreate a

new SQL Server.In the Connect to SQL Server page, in theServername box, type or select the name ofthe SQL Server to connect to.

In the Create SQL Server database page, inthe Database name box, type the name of thedatabase to create.

8/14/2019 Ax40 Enus Ins 03

5/26


Page 69

To Do this:

Connect to an existing databaseconfigured with SQL

In the Select databasepage, clickConnect toan existing SQL Server database.

In the Connect to an instance of SQL Server

page, in the Servername box, type or selectthe name of the SQL Server to connect to.

In the Database name box, type or select thename of the database to connect to.

TABLE 3.2:CREATE OR CONNECT TO SQLSERVER

9. On the Select language page, select the language in which the clientis to be displayed, and then clickNext.

10. On the Select Help languages page, select the Help languages toinstall on the client.

11. On the Install client files page, clickNext to accept the defaultlocation, or clickBrowse to designate a different location.

12. On the Ready to install page, review the summary of roles andcomponents installed on the computer. To continue, clickNext.

13. On the Installing page, it is possible to monitor the installationprogress as Setup proceeds.

14. On the Completing Microsoft Dynamics AX 4.0 Setup page,review the summary of roles installed on the computer.

15. To exit the Setup wizard, clickFinish.

Test Your Knowledge Install Microsoft Dynamics AX 4.0 ona Single Computer

What is required for Microsoft Dynamics AX computers to communicate witheach other?

8/14/2019 Ax40 Enus Ins 03

6/26


Page 70

Install Multiple Instances of Microsoft Dynamics AX 4.0

To install more than one instance of a Microsoft Dynamics AX 4.0 role on asingle computer, run Setup to install each instance on the computer. The setupwizard will not display the License Terms page.

The following roles cannot have multiple installs on a single computer:

Client

.NET Business Connector

COM Business Connector

Enterprise Portal Server

Reporting Server

Application Integration Server

Install Multiple Application Object Server Instances

For a development environment, users may have to install several ApplicationObject Server (AOS) instances on the same computer. Each AOS instance canpoint to a different application file location, one to use for the live environment,one for development, and one for testing.

1. To start the installation process, clickMicrosoft Dynamics AX 4.0.

2. On the Welcome Backpage of the Setup Wizard, clickNext to

continue.3. On the Add computer role page, select Object server, and then

clickNext.

4. On the Create an instance of ApplicationObject Serverpage, inthe Instance Name box, type a name for this AOS.

Select a different name than the first installed instance. Setupincrements the TCP/IP port assigned to the AOS by one. Forexample, when the first instance is installed on TCP/IP port 2712, thesecond instance is installed to TCP/IP port 2713.

5. This is an optional step. To send information about any fatal error inan AOS instance to Microsoft, select the Automatically sendinformation about fatal errors in any Application Object Server

service instance to Microsoft check box.

NOTE: Enabling error reporting sends information over a secure (https) connection toMicrosoft, where it is stored with limited access. Microsoft uses the reports only to

improve Microsoft Dynamics AX, and treats all information as confidential.

8/14/2019 Ax40 Enus Ins 03

7/26


Page 71

6. On the Select account for the Application Object Server page,choose whether to use the Network Service account of the localcomputer, or a domain account for the AOS account, and then clickNext.

If using a domain account, before the install, work with a System

Administrator to have a new account created solely for use by theAOS instance. We recommend that the account be set up as follows:

Log on as a service

No interactive logon rights

Depending on the other roles that have been selected, Setup grantsthe following permissions for the AOS account:

Role Permission Granted

AOS (database must exist) Adds the AOS account to the databaseas a user, and makes it a member of the

db_ddladmin, db_datareader, anddb_datawriter database roles.

AOS (application files must exist) Grants the AOS account Full Controlpermissions on the application filesdirectory.

Application integration (AIF) Webservices,

Grants the AOS account Full Controlpermissions on the AifWebServiceshare, if the AOS is installed at thesame time as the AIF Web services.

7. On the Select databasepage, select the type of database to connect toand then clickNext.

To Do this:

Create a new Microsoft SQL Serverdatabase

- In the Select databasepage, clickCreate a new SQL Server.

- In the Connect to SQL Server page,in the Servername box, type or selectthe name of the SQL Server to connectto.

- In the Create SQL Server database

page, in the Database name box, typethe name of the database to create.

8/14/2019 Ax40 Enus Ins 03

8/26


Page 72

To Do this:

Connect to an existing databaseconfigured with SQL

- In the Select databasepage, clickConnect to an existing SQL Server

database.

- In the Connect to an instance ofSQL Server page, in the Servernamebox, type or select the name of theSQL Server to connect to.

- In the Database name box, type orselect the name of the database toconnect to.

TABLE 3.3:CREATE OR CONNECT TO SQLSERVER

8. On the Locate application files page, type or browse to the locationwhere the Microsoft Dynamics AX 4.0 application files are installed.

ClickNext to continue.9. On the Ready to install page, review the summary of roles for this

computer. To continue, clickInstall.

10. On the Installing page, it is possible to monitor the installationprogress as Setup proceeds.

11. On the Completing Microsoft Dynamics AX 4.0 Setup pagereview the summary of roles for the computer.

12. To exit the Setup wizard, clickFinish.

Test Your Knowledge

Install Multiple Application ObjectServer Instances

What are some possible reasons for installing multiple Application Object Server(AOS) instances on a single computer?

8/14/2019 Ax40 Enus Ins 03

9/26


Page 73

Manage a New Microsoft Dynamics AX 4.0 AOS Instance

A configuration is a group of startup and tracing settings for an ApplicationObject Server (AOS) instance that is stored in the Microsoft Windows registryor in a configuration file. Administrators may want to create new configurationsand configuration files, save, or load configurations to support:

Having multiple environments, one instance for the liveenvironment, one instance for development, and one instance fortesting.

Moving from a development environment to a productionenvironment. Change the application directory that an AOS instancepoints to, the database, and whether a system allows for debugging.

Tuning Microsoft Dynamics AX. Save a configuration with thedefaults, and then change compression, database tuning, and tracingsettings one at a time, and save them as different configurations. Run

Microsoft Dynamics AX with each different configuration, andevaluate how it performs.

On the computer that is running the Application Object Server (AOS), onlymembers of the local Microsoft Windows Power User group or Administratorsgroup can change configuration settings. Restrict membership in these groups asmuch as is feasible, to reduce the potential for malicious mischief.

Use the Server Configuration Utility to validate that the AOS points to thecorrect database and application file server.

8/14/2019 Ax40 Enus Ins 03

10/26


Page 74

FIGURE 3.1:MICROSOFT DYNAMICS AXSERVER CONFIGURATION UTILITY

1. Open the Microsoft Dynamics AX Server Configuration Utility(Start > Administrative Tools > Microsoft Dynamics AX 4.0Server Configuration Utility).

2. ClickManage, clickCreate configuration, and then enter a namefor the configuration, and determine whether to copy it from theactive or original configuration.

3. On the Application Object Server tab, validate that the Applicationfile location is correct. If not, change it.

4. In the TCP/IP port field, enter the port number the AOS is runningon. The clients need the port number information to connect to theAOS.

5. On the Database Connection tab, validate that the AOS isconnected to the correct server and database. If not, change it.

8/14/2019 Ax40 Enus Ins 03

11/26


Page 75

Scenario

GTM is in the process of implementing Microsoft Dynamics AX 4.0. They havedecided that they will create separate environments for developing, testing, andtraining. These separate environments will help GTM implement the live system

without altering live data.

GTM has several consultants helping them with the implementation. Theseconsultants will be doing development in addition to internal GTMadministrators. The implementation consultants have developed a process forcompleting developments, testing the developments, and moving them into thelive system.

Problem

The consultants helping GTM with the implementation have experience withMicrosoft Dynamics AX 4.0. GTM in-house administrators will be helping withthe development, but are learning about Microsoft Dynamics AX 4.0 as it is

implemented. The GTM in-house administrators must be able to work inMicrosoft Dynamics AX without hindering the consultants' development.

Goal

The goal for GTM is to provide an environment for in-house development andtraining that does not interfere with other environments. Another instance ofMicrosoft Dynamics AX on each of the existing database, application file, andapplication object servers is not justified.

Solution

To accomplish their goal, GTM installs an instance of Microsoft Dynamics AX

4.0 on a single computer for use by the in-house administrators. This singlecomputer contains its own database, application file server, application objectserver, and client. To install Microsoft Dynamics AX 4.0 on a singe computer,GTM:

Selects the Single computer installation from the installation DVD

Selects the region for tax and financial functionality

Installs the application files

Creates an instance of the application object server

Creates a new database

Installs the client

8/14/2019 Ax40 Enus Ins 03

12/26


Page 76

Point a Client to a Microsoft Dynamics AX 4.0 Instance

Use the Configuration Utility to point the client to the new AOS instance.

FIGURE 3.2:MICROSOFT DYNAMICS AX4.0CONFIGURATION UTILITY

NOTE: The installer must be an administrator or power user on the computer to use theConfiguration Utility.

1. Open the Configuration Utility (STARTCONTROLPANELADMINISTRATIVE TOOLSMICROSOFT DYNAMICS AX 4.0

CONFIGURATION UTILITY).

2. In the Configuration target list, select Local client.

8/14/2019 Ax40 Enus Ins 03

13/26


Page 77

3. ClickManage, clickCreate configuration, and then enter a namefor the configuration, and determine whether to copy it from theactive or original configuration.

4. On the Connection tab, clickAdd, and then enter the Server name,Instance name, and TCP/IP port of the AOS instance to point the

client to, and then clickOKand exit the configuration utility.

5. Start the client. The client is now pointed to the new MicrosoftDynamics AX 4.0 instance.

Test Your Knowledge Point a Client to a MicrosoftDynamics AX 4.0 Instance

Who can use the Configuration Utility?

8/14/2019 Ax40 Enus Ins 03

14/26


Page 78

Set Up a Version Control Server

A Version Control Management System (VCMS) enables a team of developers towork at the same time on the code base in one or more projects. The following isa list of benefits derived from using VCMS:

Each developer can safely save extensions and modifications withoutthe risk of losing time overriding changes.

Developers can save their work periodically to make sure that nowork is lost.

Developers can share their changes when working on a project.

Developers can test changes to Microsoft Dynamics AX without therisk of losing previous work, as they can always return to an earlierversion.

Changes in the code are monitored and saved to provide an audit trail

for any potential rollbacks.

Developers can track changes and compare different versions of theobjects.

Each object in the AOT must have a unique ID. A centralized service controls theallocation of IDs when developing in a team environment. The Team Serverconnects to the VCMS to issue object IDs and Label IDs when adding newobjects.

Set Up the Team Server

Each object and label in Microsoft Dynamics AX must have a unique

identification, and developers must assign unique IDs to the new objects andlabels. A central service coordinates tasks when developing in a teamenvironment. The Team Server handles the task of issuing IDs when developerscreate new objects and labels.

NOTE:It is not recommended to install the Team server on the same computer asthe Microsoft Dynamics AX database. If the two databases are installed on thesame computer, the Application Object Server (AOS) account is authenticated by

two different user groups. Therefore, the two groups have access to either theMicrosoft Dynamics AX database or the team server database but not both.

PrerequisitesThe following are requirements for the Team server computer:

Microsoft Windows Server 2003 or Windows 2000

Microsoft SQL Server 2005

SQL Server agent is running

8/14/2019 Ax40 Enus Ins 03

15/26


Page 79

Create a New User Group and Add Members

When installing the Team server, add each Developer computer as a user on theTeam server. The administrator must create a new local user group and add allDeveloper computers as members.

1. ClickSTART

ADMINISTRATIVE TOOLS

COMPUTER MANAGEMENT.2. Expand Local Users and groups.

3. Right-click Groups and select New Group.

4. In Group name, type Dynamics Team Server Users.

5. In Description, type Dynamics Team Server Users.

6. ClickAdd to add a new member.

7. Click Object types.

8. Select Computers and then clickOK.

9. Type the Domain and computer name for the Developer computer(with the AOS installed), click Check names, and then clickOK.

10. ClickClose.

11. Repeat step 6 to 10 for each developer computer added to the usergroup.

Run the Team Server Setup Wizard

A wizard is available to help install and set up the Team server.

NOTE:Before starting the Team server installation, make sure that the SQL

Server agent is running.

1. Insert the Microsoft Dynamics AX DVD into the DVD drive on theTeam server computer. If the Setup Wizard does not startautomatically, double-click the Autorun.hta file in the root directoryof the DVD.

2. ClickBrowse additional tools.

3. ClickInstall Team Server to open the Team server setup wizard.ClickNext.

4. Select the language and read the License agreement terms carefully.

5. Accept the terms in the License agreement, and then clickNext.

6. Fulfill the Prerequisites, and then clickNext.

7. Type the SQL Server name and then clickNext.

8. Type the Team server database name and then clickNext.

8/14/2019 Ax40 Enus Ins 03

16/26


Page 80

9. Type the Team server user group name and then clickNext.

10. ClickInstall. The installation takes a few seconds. After theconfirmation, clickFinish.

Set Up the Visual SourceSafe Server

The Visual SourceSafe (VSS) server stores all versions of the application objects.When modifying an application object:

1. Check out the object from the server

2. Make the modifications

3. Check in the changed object on the server

It is best to have the VSS server installed on a separate computer.

Prerequisites

The following are prerequisites for installing and setting up the VSS 2005 Server:

Visual SourceSafe 2005 Server on the VSS Server computer

Create a database on the server

Create a new Project in the VSS database

NOTE:Follow the installation and setup instructions in the VSS 2005 Serverdocumentation.

Share the VSS Database Folder on the ServerThe developers who use the VSS database need access to the VSS databasefolder on the VSS server. Developers can change the security setup based onpreferences.

1. Open Windows explorer.

2. Right-click the VSS database folder and select Sharing andSecurity.

3. ClickShare this folder.

4. Click the Permissions button.

8/14/2019 Ax40 Enus Ins 03

17/26


Page 81

5. In the Group or User names box, clickEveryone or clickAdd toadd a specific developer to the list.

6. In the Permissions for Everyone pane, select the appropriate accesslevel, such as Power User.

7. ClickOKand OK.

Set Up Global Version Control Parameters

The administrator controls the global settings for the version control managementsystem (VCMS). This includes specifying the Team server, specifying rules forobjects, and setting rules for best practices. When the administrator has enabledthe version control system globally, the individual developers can set up theirpersonal parameters, such as repository folder.

Create a Local Repository Folder

Use the following procedure to create the local repository folder:

1. Open Windows Explorer.

2. Create a new folder to use as the local repository folder. For exampleC:\VCS_Repository.

Set Up Global Version Control Parameters (Administrator)

Use the following steps to create the global version control parameters:

1. ClickToolsDevelopment toolsVersioncontrolSetupSystem settings.

2. In SysVersionControlParameters, VCSType, select VisualSourceSafe.

3. In SysVersionControlParameters, RepositoryFolder, type thename of the local repository folder. For exampleC:\VCS_Repository.

4. In SysVersionControlParameters, TSType, select Microsoft SQLServer.

5. In Team Server Name, type the name of the Team server.

6. In Team Server Database Name, type the name of the Team serverdatabase, such as AxTS. For more information, see Set up the Teamserver.

7. Click the Visual SourceSafe tab.8. In SysVersionControlParameters, VSSIniFile, type the path and

filename for the SourceSafe.Ini file in the SourceSafe databasefolder on the VSS Server.

9. In the SysVersionControlParameters, VSSProjectRoot field, typethe name of the project in VSS. Remember to add the ROOT name,such as $/Ax40VersionControl.

8/14/2019 Ax40 Enus Ins 03

18/26


Page 82

10. Click the General tab.

11. In SysVersionControlParameters, VCSEnabled, select Enable,and then clickApply.

12. ClickYes to confirm changing the global settings.

NOTE: As default, all the Best practice settings are set to "Reject," and Run Title

Case Update is set to "No."

NOTE: After successfully setting up the global version control parameters and

clicking Apply, the definition file will be created. The vcsdef.xml definition filedefines the global settings for interaction with the version control management

system, including Team server name and information about the current project. It is

automatically created or modified, and checked in to VSS whenever global

parameters are set up or changed. It is important to protect this file from accidental

changes.

Protect the Global Version Control settings

Only the version control system administrator can have write access to this file.Otherwise developers can accidentally turn off version control for all developersby disabling version control on the System settings form.Developers can disable their personal version control parameters but cannot beable to change the global settings.

To protect the Global Version Control settings in Visual SourceSafe:

1. ClickSTARTALL PROGRAMSMICROSOFT VISUAL SOURCESAFEMICROSOFT VISUAL SOURCESAFE ADMINISTRATION.

2. ClickTOOLSOPTIONS.

3. Select the Project rights tab, select Enable Rights andAssignments commands, and then click OK.

4. ClickTOOLSRIGHTS BY PROJECT.

5. Expand the project nodes and select the Definition node.

6. Select all Developers in the users list, and clear the CheckOut/Check In check box. This will provide Read access only to allDevelopers while the Administrator maintains all rights.

Set Up Local Version Control ParametersWhen the version control management system (VCMS) administrator hasinstalled the Team server and Visual SourceSafe (VSS) server, and enabledversion control globally, then users can enable version control on thedevelopment computers.

After successfully enabling version control on the development computer, it ispossible to check out and modify objects in the AOT, add new objects, and more.

8/14/2019 Ax40 Enus Ins 03

19/26


Page 83

After checking in the changes to VSS, other developers working on the sameproject can get the updated object from the VSS server.

Prerequisites

The development computer must have the following installed:

Windows Server 2003.

Microsoft Dynamics AX application and client.

Visual SourceSafe Client (optional)


Follow these steps to create the repository folder:



Enable Version Control Locally (Developer)

Follow these steps to enable the version control:

1. ClickTOOLSDEVELOPMENT TOOLSVERSIONCONTROLSETUPPARAMETERS.

2. In SysVersionControlParameters, VCSType, select VisualSourceSafe.

3. In SysVersionControlParameters, RepositoryFolder, type thename of the local repository folder. For exampleC:\VCS_Repository.

4. Click the Visual SourceSafe tab.

5. In SysVersionControlParameters, VSSIniFile, type the path andfilename for the SourceSafe.Ini file in the SourceSafe database folderon the VSS Server.

6. In the SysVersionControlParameters, VSSProjectRoot field, typethe name of the project in VSS. Remember to include the ROOTname, such as $/Ax40VersionControl.

7. Click the General tab.

8. In SysVersionControlParameters,VCSEnabled, select Enable,and then clickApply.

Synchronize AOT Objects with the Server

At first the local version of the repository might be out of sync with the masterversion deployed by the VCMS administrator. Users can create, modify, delete,or rename objects. To obtain the latest version of all AOT objects, users cansynchronize the local version with the version on the VSS server.

8/14/2019 Ax40 Enus Ins 03

20/26


Page 84

1. ClickTOOLSDEVELOPMENT TOOLSVERSIONCONTROLSYNCHRONIZE.

2. Choose whether to force the synchronization and whether to deletethe local objects deleted on the version control server (optional).

3. ClickOKto start synchronization. The latest version of all AOTobjects on the VSS server is copied to the repository folder on thedevelopment computer. For more information, refer toSysVersionControlSynchronization Class Form

Deploy AOT Objects on VSS Server

When the administrator of the version control management system (VCMS), hasinstalled the Team server and the Visual SourceSafe (VSS) server, the next stepis to add all objects, from the master copy of Microsoft Dynamics AX, to theVSS server.

When adding the objects to the VSS server, the objects automatically register on

the Team server to have IDs assigned. Assigning IDs to all existing objects makesure that the Team server can issue unique IDs when creating new objects.


Make sure to create a repository folder on the computer. When deploying theAOT objects, a copy of each object is also added to the repository folder.



Create Repository

Follow these steps to create the repository:

1. ClickTOOLS DEVELOPMENT TOOLSVERSIONCONTROLSETUPCREATE REPOSITORY.

2. In Check-in description, type a description of the check-in, such as"Creation of repository."

3. ClickOK.

NOTE:This process might take a while depending on the computer and networkspeed.

8/14/2019 Ax40 Enus Ins 03

21/26


Page 85

Deploy Label File on VSS Server

The label files used in development must be added to Visual SourceSafe (VSS).The Team server assigns IDs when adding the label files to VSS.

Create Label File

Follow these steps to create the label file:

1. ClickTOOLSDEVELOPMENT TOOLSVERSIONCONTROLSETUPCREATE LABEL FILE.

2. In Check-in description, type a description of the check-in, such as"Initial creation of label files."

3. In File name, type the path and name of the label file or use thebrowse button to locate the master label file. Label files are usuallylocated in the C:\Program file\Microsoft DynamicsAx\40\Application\Appl\Standard folder.

4. ClickOK.

5. Repeat step 1 to 4 to add more label files to the VSS.

Test Your Knowledge Set Up a Version Control ServerWhat are some of the benefits from using a Version Control Management System(VCMS)?

8/14/2019 Ax40 Enus Ins 03

22/26


Page 86

Conclusion

In a development environment, a single computer may have to accommodatemore than one AOS. Developers can have more than one environment on a singlecomputer for development or testing by becoming familiar with the steps toinstall, manage, and set up of the development side of Microsoft Dynamics AX.

The steps provided by the installation wizard help make the single computerinstall a straightforward process. Additionally, the single computer installationcan help Partners, developers, testers, and salespeople in many ways, such as:

Easier to install

Quicker to install

Technical knowledge uneeded

8/14/2019 Ax40 Enus Ins 03

23/26

8/14/2019 Ax40 Enus Ins 03

24/26


Page 88

Lab 3.3 Point a Client to a new Microsoft Dynamics AX 4.0Instance

After the new development instance is created, the client that is used to accessthe system needs to be modified to point to the new development instance. Theconfiguration utility can be used to create a new configuration for development.This will allow the user to switch between the development and liveenvironment.

Challenge Yourself!

Create a new client configuration for development.

Need a Little Help?

1. Run the Microsoft Dynamics AX 4.0 Configuration Utility.

2. Create a new configuration.3. Enter the development instance information.

8/14/2019 Ax40 Enus Ins 03

25/26


Page 89

Quick Interaction: Lessons Learned

Take a moment and write down three Key Points you have learned from thischapter:

1.

2.

3.

8/14/2019 Ax40 Enus Ins 03

26/26


Ax40 Enus Ins 03

Documents

Transcript of Ax40 Enus Ins 03