×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
PCI compliance might be one good reason.
If you're referring to PCI requirements section 9 - "Cardholder data must
never be stored on a server connected to the Internet" - that doesn't
preclude you from running HTTP servers on a database server. Would anyone
suggest that running QZDASOINIT jobs and ODBC/JDBC interfaces on an IBM i
server are more secure?
No, PCI 9 means storing cardholder data on a network segment which is
different and separate from your Internet IP address. And to make the
interfaces even more secure, you might use an Apache HTTP reverse proxy on
a Linux server, forward traffic to your IBM i HTTP server - which would be
unquestionably PCI compliant.
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.
midrange.com
