Building a URL

[Former Member]

The scenario is the following: Siebel sends me data, through XI 3.0 using an iWAY Siebel adapter, to R/3.

I need to provide them with a URL. I built the following URL:

http://xxdmid01:8000/XISOAPAdapter/MessageServlet?channel=:BS_SalesProspects_CreateChange:CC_Siebelt...

where xxdmid01 = XI system name

BS_SalesProspects_CreateChange = Sender(Siebel) business service

CC_SiebeltoSAP_SalesProspects_CreateChange = Sender(Siebel) business service communication channel

Is this URL correct, or how do I build the correct one?

[Former Member]

Hi Dimitri,

Thanks for the reply...

I have used the same URL previously.The message is getting posted into XI without having any problem...

But you are getting authentication problem...Where r u getting this message..? How you triggering the data in Siebel ...?

Thanks & Regards,

Sekhar

[Former Member]

Hi Sekhar,

I get the message(pop-up window) with the following header: connect to xxdmid01(which is our XI box).

The sub-header is: SAP Web Application Server [XXD].

It asks me for a user name and password. It asks for authentication when it tries to come into XI.

I do not know how the data is triggered from Siebel, because the Siebel people do this for me. Do they need to build the authentication(the XI user name and password)into the message that Siebel sends and how do they do this?

I am glad that you have solved your problem.

[Former Member]

Hi Dimitri,

We have to design workflow in the siebel with bussiness service steps.In the final bussiness service step we have to provide the following input arguments..

Requested Method : POST

Requested URL : your URL is correct...

Now using simulator you can trigger the workflow and you can get the data into XI..(This is my case....)

They need not build any authentication in Siebel...

One more question...After getting the Pop window, are you enetring the user name and pwd there ? then r u getting the message in XI or not..?

Thanks ,

Sekhar

[Former Member]

Hi Sekhar,

No, the message is not getting into XI, but I did send your previous message to our Siebel people and asked them to look at the workflow as you mentioned. I will let you know if we have any breakthrough.

[Former Member]

Hi,

The URL you are using is used when you want to make your interface available as a web service. If you are using a third party adapter, you might need to refer to its manual.

If you are using http adapter, url would be something like

http://<hostname>:<port>/sap/xi/adapter_plain?namespace=<namespace>&interface=<interface>&service=<s... user ID>&sap-password=<password>&sap-client=<SAP_Client>&sap-language=<language>

leave blank wherever not applicable.

Hope this helps,

Riyaz

[STALANKI]

chk thz blogs out..for more on webservices/soap adapter

/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi

/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services

[Former Member]

Hi Dimitri,

the url seems to be correct if you are using a SOAP sender adapter:

The general format of the url is:

http://url:port/XISOAPAdapter/MessageServlet?channel=:service:channel

Kind regards,

Heiko

[Former Member]

Hi Heiko,

Thanks for the quick response. No, I am not using a SOAP adapter. I am using an iWAY Siebel adapter over HTTP protocol. I do not know what to replace "XISOAPAdapter" with in the URL??

[Former Member]

Hi Dimitri,

I am also doing the same. I am also facing the problem with URL of HTTP transport protocol of Siebel sender iway Adapter.

Can you please you give inputs if you success.

Thanks,

Sekhar

[Former Member]

Hi Sekhar,

I built the following URL.

http://xxdmid01:8000/sap/xi/adapter_plain?namespace=urn%3ASiebeltoSAP%3ASalesProspects%3ACreateChang...

where xxdmid01 = ServerHost, 8000 = ServerPort, urn:SiebeltoSAP:SalesProspects:CreateChange = SenderNamespace, MI_SiebeltoSAP_SalesProspects_CreateChange = SenderInterface/MessageInterface, SIEBEL_DEV = SenderService, xi_sap = XI SAP user, 250 = ServerClient

I now have an authentication problem, which I need to automate. I have no idea how to do this. I have logged this on OSS.