91 Install Program - Amadeus Hospitality · If the property is linked, install replication on the...

Newmarket International, Inc.For Internal Use Only

Document Version 1.6

1/31/03

Installation InstructionsFor 9.1 Delphi Suite

This version of the 9.1 Installation Instructions supersedes all other 9.1 Installation Instruction documents. As new issues are discovered, or hotfixes need to be applied, this document will reflect the necessary procedures you must perform. You are responsible for checking the Intranet’s IDD site frequently to ensure you have the most recent document.

Copyright

© 2003 Newmarket International, Inc. All rights reserved.

The information in this document is confidential and proprietary to Newmarket International, Inc., and may not be disclosed, copied, reproduced, published, translated or reduced to electronic medium or machine readable form, in whole or in part, without the prior written consent of Newmarket International, Inc.

Newmarket, Breeze, CVBreeze, CCBreeze, Functions Breeze, Delphi Multi-Property Edition are registered trademarks and Delphi is a registered service mark of Newmarket International, Inc. Delphi, Global SFA, Net Delphi, NetMetro, and NetData are trademarks of Newmarket International, Inc. MeetingBroker.com and NetXchange are service marks of Newmarket International, Inc.

Additional company and product names may be registered trademarks or trademarks of their respective companies.

Table of Contents

9.1 Installation Instructions

Documentation Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Pre-Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installation Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Procedure 1, Uninstall Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Procedure 2, Pre-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Procedure 3, Moving TempDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Procedure 4, Uninstall MTS from the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Procedure 5, Upgrading to 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Procedure 6, New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Procedure 7, Post-Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Procedure 8, Installing Hotfixes & New Manual Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Procedure 9, Install Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Procedure 10, Run Cleanup Procs and Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Procedure 11, Running 9.1 MeetingBroker 2-Way Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Appendix A - Manually Upgrading to 9.1 Database

Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

All upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.1.3b Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.2.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7.2.1 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

8.0 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

9.0 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Appendix B - Maintenance Mode

Modify – Select Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Repair –All Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Remove – All Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Document Version 1.6 iii

Table of Contents

Appendix C

MTS Registry Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Appendix D

Cleaning Up a SQL 6.5 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Appendix E

Updating BEOs and Banquet Checks from 7.1.3b or Earlier Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Appendix F

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Appendix G

Updating BEOs and Banquet Checks from 7.2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Document Version 1.6 iv

9.1 Installation Instructions

Documentation Revisions

Date Author Description of Revision

11/21/02 ver 1.2 draft A

SCushing • In the Manual Upgrade instructions in Appendix A, added a bullet to the “All Upgrades” section about running the Hotfixes for CR23016 and 23017.

• In the Manual Upgrade instructions in Appendix A, at the end of each upgrade section I added the following step:

Run Hotfix 22951

• In the Pre-Upgrade Steps procedure, added a bullet to run Hotfixes 23016 and 23017

• In the Hotfix Procedure, added running of CR 22951 which is need for both new and upgrades.

12/5/021.2 draft A continued

SCushing • Added Appendix F for troubleshooting (CR23279)• Added manual step for editing Delphi.ini with new NIWeb path (cr23169)

to Hotfixes and Manual Procedure section (Procedure 8). Also added to end of each Manual upgrade section in Appendix A.

12/18/021.2

SCushing • Added the location for hotfix and solution documents, as well as file updates: \\niftp\psg\download\delphi91

• Run the following hotfixes as part of Procedure 8: CR23021, CR23023, CR23084, for new installs and upgrades.

12/30/02ver 1.3

SCushing • Per CR23536, removed all references to running hotfixes 23016 and 23017

1/17/03ver 1.4

SCushing • Per CR23789, removed all references to running hotfix 22951.

1/23/03ver 1.5

SCushing • Per CR23801, added references to running hotfix 22951 back in to the installation instructions.

• Also per CR23801, added running of Solution S0010449• Per CR23865, removed references to running hotfixes and solutions from

manual instructions in appendix A, since the manual instructions are just for upgrading the database.

• Per CR23866, added a new hotfix to be run as part of Pre-Upgrade steps, CR23017.

Document Version 1.6 1

Documentation Revisions

1/31/03ver 1.6

SCushing • Per CR23977 - Created Appendix G (similar to Appendix E), and added step to Procedure 7, Post Upgrade Steps - If upgrading from 7.2.x, run the steps in Appendix G, Updating BEOs and Banquet Checks from 7.2.x, page 72.

• Per CR32978 - Added the following text to bullet 4 in Procedure 2-PreIn-stall tasks: The script can also be obtained from \\niftp\PSG\down-load\delphi91\712a to713b.zip.


Pre-Installation Worksheet


Use this worksheet to gather important information about your system prior to starting the installation application. The installation application will pick up certain information and place it in the dialog boxes but it may also be helpful to complete this worksheet.

Enter Information Description

Database Server Name

SQL Server System Administrator (SA) Password:

Database Name

Name of database backup file

Location of database backup file

Application Server Name (if different than DB server)

If Upgrading Existing Hardware:

Size of Nss_Database.mdf

Location of current NGS directory

Recovery Model setting

Note: This setting is found in the Properties tab of the SQL Enterprise Manager.

Newmarket Disaster Recovery jobs status:

� Exist� Don’t Exist� Disabled

PID/GID

Note: If you are performing a new install or upgrading from 7.1.3x, get this information from your Business Consultant. If upgrading from 7.2 or later, get the information from the Global_ID table.



Link Date

Note: If the site is linked, you need the link date for each property. Get this information from the Engagement Manager.

Banquet Check and BEO Names

Note: This applies to 7.1.3b or earlier upgrades.

Note: There is only one banquet check but may be multiple BEO.

Tip: See Appendix E, Updating BEOs and Banquet Checks from 7.1.3b or Earlier Version, page 69.

List of BEO & Banquet Check Tem-plates:


Installation Checklists


New Installations

Upgrade Installations

�Run script to move TempDB, and change the size of the database. See 9.1 Installation Instructions, Procedure 3, Moving TempDB, page 12.

�Run 9.1 Installation Program for a New Installation. See 9.1 Installation Instructions, Procedure 6, New Installation, page 29.

�Add hotfixes. See 9.1 Installation Instructions, Procedure 8, Installing Hotfixes & New Manual Procedures, page 40.

�If the property is to be linked, install replication on the global and property servers. See 9.1 Installation Instructions, Procedure 9, Install Replication, page 42.

�Once replication is turned on, if applicable, run proc_fix_allocate. See 9.1 Installation Instructions, Procedure 10, Run Cleanup Procs and Queries, page 43.

Note: The proc is not run at a Global Sales site.

�If the property is linked, uninstall replication. See 9.1 Installation Instructions, Procedure 1, Uninstall Replication, page 9.

Important: It is critical that you uninstall replication before starting the installation.

�Complete upgrade pre-installation steps. See 9.1 Installation Instructions, Procedure 2, Pre-Upgrade Steps, page 10.

�Run script to move TempDB, and change the size of the database. See 9.1 Installation Instructions, Procedure 3, Moving TempDB, page 12.

�Uninstall MTS. See 9.1 Installation Instructions, Procedure 4, Uninstall MTS from the Server, page 15.

