Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Using Nav app server as webservice proxy
gilbert
Member Posts: 11
Hi!
we're working on a three tier enviroment (Nav 2009), using a Point of Sale developed on .net as a client to connect to Navision (18 months on production environment).
Now we need to call a function from the .net POS on a published codeunit on the Nav App Server. This function calls an external webservice, using XmlDoc and XmlHttpRequest. At this point everything works fine, the function run OK if it's called from Classic client and from .net app too.
The problem:
In our tests from .net app if we've 2 or more users call this function, the Nav App Server not responds as a multithread service, and the calls to the external web service are processed one by one, generating a queue and timeout errors.
I'm waste a lot of time tunning the function on the published codeunit and finding info on mibuso forum or googling, but no exit, can you help me?
Thank you very much! And sorry my bad english...
Gilbert.
we're working on a three tier enviroment (Nav 2009), using a Point of Sale developed on .net as a client to connect to Navision (18 months on production environment).
Now we need to call a function from the .net POS on a published codeunit on the Nav App Server. This function calls an external webservice, using XmlDoc and XmlHttpRequest. At this point everything works fine, the function run OK if it's called from Classic client and from .net app too.
The problem:
In our tests from .net app if we've 2 or more users call this function, the Nav App Server not responds as a multithread service, and the calls to the external web service are processed one by one, generating a queue and timeout errors.
I'm waste a lot of time tunning the function on the published codeunit and finding info on mibuso forum or googling, but no exit, can you help me?
Thank you very much! And sorry my bad english...
Gilbert.
0
Answers
The problem are the automation variables XMLDOM and XMLRequest that codeunit function use to call the external webservice. This automation objects are not compatible with multi threading environment (nav app server).
The solution:
Make custom dll that call the external web service and use it in the Navision codeunit instead XMLDOM automation.
It Works!
Bye!