1
2001.1 Customer
Upgrade Instructions
Step 1. Prepare for your upgrade
Step 2. Schedule your upgrade
Step 3. Pre-Upgrade contact
Step 4. Verify Backup will occur
Step 5. Backup Server
Step 6. Be on-call for upgrader
Step 7. Installing Clients
Step 8. Post-Upgrade
Step 1: Prepare for your upgrade (Various times before upgrade)
Preparation Checklist:
[_] Patron SIF[_] Access Reports[_] Reports &
Notices
[_] Tag Tables[_] Unauthorized Headings Reports[_]
Offline Circulation
[_] Webvoyage Configuration / Preview Server[_]
Global Hedings Change Queue[_] EDI Messages
Take time to carefully read the Voyager 2001.1 Release Notes
that are posted on SupportWeb
The Patron SIF, used for patron update / extract, has NOT
changed in Voyager 2001.1. You do not need to make any
changes to any patron update / extract procedures you may
have at your institution.
The pre-packaged Microsoft Access queries and reports
(c:\voyager\AccessReports\reports.mdb) still uses Microsoft
Access 2000. The Voyager database schema changes will be
documented and posted on SupportWeb. These changes will mean
that you may not be able to use your customized reports, as
well as some 2000.1 pre-packaged reports. You must relink
your reports.mdb and any other custom databases you may have
created from the Voyager database schema. Instructions for
relinking can be found in the FAQ database on SupportWeb.
Search for "reports and relink".
All 2000.1 reports and notice inp files must be processed
2
through the 2000.1 Reporter before the upgrade takes place.
The Reporter client will only process reports and notices
produced with the same version of the servers.
Release 2001.1 tag tables for cataloging have changed. You
will want to save your old tag tables (in a directory that
is NOT C:\VOYAGER), then run VoyagerConfig.exe on each
cataloging PC during the 2001.1 client installation.
Afterwards, you may incorporate your changes (if any) into
the new files.The directory "USMarc" (which is in
C:\VOYAGER\CATALOG\TAGTABLE) has been renamed to
"Marc21".
The unauthorized headings reports (Pcatjob 1 through 4) is
one that requires a date range. In the upgrade process, the
'Create Date' of the headings will change to the date of the
upgrade. If these reports are not part of your normal
workflow, this is not an issue. However, if this is
something key to your workflow, you need to carefully plan
how the reports are run so that you get meaningful data.
Immediately prior to the upgrade, you should run the reports
with the date range from the beginning of your reporting
period to the current date (ie. day before the upgrade). At
the end of the reporting period which includes the date of
your upgrade, you will run the reports again with the
beginning date being the first full day after the upgrade
and the end date the last day of your reporting period. In
light of this, you should not perform any work that would
generate data for these reports on the actual day(s) of your
upgrade.
For example, you normally run these reports to cover a
calendar month. So, if your upgrade occurs on August 15th,
you will do the following:
On August 14th, end all cataloging activity. Run the
reports with the starting date as August 1st, and the
ending date August 14th.
On August 15th, your upgrade will be performed and no
cataloging work will be done. All existing headings will
now have a Create Date of August 15th.
On September 1st, you will run the reports again, this
time with the starting date as August 16th and the ending
date as August 31st.
In you intend to use offline circulation during the upgrade
(used to cirulate items while your Voyager system is down),
you will need to install the 2001.1 Voyager clients at your
3
circulation desk(s) before the upgrade begins. Once the
upgrade is complete, the offline circulation files can then
be processed using the 2001.1 Voyager software. Offline circ
must be locally installed on the circulation PC. It will not
run from a network installation. See the 2001.1 Circulation
manual for more information on using offline circulation.
Webvoyage configuration file changes will be made easy with
a tool that compares your old configuration files to the new
"out of the box" configuration files. (Coming Soon)
We also have put a document listing the configuration
changes on SupportWeb.
The Preview Server is also set up for you to test your local
customizations to Webvoyage prior to your upgrade. Please
see the documentation on SupportWeb for how to use the
Preview Server for this purpose. (Coming Soon)
When upgrading to Voyager 2001.1, you will need to process
the global headings change queue before your upgrade. The
global heading change queue will not be preserved during the
upgrade.
All outstanding EDI messages must be processed before the
upgrade takes place.
Step 2: Schedule your upgrade (at least 2 weeks prior to
upgrade)
Contact the Upgrade department to schedule your upgrade with
the three best dates for the upgrade. You may contact us:
email: upgrade@endinfosys.com
phone: U.S. / Canada: 1-877-44-LLOYD (1-877-445-5693) (ask for
Upgrade Department or Sean Walker)
Other International: 800-4444-3474 (ask for Upgrade
Department or Sean Walker)
Step 3: Pre-Upgrade contact (1 week prior to upgrade)
An Endeavor upgrader will contact you to discuss your upgrade.
Please have the name of the person who will be the Primary
Contact during the entire upgrade process. We will need the
following information:
Special connection instructions (if applicable)
Contact Name (someone who has access to the server during
and after business hours)
Day-time Phone Number
After Hours Phone Number (This can be a pager. This person
needs to be ON CALL, not necessarily by the server for the
4
entire upgrade. After hours contact will only be used if
customer requests this, or if there is a server emergency)
Your preference for updates during the upgrade (email,
phone, pager, etc.) and frequency of updates.
The engineer will also do a final health check of the system,
and begin transferring the files needed for the upgrade. You
do NOT need to transfer the files, unless you are doing the
upgrade yourself.
If you do not have any contact at this point, you may contact
the email or phone number that was used for scheduling.
Step 4. Verify Back-up will occur. (1 week prior to upgrade)
Please have your system administrator verify the backup
procedure of your Voyager server(s) one week prior to your
scheduled upgrade.
Please verify the output. You may contact Endeavor Customer
Support at 877-445-5693 if you should have any questions.
Step 5. Back Up Server (NIGHT BEFORE UPGRADE)
Back up server(s) the evening prior to your scheduled upgrade
Step 6. Be on call for upgrader (During Upgrade)
Have someone available for the upgrader to call in case there
is something that he/she needs.
Step 7. Installing Clients (Any time during or after upgrade)
Before you begin, make a copy of your existing configuration
and initialization files, including the OPAC files (if
desired). As indicated in Step 1, the tag tables for
cataloging have changed significantly. You must use the new
tag tables after the upgrade.
Download the new clients to a PC. The clients will be
delivered in three installation executables.
If you intend to use offline circulation, please see notes
in Step 1 for instructions for client installations.
In all cases, there will be three installation programs:
VoyagerConfig.EXE installs the directory structure and
default files
VoyagerPrograms.EXE installs the Voyager client
executables
VoyagerSystem.EXE installs the necessary system files
**Installing clients on NT or Win2000, you must be logged in
to the pc as the system administrator.
We recommend that these programs be run in the order listed.
5
Please note that the default directory for the new files to
be installed to is c:\voyager. You can change to a different
directory if you do not want to overwrite the 2000.1 version
of the clients.
Individual PC Installation
We suggest that each site install VoyagerConfig.EXE and
VoyagerPrograms.EXE in one location and update the generic
configuration (cfg) and initialization (ini) files with your
customizations. You can then distribute this customized
Voyager file structure to the individual PCs that will run
Voyager.
Then, VoyagerSystem.EXE must be run on each individual PC,
noting the caveat regarding old and new clients. If you wish
to run the VoyagerSystem.EXE installation in a 'silent
mode', simply run the installation from a command line with
the /s flag.
LAN Installation
You should install VoyagerConfig.EXE in the location on the
file server from where Voyager will be run, then update the
generic configuration (cfg) and initialization (ini) files
with your site's customizations.
Then, VoyagerPrograms.EXE should be run on the file server
from where Voyager will be run.
However, as the 32-bit clients require the system files to
be registered on each PC, the System Files installation must
be run on each individual PC that access Voyager. If you
wish to run the VoyagerSystem.EXE installation in a 'silent
mode', simply run the installation from a command line with
the /s flag.
Step 8. Post-Upgrade (After Upgrade)
After the upgrade is completed, the Endeavor upgrader will
contact you to begin your back-up process.
Please have your system administrator conduct a back up of
your Voyager system including all Oracle files.
Test your newly upgraded system. Go into each module and
perform familiar activities to see if the system performs as
expected.
If you did not prepare a WebVoyage test area pointing to the
Preview server, you will need to manually move in your
WebVoyage customizations. Please look at the configuration
changes document on SupportWeb. These have changed
significantly.
6
© 2002 Endeavor Information Systems, Inc.
Site related problems, supportwebmaster@endinfosys.com