|
 | The Service Pack install in Production was unsuccessful yesterday. Actually the Service Pack installed but Aleph could not come back up. So we had to back out of it. The problem has something to do with the way different pieces of software are connected on the server. The Service Packs require a set up that doesn't work with normal Aleph operations. We will continue to analyze the problem and try again soon.
|
|
| Aleph Staff Clients
Today, February 5th, the Nov-January service packs (up to rc 1411) will be installed on the test server. After the system is brought back up following the install new updated files will be available through the "Version Check" mechanism for updating currently installed clients on staff PCs. Note that this message concerns the Test server client and not Production. We anticipate that certain staff from each institution will do checking of the service pack in Test to vet it before it moves to Production early next month. Who should be checking in Test is a local decision.
So after the successful completion of the service pack install and after we have indicated that Test is back up, staff wanting to do testing to make sure the service pack hasn't broken any workflows can launch their Test clients and accept the files available for "Version Check". You will either be prompted automatically if the client was installed with "Version Check" on application start up or you will need to launch Version Check from the "File" menu of the module that you opened. You should accept all files by clicking "Update All" when the Version Check message appears. The client will close itself then reopen and staff will need to login again now that the client has been updated.
Here is a little more information on what should happen with this process:
With the implementation of each service pack will come the need to update clients installed on all staff workstations at your institution. In order to update the staff clients we will push out the various update files by "Version Check" (mainly .exe files that must be updated to insure correct client behavior and configuration files, i.e., .dat or .ini). After the service pack is installed the update files to be pushed to the clients will be placed in the special "Version Check" directories in preparation for staff to pull the files over to their PCs. There are two ways of handling version check in the Aleph client (1) automatic check when the client application is opened, staff accepts the files when prompted (2) manually launching version check from the "Aleph/Version Check" menu option of any client and accepting the detected files. In order to successfully detect and retrieve the update files the Version check "Type" setting must correspond to the special directory where the files are located on the server. All test clients currently posted at http://www.fcla.edu/libraryservices/aleph/clientsv18.html were packaged with the version check type setting following this pattern: xx_updates
Where xx is the institution code for your university: am, cf, fa, fi, fs, gc, nc, nf, sf, wf, uf
e.g., for FAMU the Type would equal am_updates
The type setting can be changed within the client so be sure to have staff verify that the appropriate code for your institution is present. If not they should add the code and click the "Change Type" button. Changes made to the type setting within the client persists until they are changed once again.
Here are the files that should be available after this service pack install:
.exe (executables)
acq\bin\acq.exe
catalog\bin\catalog.exe
circ\bin\circ.exe
alephcom\bin\printd.exe
.dat or .ini (configuration) or "help" files:
alephcom\help\eng\acqhlp.hlp
alephcom\help\eng\ill2hlp.hh
alephcom\help\eng\ill2hlp.hlp
alephcom\help_v\eng\acqhlp.chm
alephcom\help_v\eng\circhlp.hh
alephcom\help_v\eng\ill2hlp.chm
alephcom\help_v\eng\ill2hlp.hh
Daniel Cromwell
|
