技術(shù)開發(fā)接口服務(wù)開發(fā)

1、Chapter 3: Installation and UpgradeCHAPTER 3: INSTALLATION AND UPGRADEObjectives3-31Microsoft Official Training Materials for Microsoft Dynamics®Your use of this content is subject to your current services agreementIntroductionThe objectives are:· Discuss the installation process and the s

2、pecial considerations for Services and AIF in Microsoft Dynamics AX 2012.· Review the upgrade considerations for Services and AIF.Knowing the installation and upgrade considerations for Services and Application Integration Framework (AIF) in Microsoft Dynamics AX 2012 is critical for successful

3、 implementation.InstallationInstallation and configuration of Services and AIF has changed. In Microsoft Dynamics® AX 2012, the Application Object Server (AOS) is the Windows Communication Foundation (WCF) service host for Microsoft Dynamics AX services, and web services on IIS is an optional c

4、omponent. Additionally, the BizTalk adapter has been depreciated in favor of using the Windows Communication Framework (WCF)-based adapters that are included with BizTalk.IISInstalling Microsoft Dynamics AX web services on IIS is optional. The Application Object Server (AOS) is the Windows Communica

5、tion Foundation (WCF) service host for Microsoft Dynamics AX services that are available to users and applications across an intranet. To make Microsoft Dynamics AX services available over the Internet, you must host them on Internet Information Services (IIS).If you do not need to expose the Micros

6、oft Dynamics AX services over the Internet or need any of the additional bindings that IIS provides, you do not need to install services on IIS.Before Installing Web Services on IISVerify that the following steps are completed before you install the Microsoft Dynamics AX web services on IIS:· O

7、n the computer where you will install the web services, run the prerequisite validation utility to verify that system requirements have been met.NOTE: For more information on the prerequisite validation utility refer to the Microsoft Dynamics AX 2012 Installation Guide ( ).· Create a domainthat

8、 will be used as the Business Connector proxy . Thismight also be the one that is used for reporting service s and for the IIS Application pool identity. Each that must run as a service requires the following properties:o Be a dedicated (used only for the specific purpose)o Have sword that does not

9、expireo Have minimal access to network resourceso Be able to log on as a service· Make sure that you have the required permissions to install the web services, which requires you to be a member of the following:o The Administrators group on the local computer where you are installing Web Servic

10、es on IISo The System administrator role in Microsoft Dynamics AX 2012CAUTION: Do not install web services on IIS on a server that is a network domain controller.Procedure: Install the Web Server (IIS) RoleWhen you run the prerequisite validation utility it presents the option to configure the Web S

11、erver role. However, the prerequisite validation utility does not install the ASP.NET role service. Use the following steps to install the ASP.NET role service:· Start the Server Manager. Expand the Server Manager (computer_name) node. Right-click Web Server (IIS) and then click Add Role Servic

12、es.· On the Select Role Services dialog, expand the Web Server (Installed) > Application Development (Installed) node and then sele P.NET. Click Next and go through the wizard pages.· Restart the server.NOTE: This proceduas aly been completed in the Hyper-V image.Procedure: Create an II

13、S WebsiteCreate a website that Setup will use to install the Microsoft Dynamics AX web services. You can create a new website or use an existing one, such as the Default Web Site on IIS. If you install the Microsoft Dynamics AX web services on an IIS that also hosts a SharePoint web front end or oth

14、er web services, be sure to avoid port-binding s.Procedure: Install Web Services on IISUse the following steps to install web services on IIS:1. Double-click D:Setup.exe.2. Under Install, click Microsoft Dynamics AX components.3. If the setup support files have not yet been installed on this compute

15、r, the Select a file location page is displayed. The Setup support files are required for installation. Provide a file location or accept the default location and then click Next. On the y to install page, click Install.NOTE: In the Hyper-V image, setup install files have aly been installed.4. Click

16、 Next.5. In the Modify Microsoft Dynamics AX installation page, clickAdd or modify components, and then click Next.6. On the Add or modify components page, select Web services on IIS and then click Next.7. On the Prerequisite validation page, resolve any errors. When no errors remain, click Next.8.

17、On the Specify Business Connector proxyinformationpage, enter the password for the proxythat is used by the.NET Business Connector. Click Next.NOTE: The proxyfor the .NET Business Connector in the Hyper-V image is "CONTOSOSQLService" and the password is "Pa$w0rd".9. On the Config

18、ure IIS for Web services page, accept default values or provide information for the website, application pool, and virtual directory. Setup will create a virtual directory and an application pool for the Microsoft Dynamics AX web services under the selected website. The application pool will run as

19、the .NET Business Connector proxy user that you entered in the previous step.IMPORTANT: You must restart IIS after Setup installs the web services. SelectRestart IIS after installation is complete to automatically restart IIS.10. Click Next to continue.11. On the Specify an AOS page, provide the ser

20、vice s for the AOS instances that you will use with web services on IIS. Click Next to continue.12. On the Prerequisite validation results page, resolve any errors. When no errors remain, click Next.13. On the y to install page, click Install.14. After the installation is complete, click Finish to t

