Skip to Content

TServerLocation SOAP Receiver Adapter

I have a problem with SOAP Adapter using TServerLocation. I have read all the wikis and posts not finding the problem. When I am passing into the correct TARGET URL statically the communication works perfectly.

When I look into the Dyn Config in the monitoring, the URL is passed through with the mapping correctly:

The Channel is configured like this

But looking into the channel monitoring, the URL is not taken from the Dync Conf, it's picking up the static URL:

Is there anything I have overseen?

Regards

Helmut

Audit.gif (17.2 kB)
monitoring.png (13.1 kB)
Channel.png (3.3 kB)
Channel2.png (5.2 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Dec 10, 2015 at 03:27 PM

    Hi Helmut,

    You should populate value of message attribute TServerLocation with the required target URL somewhere before SOAP adapter is called - most commonly this will be done within mapping. Here is an example of a UDF that performs this (assuming "url" is a String variable holding the required target URL):


    Map map = container.getTransformationParameters();
    DynamicConfiguration conf = (DynamicConfiguration) map.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey asmaSoapUrl = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TServerLocation");
    conf.put(asmaSoapUrl, url);
    
    
    

    You may look at SAP JavaDocs to get some more examples: Generated Documentation (Untitled).

    Regards,

    Vadim

    Add a comment
    10|10000 characters needed characters exceeded

    • Your configuration is fine, it's a bug. I am sure, you must have tried,

      1. Check extra spaces in "TServerLocation"

      2. Provide "TServerLocation" parameter in headername1, headername2 and headername3 ,one by one and simultaneously.

      3. Provide "*" in target url.

      4. Deleting and recreating the channel.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.