'Locked-Down' Hard Drive

There are two areas to consider which apply when in traditional 'locked-down' hard drive environments.

The first is that the restrictions prevent access to the Java Home location, and secondly restrictions preventing access to the Java Class path.

1) Restrictions preventing access to Java Home

The Java Home location is dependent upon your operating system and your selected Java engine (either Sun's Java Engine or Microsoft's JVM), but for Microsoft Windows users, the Java Home is likely to be in one of the following locations:

For Windows Vista/Windows 7:
c:\users\<user name>\ (or %LOCALAPPDATA%)

For WinXP & Win2000:
c:\documents and settings\<user name>\

For WinNT:
c:\winnt\profiles\<user name>\

For Win98:
c:\windows\

For Linux users, the standard location is:
/home/<username>/

For Mac OSX users, it's most likely to be:
/Users/<username>/

The Java Home is where both ViewONE and ViewONE Pro caches image files, user preferences and button resources.

In order to use ViewONE or ViewONE Pro in such an environment, the IT Admin team needs to specify and/or enable the read and write privileges of the individual users' machines to allow the viewers to work with the Java Home directory.

Alterntively, the IT Admin team can use the CachePath parameter (one of the many HTML parameters open to configuration) to redirect the viewers' I/O to another location. Details of this can be found in the HTML manual.

This parameter needs to point the viewer to a place where it can be permitted to work and permitted to cache. This place needs to be unique to the individual and should not be a shared location.  This is particularly useful for Citrix or Terminal Services environments.

2) Restrictions preventing access to the Class Path

The Java Class Path is the specifed ordered list of the java archive files (or JAR files) in which to search for class files.

Both viewers require a Java environment to run, and a key element of this environment is the Class Path. Restrictions on defining the Class Path generates a problem when using ViewONE Pro only and only when using the Advanced Cache Manager (ACM). If the implementation of the viewer tries to use the ACM it will try to unpack itself to the Class Path and the restriction will cause a failure.

To resolve the issue, the IT Admin team can either pre-install ViewONE Pro (we have provided an example of how to do this in our downloads and have documented the procedure in the ViewONE Pro manual), or can configure ViewONE Pro to not use the ACM (for those or all chosen users), which is also documented in the same manual.