21、he wizard.Procedure: Configure IISFor IIS 7, use the following steps to configure the application pool that is associated with the Microsoft Dynamics AX 2012 web services for IIS 7. This step is required to set the correct version of the .NET Framework.1. Click Start > Administrative Tools > I

22、nternet Information Services (IIS) Manager.2. Click SEA-DEV > Application Pools.3. In the Application Pools pane, right-click MicrosoftDynamicsAXAif60 application pool, and click Basic Settings.4. In the Edit Application Pool dialog box, select .NET Framework4.0 or a later version, such as V4.0.3

23、0319. Select Integrated from the Managed pipeline mist. Notice that the Start application pool immediately option is selected. Click OK to return to IIS Manager.5. Click SEA-DEV .6. Right-click SEA-DEV and then click Stop.7. Right-click SEA-DEV and then click Start.For IIS 6, make sure that the virt

24、ual directory for the Microsoft Dynamics AX web services is associated with version 4 of .NET Framework. Refer to IIS 6.0 documentation for instructions.Procedure: Register the Website in Microsoft Dynamics AX 2012Use the following steps to register the website in Microsoft Dynamics AX.1. Open Micro

25、soft Dynamics AX 2012.2. Click System administration > Setup > Services and Application Integration Framework > Web sites.3. On the Web sites form, create a new record and provide appropriate values for the Name, Virtual directory share path, Description, and URL fields.NOTE: On the Hyper-V

26、 image a record will aly be created with the following URL and virtual directory share path.URL: Virtual directory share path: SEA-DEVMicrosoftDynamicsAXAif60 (file:/sea- dev/MicrosoftDynamicsAXAif60)4. Click Validate. Verify that the Infolog dialog confirms that the website is configured properly,

27、and that you can access the computer and the website.NOTE: When you install web services on IIS, a record for the new website is added to AifWebsites table. If you uninstall web services on IIS, this record is not deleted from the table. This record can cause a warning to be displayed if you reinsta

28、ll web services on IIS. You can manually delete the record from the AifWebsites table or simply ignore the warning.Creating Additional Web SitesYou can create additional websites if you require them. For example, you might have to expose a web service through a web server that is installed on a diff

29、erent computer than the instance of Application Object Server (AOS).When adding a website, consider the following:· You must set the appropriate permissions for a new virtual directory so that Microsoft Dynamics AX can access the file share. The group that is named Microsoft Dynamics AX Web Ser

30、vice Administrators must have full access to the new virtual directory and file share.If this group does not exist as a local group on the new computer, you must create it. You must then add, as a user, the domain for all AOS instances that require access. For these changes to take effect, you must

31、restart all AOS instances that you added to the group.· When you install web services on IIS, a record for the new website is added to the AifWebsites table. If you uninstall Web services on IIS, this record is not deleted from the table. Because this record still exists, you might receive a wa

32、rning if you later reinstall Web services on IIS. You can either manually delete the record from the AifWebsites table or ignore the warning.MSMQMicrosoft Message Queuing (MSMQ) is a technology that enables applications that are running at different times to communicate across heterogeneous networks

33、 and systems that might be temporarily offline. MSMQ provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It can be used to implement solutions for asynchronous and synchronous messaging scenarios.To send documents by using Message Queuing, you must instal

34、l it on a computer on the network and create at least one public queue.To receive documents by using Message Queuing, you must install Message Queuing and create at least one queue.MSMQ LimitationsMessages that are processed by the MSMQ adapter have a size limit of 4 megabytes (MB). For this reason,

35、 we do not recommend using Message Queuing to import data in bulk, such as by using the AIF batched-message schema.Installing MSMQAny computer that communicates through Message Queuing, including computers that run AOS, must have Message Queuing installed.Windows servers must have the Application Se

36、rver role added. For application servers, select the following options:· Inco Remote Tranions· Outgoing Remote TranionsWindows servers must have the Application Server Features added. For Message Queuing > Message Queuing Services, select the following options:· Message Queuing Ser

37、ver· Directory Service Integration· HTTP SupportFor Microsoft Dynamics AX AIF scenarios, Message Queuing must be installed in Domain mode, which connects to the Active Directory service. Do not install Message Queuing in Workgroup mode on computers that exchange messages through AIF by usi

38、ng the MSMQ adapter.NOTE: Microsoft Dynamics AX requires that inco messages be signed. If you need to send signed messages from Microsoft Dynamics AX, such as to other Microsoft Dynamics AX installations, you must run the AOS service under an Active Directory domain. By default, the AOS service runs

39、 under the Network Service. When AOS is running under the Network Service , it cannod signed messages because the Network Service is not in Active Directory.Demonstration: Set Permissions for MSMQThis demonstration shows how to set up permissions for MSMQ.Grant permissions for a computer object to t

40、he Servers object in Active Directory Domain Services before installing the Routing Service feature on a computer that is not a domain controller.1. Enable , Write, and Allow Create all child objects access to necessary computers.a. Go to Start > Administrative Tools > Active Directory Sites a