�Run 9.1 Installation Program to upgrade to New or Existing Hardware. See 9.1 Installation Instructions, Procedure 5, Upgrading to 9.1, page 17.

�Complete Post-Installation Steps. See 9.1 Installation Instructions, Procedure 7, Post-Upgrade Steps, page 39.

�Add hotfixes. See 9.1 Installation Instructions, Procedure 8, Installing Hotfixes & New Manual Procedures, page 40.



�If the property is linked, install replication on the global and property servers. See 9.1 Installation Instructions, Procedure 9, Install Replication, page 42.

�Run clean up procs and queries. See 9.1 Installation Instructions, Procedure 10, Run Cleanup Procs and Queries, page 43.

�If you are upgrading a site that is using MeetingBroker 2.0 with the integration client component, you must install the upgrade for MeetingBroker with 9.1. See 9.1 Installation Instructions, Procedure 11, Running 9.1 MeetingBroker 2-Way Upgrade, page 44.


Prerequisites

Prerequisites

This document contains instructions for new installations including migrations and Quad-base upgrades, and sites on versions 7.1.2a and later. If the site is on an older version, please call NI Support before proceeding.

• Ensure the following applications are present:

– Windows NT4 with service pack 6a or Windows 2000 with service pack 3

– Internet Explorer 6.0 or later

Note: IE 6.0 is provided with the release

– SQL 2000 SP2

Note: If you are installing SQL2000 on a server that has an older version of SQL installed, do not install it as a Named Instance. It will cause the 9.1 Installer to fail.

• You must have admin rights on the local machine

• For upgrades only - On the device where the NI_Backup subdirectory resides, verify there is enough available free space to store 3 times the size of the NI_Data.mdf file. If you create your own backup prior to the upgrade (i.e. running the DRecovery job) and select No when prompted to create a backup, verify there is enough available free space to store 1 times the size of the NI_Data.mdf file.

• If this is a new installation, you must have a 9.1 database backup file provided by Newmarket International.

Data Source Names Important Note: In the implementation of MTS, the Data Source Name (DSN) in the ODBC Administrator is case sensitive. You must make sure that the registry entries use the same case sensitive Data Source Name.


Overview

Overview

The 9.1 Installation CD allows you to install a new 9.1 application or upgrade a previous version of the application to 9.1. You can upgrade on the same server where the previous version exists or upgrade to a new server.

During installation you are presented with three options for installation:

The 9.1 Installation includes the installation of three components: Database, Application, and MTS. The three components may be installed to the same server or three different servers depending on the site’s situation.

New InstallationSelect the New Installation if the site has not previously installed any of Newmarket International’s Delphi family of products.

Upgrade to New Hardware

Select Upgrade to New Hardware if you want to install the application component for 9.1 to a different server than where the previous version is installed.

Upgrade to Existing Hardware

Select Upgrade to Existing Hardware if you want to install the application component for 9.1 on the same server where the previous version exists.


Procedure 1, Uninstall Replication

Procedure 1, Uninstall Replication

Important: It is critical that you uninstall replication before proceeding to the next procedure.

• If you are upgrading an application in a linked database environment, uninstall replication from all properties and global servers. Please refer to the Config Property link 7 and 2000.pdf and Global Link Prep 7 and 2000.pdf documents for instructions on uninstalling replication.

• If the environment is not linked, you do not need to run this procedure. Proceed to 9.1 Installation Instructions, Procedure 3, Moving TempDB, page 12.

Once replication has been uninstalled, proceed to 9.1 Installation Instructions, Procedure 2, Pre-Upgrade Steps, page 10.


Procedure 2, Pre-Upgrade Steps


This procedure is only used if you are upgrading from 7.1.2.x, 7.1.3.x, 7.2, 7.2.1, 8.0, or 9.0 to 9.1. If installing a new application, proceed to 9.1 Installation Instructions, Procedure 6, New Installation, page 29.

� Verify all users are logged out. If users are logged on, send a message warning them that the system will be coming down.

� Unshare the NGS subfolder.

� Stop and restart SQLServer.

� If upgrading from version 7.1.2a or 3.1.2a, you must upgrade to 7.1.3b prior to starting the 9.1 installation. To upgrade to 7.1.3b, run the 712a_to_713b.sql script contained on the PSG_TS CD. The script can also be obtained from \\niftp\PSG\download\delphi91\712a to713b.zip.

� If you are upgrading from 3.1.3a, 3.1.3b, or 7.1.3a, run the following query in the Query Analyzer:

update globalid set version_id = ‘7.1.3b’

� If upgrading from 7.1.3.b you must perform the following:

Note: Even if you just upgraded to 7.1.3b from an earlier version, you must perform the following.

— Complete the steps in Appendix D, Cleaning Up a SQL 6.5 Database, page 67.

— If upgrading from 7.1.3b on existing hardware, you must manually create the MTS DSN.

— Use the SQL Upgrade Wizard to convert the database to SQL 2000 on the existing server. If you are upgrading to a new server, install SQL2000 on the server, then convert the NSS_Database to SQL2000.

� If upgrading to a new server from 7.2 or greater, load SQL2000. Then backup the SQL database and copy the backup file to the new server. You can then optionally restore the NSS_Database. If the upgrade program detects NSS_Database, it will simply upgrade it. If the NSS_Database cannot be detected, you will be prompted for the backup file location during the upgrade.

� If you are upgrading to a new server, share the NGS folder on the old server. Set up the share with the User Name that will be used to log on to the new server.

� Check the Recovery Model from the Properties tab in SQL’s Enterprise Manager. Enter the setting in the 9.1 Installation Instructions, Pre-Installation Worksheet, page 3. You will need this setting later if the model is not set to



Simple. The upgrade program automatically sets the Recovery Model to Simple so if it was not set to Simple, you will need to change it after the upgrade is complete.

� Check to see if the Newmarket disaster recovery jobs exist or if they are disabled. Enter the setting in the 9.1 Installation Instructions, Pre-Installation Worksheet, page 3. If the jobs do not exist or are disabled, the site is probably using their own disaster recovery procedures. Since the upgrade program automatically enables the Newmarket disaster recovery jobs, you may need to disable or remove the Newmarket ones after the upgrade is complete.

� Run Hotfix CR23017. The hotfix, solution, and file updates are located on:

\\niftp\PSG\download\delphi91

Once you have performed all of the pre-upgrade steps, proceed to 9.1 Installation Instructions, Procedure 3, Moving TempDB, page 12.


Procedure 3, Moving TempDB


Beginning with 9.1, performance reports no longer write temp data into tables within NSS_Database. Instead, temp data is now written to the TempDB device.

Review the 9.1 hardware specifications document to determine where the TempDB device should be located based on the number of users. If necessary, move the TempDB database.

If it is not necessary to move the TempDB database, skip this procedure.

1. From Start, point to Programs, Microsoft SQL Server 2000, and click Query Analyzer.

Run the Movetempdb.sql Script

2. Open the Movetempdb.sql script from NGS\Utils\Steps.

The script appears as follows:

USE master

go

ALTER DATABASE tempdb MODIFY FILE (NAME =

tempdev, FILENAME = 'E:\tempdb.mdf')

go

ALTER DATABASE tempdb MODIFY FILE (NAME =

templog, FILENAME = 'E:\templog.ldf')

