Accessing Windows Functionality from NonStop Systems
Several years ago we began exploring how we might make functionality that was readily available on Windows™ platforms available to NonStop applications. We looked at porting some of them to the NonStop. We have been able to do that to a very small number of tools, like an HTTP server and email client. Most of the other tools were either proprietary or need features that were not possible on NonStop.
We began by looking at how most applications might want to use these functions and which were the most needed. We identified PGP encryption and PDF conversion as the top two. These two functions are available on the Windows platforms and are also very, very inexpensive (like free!). In most cases existing and new NonStop applications wanted to use these functions as if they were standard NonStop serverclasses.
This was the history of how TelePath came to be. We wanted to have a NonStop program, running as a serverclass, that would allow applications to simply do a Serverclass_Send or WRITEREAD sending instructions on what is to be done and, optionally include files to be processed. The reply could also point to files that returned.
TelePath Architecture
Utilizing experience we had with Server Object Gateway (SOG), we built two primary components. The first was a serverclass, TREMSVR, that would receive the requests and send them, via TCP/IP to a Windows server. The second, TeleRemotePC, was a Windows application that would process the request and perform whatever operation was wanted. We also wanted to provide at least some of the Tandem/NonStop fundamentals. Not only can there be multiple instances of TREMSVR, but each TREMSVR process can communicate with multiple TeleRemotePC programs.
TelePath in Production
TelePath has been robustly providing a wide variety of Windows functionality for many years with a growing number of customers. Look for an upcoming Whitepaper which will provide more technical details of TelePath or request More Info about this product.
