Ax40 Enus in 04

Microsoft Official Training Materials for Microsoft Dynamics ™ Your use of this content is subject to your current services agreement

Chapter 4: Installing a Development System

CHAPTER 4: INSTALLING A DEVELOPMENT SYSTEM Objectives

The objectives are:

• Perform a single computer install of Microsoft Dynamics™ AX 4.0. • Explain which roles cannot have multiple installs on a single

computer. • 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 separate development, test, and production environments. While a development environment can run on different hardware than the intended production environment, the test environment must copy the production environment as closely 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 development environment, and users have different ways to set this up in Microsoft Dynamics AX. This section examines the development environment and how to set it up alongside the live environment, where it may share some of the live installation servers. Additionally, the scenario examines the process of installing the database, application file server, application object server, and client on separate computers for the live system:

Page 89


Installation & Configuration for Microsoft Dynamics AX 4.0

Scenario GTM is in the process of implementing Microsoft Dynamics AX 4.0. They plan to install the database, application file server, application object server, and client on separate computers for the live system. To complete the implementation, the implementers will perform system development, testing, and training.

Problem While GTM is implementing the live system, they will have to be able to test configuration settings without altering data. They also must be able to develop forms and processes where users will not be able to access them until they are finished. GTM is also planning to train their users so that they are familiar with the 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 training systems must be similar enough to the live system so that training and testing is effective. Implementers can configure the development system differently if required, because the system will test developments before moving them to the live system.

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

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

• Configure a test environment where implementers can test objects created in development. The test environment must duplicate the live environment as much as possible

• Configure a training environment on a single computer that can be used by multiple users.

Page 90



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 single computer 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 the computer.

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 Server

where creating the database.

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

Install on a Single Computer To install Microsoft Dynamics AX 4.0 on a single computer, the implementer can use the following steps:

1. To start the installation process, click Microsoft Dynamics AX 4.0. On the Prerequisites check page, Setup validates that the software required to install Microsoft Dynamics AX 4.0 is present. If it is not, click Install. To continue after the update is completed, click Next.

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

Page 91



3. On the License agreement page, read the license agreement and then click I accept the terms in the license agreement to accept the license terms and conditions. Accepting the license agreement activates the Next button. To continue, click Next.

4. On the Select installation type page, click Single computer installation, and then click Next.

5. On the Select region page, choose a region to install. Regions provide country-specific tax and financial functionality. The following list includes the countries/regions whose tax and financial information is included in all installations.

Australia Austria Belgium Canada Denmark

Finland France Germany Ireland Italy

Malaysia Netherlands New Zealand

Norway Singapore

South Africa

Spain Sweden Switzerland Thailand

United Kingdom

United States

TABLE 4.1: COUNTRIES AND REGIONS

6. On the Install application files page, type the location, or click Browse to navigate to the location where the application files will be installed.

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

8. On the Select database page, select Microsoft SQL Server. For SQL Server, determine whether to connect to a new database or an existing database.

To Do this: Create a new Microsoft SQL Server database

In the Select database page, click Create a new SQL Server. In the Connect to SQL Server page, in the Server name box, type or select the name of the SQL Server to connect to. In the Create SQL Server database page, in the Database name box, type the name of the database to create.

Page 92



To Do this: Connect to an existing database configured with SQL

In the Select database page, click Connect to an existing SQL Server database. In the Connect to an instance of SQL Server page, in the Server name box, type or select the name of the SQL Server to connect to. In the Database name box, type or select the name of the database to connect to.

TABLE 4.2: CREATE OR CONNECT TO SQL SERVER

9. On the Select language page, select the language in which the client is to be displayed, and then click Next.

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

11. On the Install client files page, click Next to accept the default location, or click Browse to designate a different location.

12. On the Ready to install page, review the summary of roles and components installed on the computer. To continue, click Next.

13. On the Installing page, it is possible to monitor the installation progress 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, click Finish.

Test Your Knowledge − Install Microsoft Dynamics AX 4.0 on a Single Computer

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

Page 93



Install Multiple Instances of Microsoft Dynamics AX 4.0 To install more than one instance of a Microsoft Dynamics AX 4.0 role on a single computer, run Setup to install each instance on the computer. The setup wizard 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 Application Object Server (AOS) instances on the same computer. Each AOS instance can point 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, click Microsoft Dynamics AX 4.0.

2. On the Welcome Back page of the Setup Wizard, click Next to continue.

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

