Discussion:
issue with publish orchestration as web service
(too old to reply)
Siva
16 years ago
Permalink
Hi,

I want to publish orchestration as web service so client can post request
xml to my orchestration. I did the following, however it is not working. I am
not sure what i am doing wrong here.

I created request-response port with public - no limit in orchestration.
Then run the BizTalk web services publishing wizard. I selected the following:

Publish biztalk orchestration as web services.
Then selected the project assemply dll. It selected port for me(i have only
one publis-no limit port).
My input schema doesn't have target namespace. Since i can not leave target
name space blank in web service properties, I put http://samplexmlpoweb.
I left the location as default, selected allow anonymous access to web
service and create biztalk receive location in the following application - to
my project application.

Then,
Binded ports and started the orch. I wrote a sample vb scrip to post xml to
above web service using xmlhttp post. When i run the script it looks like it
is not working. Eeven i couldnt get to the web service from explorer using
http://localhost/samplexmlpo_proxy/<web_server_Name>.asmx. I even browse the
web service from IIS/default web site/. It is not working. I am getting "the
page connot be displayed".

What did i do wrong here? Do i need listen shape or something in
orchestration? How can i test orch-web service?

Thank you in advance,

Siva
--
Thank you,

Siva
Yossi Dahan [MVP]
16 years ago
Permalink
Hi Siva

It seems you have followed the process correctly, so it should work.
Best thing is to check things slowly and carefully until we find what the
problem is; I will try and help.

The main thing to understand is that when you publish a web service -
browsing to that service in a browser, and adding a web reference to it from
other porjeects (which is essentially the same as browsing) does not have
anything to do with BizTalk at this point.

So - you should be able to browse to your recently published web service
regardless of whether your Biztalk server is running or is configured
correclty.
of course you won't be able to submit requetss through BizTalk without the
whole thing being configured correctly, but this is not (yet) your problem.

so - to start with - you need to work on why you can't browse to this
service.
Start with checking the obvious - open IIS manager, find the generated
virtual directory and ASMX file, right click on it and select browse - does
that work?

if not - which Http error are you getting?
--
Yossi Dahan
Connected Systems MVP
http://www.sabratech.co.uk/blogs/yossidahan
...
Siva
16 years ago
Permalink
Thank you for helpping me Yossi,
When I right click on .amsx file from IIS/web sites/default web sites, I am
getting "The page cannot be displayed" error. HTTP 500- internal server error.
Do I have to select my orchestration project for "Location" when I publish
orchestration as web service in wizard?
My acctural biztalk solution is in one folder(D:/Samples) and published web
service is under C:/Inetpub/wwwroot/samplexmpoweb/. Do they have to be in
same folder?
--
Thank you,

Siva
...
Siva
16 years ago
Permalink
Hi Yossi,
I think i fixed the issue. My ASP.NET installation was messed up. I just
reinstall it and i could view the web serivce.
Can I do nomal http post on this web service? It looks like i can not use
orchestration as web service for normal http post.
Client want to send http post without any soap header. Would it be possible
to make a .aspx or web service page to accept response, invoke orchestration
and return response?
--
Thank you,

Siva
...
Yossi Dahan [MVP]
16 years ago
Permalink
Hi Siva

I am glad to hear you have solved your problem.
No - there is no need to have the generated web service and the BizTalk
project at the same place; basically - when you run the wizard - it looks at
your project and extracts the information it needs to create a web service,
which it then "published" to IIS; this project contains all the information
IIS needs in order to submit requests from IIS clients to BizTalk (and return
responses). all the interaction from that point (at runtime) would be against
the deployed BizTalk artifacts; the location of your source code is
irrelevant.

As for your other question - if you publish a web service the only way to
consume it is by following the web service standard - and that requires a
soap envelope and a soap action http header.
if you wish to allow your consumer to provide you with a message through
http post simply create a receive location that uses the HTTP adapter and not
using web services and the SOAP adapter - see some more information here -
http://msdn.microsoft.com/en-us/library/aa577953.aspx

(Mark this reply as an answer if it helps)
--
Yossi Dahan
MVP BizTalk Server
http://www.sabratech.co.uk/blogs/yossidahan
...
Siva
16 years ago
Permalink
I got it. Thank you for your help Yossi.
--
Thank you,

Siva
...
Loading...