1) So, you can't get a supported port of Apache Web Server unless you
also buy WebSphere? bummer.
2) Writing a CGI in Java is not a good idea except as a toy, since you
would be starting a new JVM for each request. Maybe that is what
IBMLink runs on? :-) Running Java servlets or JSPs under WebSphere or
Tomcat is a much better way to go.
3) IMO, the "MVSDS" sample for IHS is a good way to go for very simple
text-based read access. For more elaborate dataset access, one
approach might be to combine a CGI shell script with either "cp"
commands or our "Dataset Pipes" commands.
Kirk Wolf
Dovetailed Technologies
Timothy Sipples wrote:
John McKown writes:
No. IMWEBSRV is not Apache. There is a separate Apache port
for z/OS. I don't know if it is distributed with the latest z/OS
releases. IMWEBSRV came with z/OS 1.6, but Apache did not.
The last that I know of (may be out of date) is that Apache
must be downloaded and installed separately from z/OS.
What everybody is receiving with z/OS is called the "IBM HTTP Server for
z/OS," and it is Version 5.3. I think it even shipped with OS/390. So, if
you're looking for a "lowest common denominator" capability, i.e. something
everybody should already have, the HTTP Server V5.3 would qualify. This
software is not derived from Apache code.
There are some (earlier) ports of the Apache HTTP Server, available for
download from the Internet as noted previously. IBM doesn't support them,
but they're fun.
IBM is now shipping the "IBM HTTP Server for WebSphere Application Server
for z/OS," which you will also see referred to as "powered by Apache"
(because it is). The current version is 6.1. This HTTP server is orderable
as a PTF for WebSphere Application Server V6.1 for z/OS. Like the rest of
WAS, it is fully supported commercial software from IBM. The documentation
is available online here (watch the wrap):
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/welcome_ihs.html
With all that background out of the way, here's a reply primarily aimed at
the original poster. In addition to the suggestions offered previously,
there are a couple more ideas to consider.
1. WebSphere Application Server for z/OS is getting increasingly common.
CICS Transaction Server runs certain EJBs, just like WebSphere. So one
idea you might consider is to ship an EJB package that works under both WAS
and CICS TS.
2. Another approach is to write Java and package it to work with both the
IBM HTTP Server V5.3 for z/OS (as a CGI program) and WebSphere Application
Server for z/OS. The packaging might be a bit different, but the
underlying logic should be close to 100% identical. That's another way to
offer deployment choices without "forking" your code.
3. I don't think it's any secret that IBM itself has something called the
Integrated Solutions Console (ISC). That's the pretty administrative Web
interface you see embedded in products like WebSphere Application Server
for z/OS. You might ask through the appropriate IBM developer channels to
see if that's a hunk of code you can package with whatever you're shipping
and if it would be a good choice in your case.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
