WESB 6.1. Web Services. Import a Service. Basic HTTP

Hi All I need to invoke a web service on the other company's web server.<br
/>
It has the basick http authentication enabled so we need to provide username and
passwork to start talking to it.<br />
<br />
I know how to do it from the custom java program.<br />
Need to be able to call the service from the mediation flow where all the
mapping is done. Here i do not have control and ability to setup all the needed
values.<br />
<br />
It seems the way to go is <br />
1. do wsdl2java and generate client classes than can be used to call the
service<br />
2. create a class that calls those services and publishes complient
interfaces<br />
3. do java2wsdl and generate a new wsdl for the previous class to be
called<br />
4. use the wsdl(3) to invoke the target service via the interface(2) and client
classes(1)<br />
<br />
Seems a lot of work to just pass through the authentication.<br />
<br />
Do you guys know any other way?<br />
Can my original wsdl be modified to include this username and password
values?<br />
<br />
Thanks heaps in advance.<br />
<br />
Cheers.<br />

You don't need to do all that. Right click on the module and checkout the 
'Deployment editor'. In here you can specify basic auth just like for any 
J2EE application.

-- 
Dan Zrobok -Technical Architect - Perficient
WID/WPS/WESB Blog: http://blog.danzrobok.com


<dwforums@us.ibm.com> wrote in message 
news:633285723.1207901326935.JavaMail.wassrvr@ltsgwas010.sby.ibm.com...
> Hi All I need to invoke a web service on the other company's web 
> server.<br />
> It has the basick http authentication enabled so we need to provide 
> username and passwork to start talking to it.<br />
> <br />
> I know how to do it from the custom java program.<br />
> Need to be able to call the service from the mediation flow where all the 
> mapping is done. Here i do not have control and ability to setup all the 
> needed values.<br />
> <br />
> It seems the way to go is <br />
> 1. do wsdl2java and generate client classes than can be used to call the 
> service<br />
> 2. create a class that calls those services and publishes complient 
> interfaces<br />
> 3. do java2wsdl and generate a new wsdl for the previous class to be 
> called<br />
> 4. use the wsdl(3) to invoke the target service via the interface(2) and 
> client classes(1)<br />
> <br />
> Seems a lot of work to just pass through the authentication.<br />
> <br />
> Do you guys know any other way?<br />
> Can my original wsdl be modified to include this username and password 
> values?<br />
> <br />
> Thanks heaps in advance.<br />
> <br />
> Cheers.<br />
> Boris. 

     Edit



This just means that administrators of WAS will be able to maintain it.



Thanks for you help.



Cheers.