by eliasen
9. april 2007 21:27
Hi
When using the SQL Adapter wizard to generate schemas for updategrams, queries or calling stored procedures, the wizard will create an orhestration and a schema for you in your project. The orchestration is named BizTalk Orchestration.odx (or if this allready exists, then it will add _1, _2 and so on) and the xsd will be called SQLService_<chosen_rootnode_in_wizard>.xsd
These names are of course not useful in most scenarios, since most projects have naming conventions that must be followed. Moreover, the orchestration is often just annoying, since the database read/update usually must happen in an allready existing orchestration.
What you should do is this:
- Rename the xsd to follow your naming conventions
- Rename the typename of the schema to match the filename
- Open the automatically created orchestration, and:
- Update the parts of the two created multi-part messages to point to the new typename of the schema
- Rename the port type that is created to something meaningful
- Rename the multi-part message types that are created to be more meaningful.
- The last two steps are very important, if you plan to use the SQL Adapter more than once in the same orchestration, since otherwise you will get type names in both generated orchestrations that are the same. And this isn't allowed, off course.
- Cut and paste the port type and multi-part message types from BizTalk Orchestration.odx to the orchestration where you actually need them.
- Delete the BizTalk Orchestration.odx file, since it is no longer needed.
So basically, the automatically created names of things when using the SQL Adapter Wizard are useless. And also, the created orchestration is useless after moving the automatically created types away from it.
I hope this is useful for someone at some point.
--
eliasen
c7b8bd02-3db6-4870-b5a2-9e70f2ab0ca9|0|.0
Tags:
BizTalk 2006