European Experts Exchange (EEE.org) :: Free Experts PHP MySql Oracle Microsoft Web SQL Delphi


Languages :: Java :: Application Architecture Web/Desktop Application/Main Frame Process
By: JasonMarsh	Date: 02/10/2003 00:00:00	Points: 300	Status: Answered Quality : Excellent
Okay Experts I have a new application that I must write that incorporates a variety of different platforms and systems that must communicate seamlessly together. What I need are some ideas (other than what's floating around in my head) about how exactly this could be accomplished. At a remote location processors will be entering data into a mainframe system. When the processor is done entering X amount of data, they will need to fire off a process that runs locally at my location. Okay, the summary doesn't seem to difficult yet. However, said processor must fire off this application on our end and pass a username and password so our application can log into the mainframe system with their login (client security necessity). Our process, logs into the mainframe system and "automates" a great deal of processing on the backend system. The client states that user name and password cannot be stored in any fashion (i.e. database, ini, registry, etc.) and that the user must initiate the process. There may, however, be 10 processors who want to fire this process at the same or overlapping times. So... this process will need to fire multiple instances of this program processing only the information for this individual. Another thing to add is that each time a user enters whatever it is that they enter, an xml file is created for the "transaction". Our process, upon their intiation, must remotely grab (at this point unknown how this will take place exactly) the files associated to this individual, store them in a local database location, log into the system with their login information, the process the "transactions". Another note to add is the application on our end is a Windows-based application. My thoughts (as well as some others here) are the remote user will have an ASP/ASP.NET page that they fire off the application from. They will enter their username and password and hit a button, more or less. Our application (existing on a different server from the web server) must know when this action has taken place, gather the necessary remote files, fire our application with their security, and process. My questions are how do we get this user name and password passed to the command line (or somewhere else) to fire this process on our side without ever storing it? Our typical processes are fired off based on a scheduler. This obvious cannot be used because the username / password would have to be stored at some point. I'm just looking for ideas and insight here... Thank you.
By: VGR	Date: 02/10/2003 07:12:00		Type : Comment
I woud use a PHP page hosted on YOUR webserver, so that the client using any browser may trigger YOUR process on YOUR server The "multiple instances of the process" is resolved by the multiple sessions that will be open on the webserver, all indepedent from each other. Moreover, I would also do your processing using PHP, so that the user info (password etc) isn't stored anywhere. Else,I would use some kind of DB and store encrypted user data ; then your sheduler can from tiem to time check that DB and react.

By: JasonMarsh	Date: 03/10/2003 23:21:00		Type : Comment
What Microsoft equivalents are there to PHP? Our office is a mostly a Microsoft shop with the occasional Cold Fusion thrown in there.

By: VGR	Date: 03/10/2003 23:58:00		Type : Answer
ASP (1.2 times slower than PHP and less readable/portable/used) ASP.Net (slower than Zend-equivalently-compiled PHP) why shy to use PHP ? I used it in IBM and we replaced Net.Data scripts accessing a DB2 database with PHP scripts accessing a MySql one... MySql : free [or almost] PHP : free ASP : ? SQL-Server : costly Apache : free IIS : crap PHP : cross-platform MySql : cross-platform SQL-Server : Win32 only, slower, less compliant with SQL standard ASP : Win32 only Apache : cross-platform IIS : Win32 only

By: JasonMarsh	Date: 06/10/2003 23:36:00		Type : Comment
The reason for using existing technologies is because it's company mandated. SQL Server is the only database backend we use. All other web applications we use have been in Cold Fusion or ASP. Our web server is already IIS and I would be unable to pursuade otherwise.

By: VGR	Date: 07/10/2003 00:08:00		Type : Comment
You asked, I answered ;-)

Do register to be able to answer

©2010 These pages are served without commercial sponsorship. (No popup ads, etc...). Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE.
Please DO link to this page! Post to Plurk Post to Yahoo Buzz Post to Delicious Post to Digg Post to MySpace Post to Ping.fm Post to Reddit Post to StumbleUpon

Contact

page generated in 118.947980 milliseconds

Why Google AdSense ads ?

New Improved Search!