URL too long for TServerLocation

[Former Member]

Im trying to pass the target server URL to the TServerLocation parameter in the Dynamic configuration of

SOAP adapter but its says its too long the permitted length is 200 characters but my url is dynamic and

url lengths can range frpm 200-250 characters.

DynamicConfigurationKey key = DynamicConfigurationKey.create(temp, "TServerLocation");

String varURL ="http:/xidr3.bcs.de:50000/XISOAPAdapter/MessageServlet?channel=:Routing2_Service:SS_SOAP_Sender_Working_June12&version=3.0&Interface=http%3A%2F%2Fbasf-corp.com%2Fxi%2Fnafta%2Fplayground%5ERouting2_OB&nosoap=true";

So im getting a mapping exception bcos of this. Can anyone give me some suggestions for this?

Is Variable transport binding(using XHeaderName1) anywhere useful to resolve this?

[Former Member · Accepted solution]

If you enter only

String varURL ="http:/xidr3.bcs.de:50000/XISOAPAdapter/MessageServlet?channel=:Routing2_Service:SS_SOAP_Sender_Working_June12

URL still it will work ... try it out...

Gaurav Jain

Reward Points if answer is helpful

[Former Member]

Hi,

I think Variable transport binding(using XHeaderName1) will not be of any help here. I guess you cannot pass a URL(Dynamic URL) more than 200 characters as http tries to do get method for posting the data.

Thanks

Amit

Reward points if helpful

[Former Member]

Actually the problem is im using interface overriding , so i have to pass the interface namespace and interface name in the target URL so that it overrides the default values in the Sender SOAP adapter.

is there any other method to do this??

[Former Member]

Hi,

i am little confused here. Why do you need to have dynamic URL set up when you are using SOAP Sender Adapter ? All the things which is mentioned above holds good for Receiver SOAP Adapter. For sending Dynamic URL the web client(3rd Party) application should take care of this.

Can you please clarify?

Thanks

Amit

[Former Member]

Hi Amit,

My scenrio is like this

i have a SOAP -File scenario in XI which is going to act like a Webservice.

i have to trigger this webservice from another scenario File-SOAP scenario.

In the SOAP sender adapter there are default values for interface namespace and name, i want to override this with my own interface name and namespace which can be done by using the following method.... FAQ from SAP note:

+Can I set the interface name dynamically from the client?

Yes. You can overwrite these XI parameters from the client. To activate this overwriting mode, you need to turn on option "Use Encoded Header" and "Use Query String" in the channel. Then your client can append the interface name using parameter Interface.

For example, interface namespace http://sap. com/test and interface Test can be represented by the url-encoded form of http://sap.com/test^Test as in

#&version=3.0&Interface=http%3A%2F%2Fsap. com%2Ftest%5ETest+

So my target URL in the SOAP receiver adapter is like this

http:/Server:port/XISOAPAdapter/MessageServlet?

channel=:Routing2_Service:NA_SOAP_SND_Routing2_Service_Routing2&version=3.0&Interface=http%

3A%2F%2Fbasf-corp.com%2Fxi%2Fnafta%2Fplayground%5ERouting2_OB

This URL works fine if given in the SOAP receiver adapter. But if given in the Dynamic configuration parameter TServerLocation i get a mapping exception saying the string is too long....

i have no choice i cannot shorten the length of the URL....Is there any other work around to solve this?

Pls give your valuable inputs

Shakthi

[Former Member]

Hi,

I don't think that there is a way around this.

Your scenario looks like to be File-File only. Not sure why are you using SOAP in between.

As pe my understanding your scenario is

File -> SOAP(WS Exposed by XI only)

SOAP(WS exposed by XI only again) -> File

Pls correct me if I am wrong.

Thanks

Amit

[Former Member]

Actually the File is just for testing purpose, in real time its like 2 services, one a Routing service

(Now configured like a File-SOAP) that will route documents according to the Interface name to respective Webservices(SOAP-File).