File storage integration refers to the possibility for ]po[ to store project and other files on an external file server, instead of storing the data on the computer running ]po[. This option allows customers to integrate a typical Windows department file server into the ]po[ system, so that the files can be accessed (read and write) from both Windows and ]po[.
]project-open[ users want to store project related files on the organization's standard file server. This file server usually already contains a "projects" folder with a separate folder for all ongoing projects. Users should be able to access their project files both using ]project-open[ and using their normal Windows explorer.
("po34demo" is the server name instance in this example)
These above listed parameters (found at Parameters Admin Menu) allow the mapping of filestorage base directories to specific locations in the file system of the underlying operating system. The figure above shows a sample from a Unix-like operating system. Equivalent values for a Windows OS are âC:/Project-Open/filestorage/companiesâ for example (please note the forward slashes in Windows filenames).
The ]project-open[ filestorage is designed to be integrated with an existing Windows or Linux fileserver. This means that a file can be accessed not only using ]project-open[ but also directly through file managers of the respective operating systems or other applications.
]project-open[ filestorage always takes its list of files from the existing file server so that there are no possibility of conflicts or inconsistencies.
This mechanism allows users to access the files in two different ways: Staff members from âwithinâ the office are able to access the local Fileserver directly using their Windows Explorer software. Users working âoutsideâ the office (sales representatives, freelancers, customers, home usersâŠ) can access the same files via the Internet using ]project-open[ filestorage.
To implement this interoperability between machines, ]project-open[ utilizes the free software Samba which is a networking tool. The Samba How To guide may be of interest during the course of installation.
The following instructions guide you step-by-step through the process of setting up integration with a Windows file server and a Linux machine.
On the Windows Side:
Create a new Windows user:
Create a new Windows user (i.e. "projop") with a specific password ("secret").
Create a Windows share:
On Windows create a new folder (i.e. "projects") and publish this folder as a Windows "share" (Properties -> Sharing -> Share this folder). Grant "admin" permissions to user "projop".
Enable Plain Text Passwords on Windows 2k/2k3/2k7:
From the Samba HOWTO :
Using the registry editor (regedit), create the registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkStation\Parameters. Add a new DWORD value: Value Name: EnablePlainTextPassword Data: 0x01. Once these registry changes have been made, reboot the Windows machine and try to map a network drive on the Samba server again. It should work as long as the Samba server is using plain text passwords.
Check whether that works from the Windows side:
Use a second Windows (!) machine to check whether the share "projects" is accessible with the password etc.
The following instructions guide you step-by-step through the process of setting up integration with a Linux machine and a Windows fileserver.
On the Linux Side:
192.268.0.4 fs
"fs" is just and example and stands for File server. You can choose the name freely.
smbclient -L fs
mkdir /mnt/projects
mount -t cifs -o username=projop,password=secret //fs/projects /mnt/projectsIssue mount to check if the new share has been mounted. Issue:
ls -l /mnt/projects
to check for files on the Windows server.
Unmount manually:
umount /mnt/projects
//fs/projects /mnt/projects cifs username=projop,password=secret,uid=projop,gid=users
This line assumes that you are running the ]po[ AOLserver with user="projop" and group="users", as it is the case in the default ]po[ installers.
"Value too large for defined data type" errors can be avoided by adding "nounix,noserverino" to the entry:
//fs/projects /mnt/projects cifs username=projop,password=secret,uid=projop,gid=users,nounix,noserverino
mount -a
so that the new settings take effect.
Please note:
It seems that if the device is busy, 'mount -a ' will not apply any changes and returns without any message telling so.
To ensure that changes will take effect, consider un-mounting first:
umount /mnt/projectsor
umount -l /mnt/projectsif device is busy
Some corporate documents may be too sensitive to keep them in the same fileserver as the usual project documents. Therefore ]project-open[ facilitates a second Filestorage module that is only accessible by typing a particular URL. The corresponding Filestorage is shown when executing the ProjectViewPage with the URL variable âview_name=salesâ. You can enable the sales filestorage by adding a new menu entry in the Menu Administration page, similar to the âFilesâ entry.
Calle Aprestadora 19, 12o-2a
08902 Hospitalet de Llobregat (Barcelona)
Spain
Tel Europe: +34 609 953 751
Tel US: +1 415 200 2465
Mail: info@project-open.com