Installing Destiny v9.8

Overview Welcome to Destiny! This document guides you through the installation of Follett Software Companys Destiny Resource Manager. Destiny uses Microsoft SQL Express as the database. This document includes the following sections:

Before you install Installation requirements

Server requirements Installing Destiny Logging in Backing up your database Setting up your site Troubleshooting

If you cancel the installation Installation error messages Uninstalling Destiny

Configuration file settings For additional help

Before you install Installation requirements Make sure that you have: Administrative rights to the Destiny server. Stopped and disabled (or removed) the World Wide Web Publishing service. Destiny uses the

same port (80) as IIS; running both services will create a conflict. Disabled any virus-protection and anti-spyware software that may be running. Server requirements Hardware and software In order to run the Destiny installation program, make sure your server meets or exceeds the minimum hardware and software requirements: Memory: 1 GB RAM required, 2 GB RAM recommended Hard drive space: 12 GB (10 GB for the Destiny database, 2 GB for SQL Express) Operating system: Windows XP Professional 32 bit, Service Pack 3 Windows XP Professional 64 bit, Service Pack 2 Windows Server 2003, Service Pack 2 Windows XP Professional (32-bit), Service Pack 3 Windows XP Professional (64-bit), Service Pack 2 Windows Vista Enterprise, Business or Ultimate, Service Pack 2 Windows 7 Enterprise, Business or Ultimate Windows Server 2008 Standard or Enterprise Server, Service Pack 2 Windows Server 2008 R2 Standard or Enterprise Server An Internet connection

Installing Destiny

Security recommendations Make sure that your Destiny server is physically located in a secured location. Make sure that you block the Destiny servers port 1099 from the Internet with a firewall.

Ideally, you should also use an internal firewall to block this port from network users. Destiny uses port 1099 internally.

If you are allowing public internet access to your Destiny server, your firewall should block all inbound ports, except port 80. If you are using secure login (https), you must also open port 443 inbound.

If you plan to use Z39.50 server and/or client, you will need to open at least one other port (inbound for clients and outbound if you are running a Z39.50 server). The standard Z39.50 port is 210. Library of Congress uses 7090.

Installing Destiny Once you have verified that you have the required hardware and software on your server, log on to the server with administrative rights. 1. Insert the Destiny Installation CD into the CD drive. Windows should start the installer

automatically. If it does not, from My Computer, open the CD drive directory and double-click SETUP.EXE.

2. You may configure the port settings that Destiny will use by clicking the Advanced button. Only do this if the defaults are not suitable for the server.

3. Click Start on the Destiny Installer dialog that appears. 4. After reading the Product Licensing Terms, select the Accept check box and click Ok.

A message will appear notifying you that statistical data about the server will be collected and sent to Follett. Click Ok. A message prompting you to temporarily disable any virus-protection and anti-spyware software that may be running appears. Once youve complied, click Ok to continue with installation.

5. At this point, the installer will check your system for several components that are required for the installation of SQL Express. If any of these components are not currently on your computer, a dialog appears with links that will allow you to download and install the necessary components. Once you have completed these steps, you must close and restart the installer by browsing to the CD drive directory and double-click SETUP.BAT. After double clicking, it may take a few seconds for the installer to start.

Note: If the installer encounters any condition that prevents the installation from continuing, an error message appears. If this happens, refer to the Installation error messages section of this document for the steps required to remedy the condition.

6. The Select Install Path dialog appears. Accept the default path, or click Browse to select another local directory.

Important: Make sure to select or create a path with directory (folder) names that have no spaces in them.

7. When you've selected the destination directory, click Ok to continue with the installation. 8. On the Destiny Installer dialog that appears, enter and confirm a password for the Destiny

administrator. The password cannot contain spaces and cannot be longer than 10 characters (at a minimum, an 8-character password containing letters and numbers is recommended).

This password provides complete access to all aspects of the Destiny application and the database; it should be kept secure. Important: Follett Software has no backdoor password utility for Destiny. Please record and save the Destiny Administrators password in a secure location.

Page 2 of 8 Copyright 2010 Follett Software Company 10742A Rev. 12 09-10-A

Installing Destiny

9. The installer will now install SQL Express and configure the Destiny database and service. This should take a few minutes.

