Folder Security Hierarchy

[lpinkepank]

I'm working out the folder structure and security that our company wants for our Longreach app. We want to set up a hierarchy of folders and user access, and I would like to talk to someone about how folder security works with LongReach and if it is possible to do it the way we envision. Could you set up a time to give me a call to discuss it? LongReach folders is completely new territory for us and I don't know how to begin. Thanks!
Linda

[alick]

LongReach on the IBMi uses the JT400 classes to signon and operate on the IFS files and folders.

The underlyting security is controlled by the JT400 classes and OS/400.

com.ibm.as400.access.IFSFile
com.ibm.as400.access.IFSFileInputStream
com.ibm.as400.access.IFSFileOutputStream

http://www.ibm.com/developerworks/ibmi/library/i-ifs/

The owner of files and folders is the LongReach user profile you use.

File and folder authority is inherited from the parent folder.

Refer to IBM and LongReach documentation.

http://www.lansa.com/longreach/index.htm

http://www.lansa.com/longreach/documentation.htm

Using EBCDIC files in the LongReach app

File and folder access permissions

=====================================================================

By default the root folder for LongReach files and folders is the /longreachdata folder.

WRKLNK OBJ('/longreachdata')

/longreachdata

/shared
/user
/{user profile 1}
/{user profile 2}
/{user profile 3}

=====================================================================

/longreachdata/user/ALICK

Owner . . . . . . . . . . . . : ALICK

*PUBLIC *EXCLUDE
ALICK *RWX X X X X
LONGREACH *RWX X X X X

/longreachdata/user/ALICK/myfolder

*PUBLIC *EXCLUDE
ALICK *RWX X X X X
LONGREACH *RWX X X X X

/longreachdata/user/ALICK/LatestSales.pdf

Owner . . . . . . . . . . . . : ALICK

*PUBLIC *EXCLUDE
ALICK *RWX X X X X
LONGREACH *RWX X X X X