4. On the Select database page, select the type of database to connect to and then click Next.

To Do this: Create a new Microsoft SQL Server database

- In the Select database page, click Create a new SQL Server. - In the Connect to SQL Server page, in the Server name box, type or select the name of the SQL Server to connect to. - In the Create SQL Server database page, in the Database name box, type the name of the database to create.

Page 94



To Do this: Connect to an existing database configured with SQL

- In the Select database page, click Connect to an existing SQL Server database. - In the Connect to an instance of SQL Server page, in the Server name box, type or select the name of the SQL Server to connect to. - In the Database name box, type or select the name of the database to connect to.

TABLE 4.3: CREATE OR CONNECT TO SQL SERVER

5. On the Create an instance of Application Object Server page, in the Application Object Server name box, type a name for this AOS. Select a different name than the first installed instance. Setup increments the TCP/IP port assigned to the AOS by one. For example, when the first instance is installed on TCP/IP port 2712, the second instance is installed to TCP/IP port 2713.

6. On the Locate application files page, type or browse to the location where the Microsoft Dynamics AX 4.0 application files are installed. Click Next to continue.

7. Click Next to continue.

8. On the Ready to install page, review the summary of roles for this computer. To continue, click Next.

9. On the Installing page, it is possible to monitor the installation progress as Setup proceeds.

10. On the Completing Microsoft Dynamics AX 4.0 Setup page review the summary of roles for the computer.

11. To exit the Setup wizard, click Finish.

Test Your Knowledge − Install Multiple Application Object Server Instances

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

Page 95



Manage a New Microsoft Dynamics AX 4.0 AOS Instance A configuration is a group of startup and tracing settings for an Application Object Server (AOS) instance that is stored in the Microsoft® Windows® registry or in a configuration file. Administrators may want to create new configurations and configuration files, save, or load configurations to support:

• Having multiple environments, one instance for the live environment, one instance for development, and one instance for testing.

• Moving from a development environment to a production environment. Change the application directory that an AOS instance points to, the database, and whether a system allows for debugging.

• Tuning Microsoft Dynamics AX. Save a configuration with the defaults, and then change compression, database tuning, and tracing settings one at a time, and save them as different configurations. Run Microsoft Dynamics AX with each different configuration, and evaluate how it performs.

On the computer that is running the Application Object Server (AOS), only members of the local Microsoft Windows Power User group or Administrators group can change configuration settings. Restrict membership in these groups as much as is feasible, to reduce the potential for malicious mischief. Use the Server Configuration Utility to validate that the AOS points to the correct database and application file server.

FIGURE 4.1: MICROSOFT DYNAMICS AX SERVER CONFIGURATION UTILITY

Page 96



1. Open the Microsoft Dynamics AX Server Configuration Utility

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

2. Click Manage, click Create configuration, and then enter a name for the configuration, and determine whether to copy it from the active or original configuration.

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

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

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

Page 97



Scenario GTM is in the process of implementing Microsoft Dynamics AX 4.0. They have decided that they will create separate environments for developing, testing, and training. These separate environments will help GTM implement the live system without altering live data. GTM has several consultants helping them with the implementation. These consultants will be doing development in addition to internal GTM administrators. The implementation consultants have developed a process for completing developments, testing the developments, and moving them into the live system.

Problem The consultants helping GTM with the implementation have experience with Microsoft Dynamics AX 4.0. GTM in-house administrators will be helping with the development, but are learning about Microsoft Dynamics AX 4.0 as it is implemented. The GTM in-house administrators must be able to work in Microsoft Dynamics AX without hindering the consultants' development.

Goal The goal for GTM is to provide an environment for in-house development and training that does not interfere with other environments. Another instance of Microsoft Dynamics AX on each of the existing database, application file, and application 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 single computer contains its own database, application file server, application object server, 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

Page 98



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 4.2: MICROSOFT DYNAMICS AX CONFIGURATION UTILITY NOTE: You must be an administrator or power user on the computer to use the Configuration Utility.

1. Open the Configuration Utility (START→CONTROL PANEL→ADMINISTRATIVE TOOLS→MICROSOFT DYNAMICS AX 4.0 CONFIGURATION UTILITY).

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

Page 99



3. Click Manage, click Create configuration, and then enter a name for the configuration, and determine whether to copy it from the active or original configuration.

4. On the Connection tab, click Add, and then enter the Server name, Instance name, and TCP/IP port of the AOS instance to point the client to, and then click OK and exit the configuration utility.

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

