Re: Running two instances of BizTalk generated code?



Hi Jeff,

What do U mean as "Integration and a QA configuration"?

Anyway try to use two VMs with two BTS for testing.
Why testing a different from production configuration?

--

Regards,

Leonid Ganeline
BizTalk Developer,
Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/

"Jeff Tressler" <JeffTressler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:002A59AD-A6DE-4C8E-ABAD-5C6257A6D9B6@xxxxxxxxxxxxxxxx
Not quite. We have programmed an application that actually contains 11
orchestrations. It processes quite a number of messages. Since I have only
one computer, I have the BizTalk orchestrations deployed to a host
instance
(BizTalkApplicationServer) and both INT and QT send their requests to a
queue
manager MQ queue. Most of these requests us the MsgId/CorrelId processing
so
INT and QT know which response is theirs.

Unfortunatly, some of the messages so not support the MsgId/CorrelId
method
of identification so the INT and QT applications are configured to read
every
message of those types that BizTalk sends. If INT generates a test that
produces 500 messages, both INT and QT processes grab the results so half
go
to INT and half go to QT. It is the exact same message, the same schema,
generated by the same Orchestration. There is nothing in the message to
identify it should go to INT or QT.

In production, there will be only one version of the application code
running, but for now we have INT and QT applications that need support by
a
single BizTalk server. If I could find some way to create two copies of
the
BizTalk code, each could be configured to talk to different queue managers
and thus would only generate the messages its queue manager and thus INT
would grab everything but it would be isolated because it has its own
BizTalk
instance of the code.

And since we are talking configuration mangment, I need to make the fewest
changes possible to generate these two instances since the code tested by
INT
gets promoted to QT. If I have to rename huge number of components to get
them to play well together, that means once INT completes its testing, I
have
to rename, alter Orchesrations, etc before building it for QT and that
kinda
defeats the purpose of the INT environment since QT will be effectivly
testing different code.

Hope that makes more sense.
--
There are 10 kinds of people, those who understand binary and those that
don''''''''t
There''''''''s no place like 127.0.0.1
================================
3.14159 + Ice Cream = Pi ala mode


"Jan Eliasen" wrote:

On Mon, 18 Dec 2006 06:12:00 -0800, Jeff Tressler
<JeffTressler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

We have one computer and one BizTalk licence. Our BizTalk application
reads
requests from a MQSeries queue, processes the response and writes to
another
MQSeries queue. A process reads everything that arrives on that queue. I
need
to find some way to have this BizTalk process running on the same
computer to
support an Integration and a QA configuration. There is nothing about
the
messages that can identify which request came from which (INT or QA) and
each
will attempt to read all messages that arrive on the queue.
I am failing to understand what you are trying to accomplish.

Have I understood it correctly, that you have an orchestration that
can accept and process a specific messagetype, and you need another
orchestration that does the same processing, but on another
messagetype?

In that case, take all the functoinality that must be shared between
those two orchestrations, and put it into another orchestration, that
can be called from other orchestrations. Then, just have two
orchestrations, processing different messagetypes, and bind them to
the same physical receive port. Let them call the common orchestration
that has the shared code. This will work for as many messagetypes you
need it to.

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@xxxxxxxxxx



.



Relevant Pages

  • Re: Running two instances of BizTalk generated code?
    ... compoinent names or changes to orchestrations, I MUST find a way to support ... This WAS is configured to talk to a queue manager running on UNIX. ... our INT and QT WAS applications are currently being fed by a single BizTalk ...
    (microsoft.public.biztalk.general)
  • Re: Running two instances of BizTalk generated code?
    ... Microsoft Certified Technology Specialist: BizTalk Server 2006 ... This WAS is configured to talk to a queue manager running on UNIX. ... So INT and QT are isolated and when one sends a request, ... done all the time but in this case, A and B have the same orchestrations, ...
    (microsoft.public.biztalk.general)
  • Re: Running two instances of BizTalk generated code?
    ... We only have on license to support both INT and QT. ... At this point we have ONE BizTalk license and managment is interpreting this ... I have the BizTalk orchestrations deployed to a host ... manager MQ queue. ...
    (microsoft.public.biztalk.general)
  • Re: Running two instances of BizTalk generated code?
    ... I have the BizTalk orchestrations deployed to a host instance ... manager MQ queue. ... INT and QT know which response is theirs. ... message of those types that BizTalk sends. ...
    (microsoft.public.biztalk.general)
  • Re: Lahman, how ya doing?
    ... Object* recipient; int event_id; ... Timer ... Not relevant to my simulation, but generalizing to a case where any amount of time can pass between when an event is pushed on to the queue and when it is popped off and processed, it seems you can have two identical events going to the same object. ... given tick. ...
    (comp.object)