Liza's Blog

Fresh Tutorial Fixes

We have made a number of corrections to the files contained in Tutorial_update.zip (attached). The corrections to these files should alleviate some of the problems you have had with Tutorials 2 and 3. To use the updated files, you must replace the correct

Tutorial 3 / Lesson 3 / Step 4

On my installation the BizTalk Web Services Publishing Wizard doesn’t appear on the Visual Studio Tools menu, it is available from the “Microsoft BizTalk Server 2006” program group from the Start menu. This posting is provided "AS IS" with no warranties,

Tutorial 3 / Lesson 2 / Step 3

Isn’t it always going to be the case that the B2BSchemas is not visible in the Correlation Properties dialog? If so, I think you should promote the information in the note to appear before the step 6 instruction. This posting is provided "AS IS" with

Tutorial 2 / Lesson 3 / Step 7

The build of B2BSchemas gives a warning: InvoiceToPayment.btm – The destination node “Quantity” is required but the source node “Quantity” is optional. This doesn’t cause a problem but it should probably be mentioned in the documentation. This posting

Tutorial 3 issue

BizTalk Server 2006 Tutorials > Tutorial 3: Invoice and Payment Process > Lesson 3: Connect the B2B Solution to the Supplier Web Service > This tutorial cannot be tested to show the use of correlations. The SendCommomPO_Port must be configured

Tutorial 3 Issue

BizTalk Server 2006 Tutorials > Tutorial 3: Invoice and Payment Process > Lesson 2: Incorporate Correlation > In the step 24 you says: In the tree control Expand Order , click PONumber , and then click Add . But, if you check the schema the correct

Tutorial 3 Issue

BizTalk Server 2006 Tutorials > Tutorial 3: Invoice and Payment Process > Lesson 2: Incorporate Correlation > In the step 24 you says: In the tree control Expand Order , click PONumber , and then click Add . But, if you check the schema the correct

Tutorial 3 issue

BizTalk Server 2006 Tutorials > Tutorial 3: Invoice and Payment Process > Lesson 3: Connect the B2B Solution to the Supplier Web Service > In the previous step I published my orchestrations as Web Services in http://localhost/B2BOrchestrations_proxy

Tutorial 2 issue

Tutorial 2: Purchase Order Process > Lesson 1: Set Up the Supplier Side > Step 2: Enable Web Service Publishing > In this step I create a new Application Pool named TutorialAppPool , but I’ll never use this App Pool to associate with one Virtual

Tutorial 3 issue

**Tutorial Problem found by customer** After following through Tutorial 3, Lesson 3, Step 7 the Test Solution does not work. After dropping the POInstance.xml into C:\tutorial\Filedrop\ReceivePO two files are created in C:\tutorial\Filedrop\FileArchive

Tutorial 1 suggestion

Are you missing use of the ERPPipeline when configuring SendPort_SendToERP between Item 23 and 24? Since the pipeline is made during the tutorial, I assume it should be used somewhere? Text suggestion: Change 23. to: In the FILE Transport Properties dialog

Another for Tutorial 3

I have some feedback regarding Tutorial 3, Lesson3, Step 5 – “Update the Supplier Web Service References”. After Action 2 - “ Double-click B2BSupplierWebService.sln to open it in a new instance of Visual Studio 2005 ”, you may get the error “The application

Typo in Tutorial 3

Tutorial 3, Lesson 3, Step 6, Action 4 there is a small typo in the table. The text reads Use this To do this Host From the drop-down list, select BizTalkServerApplication . ReceivePO_Port From the Receive Ports drop-down list, select ReceivePO_ReceivePort

Tutorial 3, Lesson 3 Issue

(posted to the newsgroups, edited for length and to remove personal information) This is from the SDK tutorials from BizTalk 2006. There have been typos/mistakes in earlier tutorials, so I am wondering if there is a step missing. Some previous typos:

Ambitions of perfection: Continuous improvement

Hi, I'd like to introduce myself. I'm Liza. I am the writer responsible for the BizTalk Server 2006 tutorials. My ambition was to deliver perfect documentation. As you are probably aware (judging by the feedback I continue to receive) I came close, but