07-14-04 10:50 PM
Larry,
Thanks for the information!
--
Jeff Lynch
"A BizTalk Enthusiast"
http://dotnetjunkies.com/WebLog/jlynch/
""larry franks"" <larryfr@online.microsoft.com> wrote in message
news:%23FVb8scaEHA.2752@cpmsftngxa06.phx.gbl...
> There shouldn't be a need to unenlist/re-enlist. It looks like all that
is
> needed is to stop/restart the host instance that the adapter the ports use
> lives in. So for file ports, stop/restart whatever host instance the file
> adapter is bound to.
> But, if you are using a custom pipeline then you will need to
> unenlist/re-enlist the port and reselect the pipeline.
>
> Larry Franks
>
> This posting is provided "AS IS" with no warranties,and confers no rights.
> Subscribe at
>
http://support.microsoft.com/defaul...msdn/nospam.asp
> &SD=msdn
> --------------------
> | From: "Jeff Lynch" <jeff.lynch@houston-lynch.com>
> | References: <OGfovW6ZEHA.3016@tk2msftngp13.phx.gbl>
> <TDk2GkFaEHA.2924@cpmsftngxa06.phx.gbl>
> | Subject: Re: Schema/Map Best Practice Question
> | Date: Mon, 12 Jul 2004 21:07:01 -0500
> | Lines: 86
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> | Message-ID: <#PTbX4HaEHA.3508@TK2MSFTNGP09.phx.gbl>
> | Newsgroups: microsoft.public.biztalk.server
> | NNTP-Posting-Host: cs24160104-76.houston.rr.com 24.160.104.76
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.server:9875
> | X-Tomcat-NG: microsoft.public.biztalk.server
> |
> | Larry,
> |
> | Nice to hear from you again! Thanks for the best practice clarification.
> Let
> | me know when you hear something about unenlisting/re-enlisting ports
when
> a
> | schema or map changes in the "global" schema assembly.
> |
> | --
> | Jeff Lynch
> | "A BizTalk Enthusiast"
> | http://dotnetjunkies.com/WebLog/jlynch/
> |
> |
> | ""larry franks"" <larryfr@online.microsoft.com> wrote in message
> | news:TDk2GkFaEHA.2924@cpmsftngxa06.phx.gbl...
> | > It's usually better to keep your schemas in a seperate assembly than
> your
> | > orchestrations. The big reason for this is that we globally look
> through
> | > all the deployed assemblies for schemas when we are processing
> documents.
> | > If we find multiple schemas with the same namespace/root then you'll
get
> | an
> | > error if the document matches them. We expect the namespace/root
> element
> | > to be unique among all schemas in all deployed assemblies. So keeping
> | them
> | > in one place and referencing them elsewhere lets us make sure it's
only
> | > deployed in one place.
> | >
> | > Now if you know the schema is only going to be used for the one
project
> | and
> | > never again, you can keep it in the assmebly with the orchestration.
> But
> | > anything that's reusable should be in a "schema" assembly.
> | >
> | > As to unenlisting/re-enlisting ports, I haven't tested this but I
> believe
> | > you would only need to do this to the ones that were effected by the
> | > change. I'll try to find the official word on this and post here.
> | >
> | > Larry Franks
> | >
> | > This posting is provided "AS IS" with no warranties,and confers no
> rights.
> | > Subscribe at
> | >
> |
>
http://support.microsoft.com/defaul...msdn/nospam.asp
> | > &SD=msdn
> | > --------------------
> | > | From: "Jeff Lynch" <jeff.lynch@houston-lynch.com>
> | > | Subject: Schema/Map Best Practice Question
> | > | Date: Sun, 11 Jul 2004 19:17:58 -0500
> | > | Lines: 18
> | > | X-Priority: 3
> | > | X-MSMail-Priority: Normal
> | > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> | > | Message-ID: <OGfovW6ZEHA.3016@tk2msftngp13.phx.gbl>
> | > | Newsgroups: microsoft.public.biztalk.server
> | > | NNTP-Posting-Host: cs24160104-76.houston.rr.com 24.160.104.76
> | > | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
> | > | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.server:9855
> | > | X-Tomcat-NG: microsoft.public.biztalk.server
> | > |
> | > | I'm currently working on several related BTS2004 solutions at the
same
> | > time
> | > | (migrating from BTS2002, new integrations, etc.) and I'm trying to
> | > determine
> | > | the "best practice" for creating new schemas and maps for several
> | > different
> | > | but related integrations.
> | > |
> | > | Should ALL schemas and maps for a BTS2004 installation be in the
same
> | > | assembly or should the schemas and maps for each individual
> | "integration"
> | > be
> | > | in their own assembly? If they are all in the same assembly (such as
> | > | CompanyName.BizTalk.Schemas.dll) and one schema or map changes, do I
> | have
> | > to
> | > | unenlist / enlist ALL ports or just the ports affected by the
change?
> | > |
> | > | Any "best practices" comments / suggestions?
> | > |
> | > | --
> | > | Jeff Lynch
> | > | "A BizTalk Enthusiast"
> | > |
> | > |
> | > |
> | >
> |
> |
> |
>
[ Post a follow-up to this message ]
| 
