|
Home > Archive > BizTalk Server General > November 2004 > Confused: Any Send Ports create shortcuts when debugging?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Confused: Any Send Ports create shortcuts when debugging?
|
|
|
| Hello
I am still learning BIZTALK. I am starting to have a few gripes
regarding the need to re create Send Ports as a consequence of
debugging mapping sand orchestrations. This is probably because I am
not very aware of any shortcuts or the proper BIZTALK development
process.
So when I can have a problem in my Mapping schemas ( e.g. SQL database
run time errors because xml mappings do not match SQL Datatypes.) I
seem to have to go through the following process:
a) Disabling Receive Ports, Stopping and Un Enlisting Send Ports
b) Undeployment of my Assemblies
c) Correcting the Bugs in Mappings and Orchestration, and then re
deploying.
e) Recreating all my Send Ports, which is the real nause because of
all the different configuration details.
f) Enlisting and starting the Send ports, and Enabling the Receive
Ports
g) Stopping and re starting my BIZTALK Server, to ensure that it loads
the corrected Assembly.
i) Test Again
This seems a real painful process, especially when I thought the whole
purpose was to enable Business process Analysts to set up and edit
Mappings and Orchestrations, and not involve developers having to redo
lots of port configuration details
So please tell me where I am going wrong.
BTW another gripe is that several of the BIZTALK file paths, are not
supported by standard browsable file path selectors. So I have to be
very careful to get long file [tahs correct first time. It just makes
it much more like hard work !
Many Thanks for any help
Jules
| |
| Nabeel Prior 2004-11-21, 2:46 am |
| Hi Jules,
Re: development process:
There are a number of things you can do to make life a little easier. Here
are some options:
1. Create a bindings file with the biztalk deployment wizard, after you have
set everything up. Then unenlist, undeploy, deploy and import your bindings
file. This works well until you change the number or nature of the ports in
your orchestration.
2. If you know NAnt, read this blog to help you create a script-based
approach to address this:
http://www.traceofthought.net/Perma...23f80fc800.aspx
3. Another approach is that during the development stage of the process, set
the send and receive ports in your orchestration to "Specify Now", and let
the deployment process worry about reconfiguring the ports every time
(although they are created with long assembly-based names). Then, once
development is complete, you can reset these to "Specify Later".
--
Kind Regards,
Nabeel Prior
Web: http://www.brainjar.co.za
Blog: http://www.brainjar.co.za/blog.aspx
"Jules" <Julian.Nospam.Winter@blueyonder.co.uk> wrote in message
news:3i8vp0l93tcruvubf6po7h0gcspspcu5c4@
4ax.com...
> Hello
>
> I am still learning BIZTALK. I am starting to have a few gripes
> regarding the need to re create Send Ports as a consequence of
> debugging mapping sand orchestrations. This is probably because I am
> not very aware of any shortcuts or the proper BIZTALK development
> process.
>
> So when I can have a problem in my Mapping schemas ( e.g. SQL database
> run time errors because xml mappings do not match SQL Datatypes.) I
> seem to have to go through the following process:
>
> a) Disabling Receive Ports, Stopping and Un Enlisting Send Ports
> b) Undeployment of my Assemblies
> c) Correcting the Bugs in Mappings and Orchestration, and then re
> deploying.
> e) Recreating all my Send Ports, which is the real nause because of
> all the different configuration details.
> f) Enlisting and starting the Send ports, and Enabling the Receive
> Ports
> g) Stopping and re starting my BIZTALK Server, to ensure that it loads
> the corrected Assembly.
> i) Test Again
>
> This seems a real painful process, especially when I thought the whole
> purpose was to enable Business process Analysts to set up and edit
> Mappings and Orchestrations, and not involve developers having to redo
> lots of port configuration details
>
> So please tell me where I am going wrong.
>
> BTW another gripe is that several of the BIZTALK file paths, are not
> supported by standard browsable file path selectors. So I have to be
> very careful to get long file [tahs correct first time. It just makes
> it much more like hard work !
>
> Many Thanks for any help
>
> Jules
|
|
|
|
|