9700 Setup V300
9700 Setup V300
9700 Setup V300
Table of Contents
Declarations
Warranties
Although the best efforts are made to ensure that the information in this manual is complete and correct, MICROS Systems, Inc. makes no warranty of any kind with regard to this material, including but not limited to the implied warranties of marketability and fitness for a particular purpose. Information in this manual is subject to change without notice. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information recording and retrieval systems, for any purpose other than for personal use, without the express written permission of MICROS Systems, Inc. MICROS Systems, Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.
Trademarks
Windows is a registered trademark of Microsoft Corporation. FrameMaker is a registered trademark of Adobe Corporation.
Printing History
New editions of this manual incorporate new and changed material since the previous edition. Minor corrections and updates may be incorporated into reprints of the current edition without changing the publication date or the edition number.
Edition Month Year Software Version
1st
September
2005
3.0
ii
Table of Contents
Preface
vi vii viii Why Read This Manual? Finding Additional Information Notation Conventions
iii
Table of Contents
Index
iv
Preface
In This Chapter
In this preface, you will find information about the organization, conventions, and contents of this manual. Why Read This Manual? ........................................................................-vi Finding Additional Information.............................................................-vii Notation Conventions ...........................................................................-viii
Table of Contents
vi
Preface
Finding Additional Information
vii
Table of Contents
Notation Conventions
Keys
Throughout this manual, keys on a PC keyboard are shown in bold and enclosed in square brackets. Examples: [Enter] [Shift] [Page Up]
Prompts
Messages that may appear on the screen when programming are shown in Courier 11pt italics. Example: Select Menu Item Range
viii
Chapter 1\
1
System Overview
In This Chapter
This chapter introduces 9700 System communication, how the system can be configured, and the recommended hardware to use. Communications................................................................................. 1-2 Hardware Requirements..................................................................... 1-6 Hardware Recommendations ............................................................. 1-7 MICROS Eclipse Workstation ........................................................... 1-8 MICROS Workstation 4 (WS4) ......................................................... 1-8 MICROS Keyboard Workstation 4 (KWS4)...................................... 1-9 Mobile MICROS HHT....................................................................... 1-9 Epson TM88 Thermal Printer .......................................................... 1-10 Epson U200B ................................................................................... 1-10 Recommended Communications Option .......................................... 1-11
1-1
Communications
The 9700 System maintains an open design philosophy, allowing the system to communicate with MICROS peripherals, non-MICROS equipment, and other computer systems. To achieve this capability, the 9700 System provides several communication pathways for exchanging information: Local Area Network (LAN) Property Management System (PMS) Interface Table Management System (TMS) Interface Intelligent Device Network (IDN) Credit Authorization/Electronic Draft Capture (CA/EDC) Input Devices Video Security System (VSS)
1-2
Order Printers
Order printers (usually used for remote order receipts) are usually connected in a daisy-chain directly to a single channel on the NetCC or RCC controller, or a User Workstation.
Line Printers
Line printers, which are used to print back-office reports, can be connected on any serial port on the PC, parallel port on the PC, or via the network (IPCC). For more information, refer to Configuring Network and Local Printing on page 2-60. See also Printers in Section P of the 9700 A to Z Feature Reference Manual.
1-3
Input Devices
Bar Code Reader
A Barcode Reader allows an operator to enter (scan) items for sale without having to read information from the item, or find the item on the keyboard. This is especially useful in a retail establishment where a great number of items are available. For more information, refer to the 9700 Hardware Installation Manual, and the Users Maintenance Guide.
1-4
1-5
Hardware Requirements
Shown below are the basic requirements for installing the 9700 HMS application on your PC: PC configured according to the parameters detailed in the 9700 Version 3.0 Server Sizing document, located on the MICROS product page. Windows 2000 Server operating system with Service Pack 4 installed (this must be the Server edition, not Professional), or Windows 2003 Server. Internet Explorer 6.0 or higher (the 9700 HMS installation process will install IE 6.0 if it is not already installed). PC must use static IP address.
An Uninterruptible Power Supply (UPS) is strongly recommended on every MICROS 9700 System to allow the server to shutdown safely in the event of a power outage. Note
If you are installing multiple adapters (NICs), make sure the client NIC is listed first: - From the Windows Desktop, right-click on My Network Places - Select Properties - Select the Advanced tab - Select Advanced Settings - On the Adapters and Bindings tab, highlight the client NIC and move it up to the top of the list - Click OK to save the changes - Reboot the server
1-6
Hardware Recommendations
Listed below are the hardware components recommended by MICROS. For detailed information on each component, refer to the 9700 HMS Feature Overview Manual.
Server Options
MICROS Systems, Inc. requires all sites meet the minimum requirements for server configuration listed on the MICROS Product Page. For more productspecific information, go to the Hewlett-Packard Web site at www.hp.com, or contact your MICROS sales representative.
Terminal Options
MICROS recommends the following terminal options for a 9700 System: MICROS Eclipse PC Workstation MICROS Workstation 4 MICROS Keyboard Workstation 4 Mobile MICROS HHT You will find a brief description of each of these terminals starting on page 1-8. For current terminal recommendations, please consult the MICROS Product Page, or contact your MICROS sales representative.
Printer Options
MICROS recommends the following printer options for a 9700 System: Epson TM88 Thermal Printer Epson U200B You will find a brief description of each of these printers starting on page 1-10. For current printer options, please consult the MICROS Product Page, or contact your MICROS sales representative.
1-7
1-8
1-9
Epson U200B
The Epson U200B is used as a receipt printer for single workstations. Although slower in print speed than the TM88, this printer provides graphics capability and one original/two copies print ability.
1-10
1-11
1-12
Chapter 2
2
9700 Software Platform Installation
In This Chapter
This chapter provides the requirements and instructions for setting up your Microsoft Windows 2000 Server or 2003 Server system and installing the MICROS 9700 Version 3.0 System software. Installing Windows..............................................................................2-2 Software Licensing..............................................................................2-2 System Security...................................................................................2-3 Post-Windows Setup ...........................................................................2-8 Microsoft SQL Server 2000 (SP3) or Oracle9i....................... 2-11 Installing the 9700 HMS Application ...............................................2-19 Installing 9700 V. 3.0 Components on Clients..................................2-46 Starting the 9700 System ..................................................................2-59 Configuring Network and Local Printing .........................................2-60 Configuring WinStation Client Workstations ...................................2-70 Configuring Workstation 4 (WS4) Clients........................................2-82 Configuring NetCCs..........................................................................2-85 Backing Up the System: MS-SQL Maintenance Plans.....................2-99
2-1
Installing Windows
Windows 2000 with Service Pack 4 (or higher) or Windows 2003 Server must be installed prior to installing the 9700 software. Contractual obligations with Microsoft prevent MICROS Systems, Inc. from providing Service Packs on the 9700 Setup CD. As a result, the Service Pack must be downloaded via the Internet from the Microsoft Web site. For new installations, your server should already be configured with Windows 2000 Server with Service Pack 4 or Windows 2003 Server. If you are upgrading from a previous version of 9700, you will have to upgrade your server from Windows NT to Windows 2000 with Service Pack 4 or Windows 2003 before installing the latest version of 9700. Refer to the Migrating From Windows NT to Windows 2000 document (MD0006-011) for these upgrade procedures. This document is available on the 9700 V. 3.0 Companion CD. Just insert the CD into the CD-ROM drive and then navigate to MICROS\LES\POS\9700\Documentation\migrate.pdf. If you are transferring your existing 8700 system or 9700 system to a new PC, make sure the new 9700 V. 3.0 server has been configured properly with Windows 2000 Server with Service Pack 4, or Windows 2003 Server prior to attempting upgrade procedure listed in Chapter 3: Software Maintenance.
Software Licensing
The 9700 software licensing method uses a parallel or USB port hardware key to control feature licensing. To stay current with the changes in server architecture, but also provide a solution for legacy hardware, MICROS also offers a keyless licensing solution, which is suitable for both old and new systems. Key licensing is transparent to the user, and integrates seamlessly, using a single application to provide support to both the traditional hardware key and keyless licensing. The keyless licensing feature is automatically activated when a hardware key licensing code is not detected. A unique licensing code, generated by using information from the servers motherboard, ensures that the code is unique to each server. For information on how to obtain keyless licensing, go to http://www.micros.com/ members/operations/keylesslicensing.
2-2
System Security
This section briefly discusses default groups, users, and file permissions, which are created during the 9700 installation. The groups and users created during the 9700 installation will differ, depending on whether your system is configured as a domain controller, member server, or a workgroup. If the installation is on a domain controller, domain users and groups are created. If the installation is on either a member server or workgroup, local users and groups are created.
MICROS_ADMINS
csremote/EBUTO
MICROS_USERS
m9700/micros
RMC_Users
micros/micros 9700cfg/undisclosed
2-3
In a Workgroup
Group Includes These Members User/Password
MICROS_ADMINS
MICROS_USERS
Note
If additional security is needed, the m9700 and micros user passwords can be changed as needed by the site administrator. Passwords are changed through Control Panel | Administrative Tools | Computer Management | Local Users and Groups. To change the csremote password, please contact MICROS Customer Support.
2-4
x x
x x x
x x x
x x x
x*
x x
x x x
x x
x* * The Domain Users group is a subgroup within the RMC_Users group. Since the csremote, m9700, and micros users are members of the Domain Users group, they are members of the RMC_Users group.
2-5
x x
x x x
x x
Note
You should limit the number of users who have full Windows 2000/ 2003 privileges. The system administrator can make changes through Control Panel | Administrative Tools | Computer Management | Local Users and Groups.
2-6
Everyone (Full Control) Everyone (Full Control) Everyone (Full Control) Everyone (Full Control) Everyone (Full Control) Everyone (Full Control) Administrators (Full Control) Everyone (Read/Execute) SYSTEM (Full Control) Everyone (Full Control) Everyone (Full Control) Everyone (Full Control) Everyone (Full Control)
SYSTEM
Administrators (Full Control) Everyone (Read) SYSTEM (Special Access) Administrators (Full Control)
8700errlog
SYSTEM
2-7
Post-Windows Setup
After Windows is installed, there are some additional tasks you may need to complete before you install the 9700 HMS software.
Note
If you are configuring a 9700 database for a MICROS Operational Resiliency site, make sure the PC on which the database is created (e.g., your laptop) is set up as PC1 (the Primary PC) prior to programming the database. This ensures that you will start off with all of the appropriate settings to create a MICROS Operational Resiliency database (i.e., add PC2, the backup PC).
The process of setting up a MICROS Operational Resiliency pair should be performed in this order: 1. Install 9700 HMS on the Primary PC (PC1). Make sure to select MICROS Operational Resiliency - Primary in the System Type section on the 9700 HMS Setup screen during the 9700 software installation (see page 2-29 for details). 2. Once 9700 Version 3.0 finishes installing on PC1, Install 9700 HMS on the Backup PC (PC2). Make sure to select MICROS Operational Resiliency Secondary in the System Type section on the 9700 HMS Setup screen during the 9700 software installation (see page 2-29 for details). 3. Once 9700 Version 3.0 has finished installing on PC2, the Device Table needs to be configured to ensure MICROS Operational Resiliency is set up correctly. 4. For each PC, In EMC > System Hardware > Device Table, enter the Client NIC IP address and the Redundancy NIC IP address into the corresponding fields.
2-8
Note
The Redundancy NIC is connected by a crossover cable between PC1 and PC2.
6. On PC1, for every device attached to a Cluster Controller, and for journals, select the backup PC and configure CC#s and CC Channels, exactly as configured in the primary PC.
7. At this point, all hardware (workstations and MMHs) need to be manually configured to recognize the backup IP address and backup CC# (if applicable).
2-9
PostScript Printers
If you intend to use a PostScript printer, skip the printer installation steps in the Windows installation. Install the printer after youve finished installing the 9700 System software, as the software provides specific files to support PostScript printers. Follow the steps below to install a PostScript printer. 1. Complete all Windows and 9700 installation steps. 2. From the Windows Desktop, select Start | Settings | Printers. 3. Double-click the Add Printer icon. The Add Printer Wizard screen displays. 4. Click Next. 5. Select Local Computer or Network printer, as appropriate for this printer, then click Next. If you selected Local Computer: Select the Automatically detect and install my Plug and Play printer option. Click Next. When the printer is located and installed, click Yes to print a test page. Click Next. Click Finish. If the test page prints, you have installed your printer correctly. Click OK. If the test page does not print, click Troubleshoot to identify the problem. If you selected Network printer: Click Next to search for printers on the network. Select the appropriate printer and click Next. Choose if you want this print device to be your default printer, then click Next. Click Finish. To install other types of printers, refer to your Windows documentation.
2-10
Note
For those sites providing their own instance of Microsoft SQL Server 2000 (SP3 or higher) or Oracle 9i, proceed to page 2-19, Installing the 9700 HMS Application.
2-11
Note
If the installation does not start automatically, navigate to the CD-ROM drive and double-click MICROSSQLSERVER.exe. The InstallShield Wizard for MICROS SQL Server 2000 screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation.
2-12
4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
5. The Choose Destination Location screen displays, seen below. Choose the default location for the MS-SQL installation, or select Browse to choose another location. Once you have decided where you want to install MS-SQL, click Next to continue.
2-13
6. The Start Copying Files screen displays, seen below. This summarizes what will be installed as part of the MICROS MS-SQL Installation. Note that MSSQL Server 2000 Service Pack 3 is installed automatically. Once you have reviewed this screen, click Next to continue.
7. The installation commences. A series of status messages will display to indicate the progress of the installation. 8. After a few minutes, the installation completes. The InstallShield Wizard Complete screen displays, seen below, prompting you to restart your computer to complete the installation. Select Yes, I want to restart my computer now, then click Finish to complete the installation.
2-14
Installing Oracle 9i
1. Close all applications and return to the Windows Desktop. 2. On the server you wish to install the database server on, insert the Opera POS database 1 Setup CD into the PCs CD-ROM drive. The Opera POS database Setup automatically starts.
Note
If the installation does not start automatically, navigate to the CD-ROM drive and double-click OperaPOSDatabaseStart.exe. The InstallShield Wizard for OperaPOS database screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation.
2-15
4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
5. The Choose Destination Location screen displays, seen below. Choose the default location for the Oracle installation, or select Browse to choose another location. Once you have decided where you want to install Oracle, click Next to continue.
2-16
6. The Start Copying Files screen displays, seen below. This summarizes what will be installed as part of the MICROS Oracle installation. Once you have reviewed this screen, click Next to continue.
7. The installation commences. A series of status messages will display to indicate the progress of the installation. When the installation has finished copying files from the first Installation CD, the Disk Location screen displays, seen below. Insert the second Installation CD into the CD-ROM drive, and click OK to continue.
8. When the installation has finished copying files off the second Installation CD, a second Disk Location screen will display, prompting you to insert the third Installation CD into the CD-ROM drive. Once you have inserted the third Installation CD, click OK to continue the installation.
2-17
9. After a few minutes, the installation completes. The InstallShield Wizard Complete screen displays, seen below, prompting you to restart your computer to complete the installation. Select Yes, I want to restart my computer now, then click Finish to complete the installation.
2-18
2-19
Note
These instructions pertain to a first-time installation of the 9700 System software. If you are upgrading from a previous version of the 9700 System software, or migrating from an 8700 system to a 9700 system, please refer to Chapter 3Software Maintenance.
2-20
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3. After reading the 9700 V 3.0 System Setup documentation, click Next to continue the installation.
2-21
4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
5. The Component Selection screen displays. This screen allows a user to configure what elements of the 9700 V. 3.0 software are installed during this installation session. The default selection is to install all elements of the 9700 V. 3.0 software, as seen below.
Note
Unchecking the 9700 Server box, allows the user to select which components to install. For instructions on variable installations of 9700 V. 3.0, please refer toInstalling 9700 V. 3.0 Components on Clients on page 2-46. When you have decided which components of the 9700 V. 3.0 software to install, click Next to continue.
2-22
6. A status message displays, Setup is searching for Internet Information Services (IIS). If you neglected to install IIS, the installation will error out. If IIS is installed, proceed to step 7. 7. The Installation Drive Selection screen displays, seen below. Select the drive to install 9700 Version 3.0 on.
Note
MICROS strongly recommends you do not install 9700 Version 3.0 on the same drive as your Operating System (Windows). After you have selected the drive you want to install 9700 V. 3.0 on, click Next to continue.
2-23
9. The Database Information screen displays, (Local Machine configuration shown) seen below. Configure the screen according to the installation parameters detailed below:
Remote Machine - choose this option if Microsoft SQL Server is NOT located on the server you are installing 9700 Version 3.0 on, i.e., a remote installation off the sites network. Enter the computer name or the static IP address to identify the MS-SQL server on the network.
Password -
Once you have configured this screen accordingly, click Next to continue.
2-24
The default Database Name is MCRSPOS. If you wish to change the name, type the new name into the field. Once you have decided the Database Name, click Next to continue.
11. The MICROS Database Owner screen displays, seen below. Enter the name and password for the User that will own the MICROS MS-SQL database.
The default Database Owner User Name and Password are both microsdb. If you wish to change the User Name or Password, change the values now. Once you have decided the Database Owner User Name and Password, click Next to continue the installation.
2-25
12. The SQL Server Database File Location screen displays, seen below. Select the Folder where you would like the SQL Server Database files to be saved.
Accept the default location, or click Browse to select a different location. Once you have selected the Destination Folder, click Next to continue the installation.
This message informs the user that Setup will install a Sample 9700 Database Maintenance Plan. For details on the Sample 9700 Database Maintenance Plan, refer to page 2-99 Backing up the System. After you have read this message, click Next to continue.
2-26
Accept the default location, or click Browse to select a different location. Once you have selected the Destination Folder, click Next to continue the installation
15. The 9700 HMS Installation Summary screen displays, seen below.
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next.
2-27
16. The installation commences. Status windows allow the user to monitor the progress of the installation. 9700 Version 3.0 first installs Cygwin, seen below...
...Once the Cygwin installation completes, 9700 Version 3.0 begins installing the 9700 Server files, seen below...
2-28
17. After the 9700 Server Files finish installing, the Select your System Type screen displays, (Standalone PC configuration shown) seen below.
Configure this screen by selecting one of the three options detailed below.
Note
If you are installing MICROS Operational Resiliency, do not proceed past this step until you have read the information on page 2-8, MICROS Operational Resiliency. This section gives detailed instructions on how to setup and install a MICROS Operational Resiliency System.
Once you have determined the appropriate Setup Type, click Next to continue the installation.
2-29
18. The MICROS 9700 Setup: Diskless Boot Server screen displays, seen below.
After you have read the NOTE, decide whether you want to Start Diskless UWS Boot Service when Windows starts. Click Next to continue the installation. 19. The Setup Type: Make your database selection screen displays, seen below.
2-30
20. The installation commences. The Automatic CAL Service screen displays, seen below.
If you would like the CAL Service to start automatically on the server, click Yes to continue. If you do not want the CAL Service to start automatically, and instead prefer to manually start the CAL Service, click No to continue.
This message notifies the user that the IIS port has been changed to 8080. To continue the installation, click OK.
If there is a USB Software Key attached to the server, please remove it from the server now, and attach it after the installation has completed. Once you have removed the USB Software Key, if applicable, click OK to continue.
2-31
Note
If the WS4\Packages directory does not exist prior to install, you will see this message. 9700 Version 3.0 System Setup is trying to update older versions of the WS4 POS terminal platform. Because this directory only exists on previous 9700 Systems, this message will appear. Please upgrade to the latest Service Pack of 9700 Version 3.0 to obtain the latest WS4 platform updates. After reading the Note above, click OK to continue the installation.
Please refer to page 2-99, Backing up the System. After you have read this section, please click OK to continue.
2-32
To complete the 9700 Version 3.0 install, select Yes, I want to restart my computer now., then click Finish.
2-33
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation.
2-34
4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
5. The Component Selection screen displays. This screen allows a user to configure what elements of the 9700 V. 3.0 software are installed during this installation session. The default selection is to install all elements of the 9700 V. 3.0 software, as seen below.
Note
Unchecking the 9700 Server box, allows the user to select which components to install. For instructions on variable installations of 9700 V. 3.0, please refer to Installing 9700 V. 3.0 Components on Clients on page 2-46
2-35
6. A status message displays, Setup is searching for Internet Information Services (IIS). If you neglected to install (IIS), the installation will error out. If (IIS) is installed, proceed to Step 7. 7. The Installation Drive Selection screen displays, seen below. Select the drive to install 9700 Version 3.0 on.
Note
MICROS strongly recommends you do not install 9700 Version 3.0 on the same drive as your Operating System (Windows). After you have selected the drive you want to install 9700 V. 3.0 on, click Next to continue.
2-36
Remote -
Once you have selected the Database Server location, click Next to continue the installation.
2-37
2-38
11. The Opera POS Database User screen displays, seen below.
Enter the Name and Password of the User that will use the OperaPOS database. MICROS defaults are MICROSDB for both. Once you have entered the Opera POS database User and Password, click Next to continue.
The default MICROS 9700 Tablespace is MCRSPOS. If you wish to change the name, type the new name into the field. Once you have decided the Tablespace Name, click Next to continue.
2-39
13. The 9700 HMS Installation Summary screen displays, seen below.
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next.
2-40
14. The installation commences. Status windows allow the user to monitor the progress of the installation. 9700 Version 3.0 first installs Cygwin, seen below...
...Once Cygwin installation completes, 9700 HMS Setup begins installing the 9700 Server files.
2-41
15. After the 9700 Server files finish installing, the Select your System Type screen displays, (Standalone PC configuration shown) seen below.
Configure this screen by selecting one of the three options detailed below.
Note
If you are installing MICROS Operational Resiliency, do not proceed past this step until you have read the information on page 2-8 MICROS Operational Resiliency. This page gives detailed instructions on how to setup and install a MICROS Operational Resiliency System.
Once you have determined the appropriate Setup Type, click Next to continue the installation.
2-42
16. The MICROS 9700 Setup: Diskless Boot Server screen displays, seen below.
After you have read the NOTE, decide whether you want to Start Diskless UWS Boot Service when Windows starts. Click Next to continue the installation.
17. The installation commences. The Automatic CAL Service screen displays, seen below.
If you would like the CAL Service to start automatically on the server, click Yes to continue. If you do not want the CAL Service to start automatically, and instead prefer to manually start the CAL Service, click No to continue.
This message notifies the user that the IIS port has been changed to 8080. To continue the installation, click OK.
2-43
If there is a USB Software Key attached to the server, please remove it from the server now, and attach it after the installation has completed. Once you have removed the USB Software Key, if applicable, click OK to continue.
Note
If the WS4\Packages directory does not exist prior to install, you will see this message. 9700 Version 3.0 System Setup is trying to update older versions of the WS4 POS terminal platform. Because this directory only exists on previous 9700 Systems, this message will appear. Please upgrade to the latest Service Pack of 9700 Version 3.0 to obtain the latest WS4 platform updates. After reading the Note above, click OK to continue the installation.
2-44
To complete the 9700 Version 3.0 install, select Yes, I want to restart my computer now., then click Finish.
2-45
2-46
2-47
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation. 4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
2-48
5. The Component Selection screen displays. This screen allows a user to configure what elements of the 9700 V. 3.0 software are installed during this installation session.
Note
Unchecking the 9700 Server box, allows the user to select which components to install. Select Remote Management Console, as seen above, then click Next to continue.
6. The Installation Drive Selection screen displays, seen below. Select the drive to install the Remote Management Console on.
After you have selected the destination folder, click Next to continue.
2-49
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next. 8. The installation commences...
2-50
9. After a few moments, the Database Server Name screen displays (local configuration shown). This screen prompts for the Computer Name or Static IP address of the database server on the network.
Once you have entered the Computer Name or Static IP address of the database server on the network, click Next to continue. 10. After a few moments, the InstallShield Wizard Complete screen displays, seen below. To finish the installation select Yes, I want to restart my computer now., then click Finish.
2-51
Note
For MS-SQL installations, MS-SQL Client files and EMC Client files are installed into the C:\Program Files\MICROS directory. These are about 66 KB in size. For Oracle installations, those same folders are installed, along with Oracle Client files in the C:\Program Files\Oracle directory. These files are about 78 MB in size.
2-52
Note
If a service pack or upgrade is installed, Remote EMC will be automatically updated the next time Remote EMC is used. There is no need to reinstall Remote EMC. Report Writer and Autosequencer cannot be accessed from Remote EMC. Reporting for 9700 Version 3.0 is handled by the RMC. The RMC must be installed on any machine requiring these modules. Like 9700 Version 2.x, RMC must be reinstalled per Service Pack, or you can use 9700 Web Reports. If you are installing on Windows 2003, you may get the error message Your security settings prohibit running ActiveX controls on this page. As a result, the page may not display correctly. If so, in Internet Explorer, go to Tools>Internet Options>Security, and decrease your Security Level bar to Medium or lower.
Note
Note
2-53
Note
1. All Network Interface Cards (NICs) must be configured prior to the installation of the Bootp Service 2. Bootp will not function properly on a PC using DHCP (Dynamic Host Configuration Protocol) 3. Should the image file become corrupt or missing, a Diskless Client Recovery image file is located in \MICROS\LES\POS\9700\ClientInstalls\Diskless Client Recovery.
1. Close all programs and return to the Windows Desktop. 2. Insert the 9700 HMS Version 3.0 CD into the PCs CD-ROM drive. The 9700 HMS splash screen displays briefly...
2-54
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation. 4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
2-55
5. The Component Selection screen displays. This screen allows a user to configure what elements of the 9700 V. 3.0 software are installed during this installation session.
Note
Unchecking the 9700 Server box, allows the user to select which components to install. Select Bootp Server, as seen above, then click Next to continue.
6. The Installation Drive Selection screen displays, seen below. Select the drive to install the Bootp Server on.
After you have selected the installation drive, click Next to continue.
2-56
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next. 8. The Cygwin installation commences...
2-57
9. After a few moments, the Diskless Boot Server screen displays. If you want the MICROS 9700 Bootp Service to automatically start when Windows starts, select the Start Diskless UWS Boot Service when Windows starts.
From the Network Interface drop down list, choose the NIC that the Bootp Service should use. Once you have configured both of these options, click Next to continue. 10. After a few moments, the InstallShield Wizard Complete screen displays, seen below.
To complete the installation select Yes, I want to restart my computer now., then click Finish.
2-58
Note
Activating the Database button allows the user to: -Run Autosequences -Perform 8700sql -Run a CCBatch -Run a Check Print
6. Click the Operations button to allow workstations to communicate with the 9700 server
Note
If running a MICROS Operational Resiliency pair, the PC Status window changes from Idle to Primary, Live PC# and Secondary, Live, PC#.
2-59
Anything printed from the 9700 Enterprise Management Console uses the Windows print settings (refer to page 2-61). 9700 Remote Management Console uses the sample printer files that are installed with the 9700 software (refer to page 2-62). These files will print reports and configuration data in landscape or portrait mode.
2-60
Follow the steps below to print a selection in the 9700 Enterprise Management
Console.
1. From the Windows Desktop, select Start | Programs | MICROS Systems 9700 | Enterprise Management Console. 2. Select the database server, and click Connect. 3. Enter the UserName and Password, then click Login. 4. Navigate to the form to print. For example, select: Personnel | Employees | Maintenance. 5. Click 6. Click . , or select File | Print from the Menu Bar.
If you choose the Print icon, your selection will automatically print. If you choose the File | Print option, a Print dialog box displays. Click OK to start the print request. The Print dialog box also allows you to change the print format (i.e., change Portrait to Landscape, or vice-versa): Click the Properties button. Make your selection(s), and click OK. Click OK again to start the print request.
2-61
On the Server...
The sample printer files are installed in X:\Micros\LES\Pos\9700\etc (where X: is the directory where the 9700 System is installed). You can create an unlimited number of printer configuration files, however, the server only allows up to 16 printer configuration files to be linked in the Devices file, which is described on page 2-67.
2-62
The printer configuration files you create on the client can be identical to those on the server, but it isnt necessary. However, to print from a specific client, the printer configuration files must exist on that client.
Note
Printing From Report Writer: All reports in the Report Writer module, with the exception of the Income Audit report, use the printer configurations designated in the System Hardware | Device Table on the server. The Income Audit report has its own printer setup strings which much be configured on the server in Reporting | Report Configuration | Income Audit | Line Printer Parameters. These printer setup strings can be the same as those programmed in the Device Table, however, they must also be in the Report Configuration file in order for this report to print.
upgraded, the PrintLandscape.txt file will be overwritten. To avoid overwriting the changes you will make to this file, you must rename the file to preserve its contents. Example: Rename PrintLandscape.txt to Landscape.txt.
3. Open the new file using the text editor of your choice. You will see the following line: -d @MicrosDefaultPrinter lines 66 cols 150 land
2-63
4. Replace @MicrosDefaultPrinter with your printers name. Servers and Windows 2000, 2003, or XP Remote Management Console clients require the full network path and printer name. Example: If your printers network path and name is \\admin\hp4, then you would replace @MicrosDefaultPrinter with \\admin\hp4 and PrintLandscape.txt would look like the following: -d \\admin\hp4 lines 66 cols 150 land
Note
If a network printer uses spaces in its name, you must add quotes around the printers name. For example, if the printers name is \\admin\hp LaserJet 6L, then you would replace @MicrosDefaultPrinter in each sample file with \\admin\hp LaserJet 6L
5. Save and exit the new printer file. 6. Copy and rename the PrintPortrait.txt file. Do not skip this step!
upgraded, the PrintPortrait.txt file will be overwritten. To avoid overwriting the changes you will make to this file, you must rename the file to preserver its contents. Example: Rename PrintPortrait.txt to Portrait.txt.
7. Open the new file using the text editor of your choice. You will see the following line: -d @MicrosDefaultPrinter lines 90 cols 150 port
2-64
8. Replace @MicrosDefaultPrinter with your printers name. Servers and Windows 2000, 2003, or XP Remote Management Console clients require the full network path and printer name. Example: On servers and Windows 2000, 2003, or XP RMC clients, if your printers network path and name is \\admin\hp4, then you would replace @MicrosDefaultPrinter with \\admin\hp4 and PrintPortrait.txt would look like the following: -d \\admin\hp4 lines 90 cols 150 -port
Note
If a network printer uses spaces in its name, you must add quotes around the printers name. For example, if the printers name is \\admin\hp LaserJet 6L, then you would replace @MicrosDefaultPrinter in each sample file with \\admin\hp LaserJet 6L
2-65
Example
Copy PrintLandscape.txt and rename it: LandscapePrntr1.txt, LandscapePrntr2.txt, LandscapePrntr3.txt, and so on. Copy PrintPortrait.txt and rename it: PortraitPrntr1.txt, PortraitPrntr2.txt, PortraitPrntr3.txt, and so on. If you are using two network printers, for example, and you want to make Portrait your default style on \\admin\hp4, then edit your printer files as described below: \\admin\hp4 (Network Printer 1), and \\accounting\hp610 (Network Printer 2)
Edit this file: To look like this: -d \\admin\hp4 lines 90 cols 150 port -d \\accounting\hp610 lines 90 cols 150 -port -d \\admin\hp4 lines 66 cols 150 land -d \\accounting\hp610 lines 66 cols 150 land
2-66
Configuring Each PC in the Device Table for Network and Local Printers
After you have edited the sample printer files for your installation site (described on page 2-61), you must edit the Printer Settings in the Device Table for each PC to configure the 9700 System for printing. Follow the steps below to configure each PC for network printing: 1. From the Windows Desktop, select Start | Programs | MICROS Systems 9700 | Enterprise Management Console. 2. Select the database Server, and click Connect. 3. Enter the UserName and Password, and click Login. 4. Once the Control Panel has been started, select System Hardware | Device Table. 5. Select a PC from the Devices tree. 6. On the Printer Settings form, click in the Line Printer Parameter #1 field and type the new name of the text file: @Portrait.txt 7. Click in the Line Printer Parameter #2 field and type the new name of the text file: @Landscape.txt The printer settings should look like the following:
Note
8. Fill in the Line Printer Parameter #3 through Line Printer Parameter #16 fields, as needed. 9. Repeat Steps 3 through 7 for each PC in the Devices tree. 10. Save and exit the Devices form.
2-67
Configuring Each PC in the Device Table for Multiple Network or Local Printers
Follow the steps below to configure each PC with multiple printers: 1. From the Windows Desktop, select Start | Programs | MICROS Systems 9700 | Enterprise Management Console. 2. Select the database Server, and click Connect. 3. Enter the UserName and Password, and click Login. 4. Once the Control Panel has been started, select System Hardware | Device Table. 5. Select a PC from the Devices tree. 6. On the Printer Settings form, click in the Line Printer Parameter #1 field and type @PortraitPrntr1.txt 7. Click in the Line Printer Parameter #2 field and type @PortraitPrntr2.txt 8. Click in the Line Printer Parameter #3 field and type @LandscapePrntr1.txt 9. Click in the Line Printer Parameter #4 field and type @LandscapePrntr2.txt The printer settings should look like the following:
10. Fill in the Line Printer Parameter #5 through Line Printer Parameter #16 fields, as needed. 11. Repeat Steps 3 through 9 for each PC in the Devices tree. 12. Save and exit the Device Table.
2-68
Note
You cannot cancel print jobs submitted by other users unless you have Full Control access permissions. Members of the Administrators, Server Operators, or Print Operators group have Full Control by default.
2-69
2-70
Benefits of WinStation
No additional training is required to use it. From an end users perspective, this new 32-bit application functions exactly the same way as the 16-bit version. If youre already familiar with the 9700 System, you will see no difference in the way it works. The WinStation Client application increases the functionality of the workstation by allowing other applications not only to reside on the clients, but to be run simultaneously with the 9700 application. This affords the user access to all of the multitasking capabilities, functionality, and high performance of 32-bit programs running under Windows 2000. For example, a golf resort pro shop could assist a guest who requests a tee time by simply minimizing the MICROS 9700 application (which is used to ring retail and greens fee transactions) and accessing the tee time scheduler. You can integrate the WinStation Client application into your existing 9700 System, and it will coexist with your DOS clients. A comparison of peripheral support between the DOS Client and the WinStation Client application is shown in the table on page 2-72. This application has desktop security features you can enable so that users can access the Windows Desktop on a WinStation Client only if they are privileged to do so. Employee Class Supervisory Privileges and associated keycodes must be enabled to minimize the 9700 application window and access the Windows Desktop. Refer to page 2-74 for more information.
2-71
Cash Drawer (standard DIN connection) TCP/IP Connectivity LCC Connectivity Integrated Mag Card Reader External MCR (RS232) External (keyboard) Internal Rear Display External Pole Display Scanner (RS232) Scanner (keyboard) Specta Physics Scanner (V1.04 only) Scale Coin Dispenser (RS232) NA LDS (RS232) Host Communications PMS Interface Touchscreen Mouse WMF Keylock Standard (PMS Interface) MAAS S&B Chipcoin CKD Krone Krone Germany Local VSS
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y N Y
Y Y N Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y Y Y N N Y Y
2-72
Device
DOS Client
WinStation Client
Printers (IDN) Epson 290 Slip Epson 290II Slip Thermal Printer TMT80 TMT88 Ithaca Printer (roll) Ithaca Printer (validation) TM300 (Japanese only) Epson TM300 Fiscal Bematech (MD20) Fiscal Printers (RS232) None Printers (parallel) Epson TMT88 Laser Printer Line Printer Diagnostics Touchscreen Macro
Y Y Y Y Y Y Y Y Y Y
Y Y N N Y N N N Y N
Y Y Y Y
Y Y Y N
2-73
The Autologon procedure is automatically disabled by the WinStationStart.exe program if a user other than micros:micros logs on. The second layer of security is based on the WinStation Client application and the MICROS 9700 user login. This layer of security prevents anyone from switching from the WinStation application to another application without being logged in. By default, the WinStation Client application blocks the user from the use of certain shortcut keys which are used to switch or close applications. The table below identifies which shortcut keys are enabled when a user signs in. Shortcut Keys Ctrl+Esc to display the Start menu Ctrl+F4 / ALT+F4 to close the application Windows icon key to display the Start menu (may or may not be included on your keyboard) Alt+Tab to switch between programs Is this shortcut enabled? No No No
Yes
2-74
Note
The shortcut keys for the Minimize and Close buttons are disabled while the WinStation Client application is in the foregroundeven for authorized users.
2-75
Touchscreen Icons
Identical standard sets of the DOS (.px) and WinStation (.ico) icons are included with the 9700 System software. During the installation, they are stored in the following directories: DOS icons: Micros\LES\Pos\9700\xdt3\bitmaps\ws_icons WinStation icons: Micros\LES\Pos\9700\xdt3\bitmaps\winstation_icons If you are upgrading from 8700 or from an earlier version of 9700 (prior to Version 1.50), an identical set of .ico icons is automatically created from your set of .px icons during the upgrade. The new set of icons is placed in the Micros\LES\Pos\9700\xdt3\bitmaps\winstation_icons directory.
2-76
After you have read the 9700 V. 3.0 System Setup documentation, click Next to continue. 10. The Customer Information screen displays, seen below:
Enter the User Name and Company Name, and click Next to continue.
2-77
11. The Winstation Setup Type screen displays, seen below. Configure your system setup type based on the detailed description below:
2-78
13. The Start Copying Files Summary screen displays, seen below.
Once you have confirmed these settings, click Next to start the WinStation installation. 14. After a few moments the installation finishes, and the InstallShield Wizard Complete screen displays, seen below.
To complete the installation select Yes, I want to restart my computer now., and click Finish. 15. Proceed to Configuring the WinStation Client Application on page 2-80.
2-79
2-80
For example, if the number is 374236, the formula would be 3 x 7 + 2 + 6 = 29. 4. Type the Access Code for the workstation and press Enter. The Access Code provides entry to the configuration options. 5. Press the Configuration button. 6. Press the PC Interface button. 7. Press the Set Primary Address button. 8. Type the servers IP address in the Primary Host TCP/IP Name field and press Enter. 9. Press the Set Primary SCC Number button, enter the SCC range, and press Enter. 10. Press the Previous Menu button twice, then press Yes when you are prompted to save the changes. 11. Press the Restart button. 12. Repeat Steps 1 through 11 on each WinStation Client workstation in the system.
2-81
2-82
7. Press Enter twice. 8. Using the left/right cursor keys, select Save | Quit | Quit | Exit. 9. Proceed to Configuring the WS4 Serial Client Workstation, on page 2-84.
2-83
4. Type the Access Code for the workstation and press Enter. The Access Code provides entry to the configuration options. 5. Select Configuration | COM Ports. 6. Set COM 4 to Host Communications. 7. Increase the PC Port Baud Rate (e.g., 38400). 8. Save and exit the Configuration mode. 9. Restart the workstation.
2-84
Configuring NetCCs
Converting From an 8700 System to a 9700 System
For users converting from the 8700 System to the 9700 System, the NetCC is the replacement for the 8700 LCC/RCC combination. LCCs must be replaced by one or more NetCCs. RCCs can still be supported in 9700 via NetCC, but please note the following: Up to six RCCs can be connected to a NetCC device.
Important If RCC(s) are required in your system, you can only connect them to ports 1 through 6 of the NetCC. An RCC connected to Note
port 7 or 8 is not supported.
In the Device Table, make sure the CC numbers of the RCCs that are connected to the NetCC are correct. After converting to a 9700 System, these may need to be changed from the settings they used when connected to the old LCC. For detailed information on RCCs, refer to the 8700 HMS Programming Manual and the 8700 HMS PC Workstation Configuration & Installation Guide. Refer to pages 2-95 and 2-96 for examples of a NetCC/RCC setup.
2-85
The shaded area in the diagram below identifies the difference between an LCC/ RCC configuration and a NetCC/RCC configuration.
Server Server
LCC
LAN
NetCC
RCC
RCC
UWS/3 UWS/3
UWS/3 UWS/3
Each NetCC comes with the most current version of the NetCC application stored on the NetCCs Flash ROM. The NetCC application can also be updated using the 9700 Confidence Test. The NetCC Hardware kit includes the document, Installing the Network Cluster Controller, P/N MD0006-004. Please refer to that document for detailed hardware diagrams and hardware installation instructions.
2-86
Note
In most cases, the MICROS 9700 POS and MICROS POS Multiplexer services will automatically start when the server PC is turned on. By default, the MICROS 9700 Bootp/Tftp service is set up to start manually and can be changed from the Services window by selecting Startup | Automatic | OK.
2-87
2-88
Once you have gathered this information, follow the steps below to modify the bootptab file: 1. In the X:\Micros\LES\Pos\9700\etc directory (where X: is the drive where the 9700 System is installed), open the bootptab file with Microsoft Notepad. The bootptab file will display in text format. 2. Modify the bootptab by entering the information below. Be sure to replace the bold and italicized entries with the actual information youve just gathered. Refer to the Single PC System and Multiple (Backup) PC System examples below.
.nccdefault:sm=net mask:to=auto:ht=1:\ bf=NETCCAPP.IMG:\ vm=rfc1084:\ cs=PrimaryserverIP address, BackupserverIP address NetccName.DomainName:tc=.nccdefault:ha=MAC address:ip=NetCCIP address
2-89
Note
The fields that display on a Devices form are determined by the selection made in the Type drop-down list.
8. Enter the name of the NetCC device in the Name field (overwrite the default name). 9. Enter the NetCCs IP address in the IP Address field (overwrite the default address). 10. Select the PC number that the NetCC is connected to in the Primary PC dropdown list. The drop-down list includes all of the PCs that have been defined in the Devices file.
2-90
11. The CC # field defaults to the next available number for the selected device type. Either use the default value or select another value from the drop-down list. NetCCs and SCCs have their own unique sets of Cluster Controller Numbers. Each time you add a NetCC or SCC, the CC # drop-down list will only display the available (unused) cluster controller numbers for that device type.
Note
12. Click OK. 13. Click or select File | Save from the Menu Bar to save the changes. If youre upgrading your system from 8700 to 9700, dont forget to update the Device Tablethe CC numbers and channels of the devices you have attached to the NetCC may have changed! In addition, the 9700 System will not communicate with any NetCCs that do not have devices assigned to them in the Device Table. 14. Select File | Exit close the 9700 Enterprise Management Console.
Note
2-91
Troubleshooting NetCCs
This section may help to answer NetCC setup questions or address a problem you experienced while setting up the NetCC.
I entered the wrong IP address for my NetCC in the bootptab file. Can I just open the bootptab file again and change it?
Sure you can! But there is one thing you need to do after you have modified and saved the bootptab file with the new (correct) IP addressflush the Address Resolution Protocol (ARP) cache. The ARP is a cache that updates regularly, so you dont want to have the old IP address still in there. Follow these steps to flush the ARP cache: 1. From the Windows Desktop, select Start | Programs | Command Prompt. The Command Prompt window displays. 2. At the command prompt, type arp -a to view the existing IP addresses in the ARP cache. 3. Type arp -d X (where X is the IP address you wish to delete).
I modified the bootptab file. How can I make sure if I did it right?
Once youve set up the NetCC hardware and modified the bootptab file, you can check the following: POWER and ONLINE LEDsThe POWER LED will light up as soon as youve plugged the NetCC into the socket. About 15 seconds after plugging in the NetCC, the ONLINE LED should light up. If the POWER LED does not light up, you may have a faulty power source. If the ONLINE LED does not light up, you may have a defective NetCC. Contact your MICROS installer for help. LINK LEDThis LED is lit when the NetCC has established a successful physical network connection with the server.
2-92
NetCC pingYou can ping the NetCC using the ping command from the Command Prompt window. 1. From the Windows Desktop, select Start | Programs | Command Prompt. The Command Prompt window displays. 2. At the command prompt, type ping X (where X is the NetCCs IP address). You should receive a message that looks something like this: Reply from X: bytes=32 time<32ms TTL=128. If you receive the message Request timed out, check the network topology to ensure that a route exists between the Bootp server and the NetCC.
Okay, so that works. Now how do I know if Ive configured the NetCC correctly?
Once you have entered the NetCCs information into the Devices file, you can verify that the installation was a success through Confidence Test and the 9700 Control Panel. Confidence TestHeres how would you use it to check for the NetCC: 1. From the Windows Desktop, select Start | Programs | Micros Systems 9700 | Enterprise Management Console (EMC). 2. Select the database server, type your username and password, then click Connect. 3. Once EMC opens, navigate to the Control Panel module, and click the Database button to bring the System up. 4. From the Windows Desktop, select Start | Programs | Micros 9700 | 9700 Confidence Test. The Confidence Test window displays. 5. DEVICE TABLE should be highlighted by default. Press Enter. The Device Diagnostics window displays. 6. Right-arrow over to NETCCX (Where X is the CC number youve assigned to the NetCC) to highlight it and press L. A Loopback box displays in the window, which lists Send, Receive, and Timeout. If you see the Send and Receive lines displaying numbers, youve successfully hooked the NetCC up to your system.
2-93
CC TableUse the Cluster Controllers module to check the status of NetCC. With the 9700 System up and running, click on the CC Table module on the left menu bar of the EMC. The Cluster Controllers window displays, which lists the Cluster Controllers and the status for each of them. The NetCCs status should be Active. Additional TestingIf the Confidence Tests Loopback for the NetCC timed out, or the Cluster Controller Status window listed the NetCCs status as Down, you can check the following: Verify the NetCCs IP address in the Devices file matches its IP address in the bootptab file. Verify the device connected to the NetCC (and listed in the Devices file) is set up and configured correctly, i.e., the Primary PC number, CC #, and CC Channel are correct. Verify the NetCCs CC # matches the attached devices CC # in the Devices file.
2-94
NetCC/RCCSetup Example
If you upgrade your system from 8700 to 9700, and you want to maintain the current RCCs, youll need to connect the RCCs to the NetCCs. Then, add the NetCCs and RCCs to the Devices file in the 9700 Enterprise Management Console for PC1. The sample screens below show how these devices are set up to enable NetCC/ RCC.
New NetCC
Must match the Number field for the NetCC. Defaults to the next available channel. Must match the PC Number field for the NetCC.
New RCC
Note: RCCs can only be added to a NetCC device. If you add an RCC to any other device type, it will automatically default to the first NetCC in the Devices file when the changes are saved.
Once you have finished configuring the files, you can run Confidence Test and select Device Table to view the device status, as shown below.
2-95
Defaults to the next available channel. Must match the PC Number field for the NetCC. (Backup PC)
Note: RCCs can only be added to a NetCC device. If you add an RCC to any other device type, it will automatically default to the first NetCC in the Devices file when the changes are saved. In a MICROS Operational Resiliency system, make sure you select the correct PC number in the directory tree when you add the NetCCs.
Once you have finished configuring the files, you can run Confidence Test and select Device Table to view the device status.
Note
The backup PC will not display in Confidence Test unless it is the active PC.
2-96
CC Table
System
Yes
Yes
CC_Table
The following table breaks down the CC Table database file into the subordinate fields which are used by 8700sql: Field Name Record Number CC Type CC Number Field Mnemonic number cc_type cc_number Type Code N9 N1 N3 Max. Width 9 1 3 Range 1 - 999,999,999 1-2 For SCCs: 8 - 14 For NetCCs: 1-7 129 - 143 145 - 159 161 - 175 193 - 207 209 - 223 225 - 239 Description IP Address PC Number description ip_address pc_number A32 A15 N2 32 15 2 0 -32 0 - 15 0 - 32
2-97
Follow the steps below to view the CC Table in the Enterprise Management Console. 1. From the Windows Desktop, double-click on the 9700 Enterprise Management Console icon. 2. Type a valid ID (password) in the User ID field and click OK. 3. Select System Hardware | Devices. 4. Click to open Table View.
2-98
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2-99
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2. The SQL Server Enterprise Manager displays. In the directory tree on the left window, Expand Microsoft SQL Server | SQL Server Group | 3.0 Server Name. Next, Expand Management | Database Maintenance Plans. The Sample Database Maintenance Plans installed with a 9700 V. 3.0 install or upgrade display, seen below.
The Sample MS-SQL Database Plans installed with 9700 V. 3.0 are shown in blue above. Please follow the detailed instructions for configuring each Maintenance Plan: MCRSPOS SQL Simple User DB Maintenance Plan, page 2-101 MCRSPOS SQL User DB Maintenance Plan, page 2-104 MCRSPOS SQL User DB Reorganize Data Maintenance Plan, page 2-110
2-100
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
Note
To ensure proper configuration of the MCRSPOS SQL Simple User DB Maintenance Plan, the necessary settings for each of the six tabs seen aboveGeneral, Optimizations, Integrity, Complete Backup, Transaction Log Backup, Reportingwill be detailed in the steps below. If a tab is not listed, no configuration changes are needed to options on this tab.
2-101
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2-102
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
AA. Set Occurs to Daily BB. Set Daily Frequency to Occurs Once at
Time Dependant on SOD\EOD set it up for 2 hours after to be safe.
2-103
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
Note
To ensure proper configuration of the MCRSPOS SQL User DB Maintenance Plan, the necessary settings for each of the six tabs seen aboveGeneral, Optimizations, Integrity, Complete Backup, Transaction Log Backup, Reportingwill be detailed in the steps below. If a tab is not listed, no configuration changes are needed to options on this tab.
2-104
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2-105
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
AA. Set Occurs to Daily BB. Set Daily Frequency to Occurs Once at
Time Dependant on SOD\EOD set it up for 2 hours after to be safe.
2-106
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
C. Check Create a sub-directory for each database D. Check Remove files older than
Set to 4 days
2-107
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
User DB Maintenance | Transaction Log Backup Tab | Edit Recurring Job Schedule
AA. Set Occurs to Daily BB. Set Daily Frequency to Occurs Once at
Time Dependant on SOD\EOD set it up for 2 hours 10 minutes after to be safe (this should be offset from the Complete Backup).
2-108
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2-109
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
Note
To ensure proper configuration of the MCRSPOS SQL User Reorganize Data Maintenance Plan, the necessary settings for each of the six tabs seen aboveGeneral, Optimizations, Integrity, Complete Backup, Transaction Log Backup, Reportingwill be detailed in the steps below. If a tab is not listed, no configuration changes are needed to options on this tab.
2-110
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2-111
9700 Software Platform Installation Backing Up the System: MS-SQL Maintenance Plans
2-112
Chapter 3
3
Software Maintenance
In This Chapter
This chapter discusses the maintenance of the 9700 System software. Specifically, this includes what youll need to do to upgrade your existing MICROS 8700 HMS or 9700 HMS System to the latest version of 9700 software, MS-SQL or Oracle. This section also includes instructions on how to upgrade MICROS peripheral applicationsthe Remote Management Console, the BootP service, and the WinStation client application.
Upgrading to 9700 V. 3.0.................................................................3-2 MS-SQL Upgrades ..........................................................................3-3 Oracle Upgrades ............................................................................3-33 Upgrading MICROS Peripheral Applications ...............................3-63
3-1
3-2
MS-SQL Upgrades
This section details the three scenarios of MS-SQL upgrades: For a detailed description of upgrading a previous version of 9700 to 9700 V. 3.00 using the same server, refer to: Previous Version of 9700 > 9700 Version 3.0 MS-SQL, using existing 9700 Server on page 3-4
For a detailed description of upgrading a previous version of 9700 to 9700 V. 3.00 using a different server, refer to: Previous Version of 9700 > 9700 Version 3.0 MS-SQL, using new 9700 Server on page 3-16
For a detailed description of upgrading an 8700 system to 9700 V. 3.00 using a different server, refer to: 8700 > 9700 V. 3.0 MS-SQL on page 3-24
Note
Detailed instructions for upgrading MICROS peripheral applications, such as: -Remote Management Console -BootP Server -WinStation Client Can be found at Upgrading MICROS Peripheral Applications on page 3-63.
3-3
Previous Version of 9700 > 9700 Version 3.0 MS-SQL, using existing 9700 Server
Before you begin
Prior to any 9700 upgrade, you must perform the following tasks to ensure data integrity: - Take a full backup of your system. - Close all open guest checks. - Run End-of-Day. - Settle all credit card batches. - Clear all guest checks. - Reset the Audit Trail log.
3-4
Note
If you are upgrading an EBUTO system and plan to use MICROS Operational Resiliency, you must upgrade the Primary PC first. If you are upgrading a single PC, you cannot upgrade it to a MICROS Operational Resiliency system. The upgrade process can only upgrade similar system configurations (i.e., upgrade a single PC to a single PC). To upgrade a single PC system to a MICROS Operational Resiliency system, you must re-install the 9700 HMS software from scratch, and follow the prompts to configure a MICROS Operational Resiliency pair.
3-5
3-6
Upgrading your Previous 9700 System to a 9700 V. 3.0 System with MS-SQL
After you have backed up the previous 9700 system and database, upgraded your operating system to Windows 2000 Server with SP4 or Windows 2003 server, and installed MS-SQL, youre ready to upgrade to 9700 V. 3.00. Please note that your existing database will be automatically upgraded during the installation process. 1. Close all programs and return to the Windows Desktop. 2. Insert the 9700 Version 3.0 CD into the PCs CD-ROM drive. The 9700 HMS splash screen displays briefly...
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3-7
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation. 4. The Select the Database Type screen displays, seen below.
3-8
5. The Database Information screen displays, (Local Machine configuration shows) seen below. Configure the screen according to the installation parameters detailed below:
Remote Machine - choose this option if Microsoft SQL Server is NOT located on the server you are installing 9700 Version 3.0 on, i.e., a remote installation off the sites network. Enter the computer name or the static IP address to identify the MS-SQL server on the network.
Password -
Once you have configured this screen accordingly, click Next to continue.
3-9
The default Database Name is MCRSPOS. If you wish to change the name, type the new name into the field. Once you have decided the Database Name, click Next to continue. 7. The MICROS Database Owner screen displays, seen below. Enter the name and password for the User that will own the MICROS MS-SQL database.
The default Database Owner User Name and Password are both microsdb. If you wish to change the User Name or Password, change the values now. Once you have decided the Database Owner User Name and Password, click Next to continue the installation.
3-10
8. The SQL Server Database File Location screen displays, seen below. Select the Folder where you would like the SQL Server Database files to be saved.
Accept the default location, or click Browse to select a different location. Once you have selected the Destination Folder, click Next to continue the installation. 9. A 9700 HMS Setup status message displays, seen below.
This message informs the user that Setup will install a Sample 9700 Database Maintenance Plan. For details on the Sample 9700 Database Maintenance plan, refer to Backing Up the System: MS-SQL Maintenance Plans on page 2-99. After you have read this message, click Next to continue.
3-11
Accept the default location, or click Browse to select a different location. Once you have selected the Destination Folder, click Next to continue the installation. 11. The 9700HMS Upgrade Installation Summary screen displays, seen below.
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next to continue the installation.
3-12
12. After you click Next, a 9700 HMS Setup Status message appears.
Once you have read the Note above, click Yes to continue the installation. If you do not wish to upgrade at this time, because it will stop your local system processes, click No to abort the installation. Once you click Yes... 13. ...The installation starts. Status windows allow the user to monitor the progress of the installation. 9700 Version 3.0 first installs Cygwin, seen below
...Once the Cygwin installation completes, 9700 Version 3.0 begins installing the 9700 Server files, seen below...
3-13
This message notifies the user of the location of the RDBPrecheck log. This log records modifications made to the pre-3.0 database. Some modifications may be necessary to ensure referential integrity between for the 3.0 system. Click Next to continue. 15. A 9700 HMS Setup Status message displays, seen below.
This message notifies the user that the IIS port has been changed to 8080. To continue the installation, click OK.
If there is a USB Software Key attached to the server, please remove it from the server now, and attach it after the installation has completed. Once you have removed the USB Software Key, if applicable, click OK to continue.
3-14
18. After a few moments, the InstallShield Wizard Complete screen displays, seen below.
To complete the 9700 Version 3.0 upgrade installation, select Yes, I want to restart my computer now., then click Finish.
3-15
Previous Version of 9700 > 9700 Version 3.0 MS-SQL, using new 9700 Server
Before you begin
Prior to any 9700 upgrade, you must perform the following tasks to ensure data integrity: - Take a full backup of your system. - Close all open guest checks. - Run End-of-Day. - Settle all credit card batches. - Clear all guest checks. - Reset the Audit Trail log.
3-16
On the Old Server, Copy the pc1 directory to the \MICROS\LES\POS\9700 directory of the New Server. You can do this by ftp, or since both PCs are on the network, by a direct copy and paste. On the New Server, run the Database Conversion Utility.
Note
If you are upgrading an EBUTO system and plan to use MICROS Operational Resiliency, you must upgrade the Primary PC first. If you are upgrading a single PC, you cannot upgrade it to a MICROS Operational Resiliency system. The upgrade process can only upgrade similar system configurations (i.e., upgrade a single PC to a single PC). To upgrade a single PC system to a MICROS Operational Resiliency system, you must re-install the 9700 HMS software from scratch, and follow the prompts to configure a MICROS Operational Resiliency pair.
3-17
3-18
Note
If you have already decompressed your previous 9700 database, or elected to directly copy the pc1 directory over the network, please proceed to Using the Database Conversion Utility on page 3-21
1. Close all programs and return to the Windows Desktop. 2. On the 9700 V. 3.0 server, navigate to \MICROS\LES\POS\9700, seen below. Make sure the database from the previous 9700 system is located here (seen below). As a safety precaution, rename the existing pc1 directory (seen below).
3. Once you have verified the previous 9700 database file is present, and you have renamed the previous pc1 directory, open a Cygwin shell prompt.
3-19
4. Once in the \MICROS\LES\POS\9700 directory, decompress the previous 9700 database using the Cygwin shell prompt, as seen below.
To decompress the previous 9700 database, enter the UNIX command, zcat filename | tar xvf (where filename = database name), then press Enter. 5. The file decompression process begins...After a few moments, the decompression process completes, and you will be returned to the $ prompt.
Please note that this process creates a new pc1 directory. 6. Once you have decompressed the previous 9700 database, continue to Using the Database Conversion Utility.
3-20
3-21
The Utility recognizes the previous database version (Current DB Version field), and indicates what version (New DB Version field) it will be upgraded to. Once you have reviewed these settings, Click Continue to begin the conversion process. 4. A Database Conversion message appears, seen below.
3-22
6. After a few minutes, the Database Conversion finishes, and the Conversion confirmation window displays, seen below.
3-23
3-24
Transfer the compressed 8700 V. 3.00 Database to the 9700 V. 3.0 Server. On the 9700 V. 3.0 Server, convert the 8700 Version 3.0 database to a 9700 V. 3.0 database.
Note
If you are upgrading an EBUTO system and plan to use MICROS Operational Resiliency, you must upgrade the Primary PC first. If you are upgrading a single PC, you cannot upgrade it to a MICROS Operational Resiliency system. The upgrade process can only upgrade similar system configurations (i.e., upgrade a single PC to a single PC). To upgrade a single PC system to a MICROS Operational Resiliency system, you must re-install the 9700 HMS software from scratch, and follow the prompts to configure a MICROS Operational Resiliency pair.
3-25
Note
If your system is already installed with 8700 Version 3.0, skip this section, and proceed to Transfer the Database on page 3-27.
Before you begin the procedure below, make sure the Windows 2000/2003 PC and the UNIX PC are available on the network, and that they can ping each other. Follow the steps below to upgrade your 8700 database to Version 3.0. 1. On the UNIX Server, perform a Micros Stop. 2. On the Windows 2000/2003 Server, insert the 9700 V. 3.0 CD into the PCs CD-ROM drive. If the CD automatically starts, simply cancel the installation process. 3. Through Windows Explorer, navigate to the CD-ROM drive. Right-click the CD-ROM drive, and Select Explore. 4. Copy the entire Unix_DB_Conversion_Utility folder to the C drive. This folder contains all of the conversion utilities to convert any 8700 database up to a 3.0 database. You may not need all of these utilities, but it doesnt hurt to have all of them to ensure you have everything you need to convert to Version 3.0. 5. From the Windows Desktop, select Start | Run. 6. Type cmd and click OK to open a command prompt. 7. Change to the C:\Unix_DB_Conversion_Utility directory that you created in Step 4. 8. Type the following command: ftp ip_address and press Enter. (where ip_address is the IP address of the UNIX PC) -ORftp name and press Enter. (where name is the UNIX PC name) 9. Type the root username and press Enter.
3-26
10. Type the password and press Enter. 11. Type cd usr/8700/bin and press Enter. 12. Type bin and press Enter. 13. Type mput db* and press Enter. 14. Type y and press Enter. 15. Type mput conv* and press Enter. This command will start the transfer process of all of the database conversion utilities. Again, you may not need all of these utilities, but it doesnt hurt to transfer all of them. 16. Type y and press Enter each time you are prompted to transfer a conversion utility (e.g., mput convert120?, mput convert150?, mput convert201?, etc.). When all of the conversion utilities are transferred, the ftp> prompt will display. 17. Type quit to end the transfer session. You are now ready to convert your database to 8700 Version 3.0. 18. On the UNIX Server, type the following at the UNIX command prompt: mkdev m8700 and press Enter. The MICROS 8700 Maintenance and Installation Script menu displays. 19. Type menu option 11 and press Enter. Your database will convert to Version 3.0. 20. Proceed to Transfer the Database below.
3-27
4. At the command prompt, type the following to switch to the m8700 user. Type su m8700 5. Change directories to pc1. 6. At the command prompt, create a db.tar.Z file in the 9700 directory by typing: tar cvf db | compress > db.tar.Z 7. On the Windows 2000/2003 Server, login as the administrator. 8. Open the Cygwin shell prompt from Start | Programs | MICROS Systems 9700. 9. Change directories to the 9700 directory by typing the following command: cd drive_letter\Micros\LES\Pos\9700\ (where drive_letter is the drive where the 9700 System is installed) 10. Type the following command: ftp ip_address (where ip_address is the IP address of the UNIX PC identified in Step 2.) 11. Login with the root username and password. 12. Type the following command: cd /usr/8700/pc1 13. Set the file transfer type to support binary image transfer by typing: bin 14. Transfer the file to the 9700 directory of the Windows 2000/2003 Server by typing: get db.tar.Z 15. When the transfer is complete, type: bye
Note
As a precautionary measure on the Windows 2000/2003 server, rename your existing pc1 directory, as the decompression process will overwrite this directory.
16. On the Windows 2000/2003 Server, open a Cygwin shell. From the 9700 directory, type the following command: zcat db.tar.Z | tar xvf The files that are being uncompressed will scroll on the screen and a new pc1 directory will be created.
3-28
Note
Follow the steps in this section if you are: Upgrading a single PC system or upgrading the Primary PC in a MICROS Operational Resiliency system. If you are upgrading an EBUTO System to a MICROS Operational Resiliency System, the Secondary PC will retrieve the converted database from the Primary PC as part of the installation process.
3-29
The Utility recognizes the previous database version (Current DB Version field), and indicates what version (New DB Version field) it will be upgraded to. Once you have reviewed these settings, Click Continue to begin the conversion process. 4. A Database Conversion message appears, seen below.
3-30
6. After a few minutes, the Database Conversion finishes, and the Conversion confirmation window displays, seen below.
3-31
Install the Remote Enterprise Management Console (Remote EMC) on the Clients
After youve completed the upgrade from 8700 to 9700, youre ready to install the Remote Enterprise Management Console on the clients in the system. Refer to Installing Remote Enterprise Management Console (Remote EMC) on page 2-52 for installation instructions.
3-32
Oracle Upgrades
This section details the three scenarios of Oracle upgrades: For a detailed description of upgrading a previous version of 9700 to 9700 V. 3.00 using the same server, refer to: Previous Version of 9700 > 9700 Version 3.0 Oracle, using existing 9700 Server on page 3-34
For a detailed description of upgrading a previous version of 9700 to 9700 V. 3.00 using a different server, refer to: Previous Version of 9700 > 9700 Version 3.0 Oracle, using new 9700 Server on page 3-46
For a detailed description of upgrading an 8700 system to 9700 V. 3.00 using a different server, refer to: 8700 > 9700 Version 3.0 Oracle on page 3-54
Note
Detailed instructions for upgrading MICROS peripheral applications, such as: -Remote Management Console -BootP Server -WinStation Client Can be found at Upgrading MICROS Peripheral Applications on page 3-63.
3-33
Previous Version of 9700 > 9700 Version 3.0 Oracle, using existing 9700 Server
Before you begin
Prior to any upgrade, you must perform the following tasks to ensure data integrity: -Take a full backup of your system -Close all open guest checks -Run End-of-Day -Settle all credit card batches -Clear all guest checks -Reset the audit trail log
3-34
Note
If you are upgrading an EBUTO system and plan to use MICROS Operational Resiliency, you must upgrade the Primary PC first. If you are upgrading a single PC, you cannot upgrade it to a MICROS Operational Resiliency system. The upgrade process can only upgrade similar system configurations (i.e., upgrade a single PC to a single PC). To upgrade a single PC system to a MICROS Operational Resiliency system, you must re-install the 9700 HMS software from scratch, and follow the prompts to configure a MICROS Operational Resiliency pair.
3-35
3-36
Upgrading your Previous 9700 System to a 9700 V. 3.00 System with Oracle
After you have backed up the previous 9700 system and database, upgraded your operating system to Windows 2000 Server with SP4 or Windows 2003 Server, and installed Oracle 9i, youre ready to upgrade to 9700 Version 3.00. Please note that your existing database will be automatically upgraded during the installation process. 1. Close all programs and return to the Windows Desktop. 2. Insert the 9700 Version 3.0 CD into the PCs CD-ROM drive. The 9700 HMS splash screen displays briefly...
3-37
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation. 4. The Select the Database Type screen displays, seen below.
3-38
5. The Database Information screen displays, (Local Machine configuration shown) seen below. Configure the screen according to the installation parameters detailed below:
Remote -
Once you have selected the Database Server location, click Next to continue.
3-39
3-40
Enter the Name and Password of the User that will use the OperaPOS database. MICROS defaults are MICROSDB and MICROSDB. Once you have entered the Opera POS database User and Password, click Next to continue. 8. The Tablespace Name screen displays, seen below.
The default MICROS 9700 Tablespace is MCRSPOS. If you wish to change the name, type the new name into the field. Once you have decided the Tablespace Name, click Next to continue.
3-41
9. The Opera POS Database File Location screen displays, seen below. Select the Folder where you would like the Opera POS Database files to be saved.
Accept the default location, or click Browse to select a different location. Once you have selected the Destination Folder, click Next to continue the installation. 10. The 9700 HMS Upgrade Installation Summary screen displays, seen below.
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next to continue the installation.
3-42
11. After you click Next, a 9700 HMS Setup Status message appears.
Once you have read the Note above, click Yes to continue the installation. If you do not wish to upgrade at this time, because it will stop your local system processes, click No to abort the installation. Once you click Yes... 12. The installation starts. Status windows allow the user to monitor the progress of the installation. 9700 Version 3.0 first installs Cygwin, seen below...
...Once the Cygwin installation completes, 9700 Version 3.00 begins installing the 9700 Server files, seen below...
3-43
This message notifies the user of the location of the RDBPrecheck log. This log records modifications made to the pre-3.0 database. Some modifications may be necessary to ensure referential integrity for the 3.0 database. Click Next to continue. 14. A 9700 HMS Setup Status message displays, seen below.
This message notifies the user that the IIS port has been changed to 8080. To continue the installation, click OK. 16. A status notification message displays, seen below.
If there is a USB Software Key attached to the server, please remove it from the server now, and attach it after the installation has completed. Once you have removed the USB Software Key, if applicable, click OK to continue.
3-44
17. After a few moments, the InstallShield Wizard Complete screen displays, seen below.
To complete the 9700 Version 3.0 upgrade installation, select Yes, I want to restart my computer now., then click Finish.
3-45
Previous Version of 9700 > 9700 Version 3.0 Oracle, using new 9700 Server
Before you begin
Prior to any 9700 upgrade, you must perform the following tasks to ensure data integrity: -Take a full backup of your system. -Close all open guest checks. -Run End-of-Day. -Settle all credit card batches. -Clear all guest checks. -Reset the Audit Trail log.
3-46
Note
If you are upgrading an EBUTO system and plan to use MICROS Operational Resiliency, you must upgrade the Primary PC first. If you are upgrading a single PC, you cannot upgrade it to a MICROS Operational Resiliency system. The upgrade process can only upgrade similar system configurations (i.e., upgrade a single PC to a single PC). To upgrade a single PC system to a MICROS Operational Resiliency system, you must re-install the 9700 HMS software from scratch, and follow the prompts to configure a MICROS Operational Resiliency pair.
3-47
3-48
Note
If you have already decompressed your previous 9700 database, or elected to directly copy the pc1 directory over the network, please proceed to Using the Database Conversion Utility on page 3-51.
1. Close all programs and return to the Windows Desktop. 2. On the 9700 V. 3.0 server, navigate to \MICROS\LES\POS\9700, seen below. Make sure the database from the previous 9700 system is located here (seen below). As a safety precaution, rename the existing pc1 directory (seen below).
3. Once you have verified the previous 9700 database file is present, and you have renamed the previous pc1 directory, open a Cygwin shell prompt.
3-49
4. Once in the \MICROS\LES\POS\9700 directory, decompress the previous 9700 database using the Cygwin shell prompt, as seen below.
To decompress the previous 9700 database, enter the UNIX command, zcat filename | tar xvf (where filename = database name), then press Enter. 5. The file decompression process begins...After a few moments, the decompression process completes, and you will be returned to the $ prompt.
Please note that this process creates a new pc1 directory. 6. Once you have decompressed the previous 9700 database, continue to Using the Database Conversion Utility.
3-50
3-51
The Utility recognizes the previous database version (Current DB Version field), and indicates what version (New DB Version field) it will be upgraded to. Once you have reviewed these settings, Click Continue to begin the conversion process. 4. A Database Conversion message appears, seen below.
3-52
6. After a few minutes, the Database Conversion finishes, and the Conversion confirmation window displays, seen below.
3-53
3-54
Transfer the compressed 8700 V. 3.00 Database to the 9700 V. 3.00 Server. On the 9700 V. 3.0 Server, convert the 8700 Version 3.00 Database to a 9700 V. 3.00 database.
Note
If you are upgrading an EBUTO system and plan to use MICROS Operational Resiliency, you must upgrade the Primary PC first. If you are upgrading a single PC, you cannot upgrade it to a MICROS Operational Resiliency system. The upgrade process can only upgrade similar system configurations (i.e., upgrade a single PC to a single PC). To upgrade a single PC system to a MICROS Operational Resiliency system, you must re-install the 9700 HMS software from scratch, and follow the prompts to configure a MICROS Operational Resiliency pair.
3-55
Note
If your system is already installed with 8700 Version 3.0, skip this section, and proceed to Transfer the Database on page 3-57.
Before you begin the procedure below, make sure the Windows 2000/2003 PC and the UNIX PC are available on the network, and that they can ping each other. Follow the steps below to upgrade your 8700 database to Version 3.0. 1. On the UNIX Server, perform a Micros Stop. 2. On the Windows 2000/2003 Server, insert the 9700 V. 3.0 CD into the PCs CD-ROM drive. If the CD automatically starts, simply cancel the installation process. 3. Through Windows Explorer, navigate to the CD-ROM drive. Right-click the CD-ROM drive, and Select Explore. 4. Copy the entire Unix_DB_Conversion_Utility folder to the C drive. This folder contains all of the conversion utilities to convert any 8700 database up to a 3.0 database. You may not need all of these utilities, but it doesnt hurt to have all of them to ensure you have everything you need to convert to Version 3.0. 5. From the Windows Desktop, select Start | Run. 6. Type cmd and click OK to open a command prompt. 7. Change to the C:\Unix_DB_Conversion_Utility directory that you created in Step 4. 8. Type the following command: ftp ip_address and press Enter. (where ip_address is the IP address of the UNIX PC) -ORftp name and press Enter. (where name is the UNIX PC name) 9. Type the root username and press Enter.
3-56
10. Type the password and press Enter. 11. Type cd usr/8700/bin and press Enter. 12. Type bin and press Enter. 13. Type mput db* and press Enter. 14. Type y and press Enter. 15. Type mput conv* and press Enter. This command will start the transfer process of all of the database conversion utilities. Again, you may not need all of these utilities, but it doesnt hurt to transfer all of them. 16. Type y and press Enter each time you are prompted to transfer a conversion utility (e.g., mput convert120?, mput convert150?, mput convert201?, etc.). When all of the conversion utilities are transferred, the ftp> prompt will display. 17. Type quit to end the transfer session. You are now ready to convert your database to 8700 Version 3.0. 18. On the UNIX Server, type the following at the UNIX command prompt: mkdev m8700 and press Enter. The MICROS 8700 Maintenance and Installation Script menu displays. 19. Type menu option 11 and press Enter. Your database will convert to Version 3.0. 20. Proceed to Transfer the Database below.
3-57
4. At the command prompt, type the following to switch to the m8700 user. Type su m8700 5. Change directories to pc1. 6. At the command prompt, create a db.tar.Z file in the 9700 directory by typing: tar cvf db | compress > db.tar.Z 7. On the Windows 2000/2003 Server, login as the administrator. 8. Open the Cygwin shell prompt from Start | Programs | MICROS Systems 9700. 9. Change directories to the 9700 directory by typing the following command: cd drive_letter\Micros\LES\Pos\9700\ (where drive_letter is the drive where the 9700 System is installed) 10. Type the following command: ftp ip_address (where ip_address is the IP address of the UNIX PC identified in Step 2.) 11. Login with the root username and password. 12. Type the following command: cd /usr/8700/pc1 13. Set the file transfer type to support binary image transfer by typing: bin 14. Transfer the file to the 9700 directory of the Windows 2000/2003 Server by typing: get db.tar.Z 15. When the transfer is complete, type: bye
Note
As a precautionary measure on the Windows 2000/2003 server, rename your existing pc1 directory, as the decompression process will overwrite this directory.
16. On the Windows 2000/2003 Server, open a Cygwin shell. From the 9700 directory, type the following command: zcat db.tar.Z | tar xvf The files that are being uncompressed will scroll on the screen and a new pc1 directory will be created.
3-58
Note
Follow the steps in this section if you are: Upgrading a single PC system or upgrading the Primary PC in an EBUTO system. If you are upgrading an EBUTO system, the Secondary PC will retrieve the converted database from the Primary PC as part of the installation process.
3-59
The Utility recognizes the previous database version (Current DB Version field), and indicates what version (New DB Version field) it will be upgraded to. Once you have reviewed these settings, Click Continue to begin the conversion process. 4. A Database Conversion message appears, seen below.
3-60
6. After a few minutes, the Database Conversion finishes, and the Conversion confirmation window displays, seen below.
3-61
3-62
Note
To install the Remote Enterprise Management Console, please follow the directions on 2-52.
3-63
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3-64
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation. 4. The Customer Information screen displays, seen below. Enter the User Name and Company Name, and click Next to continue the installation.
5. The Component Selection screen displays. This screen allows a user to configure what elements of the 9700 V. 3.0 software are installed during this installation session.
To upgrade the BootP Server, configure this screen as seen above. Once you have done this, click Next to continue.
3-65
6. The Installation Drive Selection screen displays, seen below. Select the drive to install the BootP Server on.
After you have selected the drive you want to install the BootP Server on, click Next to continue. 7. The BootP Server Installation Summary screen displays, seen below.
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have verified these settings, click Next.
3-66
8. The installation commences. Status windows allow the user to monitor the progress of the installation. Cygwin is installed first, seen below...
9. Once the Cygwin installation completes, the MICROS 9700 Setup: Diskless Boot Server screen displays, seen below.
After you have read the note, decide whether you want to Start Diskless UWS Boot Service when Windows starts. Click Next to continue the installation.
3-67
10. After a few moments, the installation completes. The InstallShield Wizard Complete screen displays, seen below.
To complete the BootP Server upgrade install, select Yes, I want to restart my computer now., then click Finish.
3-68
Note
Although the 9700 application is only supported on Windows 2000 Server with SP4, or Windows Server 2003, the Remote Management Console is supported on the following operating systems for the client: - Windows 2000 - Windows XP - Windows Server 2003
After you have backed up the system, you are ready to upgrade the Remote Management Console on the clients in the system. Follow the steps below to upgrade the 9700 Remote Management Console on the client. These steps must be performed on each client in the 9700 System. 1. Close all programs and return to the Windows Desktop. 2. On the client running the Remote Management Console, insert the 9700 System CD into the PCs CD-ROM drive. The CD automatically starts, and the 9700 HMS splash screen displays briefly...
3-69
...and then the main installation screen, the Welcome to the InstallShield Wizard for 9700 HMS screen displays, seen below.
3. After reading the 9700 V. 3.0 System Setup documentation, click Next to continue the installation. 4. The Remote Management Console Installation Summary screen displays, seen below.
This screen provides a summary of all the parameters defined in the previous steps. Review these settings to make sure these are the correct installation parameters. Once you have tested these settings, click Next.
3-70
Upgrading will stop your local system processes. If you want to continue the installation click Yes, if not click No, and retry the installation at a time where system processes can be stopped. Click Yes to upgrade the Remote Management Console. 6. The Remote Management Console Upgrade installation commences. Status windows allow the user to monitor the progress of the installation.
3-71
7. After a few moments, the installation completes. The InstallShield Wizard Complete screen displays, seen below.
To complete the Remote Management Console upgrade install, select Yes, I want to restart my computer now., then click Finish.
3-72
Note
3-73
3-74
Click Next, to continue. 3. The Customer Information screen displays, seen below.
Enter the User Name and Company Name, then click Next to continue.
3-75
4. The Setup Type screen displays (Administrator Mode Configuration seen below). Choose the appropriate setup based on the descriptions below:
Once you have selected your WinStation Setup Type, click Next to continue. 5. The Installation Drive Selection screen displays, seen below.
3-76
Once you have reviewed these settings, click Next to continue the installation. 7. After a few moments, the InstallShield Wizard Complete screen displays, seen below.
Select Yes, I want to restart my computer now., then click Finish to complete the WinStation installation.
3-77
For example, if the number is 374236, the formula would be 3 x 7 + 2 + 6 = 29. 4. Type the Access Code for the workstation and press Enter. The Main Menu displays. 5. Select Go to MS Windows. 6. Open Windows Explorer. 7. Move the Win32.ini file from the Desktop to C:\Program Files\MICROS\WinStation Client. 8. Restart the WinStation Client application. 9. Repeat steps 2 - 4. 10. Select Configuration. Select COM Ports and reconfigure the devices attached to the com ports on the workstation.
3-78
Index
B
Backing up the System Bar Code Reader Bootp Service Installing Upgrading 2-99 1-4 Hardware Epson TM88 Thermal Printer Epson U200B Printer Recommendations Communication Options Printer Options Server Options Terminal Options Requirements 1-10 1-10 1-11 1-7 1-7 1-7 1-6
H
Hand-held Devices see Mobile MICROS Hand-held Terminal
2-54 3-64
C
Cancel a Print Job CA/EDC Credit Authorization Electronic Draft Capture Communications Intelligent Device Network (IDN) LAN PMS Interface TMS Interface Configuring NetCCs Credit Authorization see CA/EDC 2-69 1-4 1-4 1-4 1-2 1-3 1-2 1-2 1-3 2-85
I
Input Devices Bar Code Reader Liquor Dispensing System (LDS) Interface Installing the Database Server Microsoft SQL Server 2000 Oracle 9i 1-4 1-4 1-5 2-11 2-12 2-15
E
EBUTO see MICROS Operational Resiliency Eclipse PC Workstation Electronic Draft Capture see CA/EDC Epson TM88 Thermal Printer Epson U200B Printer 1-10 1-10 2-8
Installing the 9700 HMS Application 2-19 Before you begin 2-19 9700 V. 3.0 MS-SQL 2-21 to 2-33 9700 V. 3.0 OperaPOS 2-34 to 2-45 Installing 9700 V. 3.0 Components on Clients Bootp Service Remote Enterprise Management Console (EMC) Remote Management Console (RMC) Intelligent Device Network (IDN) Line Printers Order Printers Video Display Unit
1-8
Index-1
Index
K
Keyboard Workstation 4 KWS4 1-9 1-9
N
NetCCs Adding to the 9700 System 2-88 to 2-91 Before you Begin 2-87 CC Table Fields for use with 8700sql 2-97 configuring 2-85 Description 1-11 NetCC/RCC Setup for MICROS Operational Resiliency Pair-Example 2-96 NetCC/RCC Setup-Example 2-95 Troubleshooting 2-92 to 2-94 Network and Local Printing Configuring Printing in the Enterprise Management Console (EMC) TCP/IP Configuring Multiple Printers Configuring the Device Table Configuring the Device Table
L
LDS see Liquor Dispensing System (LDS) Interface Line Printers Liquor Dispensing System (LDS) Interface Local Area Network (LAN) 1-3 1-5 1-2
M
MICROS Operational Resiliency Installing New Upgrading EBUTO to Microsoft SQL Server 2000 (SP3) Installing Mobile MICROS Hand-held Terminal 2-8 2-8 2-9 2-11 2-12 1-9
O
Oracle 9i Installing Order Printers 2-11 2-15 1-3
MS-SQL Maintenance Plans 2-99 MCRSPOS SQL Simple User DB Maintenance Plan 2-101 to 2-103 MCRSPOS SQL User DB Maintenance Plan 2-104 to 2-109 MCRSPOS SQL User Reorganize Data Maintenance Plan 2-110 to 2-112 Multiple Network or Local Printers 2-66
P
PMS PostScript Printers Printer Network Line Printers Order Printers Video Display Units Printers Cancel a Print Job cancel a print job Epson TM88 Epson U200B Postscript Sample Printer Files Editing On the Server Testing Printing Options Printing in the 9700 Configurator 1-2 2-10
2-69 2-69 1-10 1-10 2-10 2-62 2-63 2-62 2-69 2-61
Index-2
Index
U
Upgrading MICROS Peripheral Applications 3-63 Bootp 3-64 Remote Management Console (RMC) 3-69 WinStation 3-73 Upgrading to 9700 V. 3.0 3-2
R
Remote Enterprise Management Console (EMC) Installing 2-52 Using 2-53 Remote Management Console (RMC) Installing Upgrading
2-47 3-69
S
Sample Printer Files Software Licensing Starting the 9700 System 2-62 2-2 2-59
System Security 2-3 Groups and Members/Passwords File Permissions for Member Server and Workgroup Configuration 2-7 9700 Installed in a Workgroup 2-6 9700 Installed on a Domain Controller 2-5 9700 Installed on a Member Server 2-5 Groups and Users/Passwords Domain Controller or Member Server2-3 Workgroup 2-4
MS-SQL Upgrades 3-3 Previous Version of 9700 Using Existing Server 3-4 to 3-15 Before You Begin 3-4 Upgrade Procedure 3-4 Previous Version of 9700 Using New Server 3-16 to 3-23 Before you Begin 3-16 Upgrade Procedure 3-16 8700 to 9700 Using New Server 3-24 to 3-32 Before you Begin 3-24 Upgrade Procedure 3-24 Oracle Upgrades 3-33 Previous Version of 9700 Using Existing Server 3-34 to 3-45 Before you Begin 3-34 Upgrade Procedure 3-34 Previous Version of 9700 Using New Server 3-46 to 3-53 Before you Begin 3-46 Upgrade Procedure 3-46 8700 to 9700 Using New Server 3-54 to 3-62 Before you Begin 3-54 Upgrade Procedure 3-54
T
Table Management System Interface see TMS TCP/IP printing Testing Printing Options TMS
V
2-60 2-69 1-3 VDU Video Display Unit see VDU 1-3
W
Windows Installing Post Install Setup 2-2 2-8
Index-3
Index
WinStation Benefits Client Security Configure the Server Configure the Workstation Configuring Fields, Security Options, and Function Buttons Installing Peripheral Support Requirements Touchscreen Icons Upgrading WinStation Client Application security touchscreen icons Workstation 4
2-71 2-74 2-80 2-81 2-70 to 2-81 2-75 2-76 2-72 2-71 2-76 3-73 2-70 2-74 2-70 1-8
Workstations Configuring as a WinStation client Configuring Workstation 4 (WS4) Clients Configure the Client Install the Serial Application Loader (SAL) Software Modifying the Configuration Overlay File (uws3.cfg) Performing the Confidence Test Eclipse Keyboard Workstation 4 (KWS4) Workstation 4 (WS4) WS4 Configuring Client Workstation install the SAL software Modifying the Configuration Overlay File (uws3.cfg) Performing the Confidence Test
Numerics
9700 HMS V. 3.0 Installing Upgrades 9700 System Backing up the System Input Devices starting 2-19 3-2
Index-4