Hi,
You might recall discussions, some time back, of how I had developed my
own
client/server middleware product called Tier3 and how I was busy
incor****ating "hotTIP" a Transaction Internet Protocol (TIP) compliant
Transaction Manager for VMS. Well, these products are now complete, tested
and even have comprehensive documentation to go with them. What I need
from
you is someone to beta-test and evaluate them.
I won't bore you here with renewed claims of how Tier3 and hotTIP will
breathe new life into VMS as a server platform; I hold these truths to be
self-evident. Just ask your Application Developers, DBAs and/or
Windows2000
System Integrators to glance through the "Tier3 Client/Server Development"
manual (all of 60 pages) and it will be like someone switching a light on
after all these years of darkness!
So please get in touch if you can at least spend the time to look through
the documentation. If you feel that you may be able to allocate the
resources necessary for a serious evaluation of Tier3, then I will mail
you
a copy of the installation kit ASAP (Zipped up on Alpha it's only 1500
blocks). In all sincerity, for everyone with even the slightest interest
in
the longevity of VMS as a development platform, whether at your specific
company or in the world at large, I can promise you that this document is
well worth the read and that you will not be disappointed. (Let me know if
you'd prefer a PDF or a Word version of the document.)
Just to let you know, I'm taking the family back to Perth WA next month
after a bit of touring/bomb-dodging, so if you can scope your expressions
of
interest for the next two-weeks that would be just peachy. (Sup****t from
the
beaches in the Mauritius will be limited :-)
Once I'm back in Oz I'll have the facilities, resources and infrastructure
to sup****t the product properly. (Who knows? If enough people get on to
their VMS or Rdb reps and tell them how much they need this product then
maybe they'll do something sensible like push Tier3 instead of
Bridgeworks?)
Cheers Richard Maher
----------------------------------------------------------------------------
-----------------------------
For those who don't remember, here's a brief functional overview of
hotTIP: -
hotTIP allows any DECdtm controlled Resource Manager, such as Rdb, to
participate in a distributed transaction with a cooperating process,
controlled by MTS/DTC on a Windows2000 environment, with the full ACID
properties of a true 2PC transaction, regardless of the middleware product
of choice! In case you are unaware, the beauty of TIP's "Two-Pipe"
strategy
is it's application-pipe (or middleware) neutrality. Whereas most XA
implementations mandate homogenous Transaction Monitor deployments (such
as
Tuxedo everywhere, Encina everywhere, MQSeries everywhere, ACMSxp
everywhere
and so on . . .), hotTIP from TIER3 Software gives you complete freedom
to
choose the middleware product(s) that best suite your particular
application
and heterogeneous network needs.
Would you like to talk to VMS with TIER3 Sockets, COM or DCE/RPC? BEA
MessageQ, IBM MQSeries or HTML? The choice is yours and yours alone. But
once you realize that you need to encase your critical transactions within
the ACID properties of a true Heterogeneous Two-Phase Commit then you will
come to the conclusion that you need a Transaction Manager that looks a
lot
like this. Another drawback of traditional "One-Pipe" strategies is that
they preclude the run-time determination of transaction participants.
(Functionality which may be advantageous in a wide-area or Internet based
application.)
"Richard Maher" <maher_rj@[EMAIL PROTECTED]
> wrote in message news:...
> Hi,
>
> I am seeking the help of volunteers to test some software that I've
> developed which facilitates distributed two-phase commit transactions,
> encompassing any resource manager (e.g. SQL/Server or Oracle) controlled
by
> Microsoft's Distributed Transaction Coordinator in a Windows2000
> environment, with any resource manager under the control of DECdtm (e.g.
Rdb
> (or Oracle via the XA Veneer)) in a VMS environment.
>
> [Yes, at some stage, I hope to sell this software and make money out of
it,
> so unless you have a large philanthropic streak or are simply a techie
who
> likes to stay on top of Windows<->VMS connectivity issues, then you may
wish
> to look away now. But if you do choose to participate, then rest assured
> that I have no interest in your personal or company details. (Just your
> work-rate :-)]
>
> What differentiates my Transaction Manager software from existing
> Transaction Monitor packages that are already in the marketplace (and
why
> you should be interested) is that it is based on the Transaction
Internet
> Protocol TIP standard. (RFC 2372) For those of you who don't know, the
> beauty of TIP's "Two-Pipe" strategy is it's application-pipe (or
middleware)
> neutrality. Whereas most XA implementations mandate homogenous
Transaction
> Monitor deployments (such as Tuxedo everywhere, Encina everywhere,
MQSeries
> everywhere, ACMSxp everywhere and so on . . .), hotTIP from TIER3
Software
> gives you complete freedom to choose the middleware product(s) that best
> suite your particular application and heterogeneous network needs.
>
> Would you like to talk to VMS with TIER3 Sockets, COM or DCE/RPC? BEA
> MessageQ, IBM MQSeries or HTML? The choice is yours and yours alone. But
> once you realize that you need to encase your critical transactions
within
> the ACID properties of a true Heterogeneous Two-Phase Commit then you
will
> come to the conclusion that you need a Transaction Manager that looks a
lot
> like this.
>
> Another drawback of traditional "One-Pipe" strategies is that they
preclude
> the run-time determination of transaction participants. (Functionality
> which may be advantageous in a wide-area or Internet based application.)
>
> Anyway, this is what I have: -
>
> On the Windows side, you need absolutely *NO* additional software! I'll
> reply to this note with a brief description of the COM+ and DTC
functions
> that you would need to invoke in order to successfully push a MTS/DTC
> transaction to VMS. NB: These are standard Windows APIs that are fully
> documented on MSDN.
>
> On the VMS side, I have a VMSINSTAL saveset that (all zipped up) is some
> 150KB that I'm happy to e-mail to you along similar lines to the VMS
> hobbyists (non-commercial use) license. I'll reply to this note with an
> Internet Daemon (INETd) example of code that uses my software to cede
> transactional control, over an SQL insert into a Rdb database, to
MTS/DTC.
> It's under 500 lines long and contains all of the DCL, 3GL, SQL required
to
> produce a working example of a TIP-2PC capable TCP/IP auxiliary server.
This
> example will insert a row into the MF_PERSONNEL.Employees table on the
VMS
> side in co-operation with Windows2000 MTS/DTC client that is inserting a
row
> into the NORTHWIND.Employee table. Commit them all or roll them all
back.
>
> So, in summary, If you'd like to volunteer to put hotTIP through it's
paces
> then simply reply to this mail.
>
> Regards Richard Maher
>
|