10. When the final check mark appears on the main installer dialog and the Quit button changes to Close, click Close to end the installation.

During the installation, the installer started the services Destiny Server and SQLServer (Destiny). To verify that Destiny is running, click the Destiny shortcut on your Desktop, or open your browser and go to http://localhost or http://127.0.0.1.

Configuring your anti-virus software Because real-time virus checking of the Destiny database and application files can cause severe performance problems, you'll need to disable your virus-checker for the following files:

On the database server, turn off virus checking on files with extensions: MDF LDF NDF It is important to do this by file type, as this will cover both the Destiny database and SQL server's temporary database.

On the application server, turn off real-time virus checking on the FSC-Destiny folder. Important: Verify the next day that your exclusions are still in effect. If you make these exclusions locally but your network is configured to use a server-based manager to centrally manage your virus software (for example, Symantec Settings Manager Service), you need to check back the next day and make sure the manager is not overwriting your exclusions. If the exclusions are missing, you'll need to contact the person maintaining the virus software to allow the exclusions.

Logging in Destiny provides two default login accounts: Destiny Administrator: This login is intended for the technical personnel managing the Destiny

server. The login User Name is destinyadmin, and the password is the password you specified in step 7 (page 2). Note: For additional information about logging in and setting up Destiny, see Getting Started as a Destiny Administrator.

Site Administrator: This login is intended for the individual managing the Destiny site. The Site Administrator user name and password are created and displayed as you set up each site. Note: For additional information about logging in to Destiny, see Getting Started with Destiny Library Manager.

Important: Follett Software has no access to your user names and passwords. Please record and save all user names and passwords in a secure location.

10742A Rev. 12 09-10-A Copyright 2010 Follett Software Company Page 3 of 8

Installing Destiny

Backing up your database Before you begin setting up your site, it is highly recommended that you back up your database. It is important to establish a backup and restore plan for your Destiny installation. The plan must be validated and monitored to ensure that your data is sufficiently backed up and can be recovered in the event of hardware failure or other disaster. For more information regarding backing up or restoring your database, see Destiny system backups white paper in the Destiny Online Help.

Setting up your site The remaining setup tasks vary based on the source of your data, the subscription services you purchased, and your situation. They generally require the expertise of a library or textbook professional.

For the library, textbook, or asset specialist Provide your library, textbook, or asset specialists with the URL for Destiny. They will also need the appropriate Getting Started guide that you can find in the documentation folder provided with your Destiny installation CD.

For the workstations

To view and print reports and labels in Destiny, staff workstations need Adobe Reader version 5.05 or higher.

Troubleshooting

If you cancel the installation If you click Quit anytime during the installation, the following message appears:

Installation is not complete. Are you sure you want to quit?

Click Yes to cancel the installation.

Click No to continue with the installation.

If you answer Yes to this message, the following message appears: Attempt to remove the installed Destiny components?

Click Yes to remove installed Destiny components. Click No to close the installer without uninstalling.

Unless specified in the following instructions, we recommend that you select Yes to Attempt to remove the installed Destiny components? Then restart the installation. Note: The installed Destiny components refers only to the Destiny components that the installer has already installed.

Page 4 of 8 Copyright 2010 Follett Software Company 10742A Rev. 12 09-10-A

Installing Destiny

Installation error messages

is not a supported operating system.

During installer step 1, System configuration check, the installer found an unsupported operating system and canceled the installation. Install Destiny on a machine running Windows Server 2003, Windows Server 2003 Enterprise, Windows XP Professional, Windows 2008 Server, Windows Vista, Windows 2008 R2 Server, or Windows 7. Note: Verify that the latest Service Pack for the operating system is installed before installing Destiny.

Destiny service is already registered

During installer step 1, System configuration check, the installer found that Destiny is already registered. If you have previously installed Destiny: 1. Click No to the "Attempt to remove the installed Destiny components?" message. 2. Run the Destiny uninstaller (FSC-DESTINY\UNINSTALL\UNINSTALL.EXE). 3. Restart the Destiny installation.

Microsoft SQL Server with Destiny database is already registered as a service.

During installer step 1, System Configuration Check, the installer found an existing instance of SQL Server. Note: If you are attempting to upgrade an existing installation, refer to the document, "Upgrading to Destiny 9.8". 1. Click Yes to the "Attempt to remove the installed Destiny components?" message. (This

refers to the Destiny components that it has already installed; it does not refer to removing SQL Server components.)

