Combine multiple messages into one batch

[ybor...@yahoo.com]

Hello,

Did anyone setup the following scenario in their Ensemble environment?
Online TCP/IP DFT messages received by Ensemble Business Service and
subsequently sent to BP to apply appropriate DTL. Next FTP BO needs to
collect all messages from BP and send them as one batch.

Thanks,

Yuriy

[Matt Simpson]

Yuriy,

You may have thought of this already but to solve the same problem
very simply we sometimes make the BO an HL7 file adapter BO that just
writes the messages to a file on disk (local or otherwise)

Then we add a business service and a second business operation to the
production.

The business service is a standard file service (not HL7) that picks
up the whole file on a schedule and sends it to the 2nd business
operation, a standard ftp bo, which then ftp's it to the destination.


Matt Simpson
Information Systems | Inland Imaging Business Associates

[David Loveluck]

Yuriy

I have a couple of questions.

1. what decides what goes into a particular batch? If it is a time based, then Matt's suggestion is a good one. If there is some other criteria then you may need a BP to gather them together into a list of some type and send them all out.

2. By batch, do you just mean a single FTP file or do you want the BHS segments are well?

dave

David Loveluck
617 225 3122

[yborokhov]

Dave,

1. Yes, it's based on particular time which isn't hard to setup.
Basically activate BO at particular time to handle FTP.
2. It would be a single batch of Fixed Length messages, which again we
have figured it out already (more or less).

The real issue is how to mimic eGate behavior, where outbound FTP
eWay, when activated, reads ALL messages from the Queue and sends them
as one batch. Can Ensemble be directed to do so as well?

Thanks

Yuriy

On Jun 15, 5:01 pm, David Loveluck <David.Lovel...@intersystems.com>
wrote:

[Ryan Hulslander]

Moving from eGate we only really had two interfaces that needed this
so we took the approach that uses both the standard HL7 file adapter
and a couple of cron scripts - which we just leveraged what we already
had.

We set the BO to start and stop on a schedule - which basically
creates a file with a time and datestamp in the name of whatever
messages are waiting in the queue. A cron script that runs offset from
that schedule just FTP's to the target system the files that match the
filename mask. Since the cron script and the cache scheduler use the
same clock we haven't hit a situation where the file is being written
to when we're trying to move/FTP it. We also use access checking in
the cron script to make sure, but in either case we've never tried
grabbing a file that is actively being written to.

The reason this works for us is that we were an eGate shop and our
monitoring tool used the output of the dgcmd to determine if an
interface was running or not - so we have a set of COS classes that
allows us to query all of our Ensemble links to get the same dgcmd
output. The cron scripts we use write output files that mimics the
output of that command, too - so it made life much easier.