The WorkFlows Java client will not affect e-Library stations, which will require only a Web browser.
Virus protection software should be temporarily disabled while installing the WorkFlows Java client.
To install or update to the SirsiDynix Symphony 3.4 WorkFlows Java client, your system must meet the following minimum requirements.
| • | OS/Platform: Windows, XP, Vista, 7, or Macintosh OS X (10.4 and higher, 64 bit machine, Dual Core required) |
| • | RAM minimum: 1 GB, suggested: 2 GB |
| • | Processor speed minimum: 700 MHz, suggested: 1 Ghz |
| • | Disk space for WorkFlows: 100 MB free hard disk space |
| • | Monitor resolution: 1024 x 768 or better |
| • | TCP/IP networking support |
| • | Ability to connect to a SirsiDynix Symphony 3.4 server |
| • | Java 1.6 |
Note: Macintosh workstations support Java 1.6 only on 64 Bit, Dual Core, running Leopard OSX 10.5, Update 2 or higher. For Macs that do not meet these requirements, users can run the SirsiDynix Symphony 3.2.1 WorkFlows Java client, which requires Java 1.5 rather than Java 1.6, against the SirsiDynix Symphony 3.3. server. Please go to the client/server specifications for SirsiDynix Symphony 3.2.1 for details on Mac hardware specifications. While SirsiDynix has tested the Mac 3.2.1 WorkFlows Java Client against SirsiDynix Symphony 3.3, SirsiDynix strongly recommends that sites using Macs that upgrade to Symphony 3.3 make plans to upgrade to the 3.3 version of the Workflows Java client in order to take advantage of new capabilities and corrections and to ensure optimal support.
On workstations running the WorkFlows Java client, SirsiDynix recommends setting the virtual memory association to equal twice the amount of physical memory, at minimum. Please work with your system administrator to check the virtual memory setting on each workstation running the WorkFlows Java client, and increase the memory if necessary.
The WorkFlows Java client will not affect e-Library stations, which will require only a Web browser.
Virus protection software should be temporarily disabled while installing the WorkFlows Java client.
Process Changes for the Version 3.3.0 WorkFlows Java Client Installation on Windows Systems
Before you install the Version 3.3.0 WorkFlows Java client, there are now essentially two modes of operation:
| • | Administrator |
| • | Non-admininistrator (individual account or shared account) |
For administrator user logins, the installation process remains the same as in previous versions of the WorkFlows Java client. That is, the administrator user installs the client and upgrades the client, and all library staff uses that copy of the client. Only administrator users can install and upgrade the client.
For non-administrator user logins, each individual installs the client, and the client is installed in that user’s \Documents and Settings folder on the workstation. The individual user can update and uninstall his or her copy of the client.
Additionally, the client can be installed using a shared, non-administrator user login account. This is useful for common, shared logins, such as CIRC or TECHSERV. The client is installed in the non-administrator user’s \Documents and Settings folder on the workstation. Only that user can update and uninstall his or her copy of the client.
Installation process changes
The Version 3.3.0 WorkFlows Java client installation process has changed as follows:
| • | If you are going to use the new non-administrator installation feature, it is recommended that the previous version of the WorkFlows Java client is either un-installed, or that you remove the Desktop icon to the older version, to eliminate confusion for the users. |
| • | A non-administrator cannot uninstall a client that was installed by an admin (which is the same for the 3.2.1 and earlier WorkFlows Java clients). However, once the non-administrator has installed the client, that user can also uninstall his or her own client. |
| • | Non-administrator installs are independent on the workstation, which is, there will be more than one client installation if more than one non-administrator user uses that workstation and installs a client. |
Where the client is installed
The client files are installed in different locations on the workstation depending on the type of installation (administrator and non-administrator) and whether the client is updated or is freshly installed.
|
Type of installation |
Where client files are installed |
Who can access, update, and uninstall the client |
|
GL3.1 update to 3.3.0 with administrator user login |
\Program Files |
Everyone can use the client, but only this administrator user login can update and uninstall the client. |
|
3.2.1.05 update to 3.3.0 with administrator user login |
\Program Files |
Everyone can use the client, but only this administrator user login can update and uninstall the client. |
|
Fresh install of 3.3.0 with administrator login |
\Program Files |
Everyone can use the client, but only the administrator user login can update and uninstall the client. |
|
Fresh install of 3.3.0 with non-administrator login (individual account) |
\Documents and Settings for this user’s home directory |
Users can only use and update this copy when logged in as this particular user. Only this login user can update and uninstall this copy of the client. |
|
Fresh install of 3.3.0 with non-administrator login (shared account) |
\Documents and Settings for this user’s home directory |
Shared accounts, such as CIRC or TECHSERV, may be used by multiple users. Only this login user can update or uninstall this copy of the client. |
© 2006, 2013 SirsiDynix