How Integration Object works

Hi,

How Integration object is different from httpQuery? I'm trying to create an Integration object to get some data from external system. It is returning some proxy error where as I've got the response when I use httpQuery. Any idea how these functions are working ? what are the core logic behind these two.

 

Thanks in Advance

Ravikumar.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    Hi couple of questions here:

    1. May i know, what version of Appian you are working with?
    2. If you are working with 17.2 or higher then you are not recommended to use httpQuery() function because this was deprecated in Appian v 17.2 and will be removed in future.

    Now, if you have used this, just for the test purpose then this shouldn't be an issue.

    Now coming to your point.

    There are few differences between httpQuery and Integration Object as mention below:

    1. While working with httpQuery() function, you need to write good amount of coding whereas Integration Object provides you this feature using few clicks.

    2. httpQuery() used for invoking read-only web service operations where as Integration Object can be used for various Web-Service Operation depending on our need as well as configure and this can be done just by changing the method and their respective content (Parameters, Headers , Body)

    3. Integration Object allows you to use Connected System Object as well whereas httpQuery() doesn't.

    4. Integration Object provides an feature of Automatic Output Parsing, Error Handling OOTB where as while using httpQuery() we need to write our custom code to do so.

    5. Because Integration Object can use Connected Systems, hence this has increased the capabilities of interacting with various services having different Authentication Mechanism e.g. OAuth

    6. httpQuery can access Third Party Credentials using a!httpAuthenticationBasic() whereas Integration Object cannot, because now the same can be done by using Connected System.

    7. While testing a service, it's easy to segregate the Request vs Response while working with Integration Object


    Now coming to the problem statement which you are facing:

    I believe, this might be because of some mismatch in the configuration. You need to make sure that the configurations (including, Auth Type, Parameters, Headers (if any)) must be same as what you have passed under httpQuery()

    Also, is it possible for you to attach the screenshot of your Integration Object and the httpQuery() so that it will be easy for the practitioner to identify the issue.


    Hope this helps.
  • 0
    Certified Lead Developer
    in reply to aloks0189
    Thanks Alok for the response, keep the differences aside, I would like to know the architecture of these two components. And for some security reasons I couldn't get the screenshots attached here, but there is no configuration issue with Integration object.

    Anyway thanks for your response on this.
  • 0
    Certified Lead Developer
    in reply to V V Ravikumar Lingupanda

    Hi Ravi,

    As per my understanding, if your Integration Object configurations are same as httpQuery then it should work as expected. However if you believe that Integration Object is not working as expected, you can raise a ticket to Appian Support.

    Also, httpQuery() is just a function like the other Appian function which exchanges the data from one system to other system via a valid API Call, hence may i know, what do you mean by "Architecture of this component"?

    It's a function which might be internally using some HTTP Client API such as Apache API which includes some several classes, Interfaces and set of methods to interact with the services e.g. HTTPClient, HTTPGet etc..

  • Hello vvravikumarl857,

    Are you still facing the issue? I recomend you to use SOAP UI, or ARC to first test the service (before coding) by doing that you will be able to figure it out how the HTTP requests should look like and how the HTTP responses are so that way you know how to handle the it in code.

    At high level, as Aloks explained. they are just functions to query an URL by executing an http request, there is not much logic behind it. at the end you have to create the http request and parse the http response.
    The httprequest function required you to write code but now the integration object makes it easier because we have now an screen which you can see as a wizard.

    In the other hand you are asking for the architecture, What exactly are you looking for ? What do you mean with “architecture”? It can be what code is executed, or which java classes get executed.

    Jose
Reply
  • Hello vvravikumarl857,

    Are you still facing the issue? I recomend you to use SOAP UI, or ARC to first test the service (before coding) by doing that you will be able to figure it out how the HTTP requests should look like and how the HTTP responses are so that way you know how to handle the it in code.

    At high level, as Aloks explained. they are just functions to query an URL by executing an http request, there is not much logic behind it. at the end you have to create the http request and parse the http response.
    The httprequest function required you to write code but now the integration object makes it easier because we have now an screen which you can see as a wizard.

    In the other hand you are asking for the architecture, What exactly are you looking for ? What do you mean with “architecture”? It can be what code is executed, or which java classes get executed.

    Jose
Children
No Data