combine data from two separate systems

[isabelledc]

We are moving an application from mainframe to a windows-environment (based
on sql-tables).
We now have interfaces on mainframe (xml that gets created) that needs data
from application that remains on mainframe (db2) and new application (sql)
The trigger for sending is now on mainframe but could shift to windows ,
that's still to be decided.
But the fact remains that we still need data ,from both sql and db2 , that
has to be sent to a third system (data combined in one message)

How would/should you do this with biztalk?
Receive data from system1 and in an orchestration , query the second system,
with that response map original message and response to schema of system 3?

Until now we've always routed/mapped data from system 1 to system 2.

In some cases the decision to send the data also needs info from the 2
systems which makes it even more complicated...I don't see how I could do
that...
This would mean...don't route a message based upon data in a second system....

Thank you for your opinion.

Isabelle

[Dan Rosanova]

Is this realtime or scheduled? I think reciving from one system and
calling the other is OK or you could use parallel convoy to do that if
you want as well. You would probably want to use scatter / gather for
that though (meaning you'd need some unique correlation token in the
records). How much data are you talking about?

Kind Regards,
-Dan

[isabelledc]

Dan,

it' not that much data but what I don't really like is the fact that I
receive data from system 1 and have to ask a second system "can i send this"
before I can forward to a third system.... and you don't really know when the
second system will finally say "yes"...so you either have to keep querying
(frequency once/twice a day) or you have to set status on system back to
"send again"
Me I like to receive a message in biztalk , perhaps add some data , but it
has to leave the database as quickly as possible....(otherwise you also have
to keep track if messages aren't staying too long)
I know it's possible using orchestrations and long-running transactions but
it's against my 'biztalk-religion'.... :-)

I'm now looking at using data that system 2 sends to system 3 to also send
to system 1 and store the data there so that the question "can I send" can be
answerred locally before giving the xml to biztalk
(do I make sense here?)

Isabelle

"Dan Rosanova" wrote:

> .
>

[Dan Rosanova]

This does make sense, but it sort of removes the whole service
oriented approach to a solution like this. I too shy away from long
running transactions, so I would have a status in System 1 that let me
reject the change from my BizTalk solution. Then have either a retry
interval or a manual job to clear. If you're not talking that many
records I actually use SharePoint with InfoPath to do this sort of
thing quite a bit. Then someone just works the forms off the
SharePoint form library and they either retry or reject for
permanently.

Does that make sense? BAM would be a good idea for that too, to
audit.

Kind Regards,
-Dan