2. After Step 1 completes, open Settings > Control Panel > Add/Remove Programs and locate SQL Server.

3. Find the instance of SQL Server with (DESTINY) appended, highlight it, and click Remove to uninstall it.

4. Restart the Destiny installation.

Microsoft SQL Server is already installed

During installer step 1, System Configuration Check, the installer found an existing install of the full version of Microsoft SQL 2005, Microsoft SQL 2008, or Microsoft SQL 2008 R2. Note: If you are attempting to upgrade an existing installation, refer to the document, "Upgrading to Destiny 9.8". Click Yes to the "Attempt to remove the installed Destiny components?" message. (This refers to the Destiny components that it has already installed; it does not refer to removing Microsoft SQL) Important: Destiny cannot be installed on a server running the full version of Microsoft SQL 2005, Microsoft SQL 2008, or Microsoft SQL 2008 R2.

10742A Rev. 12 09-10-A Copyright 2010 Follett Software Company Page 5 of 8

Installing Destiny

Destiny requires 1 GB of memory for operation. Your computer only has xxxMB of total memory.

During installer step 1, System Configuration Check, the installer found that the total RAM is less than 1 GB. 1. Click Yes to the "Attempt to remove the installed Destiny components?" message. 2. Add more memory to the computer. 3. Restart the Destiny installation.

Port 80 is in use on this computer.

During installer step 1, System Configuration Check, the installer found that another service is running on port 80. This generally occurs when IIS is installed on the server. There are two ways to fix this: Click the Advanced button and change the Web Server text field to a different port Remove the service that is using port 80, stop the service, or set its Startup type to Disabled in

Windows Services.

Port 1099 is in use on this computer.

During installer step 1, System Configuration Check, the installer found that another service is running on port 1099. There are two ways to fix this: Click the Advanced button and change the JNDI text field to a different port Remove the service that is using port 1099, stop the service, or set its Startup type to Disabled in

Windows Services.

To find your proxy settings...

During installer step 1, System Configuration Check, the installer checked for a proxy server by trying to access http://www.fsc.follett.com. It failed to access the site and assumed a proxy is required. If you have a proxy server: Follow the instructions in the Destiny Proxy Configuration tab to validate or enter your proxy

address and port number. If you do not have a proxy server: This server may not have a connection to the Internet. You must establish an internet connection and restart the Destiny installation.

Unable to install to the xx: \ drive. Please select another location.

During installer step 2, Copying application files, you selected a destination location that is on a network or removable drive. Click Ok and select another (local) drive.

The install path cannot contain spaces. Please select another location.

During installer step 2, Copying application files, you selected a destination location that has spaces in one or more directory names. Click Ok and select another directory path or rename the directory.

Page 6 of 8 Copyright 2010 Follett Software Company 10742A Rev. 12 09-10-A

Installing Destiny

Destiny requires # GB of hard drive space. Your computer only has # of hard drive space.

During installer step 2, Copying application files, the installer determined that the destination location does not have sufficient hard drive space. If you are installing Destiny to the same drive as SQL Express, you will need 12 GB of hard drive space. If Destiny is installed to a different drive, you will need 10 GB of hard drive space. 1. Click Ok. 2. Click Yes to the "Attempt to remove the installed Destiny components?" message. 3. Free up additional hard drive space. 4. Restart the Destiny installation.

Clicking Ok will continue with the installation.

To uninstall SQLExpress 1. Open the Windows Add/Remove Programs. 2. Highlight Microsoft SQL Server 2008 R2 and click Remove.

Uninstalling Destiny To uninstall Destiny, run uninstall.exe from the \Uninstall folder. Note: UNINSTALL.EXE must be run from a command prompt and not by double clicking on the file itself. The uninstaller removes everything except the uninstall log in the \UNINSTALL folder, and the \FSC-DATA and the \FSC-LOG directories. If you do not need the log files and database files, you can manually delete these folders. If the Destiny Service is still in the Services list, unregister it: 1. Open a command prompt. 2. Change directory to \FSC-DESTINY\JBOSS\BIN. 3. Type destiny unregister".