41、nd Services.b. Expand Sites > Default-First-Site-Name , right click Servers, and then and then click Properties.c. Click the Security tab of the Servers Properties dialog box.d. Click the Add button to display the Select Users, Computers, Service s, or Groups dialog box.e. Click the Object Types

42、button to display the Object Typesdialog box, click to enable Computers and then click OK.f. In theEnter the object names to select field type "SEA-DEV" and then click OK.g. Enable the following permissions for this computer object:o Allow o Allow Writeo Allow Create all child objectsh. Cl

43、ick Advanced to display the Advanced Security Settings for Servers dialog box.i. Select the SEA-DEV object from the list of permission entries and then click the Edit button.j. Select This object and all descendant objects from the Apply to drop-down listk. Click OK to all dialogs.2. Give Network Se

44、rvice allow access to Create MSMQ Configuration Objects.a. Go to Start > Administrative Tools > Active Directory Users and Computers.b. Select View > Advanced Features.c. Select View > Users, Contacts, Groups and computers as containers.d. Go to Contoso > Domain Controllers.e. Right-c

45、lick SEA-DEV and then click Properties.f. Click Security and then Advanced.g. Click Add.h. In Enter the object name to select type "Network Service" and then click OK.i. Select Allow for the Create MSMQ Configuration objectspermission.j. Click OK to all dialogs.Demonstration: Install MSMQU

46、se the following procedure to install Message Queuing 4.0 on Windows Server 2008 or Windows Server 2008 R2 for Services and AIF.1. Click Start > Administrative Tools > Server Manager.2. In Server Manager, click Roles > Application Server.3. Right-click Application Server and then click Add

47、Role Services.4. Click IncoRemote Tranions and then click Outgoing Remote Tranions.5. Click Next and then click Install.6. Click .7. In Server Manager, click Features.8. In the right-hand pane under Features Summary, click Add Features.9. In the resulting window, expand Message Queuing.10. Expand Me

48、ssage Queuing Services.11. Click Directory Services Integration (for computers that are joined to a Domain) and then click HTTP Support.NOTE: Click Yes, I've set the required permissions, in the Have you set the required permissions in Active Directory Domain Services? message box.12. Click Next

49、 and then click Install.13. Click .Configure the Distributed Tranion CoordinatorThe Distributed Tranion Coordinator (MSDTC) service coordinates tran ions in Message Queuing queues. You must start and configure MSDTC on servers that use Message Queuing with AIF.Demonstration: Configure the Distribute

50、d Tranion CoordinatorTo configure MSDTC for Services and AIF, follow these steps:1. Click Start > Administrative Tools > Component Services to open the Component Services window.2. Expand Component Services > Computers > My Computer > Distributed Tranion Coordinator.3. Right-click Loc

51、al DTC and then click Properties.4. On the Security tab, select the following check boxes and then clickOK:o Network DTC Accesso Allow Remote so Allow Inboundo No Authentication Requiredo Enable XA Tranions5. In the "The MSDTC service will be stopped and restarted. All dependent services will b

52、e stopped. Applications using MSDTC may need to be restarted to use the new settings. Please press yes to proceed." dialog click Yes.6. In the "The MSDTC service has been restarted" dialog click OK.7. Restart the server. (Click Start > Log off, then Restart)NOTE: Click Yes in the d

53、ialog that states "The MSDTC service will be stopped and restarted. All dependent services will be stopped. Applications using MSDTC may need to be restarted to use the new settings. Please press yes to proceed." Click OK to the dialog stating "The MSDTC service has been restarted.&qu

54、ot;Remote Connection to MSMQTo enable remote communication with queues, you must configure the MSMQ adapter's security mode. This mode is not configured by default. In the configuration file for the MSMQ adapter, the <security> element of the<binding> element that has the "MsmqI

55、ntegrationSendBinding" attribute must be configured as follows:<binding name="MsmqIntegrationSendBinding"><security mode="Transport"><transport msmqAuthenticationMode="WindowsDomain" msmq Level="Sign"/></security></binding>NO

56、TE: If you have installed the WCF Configuration Editor tool, you can change these settings by using the tool.Configure MSMQIn Windows Server 2008 R2, Message Queuing is managed either by using Computer Management, or if the Message Queuing Directory Service Integration feature is installed, by using

57、 Active Directory Users and Computers. Message Queuing is located under the specified computer object in Active Directory Users and Computers. Additionally, if the Message Queuing Directory Service Integration feature is installed, then certain aspects of Message Queuing in Active Directory can be m

58、anaged from Active Directory Sites and Services.NOTE: More information about MSMQ can be found at the Message Queuing ( ) TechNet site.BizTalkMicrosoft Dynamics AX 2012 no longer includes a BizTalk adapter. Earlier versions of Microsoft Dynamics AX required a BizTalk adapter for integration with Microsoft BizTalk Server. However, BizTalk Server can now connect to AIF through Windows Communication Framework (WCF)-based adapters.NOTE: More information on installing and configuring BizTalk Server 2010 c