Copyright
2006 MICROS Systems, Inc. All rights reserved. No part of this publication may be reproduced,
photocopied, stored on a retrieval system, or transmitted without the express prior written consent of the
publisher. MICROS Systems, Inc. retains the right to update or change the contents of this document
without prior notice. MICROS Systems, Inc. assumes no responsibility for the contents of this document.
OPERA is a trademark of MICROS Systems, Inc.
On Oracle and the On Oracle logo are trademarks of Oracle Corporation.
Information in this document is subject to change without notice.
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.
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 material.
Document Number:
PAGE 2
OCTOBER 2006
Table of Contents
VERSION 4.03 ...............................................................................................1
INTRODUCTION ................................................................................................4
PREREQUISITES ...............................................................................................4
ASSUMPTIONS .................................................................................................4
REQUIRED OPERATING SYSTEM CHANGES ....................................................5
Server Naming ............................................................................................................. 5
Disk Automount ............................................................................................................ 5
Network Configuration ................................................................................................... 5
CD Rom Drive............................................................................................................... 7
Enable Remote Desktop ................................................................................................. 7
Change TEMP and TMP variables ..................................................................................... 8
Startup and Recovery .................................................................................................... 9
Performance Settings ...................................................................................................10
Automatic Updates .......................................................................................................11
Internet Explorer Enhanced Security ..............................................................................11
Distributed Transaction Coordinator ...............................................................................12
PAGE 3
OCTOBER 2006
Introduction
This document describes the installation process using the cluster installation wizard, for the MICROS Cluster
System for Opera Version 4.0.03 and higher.
Please note that Oracle Fail Safe clusters are no longer supported with the introduction of this new solution
from Version 4.0.03 and higher.
Prerequisites
1.
For installation purposes, this document will assume that the installer has the technical ability to understand
the information and instructions within this document and will follows the steps contained in this document
to the letter.
2.
All installation steps outlined below should take place at the console. Using Windows2003
remote desktop with the /console option also works. Terminal server, VNC, Webex and
PCANYWHERE are not supported methods of installation. Do not install any software across a
network share. Install from local CD drives or hard drives.
3.
The cluster servers should not be a domain controller, DHCP, Wins or DNS server.
4.
The hardware required is a HP Packaged Cluster, or two servers (DL380, DL385, DL580, DL585) attached to
an MSA 500 Disk Array using SCSII cabling.
5.
The servers have been pre imaged with a Micros created Operating System Image. This image will be
different for each Major Account Client.
6.
Both Network Interfaces of both servers should be plugged into a switch. The use of a cross over cable
is not supported.
7.
Assumptions
The servers are imaged with Windows 2003 Standard or Enterprise Server.
In this example the cluster server names are set as NPLCLUST1 and NPLCLUST2. The server naming
conventions are left up to the site. Most Major Account Clients have established naming conventions valid
throughout their estate. The same applies to the IP addressing scheme of the servers.
This document also assumes that the hardware is setup correctly and configured per the hardware vendors
specifications and guidelines. If there are any hardware issues, including configuration, please contact your
hardware vendor.
The installation example in this document is per the OPERA standards outlined in the document.
PAGE 4
OCTOBER 2006
Disk Automount
Automount of new partitions needs to be enabled on both nodes.
Open a command prompt and type diskpart
Once in diskpart, type automount enable
Network Configuration
Select My Network Places Properties
Rename the NICs to the following:
NIC 1: Public
NIC 2: Interconnect
PAGE 5
OCTOBER 2006
Leave the Network Interface Cards on DHCP as they will be assigned during the wizard driven installation
process. Make sure the Interconnect NIC is plugged into a switch. The use of cross over cables for the
Interconnect NICs is not supported in the Opera 4.0.03 cluster.
For each NIC on both servers, go into File and Print Sharing
PAGE 6
OCTOBER 2006
CD Rom Drive
Rename the CD Rom drive to E:\ if it is not done already. Create a D:\ Partition on the remainder of Disk0.
PAGE 7
OCTOBER 2006
PAGE 8
OCTOBER 2006
Select Edit on the startup options and Modify the boot.ini file. Change the Execute entry to
/NoExecute=AlwaysOff
PAGE 9
OCTOBER 2006
Performance Settings
Select Start > Settings > Control Panel - System, and then click the Advanced tab.
Select Settings in the Performance section
Set Visual Effects to Adjust for best performance
Go to the Advanced tab Virtual Memory Change Set the size of the paging file to 4092
PAGE 10
OCTOBER 2006
Automatic Updates
Select Start > Settings > Control Panel - System, and then click the Automatic Updates tab.
Set Automatic Updates to Turn off
PAGE 11
OCTOBER 2006
PAGE 12
OCTOBER 2006
On the left hand side, you should see 2 controllers like below. If that is not the case, review the connection
between the servers and the SAN
REMARK: On some servers, you will see 3 controllers like below. You can ignore the 642 controller as its
sole purpose is providing a SCSI port to connect the servers to the MSA 500. This controller does not need
configuration.
Select the MSA500 G2. The configuration should look like below. If that is not the case, follow the manual
steps below to configure the MSA.
PAGE 13
OCTOBER 2006
On the right hand side, select Create Array and select disk 1 and 8
PAGE 14
OCTOBER 2006
Accept the default settings and select OK (Check Fault Tolerance is set to RAID 1+0)
PAGE 15
OCTOBER 2006
On the right hand side, select Create Array and select disk 2 and 9
PAGE 16
OCTOBER 2006
Accept the default settings and select OK (Check Fault Tolerance is set to RAOD 1+0)
On the right hand side, select Create Array and select all remaining drives by selecting Select All
PAGE 17
OCTOBER 2006
PAGE 18
OCTOBER 2006
PAGE 19
OCTOBER 2006
Allocate the complete disk (note that size value is different in this screen shot than it would be I reality)
PAGE 20
OCTOBER 2006
PAGE 21
OCTOBER 2006
Right click the first Extended Partition and select Create a Logical Drive
The New partition wizard will appear. Click Next
PAGE 22
OCTOBER 2006
PAGE 23
OCTOBER 2006
PAGE 24
OCTOBER 2006
PAGE 25
OCTOBER 2006
Click Next and you will be prompted for the Cluster Name and Public Node Names.
PAGE 26
OCTOBER 2006
PAGE 27
OCTOBER 2006
Enter the virtual IP address on which the Application Server will run.
PAGE 28
OCTOBER 2006
The Oracle Universal Installer will run some checks and be launched.
PAGE 29
OCTOBER 2006
Because we are not using additional NICs for the VIP addresses, the following message will appear. Click
OK and Click Next on OUI screen.
PAGE 30
OCTOBER 2006
The Oracle Universal Installer will be launched again in order to apply a patch. Both cluster nodes are
selected. Click Next.
PAGE 31
OCTOBER 2006
Additional patches are being applied. This takes a while. Do not close any DOS windows popping up.
PAGE 32
OCTOBER 2006
When this window appears, the wizard is moving the database files to the I: drive on the shared storage.
Note that the wizard recreates a new control file containing the new location of the datafiles, it is not just a
copy.
PAGE 33
OCTOBER 2006
PAGE 34
OCTOBER 2006
Press the Update Config button and the configuration files will get updated.
Click the Back button. Now, back on the configured entries, tick the Use IP Address entry and make
sure the virtual address is selected.
PAGE 35
OCTOBER 2006
Failover the application server and repeat the above mentioned steps using the OAPPCFGED utility.
PAGE 36
OCTOBER 2006