Note that you have taken a non-traditional approach to deploying a web site
to an AS400. The traditional approach, or rather how IBM tells you to do
it, is to use the *ADMIN server to create the server from scratch. That
obviously isn't efficient in some cases (like mine where I have an install
script for RPG-XML Suite to automate the authorities).

But on the flip side what you are asking is potentially a huge security
vulnerability - allowing the changing of securities through a derivative of
Websphere. Makes me shudder in my poop kickers (that's midwest for boots
:-)

I would much rather do the security changes from a command line and some of
that is just opinion and the other is the fact that there a large amount of
disconnect between the OS400 and Websphere folks (IMO).

Aaron Bartell
http://mowyourlawn.com


On Mon, Sep 29, 2008 at 12:58 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

That it is, Aaron. You are exactly right. But having to go back in
with a 5250 command line to give permissions?? The more likely answer
is that I don;lt know what I am doing! :) There must be a place in
the HTTP Administrator to set that. There HAS to be. I just am not
seeing it.

Aaron Bartell wrote:
To expound on that (and I agree with Matt btw) the profile *might* be
QTMHHTTP. Do some trial and error to see what you get after giving
QTMHHTTP
access to those directories and files.

HTH,
Aaron Bartell
http://mowyourlawn.com

On Mon, Sep 29, 2008 at 12:08 PM, Haas, Matt (CL Tech Sv) <
matt.haas@xxxxxxxxxxx> wrote:


It would be better to keep *PUBLIC set to *EXCLUDE and give the web
server's profile *RX authority.

Matt

------------------------------------------------------------------------


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.