Re: Middleware --- polling or triggering

Steve

I'm not sure what Michael is using this for, but the way you use the term "real time transaction" makes it sound like you're wondering if this is done synchronously. By their very nature, messaging products like MQSeries and Oracle/AQ are asynchronous in nature. You can get near real-time (a couple of seconds delay maybe) but not real real-time (if that's not confusing).

Oracle and MQSeries can talk through a number of approaches - Oracle Internet Broker has just been released to do this, there is an AQ-MQ gateway (which is probably what Michael is referring to), or there is a product from Level8 that can do this as well. Alternatively, if there is more complex data transformation that needs to occur, you could use TSI's Mercator product or STC's Datagate (I think).

HTH. Pete

steven_ma_at_my-deja.com wrote:

> Hi Michael,
>
> When you are using MQ Series and Procedural
> Gateway for MQSeries, this is a real time
> transaction, right??
>
> Is Procedural Gateway a client of MQSeries?
> How much is it?
>
> Thanks.
>
> Steve
>
> In article <7qhacj$48r$1_at_nnrp1.deja.com>,
> michael_bialik_at_my-deja.com wrote:
> > Hi.
> >
> > Look at www.quest.com.
> > They have a product that enable off-line copy
> of data
> > between 2 DBs.
> > I wonder what trigger you are going to use if
> no DBLINK is
> > possible between your databases?
> > I used IBM's MQSeries and Oracle MQ
> Procedural Gateway to
> > pass data from one DB to another and back.
> >
> > Good luck. Michael.
> >
> > In article
> <7qh35l$tol$1_at_imsp009a.netvigator.com>,
> > "Ken" <kenchowhk_at_yahoo.com> wrote:
> > > Hi there,
> > >
> > > I am studying which way is the best to
> refresh the DB.
> > > There are two DB and let say A and B, they
> are in
> > > different machine. When the update is done
> on A,
> > > then we need to refresh the corresponding
> table
> > > in B. Now let's assumed that the db_link
> can't be used.
> > > we are just thinking of two approaches
> > >
> > > 1. to set the timer in middleware to
> periodically do the
> > > synchronisation between the two DB.
> > > 2. to setup the trigger in DB A, any update
> in A will be
> > > firing a trigger to update B.
> > >
> > > Is there any whitepaper or document in
> comparing this
> > > two approach ? Should you have any other
> alternatives,
> > > kindly drop a few words also, many thanks.
> > >
> > > Ken
> > >
> > >
> >
> > Sent via Deja.com http://www.deja.com/
> > Share what you know. Learn what you don't.
> >
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.

Received on Wed Sep 08 1999 - 15:48:51 CDT