How can I Integrate Windows mobile with Axapta using Webservice

[Ahmed Al Abyad]

Hi All;



I would like to connect Windows mobile with axapta using C# code, knowing that I can connect to the Axapta using windows application through the following code:-



try

{

TryWebService.ServiceReference1.Service1Client client = new Service1Client

client.Open(); //this open the axapta which i need it in windows mobile too

}

catch (Exception ex)

{





MessageBox.Show(ex.message);

}



Note: I cant connect to the Axapta through handheld as there is no Service1Client but there is Service which when I take an object from it , it doesn't have function Open() (i.e. there is not client.Open() )



How to connect to Axapta using handheld



Thanks in advance;

Regard's

[Vadik]

Hi Ahmed,
There is no single part of AX (neither rich client nor .Net Business connector) which can be installed on WIndows mobile (Dynamics Mobile R.I.P.). Instead, have a look at AIF and .Net Business connector samples on MSDN - for example this one

[Ahmed Al Abyad]

I don't want to install AX on windows mobile, I want to connect windows mobile to AX that is on windows sever 2008 R2

AX version:-
Kernel version : 5.0.1500.2985
Application Version: 5.0.1500.2985

Solution Version: 5.0.1500.172
This product is licensed to Contoso Entertainment
Serial Number: M3048953

Note: I want to connect handheld with Axapta using webservice not install Axapta on windows mobile

[ZornFire]

Ahmed, good day.
If you want connecting to the terminal server, you should first contact your system administrator with the question "whether the connection?", because a lot depends on the server, perhaps it does not include a service charge for this type of connection.
If possible, but it does not work, then read the forums on your mobile device.

[cyrus]

Proper solution for connecting WM terminals to DAX is to use AIF Web services. There are some issues though.
1) WCF is supported only in CF3.5
2) BasicHTTPBinding shall be used. wsHttpBinding is not supported in CF3.5
3) Binding security shall be set to Transport since None is not supported by AIF (it shall know particular web-service user) and TransportCredentialsOnly is not supported by CF3.5
3) IIS shall be configured to support SSL
4) Certificate shall be installed on each consuming device, similar to cross-domain security

If you make security setup properly the connection will be plain simple just like in this example.