Skip to main content

Hi Team,

I am using the following xml snippet (thru postman) to get the response and i get the response from postman. it is working good.

Now the same thing i need to achieve thru FME. Please help me on what transformer to be used? and how can i pass the parameters?

can httpcaller do this? i tried with http caller using GET methos but Response is NULL.

 





<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:test="http://www.synchronoss.com/spatialSUITE/test">
<soap:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>HubTraceB7</wsa:Action>
<wsa:To>http://gisstrm-po-c2p.cable.comcast.com/trainingSTORM/spatialSUITE/v7_1_0/ws-i/HubTraceB7</wsa:To>
</soap:Header>
<soap:Body>
<test:TestRequest>
<test:Action>echo</test:Action>
<test:Parameter>CB10995066|Incoming|CB10995070_1</test:Parameter>
</test:TestRequest>
</soap:Body>
</soap:Envelope>

Hi @fkemminje,

I tried to read using the HttpCaller your link, but is not Works.

How is the link correct that are you using?

Thanks,

Danilo


It looks like you're doing something SOAP-related, which requires a POST rather than a GET. In any case, the HTTPCaller is probably the way to go, so you're on the right track there.

There's a pretty good walk-through on FME and SOAP services here: https://knowledge.safe.com/articles/45314/working-with-soap-services.html

More complex soap interactions can be a bit of a hassle to implement in FME as it can entail a lot of manual work. I've successfully used the Python suds module inside a PythonCaller to make it easier (not easy, but easier...). This may be a starting point for more info: https://webkul.com/blog/python-suds-client/


Hi @fkemminje,

I tried to read using the HttpCaller your link, but is not Works.

How is the link correct that are you using?

Thanks,

Danilo

@Hi Danilo

 

 

 

You are correct , it wont work for you. I am working on client machine remotely.

 

even it is not working for me locally.

Yes, FME can definitely perform the job of a Postman application by making HTTP requests. It has built-in transformers like the HTTPCaller and HTTPClient that allow you to:

  • Send HTTP requests: You can construct requests with various HTTP methods (GET, POST, PUT, DELETE, etc.), specify headers, parameters, and request bodies.
  • Receive and process HTTP responses: FME can parse the response content (JSON, XML, text, etc.) and extract relevant information.
  • Handle authentication: You can use basic authentication, token-based authentication, or other mechanisms to secure your requests.
  • Error handling and retries: FME provides tools to handle potential errors, such as connection failures or server errors, and implement retry logic.

Here are some specific use cases where FME can effectively replace Postman:

  • Automating API interactions: You can create FME workspaces to automate repetitive tasks like fetching data from APIs, submitting data to APIs, or triggering workflows based on API events.
  • Integrating with external systems: FME can seamlessly integrate with various systems and services through their APIs, enabling data exchange and workflow automation.
  • Testing APIs: You can use FME to test API endpoints, validate responses, and identify potential issues.
  • Building data pipelines: FME can create complex data pipelines that involve multiple HTTP requests to different APIs, transforming and filtering data along the way.

By using FME, you can often achieve a higher level of automation, reliability, and scalability compared to manual testing with Postman. FME's powerful data transformation capabilities and integration with other tools and technologies make it a versatile solution for various HTTP-based tasks.


Reply