Users and File System

Group: phixflow

This group is the primary group for all PhixFlow users below (phixflow, individual and tomcat)

Group: oinstall

This is the standard name for the Oracle install group. Users phixflow and tomcat should be members of this group.

User: phixflow

This user owns the PhixFlow directory (‘/opt/phixflow’) and will be used to perform certain maintenance tasks. This user should be able to

• read and write to the PhixFlow directory
• read from the Tomcat directory (‘/opt/tomcat’)

This user should not be able to:

• log on directly from a remote machine - support users should log on using their individual user names then switch (‘su’) to phixflow when required
• write to the Tomcat directory (‘/opt/tomcat’)

Individual Support Users

These represent individuals who will perform support and maintenance tasks on PhixFlow. These users should be able to

• log on from a remote machine
• transfer files to/from external PhixFlow sites via FTP
• read and write to the PhixFlow directory (‘/opt/phixflow’)
• read from the Tomcat directory (‘/opt/tomcat’)

These users should not be able to:

• write to the Tomcat directory (‘/opt/tomcat’)

At the administrator’s discretion, the phixflow user and individual support users may be combined into a single user.

User: tomcat

The tomcat user will be used to run the Apache Tomcat web server, and will own all files directly used by the web server. This user should be able to

• read and write files in the Tomcat directory

This user should not be able to

• log on directly from a remote machine - support users should log on using their individual user names then switch (‘su’) to tomcat when required

Notes

1.

If on Linux: increase the per-user limit on open files for the tomcat user to 4096.

To do this edit /etc/security/limits.conf and add the following line:

tomcat          hard    nofile          4095

2.

Set umask 22 for the tomcat  user and umask 2 for user phixflow and individual support users.

3.

Add the oracle user to the phixflow group – this will allow oracle to write data pump files into the PhixFlow directory

Directory

Link To

/opt/phixflow

$app/phixflow

/opt/tomcat

$app/tomcat

Notes

1.

/opt/phixflow and all directories beneath it have the group id bit set in order to ensure that all directories and files under /opt/phixflow can be read and written by any PhixFlow support user and by tomcat

2.

/opt/tomcat and all directories beneath it have the group permissions set to read-only so that only the tomcat user can write or modify files under /opt/tomcat

Individual Support Users

These represent individuals who will install PhixFlow and perform support and maintenance tasks on PhixFlow. These users should have local administrator rights on the server and should be able to:

• log on to the server via a remote desktop session
• transfer files to/from external PhixFlow sites via FTP
• read and write to the PhixFlow directory (‘$app/phixflow’)
• read and write to the Tomcat directory (‘$app/tomcat’)

At the administrator’s discretion, a single support user ‘phixflow’ user may be set up however we recommend setting up individual accounts.

Directory

Link To

C:/opt/phixflow

$app/phixflow

C:/opt/tomcat

$app/tomcat

Notes

1.

To set up an NTFS symbolic link:

Run cmd.exe (you might need to run as administrator)

MKLINK [/D] link target

e.g.

cmd> cd c:\opt

cmd> mklink /D tomcat c:\u02\tomcat