How to access from fme server to httpCaller ? Because I get rejected my wsdl address that in http caller(post request) ?

Wsdl address is running but it gets rejected in http caller from calling fme server. When I run in fme desktop, http caller is worked. So, please help for this problem

Can you attach a Logger to the rejected port on the HTTP Caller and see what error messages are returned

Thank you for your answer @hkingsbury​ 

I tried logger and these are outputs;

-If I run from fme server, is not updated data. It gets cache data. Logger like this;

-If I run from fme desktop, it is working and gets updated data. Logger like this; -Diffrence is "HTTPCaller_7_<REJECTED> Feature Counter -1 2147680552 (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)"

On the other hand, other diffrence is ;

-I get fme server this error : "XML Parser error: 'Error in input dataset: 'XML-Document-Stream' line: 1 column: 1 message: invalid document structure'"

-The same xml but I didnt get when I run app from fme desktop.

Seems no features are getting Rejected through the rejected port. Attach a logger to the output port as well and see if you're seeing any errors/warnings in the logger output

The logger will write the response body into the log file, you're looking for something like this.

Actually, I added Logger_2 of HttpCaller and Logger_3 of AttributeFileWriter to output ports like warning as you see,

Then, the response body of logger_3 and Logger_2;

So, Logger_3 works before logger_2. I think that it migtht be problem.

http caller is working(it gets updated data) but it works after parsing xml as you see (it save db parse data from old data,so its wrong) . The true way is work httpcaller firstly then it will create file with attributeWriter. So, it gets response old data from attributeFileWriter output. I dont understand "Why?".

-My opinion is AttributeFileWriter is overloaded to httpCaller. Because httpcaller is working and getting new data but it send to old data to database from file.