Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
SirsiDynix Symphony Client Requirements & Installation Notes Last updated November 16, 2009 Equipment Requirements Staff Workstation Specifications: WorkFlows Java Client for the PC Microsoft Windows 2000/XP, with Service Pack 2 installed 100 MB hard disk space available for application Network card Single processor 700 Mhz (1 Ghz Pentium ® 4 recommended) processor 512 MB memory minimum (* 1 GB+ recommended – see note) 1024x768 or better screen display * SirsiDynix recommends setting the virtual memory association to equal twice the amount of physical memory, at minimum. For workstations running the WorkFlows Java client simultaneously with additional applications other than a browser, SirsiDynix strongly suggests that each workstation has at least 1 gigabyte of RAM. Microsoft Windows Vista (** see note regarding Vista workstations) 2 GB+ RAM minimum recommended (* 1 GB of RAM for the OS. Another GB of RAM for WorkFlows. The more RAM the better. Less RAM may work as well, but performance will quickly become an issue. See note.) 100 MB hard disk space Network Card If system was purchased with Vista, the processor will be adequate. If machine is upgraded to Vista, processor must be 800 Mhz minimum, 1.4 Ghz recommended. 1024 x 768 screen resolution * SirsiDynix recommends setting the virtual memory association to equal twice the amount of physical memory, at minimum. For workstations running the WorkFlows Java client simultaneously with additional applications other than a browser, SirsiDynix strongly suggests that each workstation has at least 1 gigabyte of RAM. ** Due to the security features of Windows Vista, special notes regarding the Installing and Running WorkFlows on Windows Vista has been developed. Microsoft Windows 7 Windows 7 is not officially certified and supported yet by SirsiDynix and will not be certified by SirsiDynix until July 2010 at the earliest. This timeframe is typical for SirsiDynix and allows time for Microsoft to shake out bugs and security holes that typically are uncovered after the general release of an operating system. If you elect to run the SirsiDynix Java WorkFlows Client on Windows 7 and problem is not fixable: You will need to reproduce problem on supported Windows version before it can be accepted as bug by SirsiDynix You may be asked to revert to older, supported version (e.g. Vista or XP) Some SirsiDynix customers who have used SirsiDynix Java WorkFlows Client on Windows 7 have reported some problems with WordPad and with the visibility of some buttons. SirsiDynix Symphony Client Requirements & Installation Notes November 16, 2009 Page 1 of 5 WorkFlows Java Client for the MAC OS X (* Tiger 10.4.6 and higher, plus JRE 1.5 required – see note) o Effective June 2010, Leopard (10.5.x) will be required 100 MB hard disk space available for application Network card Single processor 700 Mhz PowerPC G3 (800 Mhz PowerPC G4 or later NON-Intel processor recommended) o Effective June 2010, 64-bit capable Intel-based machines, i.e.: core 2 duo machines will be required. Power PCs and core duo (32 bit) machines will not be compatible. 512 MB memory minimum (1 GB+ recommended) * Java Runtime Environment 5.0 (also known as JRE 1.5) must be installed prior to installing the WorkFlows Java Client on the Mac. Effective June 2010, JRE 1.6 will be required. StaffWeb Client IE 7.0, Firefox 3.x, or Safari 3.x Adobe Flash Player v. 9 or higher A minimum of 1 GB free memory due to Adobe Flash Player C-Client/Ecole WorkFlows Client Effective July 1, 2009, INFOhio will no longer be supporting the C-Client/Ecole WorkFlows Client Required File/Folder Permissions for Client Installation and Updates User used to install and/or update client must have administrative rights on the PC, but should be installed as non-ROOT user on a MAC. o Read, write and modify permissions to the installation directory. On PC this is C:\Program Files\Sirsi On MAC this is HD\Applications o Ability to make registry changes On PC only o Read, write and modify permissions to the Users directory. On PC this is C:\Documents and Settings\Localusername\Sirsi On MAC this is HD\Users\Localusername\Library\Preferences\WorkFlows If you do not have the appropriate permissions to do the update, you should defer the update until the administrator can do it for you. SirsiDynix Symphony Client Requirements & Installation Notes November 16, 2009 Page 2 of 5 Day-to-Day Client Operation Below are the required permissions for daily operation of WorkFlows. This is in addition to R/O access to all of the already listed files and/or folders above. For viewing/saving finished reports you must have read, write and modify permission to the User’s Temp folder or for PCs, you may redirect user to system Temp folder. On PC this is C:\Documents and Settings\Localusername\Local Settings\Temp or C:\WINDOWS\Temp On MAC this is HD\Users\Localusername\Library\Preferences\WorkFlows\tmp To save personal settings such as properties, margins, printer preferences, etc., you must have read, write and modify permission to user’s directory. On PC this is C:\Documents and Settings\Localusername\Sirsi On MAC this is HD\Users\Localusername\Library\Preferences\WorkFlows To use SmartPort and possibly other features, the user must have read, write and modify permission to the program installation folder. On PC this is C:\ProgramFiles\Sirsi On MAC this is HD\Applications\WorkFlows.app To access the Z39.50 SmartPort targets for importing MARC records the following ports need open through any firewalls: Cataloging Source Server Name Address Port Utilized Acquired Bib Records for INFOhio (ABRI) sirsi.infohio.org 66.114.5.10 3054 Library of Congress z3950.loc.gov 140.147.249.38 7090 INFOhio Curriculum Resource Catalog union.infohio.org 66.114.0.11 210 OCLC WorldCat zcat.oclc.org 132.174.11.* 210 Templates for original cataloging (TEMPL) sirsi.infohio.org 66.114.5.10 3094 New INFOhio Union Catalog sirsi.infohio.org 66.114.5.10 3064 Open ports with both TCP and UDP bi-directionally to head off any problems. SirsiDynix Symphony Client Requirements & Installation Notes November 16, 2009 Page 3 of 5 Installing and Running WorkFlows on Windows Vista Installing WorkFlows Java on Vista - Must be logged in as user with administrative rights Turn off User Access Control o Go to the Control Panel, Select Users, Uncheck ‘User Access Control’ Install as usual If you are not logged in as a user with administrative rights, some of the files will be installed with incorrect permissions. If you do the installation correctly, there is still the “User Access Control” issue, which is basically another level of security Microsoft incorporated into Vista. This feature will prevent WorkFlows from performing updates, using SmartPort, etc. Therefore, it must be disabled. This can be done by opening the Control Panel and clicking the Users option. Java/JRE Requirements Microsoft Vista requires JRE 1.6, but WorkFlows Java requires JRE 1.5. If you install the FULL version of the java client on your Vista machine, JRE 1.5 will be installed and WorkFlows configured to use JRE 1.5 automatically. If you do not have JRE 1.5 installed, WorkFlows will not work unless you update the Program Files/Sirsi/Jwf/wf.bat file. In that file, you can change the path to JRE to match that of JRE 1.6 on your Vista machine. Wf.bat If JRE 1.5 is not installed on your Vista system, you must change this path to @echo off reflect the location of JRE 1.6 on the set Vista machine. CLASSPATH=.;platform.jar;workflows.jar;custom.jar;screens.jar;wizards.jar;comm.jar;jh.jar;compon ents.jar;catcore.jar;commonutil.jar;hatwrapper.jar;uiextensions.jar set CLASSPATH=%CLASSPATH%;a2j_v2-2.0.8.jar;ki-jzkit-z3950-1_3.jar;log4j-1.2.8.jar;commonslogging-1.0.3.jar;ldap.jar;xom-1.0d19.jar set CLASSPATH=%CLASSPATH%;junit-3.8.1.jar;marc4j-b8.jar;spring-1.1.0.jar;jdbm-0.12.jar if exist upd_jwf.exe goto UPDATE if /I {%1}=={} ( start "Jwf" /D"C:\Program Files\Sirsi\Jwf" "C:\Program Files\Java\jre1.5.0_06\bin\javaw" -Dworkflows.directory="C:\Program Files\Sirsi\Jwf" -Xms256m -Xmx256m -jar workflows.jar ) ELSE ( start "Jwf" /D"C:\Program Files\Sirsi\Jwf" "C:\Program Files\Java\jre1.5.0_06\bin\javaw" -Dworkflows.directory="C:\Program Files\Sirsi\Jwf" Xms256m -Xmx256m -jar workflows.jar -w%1 ) goto END :UPDATE if exist new_jwf.exe del new_jwf.exe ren upd_jwf.exe new_jwf.exe start new_jwf.exe :END WorkFlows Java on Vista System Requirements - - 2 GB RAM minimum recommended. 1 GB of RAM for the OS. Another GB of RAM for WorkFlows. The more RAM the better. Less RAM may work as well, but performance will quickly become an issue. 100 MB hard disk space Network Card If system was purchased with Vista, the processor will be adequate. If machine is upgraded to Vista, processor must be 700Mhz minimum, 1.4 Ghz recommended. 1024 x 768 screen resolution SirsiDynix Symphony Client Requirements & Installation Notes November 16, 2009 Page 4 of 5 Tips and Tricks for Technical Coordinators Here are a few other items to be aware of to provide full availability of Workflow features to the end user. Virus scanning software can sometimes slow the startup of WorkFlows. The javaw.exe is the executable responsible for loading the java and client software during WorkFlows startup. Scanning this exe for virus detection and the network traffic it generates can slow the startup of WorkFlows considerably, to the point that it seems unresponsive. Consider excluding javaw.exe from virus scanning at the workstation. Many districts keep their workstations clean by restoring imaged software. Be advised that the user directories house unique dynamic files for each user which sets various operating environments such as properties and preferences. Therefore, for the Java client, Sirsi user directories should be saved and/or exempted from re-imaging. Creating barcode labels is one feature of WorkFlows. For the user to be able to create barcodes, a barcode font must be installed in the font library. To enable this feature, the librarian will need read, write and modify permission to the font library. An alternative is to have a power user install the barcode font for them. Review the section: Required File/Folder Permissions for Client Installation and Updates Review the section: Day-to-Day Client Operation To install on Windows Vista workstations review the section: Installing and Running WorkFlows on Windows Vista SirsiDynix Symphony Client Requirements & Installation Notes November 16, 2009 Page 5 of 5