sage 300 sdk with node js

can we integrate sage 300 SDK with node js? 

Top Replies

Parents
  • Hi Wahid,

    There are 2 SDKs

    • The Sage 300 SDK is a proprietary SDK that is used by Developer Partner Program members (e.g. third party ISVs) to extend the core Sage 300 Desktop product by creating new modules (Win32/COM DLLs and VB forms), and optionally subclassing existing core modules developed by Sage etc.
    • The Sage 300 Web SDK is an open source SDK that allows Sage 300 Desktop module developers to generate Web UIs etc. for their modules in order to port these modules to Sage 300 Webscreens (Sage's Sage 300 .Net MVC Web Application).

    AFAIA, once a Desktop module is ported to Webscreens, it's business logic (Win32/COM DLLs) is automatically exposed via SData (which is basically ODATA plus some additional rules/contracts devised by Sage) as a series of REST endpoints - Sage refers to this as the Sage 300 Web API. The Sage 300 Webscreens web application includes a Swagger interface (at protocol://servername/Sage300WebApi e.g. https://server/sage300webapi)for endpoint discovery, examples, testing etc.

    Node JS is a server side Web API, so I'm presuming you would like to use Node to integrate with Sage 300 via the Sage 300 Web API. If that's the case, you'll likely want to familiarise with the endpoints exposed by Swagger (at protocol://servername/Sage300WebApi e.g. https://server/sage300webapi) and consult the Sage 300 Web API documentation etc.

Reply
  • Hi Wahid,

    There are 2 SDKs

    • The Sage 300 SDK is a proprietary SDK that is used by Developer Partner Program members (e.g. third party ISVs) to extend the core Sage 300 Desktop product by creating new modules (Win32/COM DLLs and VB forms), and optionally subclassing existing core modules developed by Sage etc.
    • The Sage 300 Web SDK is an open source SDK that allows Sage 300 Desktop module developers to generate Web UIs etc. for their modules in order to port these modules to Sage 300 Webscreens (Sage's Sage 300 .Net MVC Web Application).

    AFAIA, once a Desktop module is ported to Webscreens, it's business logic (Win32/COM DLLs) is automatically exposed via SData (which is basically ODATA plus some additional rules/contracts devised by Sage) as a series of REST endpoints - Sage refers to this as the Sage 300 Web API. The Sage 300 Webscreens web application includes a Swagger interface (at protocol://servername/Sage300WebApi e.g. https://server/sage300webapi)for endpoint discovery, examples, testing etc.

    Node JS is a server side Web API, so I'm presuming you would like to use Node to integrate with Sage 300 via the Sage 300 Web API. If that's the case, you'll likely want to familiarise with the endpoints exposed by Swagger (at protocol://servername/Sage300WebApi e.g. https://server/sage300webapi) and consult the Sage 300 Web API documentation etc.

Children
No Data