|
Home > Archive > BizTalk Server General > February 2004 > source control, versioning with biztalk 2002
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 |
source control, versioning with biztalk 2002
|
|
| derek o'connor 2004-02-12, 8:35 pm |
| Thnaks for all the responses, all great information.
..
I have one other question, mainly concerning deployment.
Basically, how do you guys manage deploying from dev to
test to production? do have scripts, or manually setup on
each server, or do you use a tool, for example Microsoft
Application Center.
..
Also, when you are deploying changes to your environment,
do you replace existing channels or create new ones
leaving the old channel out there.
..
thanks.
derek o'connor.
>-----Original Message-----
>i have just been assigned to a biztalk project to help
>with Configuration Management. Just wondering if anyone
>out there is currently implementing source control,
>versioning with Biztalk 2002. if you can describe your
>processes and tools that would be great.
>..
>thanks.
>derek o'connor.
>.
>
| |
| R.Balaji 2004-02-12, 9:34 pm |
| Hi,
In BizTalk server 2000, we used the BizTalkConfigAssistant.exe. (you can
find it under C:\Program Files\Microsoft BizTalk Server\SDK\Messaging
Samples\BTConfigAssistant)
This will export all port,channel details as a xml file.
We can import this file in the production environment.
Additionally you can generate a VBScript. You can customize the VBScript to
deploy the configuration in the deployment server.
BizTalk 2002 has advanced deployment. I think it is called as BizTalk Seed
Wizard.
I haven't worked with BizTalk Seed Wizard much.
> Also, when you are deploying changes to your environment,
> do you replace existing channels or create new ones
> leaving the old channel out there.
I replace existing channels.
Regards,
R.Balaji
"derek o'connor" <derek.oconnor@emicap.com> wrote in message
news:f8b501c3f211$546d7050$a001280a@phx.gbl...[color=blue]
> Thnaks for all the responses, all great information.
> .
> I have one other question, mainly concerning deployment.
> Basically, how do you guys manage deploying from dev to
> test to production? do have scripts, or manually setup on
> each server, or do you use a tool, for example Microsoft
> Application Center.
> .
> Also, when you are deploying changes to your environment,
> do you replace existing channels or create new ones
> leaving the old channel out there.
> .
> thanks.
> derek o'connor.
>
>
| |
| Nick Malik 2004-02-13, 1:48 am |
| we keep the configuration as small as possible and deploy by hand. I've not
found the BiztalkConfigAssistant to be a reliable tool for deployment.
When we deploy, we don't usually delete all channels and ports and recreate
them, like we would with a code deploy. We set up once and deploy code
repeatedly (to test) and occasionally (to production).
When deploying changes... a change to a port or channel is not a trivial
change. Once done, you shouldn't leave the old channel "out there" because
any number of situatiions could cause Biztalk to push a document through it.
If I can simply change the channel, that is the best. Otherwise, I will
delete the old channel after installing the new one.
Hope this helps,
--- Nick
"derek o'connor" <derek.oconnor@emicap.com> wrote in message
news:f8b501c3f211$546d7050$a001280a@phx.gbl...[color=blue]
> Thnaks for all the responses, all great information.
> .
> I have one other question, mainly concerning deployment.
> Basically, how do you guys manage deploying from dev to
> test to production? do have scripts, or manually setup on
> each server, or do you use a tool, for example Microsoft
> Application Center.
> .
> Also, when you are deploying changes to your environment,
> do you replace existing channels or create new ones
> leaving the old channel out there.
> .
> thanks.
> derek o'connor.
>
>
|
|
|
|
|