Connecting to NAS from a Unix Web application

BobBrownBobBrown Member Posts: 17
edited 2006-04-26 in Navision e-Commerce
I need to integrate one of my clients to a Web application using Navision
Application Server. I have been a Navision developer for 11 years, so I
understand the issue from the Navision side of things, but the Web
application is running in a Unix environment and needs to connect with the NAS somehow. Can anyone suggest the most straightforward approach? The Web developers mentioned XML-RPC or SOAP. I would need some fairly explicit instructions since I am not familiar with that environment and obviously the Web developers aren't familiar with Navision.

Comments

  • meymermeymer Member Posts: 7
    BobBrown wrote:
    I need to integrate one of my clients to a Web application using Navision
    Application Server. I have been a Navision developer for 11 years, so I
    understand the issue from the Navision side of things, but the Web
    application is running in a Unix environment and needs to connect with the NAS somehow. Can anyone suggest the most straightforward approach? The Web developers mentioned XML-RPC or SOAP. I would need some fairly explicit instructions since I am not familiar with that environment and obviously the Web developers aren't familiar with Navision.

    Hi,

    first of all: Navision Application Server it self ist stupid. But it has some nice features: as you can read in the manual it is a service an it starts codeunit 1 trigger 99 with a string based parameter. But thats all, the rest is yours...

    In combination with the single instance feature of codeunits and the possibility to declare automation variables using the "withEvents"-feature you now have the possibility to develop a codeunit that waits for events. as you can read in the sdk doc on nav cd there is some com component called ComCom2.dll that can be used as this automation variable with events.

    ComCom2.dll is only an end point for a message based communication bus. MS has implemented three different ways of communication over the message bus: message queues, tcp/ip sockets and named pipes.

    for a communcation with a unix system i would prefer to use tcp/ip sockets over a vpn chanel between the two systems. a concrete implmentation example you will find in the sdk doc on the nav cd.

    the real challenge in this loosly coupled solution is then to implement the logic: wich functions, which parameters and which results are needed to fullfil the business case.

    regards,

    Marco
Sign In or Register to comment.