Inside Dynamics AX 4.0: Usage Scenarios
This section provides several scenarios to demonstrate how the Business Connector might be used in real-world situations. The usage scenarios described here fall into the following categories:
In client-based scenarios, the Business Connector and the application that uses it are installed on a user's desktop computer. To make this easier to set up, Dynamics AX 4.0 allows the installation of just the COM or .NET Business Connector, instead of the entire Dynamics AX rich client (which was required in the previous version of Dynamics AX).
Office Excel Integration Example
Microsoft Office Excel integration is probably the best illustration of client-based use of the COM Business Connector, because it is a commonly used tool and particularly appropriate for viewing and manipulating data sets from ERP systems such as Dynamics AX.
You can extend Office Excel by developing add-ins that load when Excel launches. Office Excel exposes a menu that can be accessed by users working on a spreadsheet. Here are the requirements for this type of integration:
Office Excel integration with Dynamics AX using the COM Business ConnectorThe following actions are associated with the use of the COM Business Connector from the Office Excel add-in:
PDA Synchronization Example
A potential client-based use of the .NET Business Connector is for PDA synchronization. For example, you could develop an application that allows a PDA to collect information that can be uploaded to Dynamics AX. PDAs generally rely on some kind of synchronization manager; if this synchronization program is customizable, you can extend it to integrate with Dynamics AX.
The specific requirements for this type of integration are as follows:
PDA synchronization using the .NET Business Connector
The following actions are associated with the use of the .NET Business Connector during PDA synchronization:
Earlier in this chapter, we explained how the .NET Business Connector interacts with the managed HTTP context, thus enabling Web applications, including the Dynamics AX EP, to access and use this context information. One of the primary processes in the EP is page processing, which is a good example of how you can use a Business Connector to enable a Web application.
A final usage scenario uses the .NET Business Connector on the server that hosts the AOS and the Dynamics AX database, as shown in below image.
Server-based use of the .NET Business ConnectorIn this scenario, a non-Web-based managed application uses the .NET Business Connector to integrate with Dynamics AX. This approach can be used for a variety of purposes, but one example is offline processing. Typically, a Dynamics AX user must be logged on to a computer to authenticate in Dynamics AX. In some cases, this is not possible. For example, the asynchronous integration offered by the AIF does not require the originating user to be logged on to the machine where data is processed and inserted into Dynamics AX. However, this task must be executed using the correct user identity.
The solution is to use the .NET Business Connector to impersonate a Dynamics AX user. You can do this in one of three ways:
</img> </img> </img> </img> </img>
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
|axStart: Microsoft Dynamics AX 2009 Hot Topics Web Seminar Series||Blog bot||DAX Blogs||0||06.08.2008 12:05|
|Inside Dynamics AX 4.0: The Security Framework||Blog bot||DAX Blogs||0||31.10.2007 11:40|
|Inside Dynamics AX 4.0: Security||Blog bot||DAX Blogs||0||29.10.2007 10:50|
|Inside Dynamics AX 4.0: Working with the .NET Business Connector||Blog bot||DAX Blogs||0||04.10.2007 05:15|
|Inside Dynamics AX 4.0: Inside the Business Connector||Blog bot||DAX Blogs||0||04.10.2007 05:15|
|Опции темы||Поиск в этой теме|