FAQs: Installing the WorkFlows Java Client on a Network Server
The SirsiDynix WorkFlows Java client is a Windows-based graphical software program used by library staff to perform staff operations in SirsiDynix Symphony. Typically, a separate copy of this software is installed on each library staff workstation. On occasion some libraries choose to install the WorkFlows Java client on a Windows Server, and then serve the software to individual staff workstations from this central computer.
Host Machine Requirements
|
•
|
The WorkFlows Java client must be installed. |
|
•
|
The WorkFlows Java client must be a shared folder. |
|
•
|
If you choose to store each user’s properties files on the host machine, the folder containing these files must be shared. |
Note: When a workstation connects to use the client on the host, it registers network bandwidth on the host machine. For example, a connection may initially use 10% of the bandwidth while files are downloading. After initial connection, the network traffic drops off significantly. You will have to experiment to see how many workstations can successfully connect to your host machine
User Workstation Requirements
|
•
|
Each user workstation must have the JRE installed that is appropriate for the version of the WorkFlows client on the host machine |
|
•
|
Each user workstation needs to have a specially formatted wf.bat file, and a desktop shortcut to that bat file |
|
•
|
There must be at least one drive mapped to the host machine |
|
•
|
A second drive should be mapped to the host machine if you choose to store the user’s properties files on the host machine |
|
•
|
If the user’s properties files will be stored on the individual workstation, you will need to create a special folder for this on the workstation |
|
•
|
There must be a special wf.bat file which points to the host machine, and identifies where the user’s properties files are stored. It also points to the appropriate JRE on the user’s workstation |
Below are two sample networked client configurations. The difference between the two configurations lies with where the user’s properties files are stored. (These are the files that are normally stored in \Documents and Settings\username\Sirsi\Workflows.)
Sample Setup - User’s Properties Files Stored on Own Workstation
|
1
|
On the user workstation, map a drive to the c:\Program Files\Sirsi\Jwf folder on the host machine. This should be a shared folder. In this example, let’s call the mapped drive Z |
|
2
|
On the user workstation, create a folder to store the user’s properties files. For example, create a C:\Users\Circdesk\Workflows folder. This folder can be named anything you like and stored anywhere on the workstation |
|
3
|
Create a special wf.bat (see below). You can put it anywhere you like. For example, you could put it in the folder you created above |
|
4
|
Create a desktop shortcut to the special wf.bat. |
When you click on the wf.bat file desktop icon, you will be using the client installed on the host machine. On the workstation, you will be updating the properties files in C:\Users\Circdesk\Workflows
Sample wf.bat file:
@echo off
set CLASSPATH=.;platform.jar;workflows.jar;custom.jar;screens.jar;wizards.jar;comm.jar;jh.jar;components.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;commons-logging-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
start ”Jwf” /D”Z:\Jwf” ”C:\Program Files\Java\jre1.5.0_06\bin\javaw” -Dworkflows.directory=”Z:\Jwf” -Xms256m -Xmx256m -jar workflows.jar -wC:\Users\Circdesk\Workflows
goto END
:UPDATE
if exist new_jwf.exe del new_jwf.exe
ren upd_jwf.exe new_jwf.exe
start new_jwf.exe
:END
Sample Setup - User’s Properties Files Stored on Host Machine
|
1
|
On the user workstation, map a drive to the c:\Program Files\Sirsi\Jwf folder on the host machine. This should be a shared folder. In this example, let’s call the mapped drive Y. |
|
2
|
On the user workstation, map a drive to a shared Users folder on the host machine. In this example, let’s call the mapped drive X. |
|
3
|
Create a special wf.bat (see below). You can put it anywhere you like. |
|
4
|
Create a desktop shortcut to the special wf.bat. |
When you click on the wf.bat file, you will be using the client installed on the host machine. In addition, you will be writing your properties to a folder underneath the shared Users folder. The first time you connect, you will create a subfolder for your username
Sample wf.bat file:
@echo off
set CLASSPATH=.;platform.jar;workflows.jar;custom.jar;screens.jar;wizards.jar;comm.jar;jh.jar;components.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;commons-logging-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
start ”Jwf” /D”Y:\Jwf” ”C:\Program Files\Java\jre1.5.0_06\bin\javaw” -Dworkflows.directory=”Y:\Jwf” -Xms256m -Xmx256m -jar workflows.jar -wX:\%USERNAME%
goto END
:UPDATE
if exist new_jwf.exe del new_jwf.exe
ren upd_jwf.exe new_jwf.exe
start new_jwf.exe
:END
When staff members use the networked client, they will NEVER be prompted to update the client. This is true even if stamp files would normally generate update messages.