Entries in Domain.xml for user passwords will not overwrite password changes made using the ELN user interface, the management portlets, or via webDAV when Tomcat is restarted. To enable dynamic password changes, add an ' override="true" ' attribute to the appropriate password property elements in Domain.xml.
Pop-up Window blockers used with your web browser will interfere with the ELN's ability to open pages when you double click in the table of contents. Allowing pop-ups will restore the ELN capability.
To add users to a notebook via the "Configure New Notebook" form or the ELN Client Administration dialog, they must first have SAM user accounts - defined using Domain.xml (or other means as documented at the Slide website). The ELN "Add User" capability is simply a mechanism to grant those existing SAM users access to a given notebook. (Similarly, "Remove User" only revokes permission for that user to access the current notebook.) Note: However, the "Reset Credentials" functionality in the ELN does reset the SAM account password (see first note about a work-around to fully enable this).
If you change your password through the ELN, you must restart the browser to continue. This is required due to the fact that current browsers do not ask the user for a new username/password to match the change that occurred on the server until they are restarted. You can leave the ELN Client window running during the restart.
If you switch to a new browser (different than the one you installed the ELN Client from), you will be asked to locate your ELN Client manually the first time. You will also be asked to locate the image capture editor the first time you use it (rectcap.exe or ntbkcap.exe depending on your platform). Alternately, simply repeat the Install using the new browser, overwriting the old installation. (Both browsers will now work - an eln.ini file, located in the directory each browser uses as "user.home" is the only file that gets duplicated.)
On some computers you cannot download a file from an ELN page and be prompted whether to view or save it. This is a browser setting specific to each file type. You can follow the standard procedure for your browser to change this behavior. (The ELN is using a simple HTML link for the download and your browser will do whatever it normally does when you find that type of link on the Web).
I've built a custom ELN client and want to point my new users at a local download site: change the URL in SAMELNList.jsp in webapps/sam. A future update will make this configurable via the ELN creation/edit web forms.
Entries in Domain.xml for user passwords will overwrite password changes made using the ELN user interface, the management portlets, or via webDAV when Tomcat is restarted. As a work-around, to enable dynamic password changes, comment-out all user nodes in Domain.xml after running SAM for the first time. (Uncommenting a user node in Domain.xml with a new password and restarting Tomcat will reset the password via the standard means.)
A blank screen when you attempt to open /sam/launchELN and /sam can indicate a problem with SAM finding the jaas.config file. If you check the catalina_log.(date).txt file in %Tomcat%/logs and find a 'can't find a login context' or other security-related error, recheck the JAAS Configuration step of the installation. In particular, check for misspellings, the use of '\' instead of '/' in the path, mismatch between how you defined the jaas.config location and how you started Tomcat, and the path to Tomcat. If you find errors, fixing them and restarting Tomcat should resolve the problem.
Export via the ELN Client GUI is not functional (prompts you to save, accepts a location and name, then does nothing.) Importing after exporting from note.cgi based servers does work, allowing migration from existing servers. As a work-around, you can retrieve data directly via the ELN Page displays and/or webDAV (by default data is stored within the collection defined as the notebook root during configuration.) Retrieving the data as files will not preserve the notebook structure and metadata. Copying the content and properties to another DAV server will preserve the full notebook structure.
Delete (cross-out) and Show/Hide capabilities are not yet available, in the SAM-based ELN server. We anticipate implementing these capabilities in the next minor release.
The URL editor is meant to point to other data on the same SAM server. To use - upload a file to DAV using DAVExplorer or use data already uploaded - copy it's URL into the ELN URL editor (it is case sensitive). It should display as if the file had been uploaded directly. The editor was developed primarily for use when the ELN is part of a portal such as CMCS. It may be extended to allow specification of an arbitrary URL on the Internet in a later release.
During "Add/Remove User" or "Reset Credentials" requests made via the ELN client interface, there was no error message, but the change did not take effect: The ELN Client currently displays a "Success" dialog after successful changes and does not display an error in the user interface if the change fails. You should verify the passwords you're using in the dialogs. If this does not correct the error, check the elnstdout.txt and elnstderr.txt logs in your ELN Client directory for more information. (Future versions of the ELN Client will provide better user feedback for errors.)
ELN Icon and button images don't show up ELN page display. The location from which these
images are retrieved is controlled by the ELNResourceURLBase parameter in sam.xml.
If ELNResourceURLBase is set incorrectly or if the website you're using is down, the images will
not be available. You should be able to view the images directly in your browser using the URL
Last updated: 9/03/04