go

where NAME refers to the logical name of the tempdb database and log files, and where FILENAME refers to the new location of the tempdb files.

3. Edit the FILENAME entries only.

The FILENAME path should be the same as the location of the NI_BACKUP folder.

Note: Do not change the NAME entries in the script.

4. Click the Play button to run the script.

5. Once you have run the script, you must restart the mssqlserver service in order for the script to take affect.



Change the size of TempDB

6. From Start, point to Programs, Microsoft SQL Server 2000, and click Enterprise Manager.

7. Expand the SQL Server Group, and then expand the server.

8. Expand the Databases folder.

9. Right-click the TempDB database, and click Properties.

10. Click the Data Files tab.

11. In the Space allocated (MB) column, click the cell to change and enter the new value. The new value must be larger than the existing value.

We recommend the following:



– For databases smaller than 500MB, set the size of tempdb to 200MB.

– For databases between 500MB and 1GB size of tempdb to 350MB.

– For databases larger than 1GB, set the size of tempdb to 500MB.

12. Under File properties select the Automatically grow file option.

This allows tempdb to grow as more data space is needed.

13. Select the By percent option and select 20%.

The file will grow 20% of the current file size.

14. Under Maximum File Size, select the Unrestricted file growth option.

This allows the file to grow as much as necessary.

15. Do one of the following

– If you installing a new 9.1 application proceed to 9.1 Installation Instructions, Procedure 6, New Installation, page 29.

– If you are upgrading an existing application to 9.1, proceed to 9.1 Installation Instructions, Procedure 4, Uninstall MTS from the Server, page 15.


Procedure 4, Uninstall MTS from the Server


Removing the client Newmarket Package

Remove the client Newmarket Package from the MTS server(s).

1. Shut down the Newmarket Package. The steps needed to shut down the Newmar-ket Package on an MTS Server differ for Windows 2000 and NT 4.0. Do one of the following:

– For Windows 2000 using component services, proceed to 9.1 Installation Instructions, Windows 2000 Using Component Services, page 15.

– For NT 4.0 using Transaction Explorer, proceed to 9.1 Installation Instructions, NT 4.0 Using Transaction Explorer, page 15.

Windows 2000 Using Component Servicesa. Go to File\Programs\Administrative Tools\Component Services.

b. Double-click Computers\My Computer\Com+.

c. Highlight the Newmarket package, and then right-click and choose Shut Down.

Proceed to step Step 2.

NT 4.0 Using Transaction Explorera. Go to File\Programs\Windows NT 4.0 Option Pack\Microsoft

Transaction Server\Transaction Server Explorer.

b. Double-click Computers\My Computer\Packages Installed.

c. Highlight the Newmarket package, and then right-click and choose Shut Down.

Proceed to step Step 2.

2. Delete the Newmarket Package.– Right click the package and choose Delete. At the prompt, click Yes.

3. Delete components in the NI_Com folder and/or the NI_Objects folder. 4. Go to Add/Remove Programs to see if there is a Newmarket (proxy). If it is

present, remove it. Also, check to see if there is a Newmarket (remote) applica-tion. If there is one, remove it.

Note: If there are multiple entries, you will only be able to remove one. The others cannot be removed.

5. Go to the Programs File folder and do the following:– If there is a Com Plus folder, determine which of its subfolders contains

Newmarket DLL files (i.e. klserver.dll). Once you find the subfolder, delete the entire subfolder.



6. Go to the Programs Files folder and do the following: – If there is a Remote Application folder, delete it. 2000 machines should

not have this folder. If newmarket.exe was run on the server, this folder will appear. This usually happens if a site runs workstation setup on the server.

7. Run the regclean.exe from the Utils\Regclean directory in the present NGS folder.8. To fix errors, click Fix. A .reg file will be created in the Utils\Regclean directory

to undo any fixes.9. Reboot the server.

Proceed to 9.1 Installation Instructions, Procedure 5, Upgrading to 9.1, page 17.


Procedure 5, Upgrading to 9.1


The following procedures are used when upgrading a previous version of a Newmarket Product (Delphi Single or Multi-Property Edition, Select Edition, or Global Sales Edition) to the 9.1 version.

You may upgrade the application on an existing Newmarket server or another server, referred to as New Hardware.

Note: If you install to a different server, the installation program asks you for the UNC path to the existing Newmarket application server’s NGS directory.

1. Insert the Delphi Suite 9.1 Installation CD into the CD-ROM drive of the server where you are installing the product. The installation program automatically starts.

Note: If the installation program does not start automatically, run Setup.exe from the CD drive.

The Welcome window appears.

Note: If the Modify, Repair, or Remove window appears instead of the 9.1 Welcome window, this means the 9.1 installation was already run at least once. If a component failed during installation, you may need to rerun the 9.1 Install program. See Appendix B, Remove – All Installed Components, page 64 for instructions on running the Remove program. Once Remove has been performed you can reopen the 9.1 Welcome window to install one or more components.

2. Click the Next button.

The Software License Agreement window appears.

3. Read the Software License Agreement and click Yes.



Note: If you do not agree with the Software License Agreement click No then Yes to exit the installation program.

The User Registration window appears.

4. Enter the following:

– In the User Name box, enter the desired user name.

– In the Company Name box, enter the property name.

– In the Authorization Code boxes, enter the code supplied by Newmarket International.

Note: By default, the User Name and Company Name boxes are populated with information from the registration.

5. Click Next.

The Select Information Type window appears.

6. Do one of the following:

– Select the Upgrade to New Hardware option if you have a previous version of the application on the local server but you want to upgrade the application to a new server.

– Select the Upgrade on Existing Hardware option if you are upgrading the previous version of the application on the local server.

7. Click Next.



The Select Installation Options window appears.

8. Select the check box to the left of all components.

Note: If Microsoft SQL 2000 is not installed on the local server, the Database Component option is not available. In this case, click Cancel to exit the upgrade. Then install SQL 2000 and restart the upgrade program.

9. Click Next.

Database Component Selections

The DB Server Login Info window appears.

Note: If you run the installation program and only the database component fails, and then you run the installation program again, the existence of the NGS folder causes the installation program to enter the Maintenance Mode. You will not be able to access the “Select Installation Options” window. In this case, upgrade the database using the manual steps listed in Appendix A - Steps to Manually Upgrade to 9.1 Database.




– In the Database Server Name box, enter the name of the server where the database is located (the default is the name of the server where you are installing the program).

– In the SQL Systems Administrator (sa) Password box, enter the sa name.

– In the Database Name box, enter the name of the database (the default is NSS_DATABASE).

11. Click Next.

Clicking Next causes the installation program to see if replication is running. If so, the following message appears:

Important: If this message appears, you have not properly uninstalled replication. Using the task manager, end the Upgrade Program task and uninstall replication before attempting the upgrade again.

One of the following occurs:

• If the upgrade program does not detect NSS_Database, it will attempt to restore it and you will be prompted to fill in the Database Backup File Name and Location window. See Step 12.

• If NSS_Database is detected, the Database File Location Info window appears. See Step 17.

12. Click Browse to select the location where the database backup file (i.e. DMPE.bak) is located.



The Choose Folder window appears.

13. Browse to the folder where the database backup file is located and click OK.

The location is now displayed under Full Path.

14. In the Enter File Name box, enter the name of the database backup file.

15. Click Next.

The Database File Location Info window appears.

By default, the database, index, and log files are placed in NI_DATA on the local hard drive containing the largest amount of available space. If you select a different drive without selecting a folder you may need to add NI_DATA to the path entry box. The installation program creates the new NI_DATA folder.

Important: The program does not detect the existing database or file locations when you are performing an upgrade. You must enter the correct path in the Database File Location Info window.

If multiple data drives are available, it is recommended the log file be placed on a separate drive from the database file.



16. If you want to change the location of one of the files, i.e. the log file location, click the appropriate Browse button.


17. Browse to the folder where you wish to place the files, i.e. log files, and click OK.

18. Repeat Step 16 - Step 17 for any of the other file locations you want to change.

19. Click Next.

The Select Database Environment window appears.

20. Select the Non-Linked option.

Note: If the database is to be linked, you will link the database manually after the upgrade is complete.

21. Click Next.



If you are upgrading to existing hardware, the Select Database Backup Option window appears.

MTS Services Component Selections

If you selected the MTS Services Component option to install, the MTS Installation Information window appear.

22. If you selected Upgrade on Existing Hardware in Step 6, the Enter/Select the directory location of the existing MTS Objects box is displayed. Enter the path where the existing NI_COM or NI_OBJECTS is located. You can use the Browse button to select the location.

Note: This entry only appears when you are upgrading to existing hardware.

23. In the Enter/Select the directory location to install the MTS Objects box, enter the path where you want to install the new NI_COM objects. You can use the Browse button to select the location.

Note: This is where the MTS objects associated with the Newmarket package will be located. The default is the NI_COM on the fixed drive with the largest amount of free space. If you are performing an upgrade, the program does not

This entry only appears when you are upgrading on existing hard-ware



detect your existing NI_COM or NI_OBJECTS folders exist. You must browse to the correct path.

24. In the User Login box, enter the user name and password.

Note: The user must have administrator privileges to perform actions on the local machine. The default is NIAdmin.

25. In the Database Server Name box, enter the name of the database server to which you are connecting.

The Database Server Name box defaults to the name of the local machine if you selected the Database Component option in step 8. If you did not select this option, the Database Server Name box is blank and you must enter the name of the database server to which you are connecting.

26. Click Next.

Application Component Selection

If you selected the Application Component option to upgrade, the Application Destination Location window appears.

27. Click the Browse button to select the location of the NGS directory.

Note: The default entry is NGS on the fixed drive with the largest amount of free space.

28. The Enter the name of the application server if different than the default box, defaults to the name of the local machine. Change if necessary.

29. Under Date Format, select the appropriate date format to be used for installing the correct Details files.

30. Click Next.

One of the following occurs:



If Upgrading toExisting Hardware

The Start Copying Files window appears. Proceed to Step 35.

If Upgrading to NewHardware

If you selected Upgrade to New Hardware in Step 6, once you specify the application destination in Step 27 - Step 29, clicking Next opens the Previous Application Version UNC Path window.

Note: This window only appears when installing to New Hardware.

31. Enter the path where the NGS directory is located. The path must include the shared server and NGS folder, i.e. \\servername\NGS.

32. Click Next.

Previous Version Number

This window appears only if the database component was not selected.

33. Select the version of the Delphi product that is already on the server.

34. Click Next.



The Start Copying Files window appears.

Start Copying Files

Once information has been gathered for the installation, the Start Copying Files window appears. The selections you made during the installation are displayed in the window. You can select the Back button if you want to revise any of the selections, or click Next to continue the installation with the selections you chose earlier.


– Click the Back button to make changes to the selections.

– Click Next to continue.

Database ComponentInstallation

If the database component was selected in step 8, the selected database is installed. Prior to installing the database, SQL Server is stopped and started. A series of messages appear showing you various steps in the installation.

Once the database has been restored, SQL Server starts and stops.

MTS ServicesComponentInstallation

If the MTS Services Component option was selected in Step 8 several message boxes appear informing you of the progress of the MTS installation.

Note: If the MTS installation fails (i.e. you type in an incorrect password), the 9.1 installation program may prompt you to try the MTS installation again. If this occurs, select No, and install MTS manually.

ApplicationComponentInstallation

If the Application Component option was selected in Step 8, all critical user files are copied to a temporary directory while the new files are installed. Once the installation of the new files is complete, the critical user files are copied back to the appropriate directories.

A setup status window appears with a progress bar showing the installation of program files to the NGS directory.



Once the files have all been copied, the installation error log opens. Any errors that occurred during installation are displayed in the log.

36. Make note of any errors and call Newmarket’s Technical Support.

Note: The error log file can be found on the root of the C:\ drive and is named InstallError.log.

37. Click Next.

A window appears asking if you have Quick Address Pro (QAP) installed.


– If you do not have QAP installed, click No.



– If you have QAP installed, click Yes. The Location of QAPro Data Directory window appears.

39. Enter the path where the QAP executable is located.

The final window appears, InstallShield Wizard Complete.

40. Click Finish to complete the installation.


Proceed to 9.1 Installation Instructions, Procedure 7, Post-Upgrade Steps, page 39.


Procedure 6, New Installation


The following procedures are used when installing a Delphi product at a site that has not previously installed any of Newmarket International’s Windows-based products.

If you are performing a new installation, make sure you have performed Procedure 3, Moving TempDB, page 12.

If you are upgrading a previous version to 9.1, please refer to the Upgrade Installation section of the Installation Checklists, page 5.

1. Insert the Delphi Suite 9.1 Installation CD into the CD-ROM drive of the database server. The installation program automatically starts.

Note: If the installation program does not start automatically, run Setup.exe from the CD drive.

The Welcome window appears.

Note: If the Modify, Repair, or Remove window appears instead of the 9.1 Welcome window, this means the 9.1 installation was already run. If a component failed during installation, you may need to rerun the 9.1 Install program. See Appendix B, Remove – All Installed Components, page 64 for instructions on running the Remove program. Once Remove has been performed you can reopen the 9.1 Welcome window to install one or more components.

2. Click the Next button.

The Software License Agreement window appears.

3. Read the Software License Agreement and click Yes.

Note: If you do not agree with the Software License Agreement click No then Yes to exit the installation program.



The User Registration window appears.


– In the User Name box, enter the desired user name.

– Ιn the Company Name box, enter the property name.

– In the Authorization Code boxes, enter the code supplied by Newmarket International.

Note: By default, the User Name and Company Name boxes are populated with information from the registry.

5. Click Next.

The Select Installation Type window appears.

6. Ensure the New Installation option is selected.

7. Click Next.



The Select Installation Options window appears.

8. Select the check box to the left of each component you want to install on this server.

Note: If Microsoft SQL 2000 is not installed on the local server, the Database Component option is not available. In this case, click Cancel to exit the upgrade. Then install SQL 2000 and restart the upgrade program.

9. Click Next.

Database Component Selections

If you selected the Database the DB Server Login Info window appears.


– In the Database Server Name box, enter the name of the local server.

– In the SQL Systems Administrator (sa) Password box, enter the sa password.



