From MicroFocusInternationalWiki
Jump to: navigation, search

Welcome to the iFolder Wiki!!

As already mentioned on the wiki main page, please feel free to join in. You can read anything in here without logging in, but if you feel like commenting on something, or starting a new topic, you'll need to use a Novell Login account (which you'll be prompted to create if you don't already have one). If you are unfamiliar with using Wiki's in general, please visit Novell Wiki or the grandaddy wiki info site www.wiki.org for some background info.

You can read more about iFolder 3.x on the iFolder home page


I did not see an answer for the posted question. We know iFolder 3 does not encrypt files on the server, but will it in the futur--Gabaurre 07:01, 4 May 2006 (MDT)e?

Data Encryption

Q: I'd like to ask why encryption was taken out of iFolder 3.x. I loved the multi-user iFolders, but I work in an institution where research is done on sensitive information. For our faculty to fully use this software, the information would have to be encrypted on the local stores at least in case they put some sensitive information in their iFolder. I can tell them not to, but that won't guarantee they won't leave a patient's medical record on a hard drive in an internet cafe somewhere in China...

A: See 2.17 Storing iFolder 3.x Data Nonencrypted on the Server and 4.4 Migrating User Files from an iFolder 2.1x to a 3.x Server.

iFolder 3.5 on SUSE 10.1

If using the Configuring iFolder Enterprise Server on SUSE Linux 9.3, 10.x, and SLES 9 guide on the iFolder website for SUSE 10.1 the result may not be a working server. You can see the http://localhost/admin login screen, but can not log in with the admin:simias account and you get a message: "Your session has been closed. Please log in." The problem lies with the file /usr/lib/simias/web/bin/FlaimWrapper.so which is linked to the /usr/lib/libFlaimWrapper.so which is supplied with SUSE. To correct the problem remove the /usr/lib/simias/web/bin/FlaimWrapper.so and replace with a one pointing to /opt/novell/ifolder3/lib/libFlaimWrapper.so

rm /usr/lib/simias/web/bin/FlaimWrapper.so

ln -s /opt/novell/ifolder3/lib/libFlaimWrapper.so /usr/lib/simias/web/bin/FlaimWrapper.so

--Ppodbevsek 00:39, 17 May 2006 (MDT)

iFolder Cllient on MAC experience

I have been trying to gather my experience from the new 3.7.2 client into a readable text. Hope someone will learn from this. Overall my experience is good with iFolder as a product but there are still issues. If you plan to use the iFolder in a cross-enviroment (win, linux, mac) there is no cross-over sync issues between the windows and linux client but with the mac and the former two there are issues if you use scandinavian characters - my advice: DON'T use them (scandinavian characters) in a mixed enviroment.

When first putting up the MAC client I've had no difficulties using the last opensource 3.7.2 client. It seems once in a while not to start properly or very slowly, but thats cured with quitting once and restarting it. Once or twice I've had to restart it three times.

If you sometimes have to move the folder you are syncing to a new location on your mac - DON'T revert it/ delete it and download/upload it again after the move. It will completely mess up the system (iFolder). We did and it took us three days to sort it out (if you ever stumble accross the same - don't hesitate to ask what to do). If you for some reason have to move the folder to a new location be sure to RENAME it and resync to the server.

If your iFolder client on your mac hangs for some reason sometime (it occurs). It's usually the mono instance that does this. I have solved this by quitting the iFolder client (it may take a couple of minutes, if it doesn't just force quit). After this check that no mono is left running by killing all mono instances. Do this by opening a terminal window and writning "killall mono" [enter] This will take care of it. Now you can restart the client and it usually works. Sometimes I've had to restart the MAC itself.

To conclude

When you get the client up and syncing it works well, but be sure that it does start. I don't start it automatically at startup - just manually when everything else is up.

--Dominicus 06:25, 20 May 2009 (MDT)