[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Apache configuration
Vince,
what program do you get the message in - the HTTPAPI program that makes
the request�
or the�CGI program that makes the response to the HTTPAPI request?
On Tue, Apr 24, 2012 at 9:51 PM, Julius Kaj <[1]Kaj.Julius@xxxxxx>
wrote:
Hi Vince,
I don't know anything about how to set up a web service and what
Apache configuration entries are needed.
However, I know there are a lot of knowledgeable people in that
field over in the easy400 list. I'm sure they'll be very willing to
help out.
In your initial post you wrote that your old test web service was a
CGI program (or so I gather from the URL specifying a directory
named /cgibin), so it would be a good guess that you (or someone
else) developed it using the CGIDEV2 service program.
[2]www.easy400.net is devoted to promoting the use of CGIDEV2
(primarily for generating normal dynamic web pages to be shown in
web browsers, but increasingly also for use in the web service
field) and Giovanni Perotti and other participants in the easy400
list have shown that they know how to set up the Apache
configuration on other occasions.
I'm sure that once you tell them what your web service program is
called (I'd guess VESCL.PGM), where it's located (library) and how
it's called (what URL to use -- I'd guess
[3]http://sysName:14444/cgibin/vescl) they'll be able to tell you
what is needed with regards to the Apache configuration for it to
work.
In essence from an Apache point of view there's no real difference
if the CGI program works as a web service returning XML or if it
works as a dynamic web page returning HTML.
NB! If you haven't already signed up for the easy400 list, you can
do so from the easy400 site.
FWIW, this is from the FAQ on the Easy400 site:
How to implement an Apache HTTP configuration for CGI?
[4]http://www.easy400.net/cgidev2o/faq39.htm?ts=0.18315931829076781
Who knows, maybe this all you need to know. :-)
Best of luck!
Regards,
Kaj
-----Oprindelig meddelelse-----
Fra: [5]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[6]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] På vegne af
Selders, Vince E
Sendt: 24. april 2012 19:20
Til: HTTPAPI and FTPAPI Projects
Emne: RE: Apache configuration
Thanks for the info. �I probably will drop this like a hot potato. �I
don't have the authorities I need, the intelligence to ask questions,
or the patience (anymore)
My admins want me to sit with them to explain what to set up, etc.
However, �without having the authorities (*IOSYSCFG) I have no idea
what screens are going to pop up. �So each step will be painful ,
resulting in me walking back across the street to my cubicle, research
what is needed next, and so on and so forth. �I guess some shops just
aren't coder-friendly, and this is one.
v-out
-----Original Message-----
From: [7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott
Klement
Sent: Tuesday, April 24, 2012 11:47
To: HTTPAPI and FTPAPI Projects
Subject: Re: Apache configuration
Hi Vince,
>
> All that I am trying to get to (at this point) is how to configure
> apache to provide a place for me to build a web service with
> HTTPAPI.
>
I'm not certain whether you understand this already, so I'll say it
just
to make sure we're on the same page: �HTTPAPI cannot be used to
provide
a web service.
HTTPAPI is a client-side tool. It can be used to _call_ a web service
that's provided by another tool (such as Apache, IWS, Tomcat,
WebSphere,
IIS, etc)
If you use a traditional web site as an analogy, HTTPAPI takes the role
of the "web browser". �Apache takes the role of the "web server."
That said, you'd never set up a web service (or web site) without
testing it. �So you might use HTTPAPI for calling/testing your web
service (I know that I do!)
> I know that there is a file somewhere in which some entry goes into
> to determine a port for the server. �The fact is, rambling on as I
am
> I've begun to recall some of this and will pursue it.
>
Apache configuration files normally live in:
� �/www/your-instance-name/conf/httpd.conf
however, the proper way to edit them is with the IBM HTTP *ADMIN tool.
You aren't supposed to change these files by hand.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. �To unsubscribe, please go to:
[9]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. �To unsubscribe, please go to:
[10]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. �To unsubscribe, please go to:
[11]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
--
Regards,
Henrik Rützou
� [12]http://powerEXT.com
� [plogofull200.png]
References
1. mailto:Kaj.Julius@xxxxxx
2. http://www.easy400.net/
3. http://sysName:14444/cgibin/vescl
4. http://www.easy400.net/cgidev2o/faq39.htm?ts=0.18315931829076781
5. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
6. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
7. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. http://www.scottklement.com/mailman/listinfo/ftpapi
10. http://www.scottklement.com/mailman/listinfo/ftpapi
11. http://www.scottklement.com/mailman/listinfo/ftpapi
12. http://powerext.com/
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------