– In the Database Name box, enter the name of the database (the default is NSS_DATABASE).

11. Click Next.

The Database Backup File Name and Location window appears.

12. Click Browse to select the location where the database backup file (i.e. DMPE.bak) is located. (The database backup file is provided by Newmarket International).


13. Browse to the folder where the database backup file is located and click OK.

The location is now displayed on the Database Backup File Name and Location window.

14. In the Enter File Name box, enter the name of the database backup file you received from Newmarket.

15. Under Full Path, verify the path and backup file name are correct.



16. Click Next.

The Database File Location Info window appears.

By default, the database, index, and log files are placed in NI_DATA on the local hard drive containing the largest amount of available space. If you select a different drive without selecting a folder you may need to add NI_DATA to the path entry box. The installation program creates the new NI_DATA folder.

If multiple data drives are available, it is recommended the log file be placed on a separate drive from the database file.

17. If you want to change the location to one of the files, i.e. the log file location, click the appropriate Browse button.


18. Browse to the folder where you wish to place the files, i.e. log files, and click OK.

19. Repeat Step 17 - Step 18 for any of the other file locations you want to change.

20. Click Next.



The Select Database Environment window appears.

21. Select the non-linked option.

Note: If the database is to be linked, you will link the database manually after the installation is complete. Under no circumstance are you to ever choose the linked option on this window.

22. Click Next.

MTS Services Component Selections

If you selected the MTS Services Component option to install, the MTS Installation Information window appears.

23. If you want to change the location from the default, do one of the following:

– In the Enter/Select the directory location to install the MTS Objects box, enter a new path for NI_COM.

– Click the Browse button to select a different location.



Note: This location is where the MTS objects associated with the Newmarket package will be located. The default folder is the NI_COM on the fixed drive with the largest amount of free space. You can enter a folder that does not exist and the installation program will create the folder.

24. In the User Login box, enter a user name.

Note: The user must have administrator privileges to perform actions on the local machine. The default NIAdmin user login is created by the installation program.

25. In the Password box, enter the user’s password.

26. In the Database Server Name box, enter the name of the database server to which you are connecting.

The Database Server Name defaults to the local server name.

27. In the DSN Name box, enter the MTS DSN Name that will be used.

The Database Server Name box defaults to MTS_< local server name> (i.e. MTS_Delphi) if you selected the Database Component option in step 8, and the database is located on the local machine. If you did not select this option, the Database Server Name box is blank and you must enter the name of the database server to which you are connecting.

28. Click Next.

Application Component Selections

If you selected the Application Component option to install, the Application Destination Location window appears.

29. Click the Browse button to select the location where the NGS folder is to be installed.

Note: The default entry is NGS on the fixed drive with the largest amount of free space.



30. The Enter the name of the application server if different than the default box, defaults to the name of the local machine. Change if necessary.

31. Under Date Format, select the appropriate date format to be used for installing the correct Details files.

32. Click Next.

Start Copying Files Once information has been gathered for the installation, the Start Copying Files window appears. The selections you made during the installation are displayed in the window. You can select the Back button if you want to revise any of the selections, or click Next to continue the installation with the selections you chose earlier.


– Click the Back button to make changes to the selections.

– Click Next to continue.

Database Component Installation

If the database component was selected in Step 8, the selected database is installed. Prior to installing the database, SQL Server is stopped and started by the installation program. The following messages appear with the status of the database installation: Restoring Database File, and Running Stored Procedures.

MTS Services Component Installation

If the MTS Services Component option was selected in Step 8, several message boxes appear informing you of the progress of the MTS installation.

Note: If the MTS installation fails (i.e. you type in an incorrect password), the 9.1 installation program may prompt you to try the MTS installation again. If this occurs, select No, and install MTS manually.



Application Component Installation

If the Application Component option was selected in Step 8, a setup status window appears with a progress bar showing the installation of program files to the NGS directory.

Once the files have all been copied, the installation error log opens. Any errors that occurred during installation are displayed in the log.

34. Make note of any errors and call Newmarket’s Technical Support.

Note: The error log file can be found on the root of the C:\ drive and is named InstallError.log.

35. Click Next.



A window appears asking if you have Quick Address Pro (QAP) installed.


– If you do not have QAP installed, click No.

– If you have QAP installed, click Yes. The Location of QAPro Data Directory window appears.

37. Enter the path where the QAP executable is located.

The final window appears, InstallShield Wizard Complete.

38. Click Finish to complete the installation.

Proceed to 9.1 Installation Instructions, Procedure 8, Installing Hotfixes & New Manual Procedures, page 40.


Procedure 7, Post-Upgrade Steps

Procedure 7, Post-Upgrade Steps

� Reset Recovery Model if it was not set to Simple prior to this upgrade.

Note: If the Newmarket DR jobs are being used, this must be set to Full.

� If NI DR jobs were disabled or did not exist prior to the upgrade, disable them or remove them.

� If the job NI_Queue_Purge exists, delete it.

� If the job Ni_Nightly_Account_Access exists, delete it.

� Check for contents in the NI_Temp folder. If there are any files, delete all of them but keep the Ni_Temp folder itself.

� If the site is linked, go into Setup and update the Link Date field.

1.From File, click Setup.

2.Click Property Details.

3.In the Link Date field, enter the correct link date.

The Engagement Manager should have supplied you with the link date for each property in the database.

Note: You will not be able to run the Veribook Utility until the link data field is populated.

� Log on to Delphi or Global as Breezeop and run the Update User List utility.

1.From File, point to Utilities, and click Newmarket Tools.

2.Select the Update User List tool.

3.Click OK.

Note: This step may not always be required but it is recommended that you run the tool to ensure the user list is accurate.

� If upgrading from 7.1.3b or earlier, run the steps in Appendix E, Updating BEOs and Banquet Checks from 7.1.3b or Earlier Version, page 69.

� If upgrading from 7.2.x, run the steps in Appendix G, Updating BEOs and Banquet Checks from 7.2.x, page 72.

� If upgrading to new hardware, copy the contents of NGS\Forms from the old server to NGS\Forms on the new server (overwrite like-named files if they exist).

� Verify NGS\MVSETUP exists. If it does not, run the 9.1 Installation program, select Repair, and verify again.


Procedure 8, Installing Hotfixes & New Manual Procedures

� If upgrading to new hardware, copy all of the user’s Word documents, Excel spreadsheets, and Market Vision queries to the new server in the same locations as on the old server.

Note: Check MKTVISN\MARKETVISIONUSER\QUERIES as a starting point.

� Copy NIMTSCLEANUP.EXE from the MTS Cleanup Utility sub-folder on the 9.1 Installation CD, to NGS\Utils\RegClean sub-folder.

Proceed to 9.1 Installation Instructions, Procedure 8, Installing Hotfixes & New Manual Procedures, page 40.


Below is a list of hotfixes and/or manual procedures that should be applied after you have completed the above procedures. Hotfix documents, solutions, and any file updates are located on:

\\niftp\PSG\download\delphi91

Hotfixes to Apply

Upgrades Run the following hotfixes if you are performing an upgrade to 9.1.

� Run hotfixes: CR22951, CR23021, CR23023, CR23084

� Run solution: S0010449

New Installs Run the following hotfixes if you are performing an new 9.1 installation.

