Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Best alternate of Win...
Microsoft Dynamics AX (Archived)

Best alternate of Window Service for Ax 2012 integration scheduling

(0) ShareShare
ReportReport
Posted on by B K Sharma 735

Hi Experts,

Right now we have some window services to sync outside application data (Sales order, transfer order, SO packing slip, TO shipment and SO invoice almost all the transaction related to stock transfer and sales order shipment... etc) to the dynamics ax 2012, But after 3 years here transaction has increase 10 times and these window service is not performing well and we are even not able to sync last day transaction till morning today, so we are not able to collect reporting on the time, Now I am planning to switch to new integration engine which should be very effecting and perform well , So I request you to please guide me if any best solution available in the market which can selected data from outside application DB and can able to call the web service, able to handle responses from the service call and I can schedule it, the first thing come in my mind is SSIS.

Waiting for your suggestions

*This post is locked for comments

  • Mea_ Profile Picture
    Mea_ 60,278 on at
    RE: Best alternate of Window Service for Ax 2012 integration scheduling

    AX inbound services are capable to process multiple request in parallel, so you may want to send multiple records using multiple threads, that should help.

  • Martin Dráb Profile Picture
    Martin Dráb 230,458 Most Valuable Professional on at
    RE: Best alternate of Window Service for Ax 2012 integration scheduling

    Windows service isn't a task scheduling system, it's just a way to execute code. You write some code and decide whether you want it to run as an application (which needs to be explicitly started) or as background service. It doesn't say anything at all about what the code does.

    If you say that your service is the bottleneck, you should change what your service does, not avoiding Windows services.

    Processing records in batches instead of one by one (as I suggested before) indeed may increase throughput. Also, if there isn't a risk of blocking, you could send several concurrent requests to AX (a single Windows service can do that; you don't have to run several instances).

    But maybe the actual problem isn't in the service but the time needed to process each record and you should focus your effort there.

  • B K Sharma Profile Picture
    B K Sharma 735 on at
    RE: Best alternate of Window Service for Ax 2012 integration scheduling

    Hi Martin,

    you are right, here we are integrating documents sequentially and do not have more than one service for same type of document sync means only single service is executing all the sales order invoice integration in sequence and all other pending invoices in the queue waiting for their turn, This work well for all over the month but at the end of month it creates problem and take 7 hours extra to sync. We have also planned to develop more than one window service for same type of document processing for parallel sync but I was thinking to change the window service with something new scheduling service which can perform well, We discussed about the SSIS but i don't know it will call web service or handle the exception and responses of the service.

    Your expert guidance required in this case, shall we move from window service to another task scheduling engine and if yes what should we choose or continue with existing system

    Technical details : There is a method in widow service which connect external application DB and loop through all the pending record one by one and call the web service which actually pointing to the ax inbound service and get the response, if it return true than we update the current record with returned document number and process the next document and if we receive false (failure) then we update it in a log table which further stop this document for next processing till necessary action not taken, all the functionality developed in the c#

    Thanks for the suggestion

  • Martin Dráb Profile Picture
    Martin Dráb 230,458 Most Valuable Professional on at
    RE: Best alternate of Window Service for Ax 2012 integration scheduling

    Windows Service is fine (even AX AOS is a Windows Service), the question is what it does and what's the bottleneck. You should look for a solution that addresses this bottleneck; just using something "different" may keep the problem in place.

    For example, maybe you're currently transferring transactions one by one and the problem is the overhead of each message, which can be solved by switching to a smaller number of larger batches. If so, you can modify your current solution or switch to something designed for working with batches. DIXF, which utilizes SSIS under the hood, may be such a solution.

    Or maybe the bottleneck is inside AX and replacing the service with something would make no difference at all. It's just impossible to say without more information.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans