Call NAV WS from NAS asynchronously

Lars_Westman

I have a setup where the NAS loops through a job que to call NAV web services to perform automation. The web services are called using 'Microsoft XML, v6.0'.XMLHTTP60 asynchronously. Meaning that we don't wait for the response. Instead we go on to the next job and start that and it's up to the codeunit we called to give a response back to the queue with the result. The purpouse with this setup is to process in parallell in multiple companies. Everything is working nicely but I cant get more than two paralell sessions running.

There seems to be a limitation in the way NAV calls the ws. If I create a ws that sleeps a while I can start that ws 5 times in parallell using e.g. Web Service Stuido and get five different sessions in NAV, but NAV can only open up two sessions from one single client. If I open up one more NAV client I can get two more sessions and so on.

Anyone seen this before?

//Lars

Lars_Westman

Found it \:D/

http://support.microsoft.com/kb/183110

mdPartnerNL

We have a .net application which calls a NAV webservice repeatedly. Will it have the same problem? and which of the two values did you change?

Lars_Westman

If you call the WS async you probalby have the same issue. You can spot this by looking at the session table and see that you only have two sessions regardless how manny calls you fire against the NAV WS.

It wasn't until I added the latter of the two keyes more sessions where available. You wont get any errors without this change, you simple don't get the degree of parallellism you thought you would.

//Lars

mdPartnerNL

ok, I will test this and let you know

Lars_Westman

Just remember that you have to do the register change for the actual user running the code.