by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
Last week WSE 2.0 Service Pack 1 released to web, coinciding with BizTalk Server 2006’s generally availability in the field. This adapter enables interoperability between BizTalk Server and other applications that require use of WS-Security, WS-SecurityPolicy, WS-SecureConversation, WS-Trust, WS-Policy protocols as implemented in WSE 2.0 protocol stack. This service pack, in particular, allows the WSE 2.0 adapter to work with BizTalk Server 2004 as well as BizTalk Server 2006.
More information on this release can be found on Microsoft.com:
http://www.microsoft.com/biztalk/evaluation/adapter/adapters/wse/default.mspx
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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 box, on the General tab, in the File name box, type %MessageID%.txt, and then click OK.
Change 24. to: In the SendPort_SendToERP – Send Port Properties dialog box, from the Send pipeline drop-down list, select ERPPipeline, and then click OK.
This posting is provided “AS IS” with no warranties, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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 for project ‘http://localhost/B2BSupplierProcessPO’ is not installed. Make sure the application for the project type () is installed.”
I ran into this problem and I have seen it posted in newsgroups too, so it might be worth adding a note about it.
This problem occurs if you have not configured the Visual Web Developer component of Visual Studio to be installed. Reconfigure Visual Studio and the problem is resolved J
This posting is provided “AS IS” with no warranties, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
Tutorial 3, Lesson 3, Step 6, Action 4 there is a small typo in the table. The text reads
The third port should be called ReceiveASN_Port.
This posting is provided “AS IS” with no warranties, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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 no warranties, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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 is provided “AS IS” with no warranties, and confers no rights.
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
I took a lot of your valuable reviewer feedback (thank you, see earlier post) and completed my whitepaper entitled, “Developing a Transactional BizTalk Adapter Using the Microsoft Base Adapter Classes“. You can download it at http://download.microsoft.com/download/3/7/6/376a6f6c-8c97-4ab5-9d5a-416c76793fbb/Transact_Adapter.doc. The paper discusses at a low-level (with code snipets) transactional adapters, the Base Adapter classes and their hierarchy, and additional rarely-documented adapter design issues. So take a look and pass it on to anyone doing adapter development.
After you read it I am very interested in your feedback – please post here if you would. Hope this helps!
Mike
by community-syndication | May 16, 2006 | BizTalk Community Blogs via Syndication
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 to go to http://localhost/B2BSupplierProcessPO/Process.asmx instead of c:\tutorial\filedrop\filearchive\PO%MessageID%.xml.
I think that in Step 1 of Lesson 3 in the section “To configure a port that sends the PO to the supplier’s Web service” I changed the configuration, and I must set the Port Binding to Specify Now. Additional, in the Step 6 of Lesson 3 in the numeral 22 you must remove this section:
SendCommonPO_Port |
From the Send Ports/Send Port Groups drop-down list, select SendCommonPO_SendPort. |
This posting is provided “AS IS” with no warranties, and confers no rights.