Test Your Knowledge − Point a Client to a Microsoft Dynamics AX 4.0 Instance

Who can use the Configuration Utility?

Page 100



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

• Each developer can safely save extensions and modifications without the risk of losing time overriding changes.

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

• Developers can share their changes when working on a project. • Developers can test changes to Microsoft Dynamics AX without the

risk of losing previous work, as they can always return to an earlier version.

• 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 the objects.

Each object in the AOT must have a unique ID. A centralized service controls the allocation of IDs when developing in a team environment. The Team Server connects to the VCMS to issue object IDs and Label IDs when adding new objects.

Set Up the Team Server Each object and label in Microsoft Dynamics AX has a unique identification, and unique IDs must be assigned to new objects and labels. A central service coordinates tasks when developing in a team environment. The Team Server handles the task of issuing IDs when developers create new objects and labels. NOTE: It is not recommended to install the Team Server on the same computer as the Microsoft Dynamics AX database. If the same computer contains two databases, the AOS account authenticates by two different user groups. Therefore, the two groups have access to either the Microsoft Dynamics AX database or the Team Server database, but not both. The database server only authenticates the user access to one of the two databases and not both.

Prerequisites The following are requirements for the Team server computer:

• Microsoft® Windows Server™ 2003 or Windows 2000 • Microsoft SQL Server 2005 • SQL Server agent is running

Page 101



Create a New User Group and Add Members When installing the Team server, add each Developer computer as a user on the Team Server. The administrator must create a new local user group and add all Developer computers as members.

1. Click START→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. Click Add to add a new member.

7. Click Object types.

8. Select Computers and then click OK.

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

10. Click Close.

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

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 the Team server computer. If the Setup Wizard does not start automatically, double-click the Autorun.hta file in the root directory of the DVD.

2. Click Browse additional tools.

3. Click Install Team Server to open the Team server setup wizard. Click Next.

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

5. Accept the terms in the License agreement, and then click Next.

6. Fulfill the Prerequisites, and then click Next.

7. Type the SQL Server name and then click Next.

8. Type the Team server database name and then click Next.

Page 102



9. Type the Team server user group name and then click Next.

10. Click Install. The installation takes a few seconds. After the confirmation, click Finish.

NOTE: When creating the repository and the label files in the version control database, all objects and labels are assigned IDs. For more information, refer to the topics on "Deploy AOT Objects on the VSS Server" and "Deploy Label File on the VSS Server."

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 Server documentation.

Share the VSS Database Folder on the Server The developers who use the VSS database need access to the VSS database folder on the VSS server. Developers can change the security setup based on preferences.

1. Open Windows explorer.

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

3. Click Share this folder.

4. Click the Permissions button.

Page 103



5. In the Group or User names box, click Everyone or click Add to add a specific developer to the list.

6. In the Permissions for Everyone pane, select the appropriate access level, such as Full control.

7. Click OK and OK.

Set Up Global Version Control Parameters The administrator controls the global settings for the version control management system (VCMS). This includes specifying the Team server, specifying rules for objects, and setting rules for best practices. When the administrator has enabled the version control system globally, the individual developers can set up their personal parameters, such as repository folder.

Create a Local Repository Folder 1. Open Windows Explorer.

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

Set Up Global Version Control Parameters (Administrator) 1. Click Tools →Development tools →Version

control→Setup→System settings.

2. In SysVersionControlParameters, VCSType, select Visual SourceSafe.

3. In SysVersionControlParameters, RepositoryFolder, type the name of the local repository folder. For example C:\VCS_Repository.

4. In SysVersionControlParameters, TSType, select Microsoft SQL Server.

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

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

7. Click the Visual SourceSafe tab.

8. In SysVersionControlParameters, VSSIniFile, type the path and filename for the SourceSafe.Ini file in the SourceSafe database folder on the VSS Server.

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

10. Click the General tab.

Page 104



11. In SysVersionControlParameters, VCSEnabled, select Enable, and then click Apply.

12. Click Yes 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 file defines 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 developers by disabling version control on the System settings form. Developers can disable their personal version control parameters but cannot be able to change the global settings. To protect the Global Version Control settings in Visual SourceSafe:

1. Click START→ALL PROGRAMS→MICROSOFT VISUAL SOURCESAFE→ MICROSOFT VISUAL SOURCESAFE ADMINISTRATION.

