using biztalk web service - golddo

01-Jun-07 01:04:01
A couple questions at the end about publishing/using web service in BizTalk.

My requirements seem super-simple: create a web service which will receive
an XML document and FTP it somewhere.

So, I created a project with a simple orchestration.  After deploying it to
my local area, initially configured the receive port to use a FILE adapter,
and the send port to use FTP, worked great.

Used the web services publishing wizard to expose my orchestration, then
configured the receive location to use SOAP.  I see the things BizTalk
generates in C:\Inetpub\wwwroot\<application name>, and when I hit
localhost/<application name> in a browser, the index page shows the .asmx
file as an available web service.

The thing I don't understand is if I hit the link to the .asmx (or try to
add a web reference in a project, which I understand to be the way I'll test
this), I get a 404 page.  I mean either trying to browse to .asmx in IE or
the "Add Web Reference" wizard.

We turned on directory browsing in IIS, and it shows the name of the .asmx
file just fine, but clicking that results in 404 as well.

Questions
1) Anyone have an idea what I'm doing wrong, not being able to "see" the web
service?

2) Does this sound about right for an approach?  What I think I need to do
to test is set up some test project which has a web reference to my web
service, which will create a proxy to the web service.  I'll read in my xml
document, figure out how the web service interface works, and shoot the
document over there in that manner.

Thanks a lot to anyone who has input.
button
 
 

using biztalk web service - Saravana Kumar

01-Jun-07 01:25:55
Have you configured the webserver for asp .net. Its not recognizing your
.asmx file extension. I guess you haven't installed it in the webserver.

you can install asp.net by running aspnet_regiis -i in the visual studio
command prompt.

Once you get past this situation, then you need to configure IIS to use
application pool with the user name who is part of biztalk isolated user
group and IIS WPG group.

Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]
button
 

using biztalk web service - golddo

01-Jun-07 04:09:01
Thank you for the response.  No luck so far (I think), but something
different, so maybe progress?

Installed asp.net, no worries.

What I took the last paragraph to mean is that I needed to have the user
running the pool in which my web service resides to be someone who is in the
group of the BizTalkServerIsolatedHost.

First I created a new app pool for this web service, and changed the
application settings to run in this BizTalkWebServices pool.

The isolated host instance (Hosts under Platform Settings in admin) reveals
the group to be our developers group.  So, I then set the username for the
new app pool (Identity tab) to my user and password.

Trying to hit the asmx file via browser now gives me "Service Unavailable"
instead of 404.  I'm off to google around on that.
button
 

using biztalk web service - Saravana Kumar

01-Jun-07 04:43:02
The user you configured in the application pool (from your post its your
user name) must be part of IIS_WPG NT group (so add your username to iis_wpg
group).


Open "properties" window of the virtual directory inside IIS, and select
ASP.NET tab check the .NET version is selected. Sometime nothing will be
selected from the combo.

Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]
button
 

using biztalk web service - golddo

01-Jun-07 05:51:01
Yes, thanks.   In case anyone else reads this for help, there was another
setting.  Saravana probably said this and I just didn't understand.

In the IIS "Web Service Extensions" tab, ASP.NET v2.0.50727 was prohibited
and needed to be allowed.

If I understand our senior people correctly, that's a default setting on
server 2003 which we had to turn on.

Although a 403 (permission denied) error rather than 404 (not found)
might've been more helpful.

Thanks a lot, Saravana.  I sincerely appreciate you extending my knowledge.

Now off to code a test application to hit this service.
button
 
Newbie problem removing Biztalk Application