� Run hotfixes: CR22951, CR23021, CR23023, CR23084

� Run solution: S0010449

Manual Procedures

Upgrades Run the following manual procedure(s) if performing an upgrade to 9.1.

� Edit the 'NIWeb' line in the [DELPHI] section of the Delphi.ini as follows:

NIWeb=www.newmarketinc.com

New Installs Run the following manual procedure(s) if performing a new 9.1 installation.



� Edit the 'NIWeb' line in the [DELPHI] section of the Delphi.ini as follows:

NIWeb=www.newmarketinc.com

Once you have performed the necessary hotfixes and manual procedures, proceed to one of the following:

– If you installing a new 9.1 application in a linked environment, proceed to 9.1 Installation Instructions, Procedure 9, Install Replication, page 42.

– If you installing a new 9.1 application in a non-linked environment, proceed to 9.1 Installation Instructions, Procedure 10, Run Cleanup Procs and Queries, page 43.

– If you are upgrading an existing application to 9.1, proceed to 9.1 Installation Instructions, Procedure 7, Post-Upgrade Steps, page 39.


Procedure 9, Install Replication

Procedure 9, Install Replication

If you installed or upgraded an application in a Linked database environment, install replication to all properties and global servers. Please refer to the Config Property link 7 and 2000.pdf and Global Link Prep 7 and 2000.pdf documents for instructions on installing replication.

• Once you have installed replication, proceed to 9.1 Installation Instructions, Procedure 10, Run Cleanup Procs and Queries, page 43.


Procedure 10, Run Cleanup Procs and Queries

Procedure 10, Run Cleanup Procs and Queries

Linked or Non-Linked

Whether or not the property is linked, Proc_Fix_Allocate must be run after the installation. If the property is linked, this proc must be run after replication has been reinstalled and turned on.

RunProc_Fix_Allocate

Note: Do not run the proc at a Global Sales site.

1. Open the Query Analyzer from Start/Programs/Microsoft SQL Server.

2. Before the Query Analyzer opens you must log on to the server. If it is not available from the SQL Server drop down box, enter it by hand into the SQL Server entry.

3. Enter the appropriate password for the server.

4. Click OK. This opens the Query Analyzer.

5. From the Query Analyzer select the drop down box for DB and select the NSS_Database.

6. Type proc_fix_allocate and select the Execute Query (F5) button.

Linked Only If the site is linked, after you run the Proc_Fix_Allocate proc mentioned above, the following steps must be performed.

Run Queries The following two queries must be run from the Query Analyzer:

Note: Run both queries at the property and global sites.

• Update Country Set Import = Import

• Update Currency Set Import = Import

Run Replication Cycle Once you have run the two queries, you must force a replication cycle.

Run Compare/Repair Once the replication cycle is complete, run the compare/repair and check that the Country and Currency tables have no row count violations. Please see the Configure and Establish Link document for more details on running the compare/repair. The document is located on the Intranet’s IDD site, under any product version.

Do one of the following:

If the site is using MeetingBroker 2.0, proceed to 9.1 Installation Instructions, Procedure 11, Running 9.1 MeetingBroker 2-Way Upgrade, page 44.


Procedure 11, Running 9.1 MeetingBroker 2-Way Upgrade

Procedure 11, Running 9.1 MeetingBroker 2-Way Upgrade

If you are upgrading a site that is using MeetingBroker 2.0 with the integration client component, you must install the upgrade for MeetingBroker with 9.1.

Please follow the instructions in the MB2WayInstallationGuide91.pdf document found on the NetXchange intranet site.


Appendix A - Manually Upgrading to 9.1Database

Prerequisite

• The database must have SQL Server 2000, service pack 2 or higher

• Please see the Prerequisites section in the 9.1 Installation Instructions chapter, for more prerequisites.

All upgrades

Run this section for all upgrades (for 713b, run this after the wizard upgrade).

1. Run the following query for all upgrades and save the results:

Select version_id from globalid –(* results will be run in an update later)

2. Run database integrity checks:

– Set database mode to single user: Alter database nss_database set single_user with rollback immediate

– Integrity Check - Dbcc checkdb (‘nss_database’, repair_rebuild) with all_errormsgs

– Set database back to Multi-User - Alter database nss_database set multi_user

7.1.3b Upgrade

Unless noted, all scripts are to be run against nss_database.

1. Upgrade the 7.13b database (SQL 6.5) to SQL Server 2000 using the SQL Server upgrade wizard.

2. Open the following file in Query Analyzer:

– 713TO91_ALTER_TABLE.SQL

3. Search for the following line within the script:

UPDATE ##Globals SET PID = 10, GID = 12 -- this line needs to be passed in from installer

4. Replace the PID and GID values with the appropriate values determined for this installation.

5. Execute the above script.

6. Execute the following scripts:


7.1.3b UpgradeAppendix A - Manually Upgrading to 9.1 Database

– STEP03-DBPROCS.SQL

– STEP04-DBINTEG.SQL

7. Run the following statements:

– Truncate table zip_code

– Truncate table holiday


– STEP06-ZIPCODE.SQL– STEP07-HOLIDAY.SQL

– REFRESH.SQL

– REFRESH_INDEXES.SQL

– STEP10-TRIGS.SQL

– ALTER_TABLE_713b_QUERIES.sql

– MANUAL_UPDATES.SQL

9. Run the following update statement with the value captured from the version_id column in the globalid table:

– UPDATE globalid SET version_id2 = X

where X is the value captured from first step of All upgrades, page A-45. For example, the value might be 7.1.3b but could differ from site to site.

Note—This value may change from version to version because of service packs, etc. Be sure to refer to All upgrades, page A-45 for the correct value.

10. If product is global then run the following updates:

(product is global if: select databasetype from globalid = 3)

update referral

set comprooms = bus.comprooms

from business bus, referral ref

where bus.ref_id = ref.ref_id and

bus.ref_gid = ref.ref_gid and

bus.comprooms is not null

update refperf

set comprooms = ref.comprooms , p_comprooms = ref.comprooms

from referral ref, refperf rp

where ref.ref_id = rp.ref_id and

ref.ref_gid = rp.ref_gid

11. Run the following statements for all products:

update sysuser

set accessall = 1

where (select version_id2 from globalid) not like '%7.2.1%' and


7.1.3b UpgradeAppendix A - Manually Upgrading to 9.1 Database

(select databasetype from globalid) = 3 and coalesce(accessall,0) = 0 and

person_gid = (select globgid from globalid)

GO

insert into evsetupos (evsetup_id, evsetupgid, pid, ossetupid, createper,

createperg, create_dat, createtime, lastmodper, lastmdperg, lastmoddat, lastmdtime)

select evsetup_id, evsetupgid, pid, ossetupid, createper, createperg,

create_dat, createtime, lastmodper, lastmdperg, lastmoddat, lastmdtime

from evsetup

where ossetupid is not null and

(select count(ossetupid) from evsetupos) = 0 and

(select databasetype from globalid) <> 3

GO

truncate table perfbucket

GO

truncate table ubucket

12. Run the following script in the master database:

– DRECOVERY.SQL

13. Run the following procs in nss_database (one at a time)

– Exec proc_findsystemids

– Exec proc_fix_allocate