If SQL Express still exists, remove it: 1. Open Add/Remove Programs. 2. Click on Microsoft SQL Server 2008 R2.

3. Click Remove.

Configuration file settings You can find the config.properties file in the \FSC-DESTINY\FSC\BIN directory. It contains all of the technical information about the Destiny application. Any line that starts with a # is considered a comment line and is skipped by our software. To apply your changes: 1. Open a command prompt 2. Change the directory to FSC-DESTINY\FSC\BIN. 3. Type in CONFIG.BAT and press Enter.

Important: Do not run config.bat when Destiny is running.

10742A Rev. 12 09-10-A Copyright 2010 Follett Software Company Page 7 of 8

Installing Destiny

Page 8 of 8 Copyright 2010 Follett Software Company 10742A Rev. 12 09-10-A

Below are the specific entries that you can change, if needed:

Running on a port other than 80

You may specify the port to use at the beginning of the installation by clicking on the Advanced button. This will display default port settings that may be changed. If you would like to change the port after the installation has completed, modify this line to specify the port you want:

TOMCAT_PORT=80 Memory Settings

The installer will detect the available RAM on the machine and will configure the Destiny server using four predefined memory settings for machines having 1, 2, 3, and 4 or more gigabytes of RAM.

SSL

For information on setting up SSL with Destiny, please see the Configuring HTTPS support guide that is located in Destinys online help system. It contains instructions for generating and installing an encryption key pair for Destiny.

Z39.50 Server

If you want to use the Z39.50 Server included with Destiny, youll need to configure the following settings. If they are commented out, remember to remove the comment symbol (#):

ZSTART_SERVER=false Setting to start the Z39.50 Server. To turn it on, set to true.

#ZUSERNAME= If the Z39.50 server requires authentication, use this username.

#ZPASSWORD= If the Z39.50 server requires authentication, use this password.

#ZALLOWABLE_IP_MASK=192.168.*.* Filter option based on IP

#ZSERVER_IP_ADDRESS=127.0.0.1 The IP Address of the Z39.50 server

#ZSERVER_PORT=210 The Port of the Z39.50 server

#ZMAX_SESSIONS=50 Sets the number of individual ZClients that can simultaneously hit your database

#ZDATABASE_NAME=Main The name of your Z39.50 database

ZSHOW_HOLDINGS=true Option to set whether to pass back copy records to clients

ZUSMOC_SUBFIELD=a Subfield in the copy that contains the USMOC

ZSHORT_SITE_NAME_SUBFIELD=b Subfield in the copy that contains the Destiny Short Site Name

ZBARCODE_SUBFIELD=p Subfield in the copy that contains the copy barcode

ZCALL_NUMBER_SUBFIELD=h Subfield in the copy that contains the call number

ZPRICE_SUBFIELD=9 Subfield in the copy that contains the price

ZCOPY_NUMBER_SUBFIELD=t Subfield in the copy that contains the copy numbers

ZAVAILABILITY_SUBFIELD=y Subfield in the copy that contains the availability

ZFULL_SITE_NAME_SUBFIELD=4 Subfield in the copy that contains the Destiny Full Site Name

For additional help To access the About Destiny page, click Follett Software Company at the bottom of any Destiny page. Youll find Destinys version number, Follett Softwares address and telephone numbers, a link to the Follett Software web site, and email links to our Customer Service and Technical Support departments.

OverviewBefore you installInstallation requirements Server requirementsHardware and software Security recommendations

Installing Destiny Configuring your anti-virus softwareLogging inBacking up your databaseSetting up your siteFor the library, textbook, or asset specialistFor the workstations

TroubleshootingIf you cancel the installationInstallation error messages is not a supported operating system.Destiny service is already registeredMicrosoft SQL Server with Destiny database is already registered as a service.Microsoft SQL Server is already installedDestiny requires 1 GB of memory for operation. Your computer only has xxxMB of total memory.Port 80 is in use on this computer.Port 1099 is in use on this computer.To find your proxy settings...Unable to install to the xx: \ drive. Please select another location.The install path cannot contain spaces. Please select another location.Destiny requires # GB of hard drive space. Your computer only has # of hard drive space.To uninstall SQLExpress

Uninstalling Destiny

Configuration file settingsRunning on a port other than 80Memory SettingsSSLZ39.50 Server

For additional help