IRIS 8.14 Installation Instructions Part 2 (GUI)
IRIS 8.14-PTF-004 Installation Instructions Part 2 (GUI)
Copyright notice
(c) Copyright Xchanging Global Insurance Solutions 2005. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of XGIS.
Disclaimer
Information in this document is subject to change without notice and does not represent a commitment on the part of XGIS. XGIS provides no warranty of any kind with regard to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. XGIS shall not be liable for errors contained herein or for any direct, incidental or consequential damages resulting from the use of this material
Author : Neil Winter
Last Updated : 3rd November 2005.
1. Amendment History
Reason / Date / New ReferenceVersion 1 / 31/03/2005 / Q:\IRIS GUI Installations\Installation 8.14 \IRIS 8.14 Installation Instructions Part 2 (GUI).01.doc
Version 2 / 28/072005 / Q:\IRIS GUI Installation 8.14 ENH-001\IRIS 8.14 Installation Instructions Part 2 (GUI).01.doc
Version 3 / 26/09/2005 / Q:\IRIS GUI Installation 8.14 ENH-002\IRIS 8.14 Installation Instructions Part 2 (GUI).01.doc
Version 4 / 03/11/2005 / Q:\IRIS GUI Installation 8.14 PTF-002\IRIS 8.14 Installation Instructions Part 2 (GUI).01.doc
Version 5 / 21/11/2005 / Q:\IRIS GUI Installation 8.14 PTF-003\IRIS 8.14 Installation Instructions Part 2 (GUI).01.doc
Contents
1. Amendment History 4
List of figures 8
2. Installation Issues 9
2.1 Introduction 9
2.2 Contacts 10
2.3 PC Specification 11
2.4 iSeries Requirements 12
2.5 Data Sources 13
2.6 Installed Components 14
2.6.1 Data Access Components 14
2.6.2 Location of Applications 14
2.6.3 Help 14
2.6.4 EXE and DLL Registration 14
2.6.5 Microsoft SQL Server Data Engine. 14
3. Installation Checklist 15
Server Checklist 15
Pre-Installation 15
Installation 15
Post-Installation 15
Client Checklist 16
Post Installation 16
Scheduler Checklist 16
Post Installation 16
Admin Checklist 16
4. Installation Procedure 17
4.1 Set-up Process 17
4.2 Server Set-up 17
4.2.1 Overview of Server Set-up 17
4.2.2 Running the Server Set-up 18
4.3 Client Set-up 33
4.3.1 Overview of Client Set-up 33
4.3.2 Running the Client Set-up 33
4.4 Microsoft SQL Server Data Engine. 37
4.4.1 Uncompress the MSDE files. 37
4.4.2 Run the Setup. 37
4.4.3 Update IRIS Settings. 38
4.5 Scheduler Set-up 39
4.5.1 Overview of Scheduler Set-up 39
4.5.2 Running the Scheduler Set-up 39
4.6 Administration Set-up 41
4.6.1 Overview of the Administration Set-up 41
4.6.2 Running the Administration Set-up 41
5. Post Installation 43
5.1 Component Update 43
5.2 Review Security Settings (Server Upgrade) 44
5.3 System Administration (Server Not an Upgrade) 44
5.3.1 To Add Users: 45
5.3.2 To Add Roles: 47
5.3.3 To Add Environments: 49
5.4 System Product Codes (Server Upgrade) 57
5.5 LBRCUpdate (Server Upgrade) 58
5.6 Customer Configuration (Server Not an Upgrade) 58
5.7 Codes Transfer (Server Upgrade and New Installation) 59
5.8 Business Items (Server Upgrade) 60
5.8.1 Preview Each Business Item ( If Server Upgrade) 60
5.9 Product Codes (Server Not An Upgrade) 60
5.9.1 Policy Product Codes 60
5.9.2 Quotes/Promises/Memos/Declinatures Product Codes 62
5.9.3 Bureau Product Codes 63
5.10 Closings Input (Server Not an Upgrade) 64
5.11 Setting Up DecisionBase (Server or Client with no previous DecisionBase) 64
5.12 Setting up Scheduler and Bureau Message Receipt 66
6. Appendix 1: IBM Client Access ODBC Drivers 67
6.1.1 Setting up an ODBC Data Source to an AS/400 Database 67
Testing an ODBC Connection 71
Appendix 2: IRIS GUI 8.14-PTF002 73
IRIS Components 73
Shared Components 76
Appendix 3: IRIS GUI Release Notes 80
Appendix 4 : NTFS 81
Appendix 5 : Client Access Issues 82
Client Access Express v4r4m0 82
Client Access Express v4r5m0 82
iSeries Access Express v5r1m0 83
iSeries Access Express v5r2m0 83
iSeries Access Express v5r3m0 83
Appendix 6 : OS/400 Issues 84
OS/400 V4R2M0 84
OS/400 V4R3M0 84
OS/400 V4R4M0 84
OS/400 V5R1M0 84
OS/400 V5R2M0 84
OS/400 V5R3M0 84
Appendix 7 : General Installation Issues 85
ODBC Library Locked 85
List of figures
Figure 1: Set-up Screen 19
Figure 2: Welcome Dialog 20
Figure 3: License agreement 21
Figure 4: User Information 22
Figure 5: Select set-up type 23
Figure 6: Enter Information 24
Figure 7: Server Location 25
Figure 8: Client Install location 26
Figure 9: Select Components 27
Figure 10: Application components 28
Figure 11: Select Program Folder 29
Figure 12: Start copying files 30
Figure 13: Environment Upgrade 32
Figure 14: Enter Server Location 34
Figure 15: Server location warning 34
Figure 16: Application choice 35
Figure 17: Application Sub-components 36
Figure 18: Application components 37
Figure 19: Run the command prompt 37
Figure 20: Install MSDE 38
Figure 21: Enter Server Location 40
Figure 22: Server location warning 40
Figure 23: Select set-up type 41
Figure 24: Select Program Folder 42
2. Installation Issues
2.1 Introduction
This section of the document highlights the issues that are to be considered for an installation of IRIS GUI.
In order to be able to run the IRIS GUI, the following conditions must be satisfied (N.B. these are given in the order that they should generally be performed):
1. Check for known issues with the version of Client Access Express being run (see page 82) and also for known issues on the version of OS/400 being run (see page 84)
2. The IRIS AS/400 software should be installed (see the “IRIS 8.14 PTF Installation Instructions Part 1 (AS400).01.doc” also included on the CD for instructions for doing this).The AS/400 must be configured correctly. See iSeries Requirements on page 12.
3. PCs should meet the minimum recommended specifications. See PC Specification on page 11.
4. The Administrator must run the ‘Server’ installation from the CD (from a client PC), installing to a shared network drive. See Server Set-up on page 17.
5. Having installed the GUI onto the server, the next step that must be performed is to ensure the security, product codes etc are all set up as required. See Post Installation on page 43
6. For each new PC, the Set up program (Setup.exe) from the ‘Client’ folder contained within the location on the server to which the GUI was installed must be run. See Client Set-up on page 33
This document covers each step of the installation process in detail.
For a summarised list of all the steps in the process, there is an ‘Installation Checklist’ in section 3 on page 15. It is highly recommended that the person performing the installation uses this to ensure that they don’t miss any steps.
If performing an upgrade from a previous version of the IRIS GUI it is also highly recommended that you review the Release notes in Appendix 3: IRIS GUI PTF005 on page 80.
The appendices contained within this document are as follows:
Information / PageIBM Client Access ODBC Drivers / 67
Installed Components / 73
Release Notes / 80
NTFS Issues / 81
Client Access Issues / 82
OS/400 Issues / 84
2.2 Contacts
If you require any help during the Installation process, please contact the IRIS Helpdesk on either:
· Telephone 020 7780 5373
2.3 PC Specification
The minimum recommended specification for PC’s on which the GUI is to be installed is as follows:
· Pentium III 1GHz
· 512MB RAM (1024 MB if running Windows XP)
· 50MB of free hard drive space plus approximately an additional 15 MB per environment
· Windows 2000/WindowsXP
· 16 bit colour
· Minimum resolution 1024 x 768
· 32 bit ODBC connection to AS/400 (Client Access) *
· Internet Explorer 6 SP1
N.B. The IRIS GUI will run on lower specified PCs than indicated above but there will be a noticeable drop in performance.
It is recommended that there is approximately 70MB plus an additional 15 MB per environment of free space on the server.
* For information on known issues in specific versions of Client Access see the appendix on page82.
Similarly information on known issues in specific versions of OS/400 can be found in the appendix on page 84
2.4 iSeries Requirements
The following are requirements need to be met to ensure that IRIS GUI is installed and operated effectively:
- Ensure that the iSeries is running OS/400 v5r2m0 or above (
- The Data Library and System Library for all environments need to be established. For example, for a LIVE environment of IRIS these may be XUNMDTA and XUNMSYS respectively.
- All commands in this document that refer to Data Library must be executed over all required environments.
- Ensure that the database parameter for each GUI Environment is configured to the correct AS/400 IRIS data library and system library.
- Ensure that the SQL packages in the library QGPL and the IRIS data libraries are deleted. Ensure everyone is logged off every environment when the following command is run: DLTSQLPKG QGPL/IRIS*. It is also worth checking for IRIS SQL packages in all other libraries to ensure that all have been deleted.
- The IRIS GUI requires a Relational Database entry to exist on the AS/400 from which it will be accessing data. To check whether this needs to be done or not, run the following command on the AS/400:
WRKRDBDIRE
If the list displayed by this command contains an entry for a ‘remote location’ of *LOCAL then nothing further needs to be done in relation to this.
If there is not an entry for a ‘remote location’ of *LOCAL then one will need to be added by running the following command on the AS/400:
ADDRDBDIRE RDB(system name) RMTLOCNAME(*LOCAL)
The ‘system name’ should be replaced with the system name of the AS/400 (this is usually displayed in the top right corner of the AS/400 logon screen).
- Ensure that the library XUNMTOOLS is in the library list. This can be checked using the following command
DSPLIBL
If the library XUNMTOOLS is not in the library list then add it with the following command
ADDLIBLE LIB(XUNMTOOLS)
CRTSTP needs to be run for each IRIS environment over which the GUI is to be run. The example of this command that follows uses the typical names of the data library and system library of an IRIS environment. These may be different on some environments and replaced with the appropriate system and data library names for the environment over which the GUI will be run:
CRTSTP SYSLIB(XUNMSYS) DTALIB(XUNMDTA)
2.5 Data Sources
The IRIS GUI no longer requires ODBC data sources, but now has a connection that can be defined centrally in the System Administration function. However, this does require that the AS/400 is defined with a common name within Client Access across all PCs.
If DecisionBase is installed for the first time, as part of IRIS GUI then an ODBC data source needs to be set up on each PC. See appendix 1 (page67)
For more information on how the connection is now defined from within the System Administration function then see the section titled Review Security Settings (Server Upgrade)
On each new release of IRIS there will be new security options made available.
It will be necessary for the System Administrator to visit the IRIS System Administration function and review the security settings. The default setting for any new security options will be to make all existing users ‘unauthorised’ to the new option.
In the IRIS GUI upgrade it is highly recommended that all the security settings are reviewed to make sure that all the original security settings have been imported correctly.
New security options that did not exist in the original security set-up will definitely need to be visited.
These include the following:
1. Bureau Closings
2. Policy Reinsurance Screen
3. INCAS
4. IMEX
5. System Setting and Reference Files
6. Environment library names(in case system library was renamed during AS400 upgrade)
7. Bureau Message Receipt
8.
9. N.B. It is important that for each Role within ‘System Settings and Reference Files’ that the ‘Configure’ button is pressed and at least one code is something other than ‘No Access’. Failure to do this could stop superqueries working.
System Administration (Server Not an Upgrade) on page 44
2.6 Installed Components
For a comprehensive list of the components installed by the installation routine please see Appendix 2 on page 73. What follows is a brief overview of what is installed.
2.6.1 Data Access Components
During the IRIS set up process all relevant components of Microsoft’s Data Access Components (MDAC) are installed.
Note: MDAC actually consists of many data access components (e.g. ODBC, OLE DB, ADO, and DAO), of which IRIS only requires ODBC, DAO, JET and RDO. However, the latest version of MDAC (version 2.1) installs Jet 4.0 and IRIS will only run with Jet 3.5 (the Codes and User Enquiries databases are in “Access 97” format). Therefore, installing the latest version of MDAC will not result in a successful IRIS installation. For information purposes, the IRIS set up routine installs the following components:
· DAO 3.6
· ODBC 3.51
· RDO 2.0
· JET 3.5 (but not the ODBC driver)
2.6.2 Location of Applications
Due to the nature of DCOM, all application files are now installed on a local basis only. This will minimise any issues for future patches and/or upgrades.
2.6.3 Help
Help documentation is installed as part of the set up procedure. A shortcut to both the AS/400 IRIS documentation (which is installed onto a server) and the IRIS GUI help documentation (installed locally) will appear in the IRIS menu.
2.6.4 EXE and DLL Registration
The registration of all the DLL's are handled by InstallShield and IRIS Server.exe is registered within the set up routine.
2.6.5 Microsoft SQL Server Data Engine.
From version 8.14 of IRIS onwards, the IRIS Report Designer component of IRIS will require the Microsoft SQL Server Data Engine to be installed as part of the client setup.
3. Installation Checklist
Server Checklist
Pre-Installation
PC (page 11)
1 Decide where to install the Server components, and ensure all users have access to it.