Today I worked on a BizTalk project where I have two Orchestrations in one BizTalk Project and I want to publish them as WebService. There are some things to consider when publishing WebServices:
- To publish an orchestration the orchestration's receive porttype has to be public. (Don't make the orchestration itself public)
- If you have already deployed one Orchestration to BizTalk and after that you develop a new orchestration (not deployed), you don't see the second orchestration in the Publishing Wizard's orchestration list. Although you choose the assembly manual from the file system the wizard looks if there is an assembly with the same name and version in the gac. If this is the case he will take the gac assembly.
Redeploy the orchestration and it will work.
- Another interesting behaviour is an invalid generation of the proxy WebService. One of my two orchestrations required an input message that consisted of a root node and one child. (type: string, occourence: 1 to unbounded) The publishing wizard successfully generated my webservice but calling it fails. Opening the solution and building up ends up in an error. (type of the RequestMessage is not found)
I finally found out that everything works fine when I add a further node between the root node and the child string in my input message in the orchestration. After that I started the publishing wizard again and it worked fine.
posted @ Friday, July 27, 2007 6:52 PM