|
An inhouse NT server is the webserver. Dual NIC adapters (one intra, one inter) provides for the AS/400 security. TCP/IP addresses the Internet through ISP connection and CA/400 is used to connect to the AS/400. IP routing is disabled on the NT. Ken Slaugh Programmer/System Analyst Certified Network Administrator MSE Specialist - Client Access/400 > -----Original Message----- > From: Rob Berendt [SMTP:rob@dekko.com] > Sent: Monday, August 09, 1999 11:29 AM > To: MIDRANGE-L@midrange.com > Subject: Re: dataq between NT & AS400 > > Where will your webserver be residing? On the 400 or an intermediate > machine? > Either way, it shouldn't matter which client platform your browser > comes from. > Therefore no need to worry about connecting the dataqueue to NT. > UNLESS the NT is your web server and it will be using dataqueue's to > communicate > with your 400. > > > > > > wayne@redoaktech.com on 08/09/99 01:12:07 PM > Please respond to MIDRANGE-L@midrange.com@Internet > To: MIDRANGE-L@midrange.com@Internet > cc: > Fax to: > Subject: dataq between NT & AS400 > > Good morning, > I have been asked to determine whether it is possible to set up > dataqueues between an NT server and the AS/400. The design requires a > brower at the client to talk to a web server application, which in > turn > will call AS/400 programs. The AS/400 programs will use dataqueues to > converse with the web server. The web application assembles the data > into HTML and passes it along to the browser. > Any help in this area is appreciated. Are there products or tools to > establish and maintain the dataqueue connections? Does anyone know of > products that use this design? Any examples or utilities that I can > use > to piece this together? > Thanks > Wayne > -- > ______________________________________ > Wayne W. Capwell > Red Oak Technologies, Inc. > 11301 Carmel Commons Blvd., Suite 114 > Charlotte, NC 28226 > 704-945-1067 > > Manufacturing...Production...Solutions > http://www.redoaktech.com/ > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.