Welcome Guest! Log in

Accessing and visualizing Swagger definition

    Stambia exposed web services are described in an automatically generated Swagger definition file which can be accessed easily from a dedicated URL.

    This Swagger definition is updated automatically by the Runtime when new web services are exposed or updated, and it can moreover be accessed and visualized through Swagger-UI tool which is shipped with the Runtime.

    You can find in this article how to access to Runtime's automatically generated Swagger definition, and how to play with it through Swagger-UI.

    Read more: Accessing and visualizing Swagger definition

    Customizing HTTP Path and Methods on which a delivery can be invoked

      HTTP REST Web services are defined through an HTTP invocation path which will be used as an URL for invoking a given web service.

      They are moreover also defined through an HTTP Method such as POST, GET, PUT, DELETE, ... which are used to differentiate the functional operation which are performed on a given web service, such as creating an item, retrieving information on this item...

      When exposing Stambia Web services, both HTTP Path and HTTP Method on which a delivery can be invoked can be customized.

      This article demonstrates how to configure Processes to customize this.

      Read more: Customizing HTTP Path and Methods on which a delivery can be invoked

      Customizing the Input / Output HTTP Memorization of messages of a Stambia Web Service

        In Runtime Configuration file (engineParameters.xml), it's possible to set the memorization of the messages of a web service.

        This configuration is global for all Processes, as explained in the following article.

        If a Process need different settings, a dedicated meta-inf parameter can be defined to override global behavior.

        Read more: Customizing the Input / Output HTTP Memorization of messages of a Stambia Web Service

        Articles

        Suggest a new Article!