Note—Do not run proc_fix_allocate at a Global Sales site.

Note—Run at the property, whether linked or not. If the property is linked, run proc_fix_allocate after replication has been reinstalled and you have performed the initial sync.

– Exec proc_ni_init 1,0

– Exec proc_kl_keysall -1

14. Run the following statements: (one at a time)

– Update globalid set trig_status = 0

– Exec Proc_db_icheck 3, NULL

Note—Proc_db_icheck3 may return thousands of rows. This is expected since it is cleaning up the database.

– Update globalid set trig_status = 1

– Exec proc_roomlink 1, 1, 1

– Exec proc_ecriteria_create_defaults

– Exec proc_mb_default


7.2.0 UpgradeAppendix A - Manually Upgrading to 9.1 Database

– Exec PROC_WPDETAIL -1

15. Run this final batch of statements.

ALTER DATABASE nss_database SET RECOVERY FULL

GO

USE master

EXEC drecovery '@inaction', '@BackupPath', 'nss_database'

--example: exec drecovery 'c', 'c:\database\backups\', 'nss_database'

GO

EXEC sp_dboption nss_database , 'dbo use only', FALSE

EXEC sp_dboption nss_database , 'single user', FALSE

EXEC sp_dboption nss_database , 'read only', FALSE

EXEC sp_dboption nss_database , 'ANSI null default', TRUE

EXEC sp_dboption nss_database , 'recursive triggers', FALSE

EXEC sp_dboption nss_database , 'select into/bulkcopy', TRUE

EXEC sp_dboption nss_database , 'trunc. log on chkpt.', TRUE

EXEC sp_dboption nss_database , 'torn page detection', FALSE

EXEC sp_dboption nss_database , 'autoclose', FALSE

EXEC sp_dboption nss_database , 'autoshrink', FALSE

EXEC sp_dboption nss_database , 'auto create statistics', TRUE

EXEC sp_dboption nss_database , 'auto update statistics', TRUE

EXEC sp_dboption nss_database , 'quoted identifier', FALSE

16. If DRECOVERY jobs are to be used, the database recovery mode must be set to full. (The 'trunc. log on chkpt.' statement above set the database recovery mode to Simple.)


17. *** Stop and restart SQL server Service***

Upgrade complete.

7.2.0 Upgrade




2. Execute the script.










– STEP06-ZIPCODE.SQL

– STEP07-HOLIDAY.SQL

– REFRESH.SQL






where X is the value captured from first step of All upgrades, page A-45. For example, the value might be 7.2.0 but could differ from site to site.

Note—This value may change from version to version because of service packs, etc. Be sure to refer to All upgrades, page A-45 for the correct value.



update referral






update refperf






update sysuser

set accessall = 1






GO





from evsetup




GO


GO



– DRECOVERY.SQL












– Exec PROC_NEWDETAILSETS –1

– Exec PROC_DETAILSETS90 -1



GO

USE master





GO

















Upgrade complete.

7.2.1 Upgrade
















– REFRESH.SQL






where X is the value captured from first step of All upgrades, page A-45. For example, the value might be 7.2.1 but could differ from site to site.

– This value may change from version to version because of service packs, etc. Be sure to refer to All upgrades, page A-45 for the correct value.



update referral






update refperf






update sysuser

set accessall = 1




GO







from evsetup




GO


GO



– DRECOVERY.SQL












– Exec PROC_DETAILSETS90 -1



GO

USE master



GO





8.0 UpgradeAppendix A - Manually Upgrading to 9.1 Database














Upgrade complete.

8.0 Upgrade














– REFRESH.SQL








where X is the value captured from first step of All upgrades, page A-45. For example, the value might be 8.0 but could differ from site to site.




update referral






update refperf





g.Run the following statements for all products:

update sysuser

set accessall = 1




GO





from evsetup






GO


GO



– DRECOVERY.SQL












– Exec PROC_DETAILSETS90 –1



GO

USE master


--example: exec drecovery 'c', 'c:\database\backups\', 'nss_database''

GO



















Upgrade complete.

9.0 Upgrade














– REFRESH.SQL






where X is the value captured from first step of All upgrades, page A-45. For example, the value might be 9.0 but could differ from site to site.






update referral






update refperf






update sysuser

set accessall = 1




GO





from evsetup




GO


GO





– DRECOVERY.SQL












– Exec PROC_DETAILSETS90 –1



GO

USE master



GO



















Upgrade complete.


Appendix B - Maintenance Mode

The following procedures may be performed after installing the 9.1 Delphi application at a site. Maintenance procedures include:

• Modification of the existing install –includes installing or removing component files

• Repair of an existing install – restoring a previously installed component files

• Removal of all components – removing all component files

Modify – Select Installed Components

Use the Modify option to install, uninstall, or reinstall 9.1 components. Modify may be used to restore files to their original “factory settings”. For example, if the site’s screen files become corrupted, you may restore just the screen files by first uninstalling the files, then running Modify again to reinstall the files.


Note— If the installation program doesn’t start automatically, click Setup.exe.

If you previously installed one or more component, the Maintenance Program window is displayed.

2. Ensure the Modify option is selected.

3. Click Next.


Modify – Select Installed ComponentsAppendix B - Maintenance Mode

The Select Components window opens.

The following rules apply for modifying files:

– If you want to restore corrupted files, i.e. screen files, you must uninstall the Screen Files the first time you run Modify. You must then run Modify again to reinstall the Screen Files.

– If you select a check box, those files will be installed.

– If you deselect a check box, those files will be uninstalled.

4. Select all components you want to install.

5. Deselect all components you want to uninstall.

Note—Be careful when selecting and deselecting. Remember to leave the check boxes selected for all items you want installed. Any deselected check boxes will cause those files to be uninstalled.

6. Click Next.

The Setup Status window appears.

Once all files have been copied or removed, the Maintenance window appears.


Repair –All Installed ComponentsAppendix B - Maintenance Mode

7. Click Finish to close.

8. If you uninstalled files that were corrupted, you must repeat steps 1- 7 to reinstall the files.

Repair –All Installed Components

Use repair to restore all files that are missing from the components whose check boxes are selected.



2. Ensure the Repair option is selected.

3. Click Next.

The Setup Status window appears.

Once all files have been repaired, the Maintenance window appears.

4. Click Finish to close


Remove – All Installed ComponentsAppendix B - Maintenance Mode

Remove – All Installed Components

Use remove to delete all files that were installed by this release. Remove deletes the files from the components whose check boxes are selected.

Note—Once you have run setup.exe on the Delphi Suite 9.1 Installation CD, if you try to run it again, the Modify, Repair, or Remove maintenance window appears rather than the 9.1 Installation Welcome window. When this happens, you should run Remove to remove all components. You can then reopen setup.exe to reinstall the necessary components.

Important: Be careful when using Remove. As a precaution, always back up your valuable data before deleting any files.



2. Select Remove and click the Next button.

Depending upon the currently installed components various screens appear.

The following message box appears.

All files for all components that you installed will be removed.

3. Click OK to continue.


Remove – All Installed ComponentsAppendix B - Maintenance Mode

The Setup Status window appears. As the files are moved, you may see the following ReadOnly File Detected message.

4. Click Yes each time the message appears.

