|
Home > Archive > BizTalk Server General > February 2006 > Sharing a Biztalk system
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 |
Sharing a Biztalk system
|
|
| BizTalk Benjamin 2006-02-21, 5:51 pm |
| Hi,
(I am keeping this separate from my previous post on isolating bts db's so
its easier to track and respond to)
I am now in a fairly large project where we need to share our BTS
development server amongst several teams all doing BTS work. For instance we
have a 'core services' team building some standard orchestrations etc and
other business process teams that use these core services in their BTS
orchestrations (as well as their own stuff that doesnt concern the 'core').
I have two questions
(1) on the application server, would it be a good idea to have different
host instances so that we can take down our host without affecting others?
At run time if some of the other systems orchestrations call out to ours,
would the fact that we were bound to a different host be an issue? What about
production? would it be better to share the same host or maintain this
isolation?
(2) what about the database? should i have an instance for each project or
can they all just use the same set of databases. or, can i just prefix the
databases with a project code so all BTS databases can live in the same
instance? Has anyone tried this?
Thanks in advance,
benjy
| |
| McGeeky 2006-02-21, 5:51 pm |
| Faced with a simlar scenario I would certainly host each team's assemblies
in separate BizTalk instances. However, I don't like the idea of one team's
orchestration directly calling the orchestration of another team. I would
decouple them by putting a web service or file system or MSMQ queue in
between them.
Not sure what you mean in point 2).
--
McGeeky
http://mcgeeky.blogspot.com
"BizTalk Benjamin" <BizTalkBenjamin@discussions.microsoft.com> wrote in
message news:53098324-A7BD-4305-ACC4-12AAD616BE17@microsoft.com...
> Hi,
>
> (I am keeping this separate from my previous post on isolating bts db's so
> its easier to track and respond to)
>
> I am now in a fairly large project where we need to share our BTS
> development server amongst several teams all doing BTS work. For instance
> we
> have a 'core services' team building some standard orchestrations etc and
> other business process teams that use these core services in their BTS
> orchestrations (as well as their own stuff that doesnt concern the
> 'core').
>
> I have two questions
> (1) on the application server, would it be a good idea to have different
> host instances so that we can take down our host without affecting others?
>
> At run time if some of the other systems orchestrations call out to ours,
> would the fact that we were bound to a different host be an issue? What
> about
> production? would it be better to share the same host or maintain this
> isolation?
>
> (2) what about the database? should i have an instance for each project or
> can they all just use the same set of databases. or, can i just prefix the
> databases with a project code so all BTS databases can live in the same
> instance? Has anyone tried this?
>
> Thanks in advance,
> benjy
| |
| BizTalk Benjamin 2006-02-21, 5:51 pm |
| Hi,
Thanks.
In terms of the orchestrations, you're right. Actually they dont connect
directly (or shouldnt). The core services will be exposed as web services
(for example, Customer Lookup Service, Transaction Profile Service etc)
which are consumed by the other orchestrations.
I can see I didnt make point 2 clear at all. I keep my Biztalk databases in
a separate instance from my app databases. In future, i may come to a point
where i had a server running multiple VM's (one for each team) each with a
Biztalk instance. Each instance would need to connect to a set of db's. I was
just wondering if i could share a single instance on the SQL Server for all
db's or if i should have separate instances for each team. In any case i cant
go beyond 8 instances on a single SQL box (and theres the license issue to
consider)
Cheers
Benjy
"McGeeky" wrote:
> Faced with a simlar scenario I would certainly host each team's assemblies
> in separate BizTalk instances. However, I don't like the idea of one team's
> orchestration directly calling the orchestration of another team. I would
> decouple them by putting a web service or file system or MSMQ queue in
> between them.
>
> Not sure what you mean in point 2).
>
> --
> McGeeky
> http://mcgeeky.blogspot.com
>
>
> "BizTalk Benjamin" <BizTalkBenjamin@discussions.microsoft.com> wrote in
> message news:53098324-A7BD-4305-ACC4-12AAD616BE17@microsoft.com...
>
>
>
|
|
|
|
|