官术网_书友最值得收藏!

Architectural overview

Depending on the requirements of your projects, a different architectural approach will be needed. To make the right decisions when designing your solutions, it is important to understand the services and AIF architecture.

Compared to Microsoft Dynamics AX 2009, there have been a lot of improvements made to the service architecture in Microsoft Dynamics AX 2012. The biggest improvement is the native Windows Communications Foundation (WCF) support. As a result, the proprietary Microsoft Message Queuing (MSMQ) and BizTalk adapters that were available in Microsoft Dynamics AX 2009 have been deprecated and replaced by adapters that use WCF. The MSMQ adapter in particular is replaced by an adapter that uses the WCF NetMsmq binding. The filesystem adapter remains intact and still allows you to import and export messages from and to the filesystem.

All services are WCF services and are hosted on the AOS. When an application wants to consume these services on the local network, no further deployment is needed because it can connect directly to the AOS. Just like with Microsoft Dynamics AX 2009, deployment on Internet Information Services (IIS) is needed for consumers that are not on the intranet. However, the services themselves are no longer deployed on IIS; instead, a WCF routing service on the IIS routes everything to the AOS.

If you want to modify messages before they are received or after they are sent, you can use pipelines and transformations. Pipelines only apply to the body of a message and are handled by the request preprocessor and response postprocessor. You can use transformations to transform a complete message, including the header. This allows you to exchange messages in a non-XML format.

The following diagram depicts the architecture as it is in Microsoft Dynamics AX 2012 and clearly shows the central role of WCF:

Architectural overview

While not displayed in the diagram, there is now load balancing support for services using Windows Server Network Load Balancing (NLB). Combined with NLB for IIS, which was already available, this enables high availability and load balancing for services.

主站蜘蛛池模板: 广德县| 祁阳县| 扶余县| 疏附县| 安丘市| 惠水县| 长子县| 辽阳县| 石狮市| 麻江县| 宜兰县| 阿拉善右旗| 上犹县| 淅川县| 炎陵县| 化州市| 右玉县| 红桥区| 托里县| 固阳县| 灯塔市| 息烽县| 利辛县| 新营市| 海口市| 桃源县| 台州市| 娄烦县| 嘉禾县| 吴桥县| 南溪县| 正安县| 房山区| 淮滨县| 彝良县| 慈溪市| 定日县| 磐石市| 兴文县| 班玛县| 论坛|