Once all files have been removed, the Maintenance Complete window appears.

5. Click Finish to close.

6. If you need to reinstall 9.1, be sure to reinstall all programs and MTS.


Appendix C

MTS Registry Information

Important: In the implementation of MTS, the Data Source name (DSN) in the ODBC Administrator is case sensitive. You must make sure that the registry entries use the same case sensitive Data Source Name.

MTS Registryinformation on Client

Note— The 'CentralDSN' key lists the DSN that the client will use on the central application/database server. (i.e. Where the COM components reside). Running the 'MTSinstall.exe' will overwrite all information in the HKLM\Software\NewmarketSoftware\GlobalSFA part of the registry.

MTS Registryinformation on Server

Note— The 'DSN' key must correspond to the DSN that is created on the server for COM screens (i.e., meeting profiles) to work in the application.


Appendix D

Cleaning Up a SQL 6.5 Database

The following steps must be complete prior to upgrading a Delphi 7.1.3b database.

1. Backup the database.

2. Run the Step1 stored procedure.

3. Run the following SQL script:

/* This Script will update Statistics for the SQL65 NSS_DATABASE */use masterGODECLARE @tblname varchar(30)DECLARE @tbl_header varchar(75)DECLARE @dbname varchar(30)DECLARE @db_header varchar(75)DECLARE db_cursor CURSOR FOR SELECT name FROM sysdatabases WHERE name in ('NSS_database')

OPEN db_cursor

FETCH NEXT FROM db_cursor INTO @dbname

WHILE (@@fetch_status <> -1) BEGIN IF (@@fetch_status = -2) BEGIN FETCH NEXT FROM db_cursor INTO @dbname CONTINUEEND SELECT @db_header = + RTRIM(UPPER(@dbname))PRINT " "PRINT @db_headerPRINT " "

/* Create cursor for NSS tables */ EXEC ("USE " + @dbname + " DECLARE tnames_cursor CURSOR FOR SELECT name from sysobjects where type = 'U'")

OPEN tnames_cursor

FETCH NEXT FROM tnames_cursor INTO @tblname


Cleaning Up a SQL 6.5 DatabaseAppendix D

WHILE (@@fetch_status <> -1)BEGIN IF (@@fetch_status = -2) BEGIN FETCH NEXT FROM tnames_cursor INTO @tblname CONTINUE END SELECT @tbl_header = " Updating NSS Table " + RTRIM(UPPER(@tblname)) PRINT @tbl_header EXEC ("UPDATE STATISTICS " + @dbname + ".." + @tblname ) FETCH NEXT FROM tnames_cursor INTO @tblname END

DEALLOCATE tnames_cursor FETCH NEXT FROM db_cursor INTO @dbname END

DEALLOCATE db_cursor

PRINT "Statistics have been updated for NSS_DATABASE tables."

GO

4. Run the following SQL script:

use Nss_databasegodbcc checkdbgodbcc newallocgo

5. Check combined results from step-4 by searching for these key words\numbers. If any reference is found, contact Support with instructions on how to proceed. The database may have significant data corruption that must be corrected before continuing with the upgrade.

corruridleaffetch254025412558


Appendix E

Updating BEOs and Banquet Checks from 7.1.3b or Earlier Version

Find Existing BEOs & Banquet Check

1. Log on to the Delphi application.

2. On the File menu, point to Setup, and click Power BEO.

The Power BEO Setup Options window appears.

3. Double-click Forms.

4. Note the BEO templates listed in the Template column and enter each one in the Pre-Installation Worksheet, page 3.

BEOs 1. On the application server, or workstation, copy the BEO templates (e.g. BEO2.rpt, BEO7.rpt) and Banquet Check (Bqtcheck.rpt) to a disk from the NGS\EXE directory.

2. Open Crystal on your laptop.

3. Click the Open Report button on the pop up window or on the tool bar.

4. Find the BEO or Banquet Check on the A: Drive.

5. Open the desired BEO template.

6. In the Crystal report, click File/Options and select the Show Field Names check box. This shows the database tags for the fields in the report.

7. In the upper right hand corner find the BEO_ID field.

8. Click the lower right-hand corner of the BEO_ID field to select it.

9. Press the Delete key.

10. On the menu bar, select Insert/Database.

11. In the pop up window, search the BEO table and select the BEO_Number field by double-clicking on it.

12. Drag the field into the report and place it where the BEO_ID used to be located. You may find it easier to place the field if you increase the zoom to 150%.

13. Save the BEO.

14. Repeat steps 4 - 13 for each BEO.

15. After BEO modifications have been completed, copy the BEOs back into the NGS\EXE folder.

Banquet Check 1. Click the Open Report button on the pop up window or on the tool bar.

2. Find the Bqtcheck.rpt on the A: drive.

3. In the Crystal report, click File/Options and select the Show File Names check box. This shows the database tags for the fields in the report.

4. In the upper right-hand corner, find the BEO_ID field.

5. Click the lower right-hand corner of the BEO_ID field to select it.


Updating BEOs and Banquet Checks from7.1.3b or Earlier Version

Appendix E

6. Press the Delete key.

7. On the menu bar, select Insert/Database field.

8. In the pop up window, find the BEO table by pressing the dash key on the keyboard 3 times. In the BEO table, select the BEO_Number field by double-clicking it.

9. Drag the field into the report and place it where the BEO_ID used to be located. You may find it easier to place the field if you increase the zoom to 150%.

10. Save the Banquet Check.

11. Copy the file back to the NGS\EXE folder.


Appendix F

Troubleshooting

Error D:\NI_DATA\REFRESH.out

Server: Msg 1203, Level 20, State 1, Line 4

Process ID 52 attempting to unlock unowned resource PAG: 5:3:11944.

Problem: SQL Server 2000 SP2 may not be installed.

Resolution: Verify if SP2 is installed. If not, install SP2 and re-upgrade the database from the backup.


Appendix G

Updating BEOs and Banquet Checks from 7.2.x

Find Existing BEOs & Banquet Check

1. Log on to the Delphi application.

2. On the File menu, point to Setup, and click Power BEO.

The Power BEO Setup Options window appears.

3. Double-click Forms.

4. Note the BEO templates listed in the Template column and enter each one in the Pre-Installation Worksheet, page 3.

BEOs 1. On the application server, or workstation, copy the BEO templates (e.g. BEO2.rpt, BEO7.rpt) and Banquet Check (Bqtcheck.rpt) to a disk from the NGS\EXE directory.

2. Open Crystal on your laptop.

3. Click the Open Report button on the pop up window or on the tool bar.

4. Find the BEO or Banquet Check on the A: Drive.

5. Open the desired BEO template.

6. Save the BEO.

7. Repeat steps 4 - 13 for each BEO.

8. After BEO modifications have been completed, copy the BEOs back into the NGS\EXE folder.

Banquet Check 1. Click the Open Report button on the pop up window or on the tool bar.

2. Find the Bqtcheck.rpt on the A: drive.

3. Save the Banquet Check.

4. Copy the file back to the NGS\EXE folder.


91 Install Program - Amadeus Hospitality · If the property is linked, install replication on the...

Documents

Transcript of 91 Install Program - Amadeus Hospitality · If the property is linked, install replication on the...