Installation Notes for USFE Release 1.0 Production ====================================================== Table of contents 1 Introduction 2 Software Delivery 2.1 List of transferred files 2.2 Necessary Disk Space 3 Preinstallation tasks 3.1 Back-up of existing EurexUS Production software 3.2 Copy the received software 4 Installation steps 4.1 Installation on Solaris 4.2 Installation on Windows 5 Postinstallation steps 5.1 Configuration of the EurexUS Production Software 5.2 Usim File Installation 5.3 Creating User, Groups and File Permissions on Windows 5.4 User, Groups and File Permissions on Solaris 6 Rollback 6.1 Rollback on Solaris 6.2 Rollback on Windows 7 Additional Information 1 Introduction This document contains important information concerning the installation of USFE Release 1.0 Production. Please read the following pages carefully as you may otherwise encounter difficulties during installation. The information in this document should be used in conjunction with the USFE Release 1.0 Frontend Software Installation Guide. The kit can be used for upgrading an existing EurexUS Release 1.0 Production installation or for a completely new installation. In case of an upgrade no user interaction is necessary, the existing configuration files will be reused and converted for the new release, preserving all individual data entries. If any problems during the installation occur do not hesitate to call the USFE Customer Service. (Help Desk: +1-312-544-1110) 2 Software Delivery 2.1 List of transferred files The kits for USFE will be transferred to the following subdirectories of transferdir : ../release40/readmer10.usfe (this file) ../release40/win/usfer10.msi ../release40/sun/instusfer10.sun usfer10.sun.Z rollbackusfer10.sun 2.2 Necessary Disk Space The necessary disk space to receive and install the software depends on the MISS platform. The following values are estimated. Windows file transfer: 35 MB installation: 70 MB Solaris file transfer: 75 MB (without Windows software) installation: 150 MB on /opt Please refer to the Sizing Guidelines to determine the required disk space during runtime. 3 Preinstallation tasks You have to install or update GATE first since the USFE 1.0 kit checks for a valid GATE 3.5 (or higher) installation. 3.1 Back-up of existing EurexUS Production software It is strongly recommended to back-up an existing EurexUS Release 1.0 Production installation before upgrading. ATTENTION! It is not enough to simply copy all files. A full system back-up should be performed instead. 3.2 Copy the received software The first step when preparing for the installation is to save the received installation kit files in a directory location which should be easily accessible from all computers (MISSes and Workstations) used in USFE Production. 4 Installation steps Please make sure that no EurexUS or GATE software component is running in Production before upgrade or new installation. When installing a new MISS the installation procedure asks whether this is the first (primary) MISS of a given MISS group. - If "yes" is selected as an answer to this question, the configuration has to be done after installation has finished. - If "no" is selected then the installation kit will prompt for the location of the configuration files of the MISS installed and configured first. ATTENTION! The USFE kit can only be installed under the root account (Solaris) or the Administrator account (Windows) respectively. 4.1 Installation on Solaris To start the installation procedure, change to the directory where the USFE kit files have been copied to and enter the following commands: # chmod a+x *usfexr10.sun # ./instusfer10.sun ATTENTION ! Please make sure that your administrative account for GATE (default: gateadm) is not in use during a new USFE installation as it will be modified. Otherwise group "xeusft" will not be added to the account's supplementary groups. 4.2 Installation on Windows To begin the installation, start the Windows Explorer and simply double-click on the copied USFE kit file "USFER10.msi". The installation can also be started directly from the DOS prompt by running "msiexec /i USFER10.msi". To start an unattended installation the following parameters can be specified: /qn no GUI will be displayed, no questions will be asked PATH_TO_MBR_INI= to specify a path where the file "USFEmbr.ini" will be copied from PATH_TO_SUBLIST= to specify a path where the files "usfesublist.dat" and "usfeexclist.dat" will be copied from (MISS only) FTP_ROOT_DIR= to specify the FTP root directory (MISS only, not nescessary for Microsoft FTP server) Example: msiexec /i USFER10.msi PATH_TO_MBR_INI=e:\tmp PATH_TO_SUBLIST=e:\tmp FTP_ROOT_DIR=c:\Inetpub\ftproot /qn 5 Postinstallation steps 5.1 Configuration of the USFE Production Software USFE Production software can be configured using the included Configuration Utility. The Configuration Utility can be started by clicking the Configuration Utility Icon or by executing the following command: Platform Command SUN # cd /opt/gate/base90/bin # ./configMenu.pl WIN # : # cd \opt\gate\base90\bin # perl configMenu.pl Should any settings need to be configured in order to start USFE, the menu entry "Required Minimum Configuration" will appear. All entries in this submenu have to be configured before USFE can be started. After the initial configuration the Configuration Utility can also be started from Xmenu to change the USFE configuration, e.g. to add MISS and Workstations or to configure IP Multicast. It is still possible to configure USFE manually by editing the USFEmbr.ini file as described in the manual. 5.2 Usim File Installation In case of a new installation, you have to request a library file (Usim file) for each MISS from USFE Customer Service. The Usim file contains a MISS-specific encoded password which is validated against the Backend during sign-on. The Usim file will be transferred to the transferdir/release40 of each MISS. During the "Start-of-Day" procedure the USIM file will automatically be copied to the appropriate platform dependent directory according to the following table: Solaris /opt/gate/base90/lib/libusfeusim.so Windows "GATE_Drive":\opt\gate\base90\bin\usfeusim.dll 5.3 Creating User, Groups and File Permissions on Windows On Windows the accounts, groups and their permissions have to be created after the installation. The group "xeusft" (for file transfer) with the permission "Logon locally" has to be created. In an Active Directory environment, this setting has to be applied to "Local Security Policy" and "Domain Controller Security Policy". The account "XEUSTrd" has to be member of the group "gatetrd". For file transfer the account "eusnet40" has to be member of the group "FT_GROUP". The file access permissions should be granted to the above mentioned accounts and groups. - The transferdir (ftproot) must be read/writeable for the file transfer account and group. If transferdir - subdirectories are created, they must be owned by the respective file-transfer account/group. Please check also your FTP server for the appropriate setup. - The active, archive, ROB, transfer-directories and all its subdirectories must be read/writeable, all other directories readable and all binaries and scripts read/executable for the account operating on the system. - The configuration files must be editable for the account configuring the system. 5.4 User, Groups and File Permissions on Solaris The users and groups have to be entered during the kit installation. The file permissions will be set accordingly. ATTENTION ! Running the Trading application on the MISS: The user starting the application on the MISS needs to be either the administrative GATE user (default: "gateadm") or a member of the GATE group (default: "gategrp"). 6 Rollback If EurexUS Release 1.0 has been found on the machine a rollback will be prepared by the installation script during upgrade. ATTENTION! You must not perform a rollback restore unless USFE Customer Service informs you to do so. If you performed a rollback restore by accident please contact USFE Customer Service immediately. 6.1 Rollback on Solaris The rollback archive is created in /opt/gate/rollback by the installation script and will be compressed if possible. In case the USFE Customer Service informs you to perform a rollback restore you have to execute the following commands as root: # chmod a+x rollbackusfer10.sun # ./rollbackusfer10.sun restore Please note that you will need the rollback script not only during the installation but also in case of a rollback. 6.2 Rollback on Windows In case the USFE Customer Service informs you to perform a rollback restore you have to execute the following command: :\opt\gate\rollback> rollback_USFER10.pl 7. Additional Information During MISS network infrastructure setup it is essential to ensure that the MISS servers in the same group are able to communicate with each other in each of the LANs they are in (MISS/Router LAN and MISS/Workstations LAN). LAN configuration and IP addressing defined by Deutsche Boerse Systems (DBS) ensures that the above requirement is fullfilled in the DBS controlled network (MISS/Router LAN). In a two-LAN configuration the MISSes of a MISS Group must also be connected to each other on the MISS/Workstation LAN. This is under the system administration and management responsibility of the member and network configuration and addressing should ensure that the MISSes are connected. The consequences of an incorrect network connection set-up of a MISS Group include a heavy increase in "non-product-related system transactions", which leads to a situation where the defined transaction limits are exceeded (Report CB065, CB068). The execution of a fail-over test after the installation of a new MISS Group helps to uncover any problems in the area described above and will guarantee the correct operation of the application and subsequent trouble-free operation.