on 11-17-2011 12:02 PM
Hi experts
i have a scenario
JBoss server -
> SAP XI -
> SAP
i had create the webservice in SAP XI through senderagreement --->publish URL
its automatically generated the WSDL file
URL is like this
1)"http://host:port/dir/wsdl?p=sa/0dacd6e6ede73794b0e9d4814430fced"
but in address location we found another URL
2) https://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=(bussiness component name)&receiverParty=&receiverService=&interface=SI(service interface name)&interfaceNamespace=%3A%2F%%2F (namespace)
we are able to call the wsdl in internet explorer by using first URL
we unable to call the same wsdl using second URL.
why URL were different ?
is it possible to change the first URL format?
i followed the below forums
and i tried what mentioned in above forums but no luck .
if i use the below URL format
http://host:HTTPPort/XISOAPAdapter/MessagingServlet?channel=party:sendersystem:CC_sender
http://host:port /XISOAPAdapter/MessageServlet?senderParty=FP& senderService=FS& interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
it gives the some ssl missing error
please help me out
Thanks In advance
Hi katakoti,
could you send the message sucessfully to PI if you use the first URL which you mentioned?
I am not very clear your problem but give u some input.
when u display WSDL file in ID, use below URL in step 2/5.
if there is a party in ur scenario: http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>
if there is no party in ur scenario: http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
also u can send the message directly into Integration Engine by using below URL.
http://<server>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<Business Component>&Interface=<InterfaceNamespace>%5E<Interface>
in previous, we used SoapUI for the WSDL testing. there is no problem. and i have not seen the URL like ur first one.
regenerate the WSDL file and try again. good luck.:)
Regards,
Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The first URL is the WSDL url. This is used to generate the proxy client on the consumer side.The second one is web service target URL. This is used to invoke the web service on the provider from the consumer.
VJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dont worrry about URLs. You can generate WSDL using sender agreement or classical way going through several steps of giving input values. Both are same.
>is it possible to change the first URL format?
Yes. Use the below URL for the client coding and testing.
http or https://host:port:/XISOAPAdapter/MessageServlet?channel=:senderbusinesscomponent :sendercommunicationchannel
Note if you use https transport protocol then you might have to share your pi certificate to the jboss system so that when they consume your webservice they communicate to pi using the shared certificate at their side. THatswhy you get ssl error. THis ssl error is due to using https communication. The behaviour is usual. Hope that helps.
Note: You can always find WSDL url in the wsdl file at tag element address:location. That is the endpoint URL address. Just follow the above mentioned URL for testing and sharing to the jboss client team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhaskar,
Thanks for replying
how we share the XI certificates to JBoss server ?
please explain process?
i have one more query is it possible to call webservice in a scenario like SAP -
> client proxy -
XI/PI---->SOAP-JBoss
we dont have sender communication channel,sender agreement, how we create the WSDL in this scenario
is it possible webservice creation in XI in this type of scenarios?
Thanks & Reagrds,
kata koti
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.