Re: IFS permissions for Apache HTTP and Websphere 5 - Resolution (for the archives)

It actually fixed it for both instances, but on our internal instance we 
had an application that was creating a directory per upload.  In that case 
you will need to add "-Dos400.dir.create.auth=RX" to the jvm arguments.

To:
web400@xxxxxxxxxxxx
Subject:
[WEB400] Re: IFS permissions for Apache HTTP and Websphere 5 - Resolution 
(sort of)
You must add "-Dos400.file.create.auth=R" to the generic jvm arguments in 
the WAS5 admin console.  It is located under servers, application servers, 

your server, process definition, java virtual machine.

Then you must change the umask to "000" under ...process definition, 
process execution.

This fixed our problem for our public instance, but not our internal 
instance.


RE:

We're having difficulty accessing a file on the IFS that is created via a 
Websphere 5 app using standard java file io.  The file gets created with 
public none data authority.  When the same file is attempted to be served 
from the HTTP server it gets a permission denied:

[Tue Dec 23 14:51:11 2003] [error] [client 192.100.2.90] (3401)Permission 
denied.: ZSRV_MSG0019: Permissions on file /eCommerce/onlineads/ad_44.jpg 
deny server access, referer: 

If we manually change the ad_44.jpg's permission so *public has read 
access, it works, but we're not sure if that's the correct way to do it, 
or how to default to this behavior (other than using the toolbox to change 



the permissions).  The file is owned by QEJBSVR.