I am afraid PHP (and Java for that sake) cannot connect directly to NAV Web Services.
Reason is the authentication schema used by NAV Web Services is not supported by these two.
I have filed a bug on this and hope we get this fixed for SP1.
I will create a description of how to do this on my blog (being an "old" PHP developer) once we have a fix for it.
Now I deliberately wrote directly - because you can always create a service proxy (in .net - Vb or C#) and connect to this service from Java or PHP. This service would then act as the "middle man" between your app and NAV Web Services.
This is pretty simple to do for codeunits - but pretty hard for pages.
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
I hope they fix it for SP1. I hope MS doesn't follow the embrace and extend tactic in the ERP world.
What I mean is that they have embraced a technology and then extended it so that it's no longer compatible with other existing solutions.
Examples.
Java (implementing own functionality),
HTML (VBscript and ActiveX, releasing incompatible browser).
Now web services ( encapsulating it with an authentication system, that makes it useless to integrate)
NAV and NAV Web Services used Windows Authentication and in order to make 3T run decently we use Kerberos as ticket issuer (I don't know if this is the right terminology).
That is in everybody's interrest for security, delegation, single login etc.
The protocol used by NAV Web Services is public and not proprietary and over time there probably will be support made for this protocol (as it happened with NTLM and other protocols starting out in MS).
My reason for filing this bug was, to open up more broadly and help people using other tools than Microsoft tools to get going sooner than later (mostly because nobody really knows when later is going to be).
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
Comments
Reason is the authentication schema used by NAV Web Services is not supported by these two.
I have filed a bug on this and hope we get this fixed for SP1.
I will create a description of how to do this on my blog (being an "old" PHP developer) once we have a fix for it.
Now I deliberately wrote directly - because you can always create a service proxy (in .net - Vb or C#) and connect to this service from Java or PHP. This service would then act as the "middle man" between your app and NAV Web Services.
This is pretty simple to do for codeunits - but pretty hard for pages.
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
What I mean is that they have embraced a technology and then extended it so that it's no longer compatible with other existing solutions.
Examples.
Java (implementing own functionality),
HTML (VBscript and ActiveX, releasing incompatible browser).
Now web services ( encapsulating it with an authentication system, that makes it useless to integrate)
I'm sure there are countless of other examples.
That is in everybody's interrest for security, delegation, single login etc.
The protocol used by NAV Web Services is public and not proprietary and over time there probably will be support made for this protocol (as it happened with NTLM and other protocols starting out in MS).
My reason for filing this bug was, to open up more broadly and help people using other tools than Microsoft tools to get going sooner than later (mostly because nobody really knows when later is going to be).
I hope people see this as a positive thing.
/Freddy
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
I wish you all the luck be resolved in 2009 sp1.
I've posted a example on how to create a web service proxy.
http://mibuso.com/blogs/ara3n/2009/05/0 ... b-service/
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n