How to Use BizTalk 2006 with Windows SharePoint Services 3.0
page 7 of 9
by Arnulfo Wing
Feedback
Average Rating: 
Views (Total / Last 10 Days): 47379/ 105

Deploying BizTalk Orchestration as a Web Service

From the Microsoft BizTalk Server 2006 group, select the BizTalk Web Services Publishing Wizard.  Then select the option to Publish BizTalk Orchestrations.

On the next screen you will be prompted for your project assembly.

Figure 17

Click Next to continue. Keep the defaults on the next screen and select Next. Once you get to the Web Service Properties screen, you will be prompted for the namespace to be used in your web service.

Figure 18

Type: http://BookReview.Demo.Sample/ at this text prompt. Do not forget to put the last "/" at the end. This namespace is NOT the one being used when your document is being submitted to BizTalk; instead, this namespace is mostly used on the WSDL definition.

Now, click Next and you will be at the Web Service Project screen. In here you will specify the name that you want to give to your web service. Select the name of the site that we excluded earlier, bookServices. This is what this screen should look like:

Figure 19

After this screen you will get the Create button, click on it and you will be done with this step. To test that the web service is up and running, you can do the small test of see if IIS will render this site.

In order to tie the WSS and BizTalk, you will need to bind the logical port of the orchestration with the physical ports. This is accomplished by opening the BizTalk 2006 Administration Console. Then open the AW.BookReview application. 

In there, open the Receive Locations and you will see that there is a new location of type SOAP. This location was generated by the Web Service Publishing Wizard we ran before. Now bind your Orchestration ports to the appropriate location. You will only be able to bind Inbound ports to receive ports and outbound ports to send ports.

Figure 20

Notice that we have bound the orchestration logical port to the Web Service receive location. Then bind the outbound logical port of the Orchestration to the Dynamic Soap that will be connected to SharePoint.

Start the Application and it is ready for BizTalk to start processing web services request.


View Entire Article

User Comments

Title: Elaborate the Biztalk Orchestration   
Name: Vaibhav Sali
Date: 2010-11-01 8:42:02 AM
Comment:
Hi,
Please if possible can you give the clear code view of the orchestration..


Thanks
Title: Project Manager   
Name: NAz Sha
Date: 2009-04-17 9:00:47 AM
Comment:
Want more infor on sharepoint and vbiztalk
Title: Elaborate the Biztalk Orch   
Name: PM
Date: 2009-01-26 10:49:37 AM
Comment:
Hi
It would be gr8 if u can elaborate more on each component used in Orchestration and their settings.. Article is gr8 but of little use as the Orch cant be completed without the details.. Pls post the source code for it if its possible
Title: My Thoughts   
Name: Steven Barden
Date: 2007-10-29 11:23:27 AM
Comment:
Congratulations on such a great article!
Title: Want Code   
Name: Jamil Khan
Date: 2007-07-10 12:52:42 PM
Comment:
How can i Find the code of above sample plz tell us. Thank in advance.
Title: Great Article   
Name: Brian Prince
Date: 2007-06-06 4:20:44 PM
Comment:
Arnulfo,
Great article. At first, I thought it was going to talk about how to get the wssv2 adapter to work with wssv3. I am glad to see you aren't doing that, and are using the wssv3 native web services.

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2019 ASPAlliance.com  |  Page Processed at 2019-09-20 8:57:57 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search