Using Standalone for Circulation on JWF

There is no separate standalone program; it is just part of the Java Client. If you are running only the C-client and want to run Standalone, you must install the Java Client.

When the Java Client Workflows loses connection, you get the message "connection closed to remote host, you must exit and restart the staff client."

Respond to this by saying YES, then re-launch Workflows and check the standalone check box. Click OK.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
On the Module Toolbar, click on Offline. Click on the Offline Session wizard to set the properties. The User Access should be set to STANDALONE. The library should be set to your library. Take note of the Log directory where you'll save the offline file on your pc. It defaults to the Workflows directory under Documents and Settings\[Windows user logon name]. Click OK to save the settings. When connectivity has been restored, exit Workflows. When you log into the system, Workflows automatically uploads the offline file.

There are two ways you can process the offline files:

1) Logon all staff workstations that ran Standalone, then on any one pc, go to the Schedule New Reports wizard. Find the Circcustom tab and run the Load Standalone report. Be sure to look at the report to see what problems may occur that need attention, such as patron or item not in catalog.

2) Logon one workstation at a time, run the Load Standalone report, wait for it to finish, logon the next workstation, run the report, wait for it to finish, and so on.

What happens behind the scenes? Each workstation’s offline file is uploaded to a library directory and given a unique name. When the report runs, it appends all the files together. Either option 1 or 2 works for the WYLD Office; it’s your choice how you want to upload the files.

One caution to consider: When Workflows automatically uploads the file, once it’s transferred from the workstation to the server, it removes the file. There is no backup at this point. Other SirsiDynix libraries have complained about this, asking what happens if there is some sort of disruption. WYLD Office staff have not actually heard of any real problems with this, however, so we do not believe this is really an issue. We suspect that Workflows does not remove the file if it doesn't hear back from the server that the transfer was completed. On the server, the file remains until the next run of the report, so there is a backup there should the load report have a problem.

You can practice the whole standalone process anytime, just setup the Standalone properties and actually do some work in the offline wizards. You can be connected or not when you do this. However, you do have to restart Workflows to trigger the file upload. Then just run the report to evaluate the results.