2. Click TOOLS→OPTIONS.

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

4. Click TOOLS→RIGHTS BY PROJECT.

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

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

Set Up Local Version Control Parameters When the version control management system (VCMS) administrator has installed the Team server and Visual SourceSafe (VSS) server, and enabled version control globally, then users can enable version control on the development computers. After successfully enabling version control on the development computer, it is possible to check out and modify objects in the AOT, add new objects, and more.

Page 105



After checking in the changes to VSS, other developers working on the same project 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)

Create a Local Repository Folder 1. Open Windows Explorer.


Enable Version Control Locally (Developer) 1. Click TOOLS→DEVELOPMENT TOOLS→VERSION

CONTROL→SETUP→PARAMETERS.

2. In SysVersionControlParameters, VCSType, select Visual SourceSafe.

3. In SysVersionControlParameters, RepositoryFolder, type the name of the local repository folder. For example C:\VCS_Repository.

4. Click the Visual SourceSafe tab.

5. In SysVersionControlParameters, VSSIniFile, type the path and filename for the SourceSafe.Ini file in the SourceSafe database folder on the VSS Server.

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

7. Click the General tab.

8. In SysVersionControlParameters, VCSEnabled, select Enable, and then click Apply.

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

1. Click TOOLS→DEVELOPMENT TOOLS→VERSION CONTROL→SYNCHRONIZE.

Page 106



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

3. Click OK to start synchronization. The latest version of all AOT objects on the VSS server is copied to the repository folder on the development computer. For more information, refer to SysVersionControlSynchronization Class Form

Deploy AOT Objects on VSS Server When the administrator of the version control management system (VCMS), has installed the Team server and the Visual SourceSafe (VSS) server, the next step is to add all objects, from the master copy of Microsoft Dynamics AX, to the VSS 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 make sure that the Team server can issue unique IDs when creating new objects.

Create a Local Repository Folder Make sure to create a repository folder on the computer. When deploying the AOT objects, a copy of each object is also added to the repository folder.

1. Open Windows Explorer.


Create Repository 1. Click TOOLS→ DEVELOPMENT TOOLS→VERSION

CONTROL→SETUP→CREATE REPOSITORY.

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

3. Click OK.

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

Page 107



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 1. Click TOOLS→DEVELOPMENT TOOLS→VERSION

CONTROL→SETUP→CREATE 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 the browse button to locate the master label file. Label files are usually located in the C:\Program file\Microsoft Dynamics Ax\40\Application\Appl\Standard folder.

4. Click OK.

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

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

Page 108



Conclusion In a development environment, a single computer may have to accommodate more than one AOS. Developers can have more than one environment on a single computer for development or testing by becoming familiar with the steps to install, manage, and set up of the development side of Microsoft Dynamics AX. The steps provided by the installation wizard help make the single computer install a straightforward process. Additionally, the single computer installation can help Partners, developers, testers, and salespeople in many ways, such as:

• Easier to install • Quicker to install • Technical knowledge uneeded

Page 109



Lab 4.1 − Install Microsoft Dynamics AX 4.0 on a Single Computer

You are part of an implementation team installing Microsoft Dynamics AX 4.0. The team has completed the installation of the database, application file server, application object server, and client on separate computers. In order to train users on the application without giving them access to the live system, the team decides to install an instance of Microsoft Dynamics AX 4.0 on a single computer to use as a training computer.

Challenge Yourself! Install an instance of Microsoft Dynamics AX 4.0 on a single computer.

Need a Little Help?

1. Run the setup program.

2. Select Single Computer Installation.

3. Install the database, application file server, application object server and client.

Page 110



Lab 4.2 − Manage a new Microsoft Dynamics AX 4.0 Instance In addition to the training computer, a separate environment will be required for development to work in, without affecting the live system. This will require a duplicate system on the same servers and PCs as the live system. Create a new development environment.

Challenge Yourself! Verify the Application Object Server settings for the Development instance.

Need a Little Help?

1. Run the Microsoft Dynamics AX 4.0 Server Configuration Utility.

2. Create a new configuration

3. Select the Application Object Server file location and database name.

Page 111



Lab 4.3 − Point a Client to a new Microsoft Dynamics AX 4.0 Instance

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

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.

Page 112



Quick Interaction: Lessons Learned Take a moment and write down three Key Points you have learned from this chapter: 1.

2.

3.

Page 113



Page 114

Documents

Ax40 Enus in 04