IRIS 10.16 Installation Instructions Part 2 (GUI)

IRIS 10.16-PTF-003 Installation Instructions Part 2 (GUI)

Copyright notice

(c) Copyright Xchanging Global Insurance Solutions 2007. 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:10th July 2008.

1.Amendment History

Reason / Date / NewReference
Version 1 / 20/10/2006 / Q:\IRIS GUI Installations\Installation 9.15 ENH000\IRIS 9.15-ENH-000 Installation Instructions Part 2 (GUI).01.doc
Version 2 / 18/01/2007 / Q:\IRIS GUI Installations\Installation 9.15 ENH001\IRIS 9.15-ENH-001 Installation Instructions Part 2 (GUI).01.doc
Version 3 / 05/03/2007 / Q:\IRIS GUI Installations\Installation 9.15 ENH002\IRIS 9.15-ENH-002 Installation Instructions Part 2 (GUI).01.doc
Version 4 / 08/05/2007 / Q:\IRIS GUI Installations\Installation 9.15 ENH003\IRIS 9.15-ENH-003 Installation Instructions Part 2 (GUI).01.doc
Version 5 / 05/10/2007 / Q:\IRIS GUI Installations\Installation 10.16 PTF000\IRIS 10.16-PTF-000 Installation Instructions Part 2 (GUI).01.doc
Version 6 / 13/11/2007 / Q:\IRIS GUI Installations\Installation 10.16 PTF001\IRIS 10.16-PTF-000 Installation Instructions Part 2 (GUI).01.doc
Version 7 / 10/07/2008 / Q:\IRIS GUI Installations\Installation 10.16 PTF003\IRIS 10.16-PTF-003 Installation Instructions Part 2 (GUI).01.doc

Contents

1.Amendment History

List of figures

2.Installation Issues

2.1Introduction

2.2Contacts

2.3PC Specification

2.4iSeries Requirements

2.5Data Sources

2.6Installed Components

2.6.1Data Access Components

2.6.2Location of Applications

2.6.3Help

2.6.4EXE and DLL Registration

2.6.5Microsoft SQL Server Data Engine.

3.Installation Checklist

Server Checklist

Pre-Installation

Installation

Post-Installation

Client Checklist

Post Installation

Scheduler Checklist

Post Installation

Admin Checklist

4.Installation Procedure

4.1Set-up Process

4.2Server Set-up

4.2.1Overview of Server Set-up

4.2.2Running the Server Set-up

4.3Client Set-up

4.3.1Overview of Client Set-up

4.3.2Running the Client Set-up

4.4Microsoft SQL Server Data Engine.

4.4.1Installing MSDE files.

4.4.2Run the Setup.

4.4.3Update IRIS Settings.

4.5Scheduler Set-up

4.5.1Overview of Scheduler Set-up

4.5.2Running the Scheduler Set-up

4.6Administration Tools Upgrade

4.6.1Overview of the Administration Set-up

4.6.2Running the Administration Set-up

5.Post Installation

5.1Component Update

5.2Review Security Settings (Server Upgrade)

5.3System Administration (Server Not an Upgrade)

5.3.1To Add Users:

5.3.2To Add Roles:

5.3.3To Add Environments:

5.4System Product Codes (Server Upgrade)

5.5LBRCUpdate (Server Upgrade)

5.6Customer Configuration (Server Not an Upgrade)

5.7Codes Transfer (Server Upgrade and New Installation)

5.8Business Items (Server Upgrade)

5.8.1Preview Each Business Item ( If Server Upgrade)

5.9Product Codes (Server Not An Upgrade)

5.9.1Policy Product Codes

5.9.2Quotes/Promises/Memos/Declinatures Product Codes

5.9.3Bureau Product Codes

5.10Product Codes (Server Upgrade from 7.13 or earlier)

5.11Closings Input (Server Not an Upgrade)

5.12Setting Up DecisionBase (Server or Client with no previous DecisionBase)

5.13Setting up Scheduler and Bureau Message Receipt

5.14IRIS Reporting.

6.Appendix 1: IBM Client Access ODBC Drivers

6.1.1Setting up an ODBC Data Source to an AS/400 Database

Testing an ODBC Connection

Appendix 2: IRIS GUI 10.16

IRIS Components

Shared Components

Appendix 3: IRIS GUI Release Notes

Appendix 4 : NTFS

Appendix 5 : Client Access Issues

Client Access Express v4r4m0

Client Access Express v4r5m0

iSeries Access Express v5r1m0

iSeries Access Express v5r2m0

iSeries Access Express v5r3m0

Appendix 6 : OS/400 Issues

OS/400 V4R2M0

OS/400 V4R3M0

OS/400 V4R4M0

OS/400 V5R1M0

OS/400 V5R2M0

OS/400 V5R3M0

OS/400 V5R4M0

Appendix 7 : General Installation Issues

ODBC Library Locked

List of figures

Figure 1: Set-up Screen

Figure 2: License agreement

Figure 3: User Information

Figure 4: Enter Information

Figure 5: Server Location

Figure 6: Start copying files

Figure 7: Begin Install

Figure 8: Environment Upgrade

Figure 9: Installation Complete

Figure 10: Welcome Dialog (Upgrade only)

Figure 11: Installation Aborted

Figure 12: Application components

Figure 13: Run the command prompt

Figure 14: Install MSDE

Figure 15: Installation Aborted

2.Installation Issues

2.1Introduction

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 74) and also for known issues on the version of OS/400 being run (see page 76)
  2. The IRIS AS/400 software should be installed (see the “IRIS 9.15 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 11.
  3. PCs should meet the minimum recommended specifications. See PC Specification on page 10.
  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 16.
  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 Installationon page 35
  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 28

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 14. 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 on page 72.

The appendices contained within this document are as follows:

Information / Page
IBM Client Access ODBC Drivers / 59
Installed Components / 65
Release Notes / 72
NTFS Issues / 73
Client Access Issues / 74
OS/400 Issues / 76

2.2Contacts

If you require any help during the Installation process, please contact the IRIS Helpdesk on either:

  • Telephone 020 7780 5373
  • Email

2.3PC Specification

The minimumrecommended specification for PC’s on which the GUI is to be installed is as follows:

  • Pentium 4
  • 1gb RAM
  • 100MB of free hard drive space plus approximately an additional 30 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
  • Microsoft Installer 3.0

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 300MB plus an additional 30 MB per environment of free space on the server.

to Data Library must be executed over all required environments.

* For information on known issues in specific versions of Client Access see the appendix on page74.

Similarly information on known issues in specific versions of OS/400 can be found in the appendix on page 76

2.4iSeries Requirements

The following are requirements need to be met to ensure that IRIS GUI is installed and operated effectively:

  1. Ensure that the iSeries is running OS/400 v5r2m0 or above
  2. 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.
  3. All commands in this document that refer
  4. Ensure that the database parameter for each GUI Environment is configured to the correct AS/400 IRIS data library and system library.
  5. 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.
  6. 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).

  1. 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.5Data 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 (page59)

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 36

2.6Installed Components

For a comprehensive list of the components installed by the installation routine please see Appendix 2 on page 65. What follows is a brief overview of what is installed.

2.6.1Data 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.2Location 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.3Help

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.4EXE 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.5Microsoft 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. If installing on Windows Vista, be aware that MSDE is not supported by Microsoft and SQL Server Express is the recommended replacement.

3.Installation Checklist

Server Checklist

Pre-Installation

PC (page 10)

1Decide where to install the IRIS Server components, and ensure all users have full update access to it.

2Decide whether the server path will be specified using a UNC path (e.g. \\Server01\IRIS) or a mapped drive letter path (e.g. R:\IRIS\); see the section Server Location on page 16.

3Check disk space is adequate.

4PC Specification must meet requirements.

5Prerequisite software: Client Access, ODBC and Internet Explorer, Microsoft Installer 3.0. Microsoft .NET 2.0 Framework. The correct versions must be installed. If installing on Windows 2000, the PC should have all the latest Microsoft service packs and updates installed.

6If installing on an NTFS formatted drive then please review the section on NTFS issues on page 73.

7If this installation is an upgrade of an existing IRIS installation, it is recommended that a backup copy is made of the folder containing the IRIS server components.

AS/400 (page 11)

8Determine the names of the IRIS data and system libraries.

9Delete SQL Packages in QGPL.

10Check Relational Database entry.

11Library list.

Installation

12Run Server set-up from the CD. (page 16); N.B. the server install is designed to be run from any PC or from the server itself.

Post-Installation

12If the PC is Windows2000 then the Scripten utility needs to be run (if it has not been installed before). (page35 )

13If this Installation is not an upgrade and this PC/Server will be used to access/configure IRIS then run the Client setup from the Client folder in the IRIS Server location. Then run the Administration Tools setup from the Administration Tools folder in the IRIS Server location.

N.B If it has been decided to use UNC paths for the configuration of IRIS, then you should browse to the Client and Administration Tools folders using UNC paths NOT mapped network drive letters.

14 If this Installation is not an upgrade then set up System Administration: set up Users, Roles and Environments. (page 36)

15If this Installation is an upgrade then Review security settings (page 39)

16If this Installation is an upgrade then check that the required system product codes are present (page 49)

17If this Installation is an upgrade from IRIS 7.13 or earlier then check the upgraded rules (page 55)

18Run Codes Transfer for each environment. (page 51)

19If this Installation is an upgrade then preview Business Items (page 52)

20If this Installation is not an upgrade then set up the Product Codes for each environment. (page 52)

21If this Installation is not an upgrade then run the Quote/Promise/Memo/Declinatures conversion program for each environment. (page 54)

22If this Installation is not an upgrade then assign Workstation IDs for Closings Input for each environment. (page 56)

23If DecisionBase was installed for the first time then set up DecisionBase. (page 56)

Client Checklist

  1. Ensure a Server Installation has been performed as above.
  2. Check disk space is adequate. (page 10)
  3. PC Specification must meet requirements. (page 10)
  4. Prerequisite software: Client Access, ODBC and Internet Explorer. The correct versions must be installed. (page 10)
  5. If installing on an NTFS formatted drive then please review the section on NTFS issues on page 73
  6. Run Client set-up from the Client folder of the Server. (page 28)

N.B. Remember to run the setup via a UNC path if it has been decided to use UNC paths in IRIS.

  1. Run the MSDE set-up from the MSDE folder of the Server. (page 35)

Post Installation

1.If the PC is Windows2000 and this installation is not upgrading from 5.11 PTF003 or later then the Scripten utility needs to be run. (page35 )

  1. If DecisionBase was installed for the first time then set up DecisionBase. (page56)

Scheduler Checklist

  1. Run Scheduler set-up from the IRIS Scheduler folder of the Server (page32)

N.B. Remember to run the setup via a UNC path if it has been decided to use UNC paths in IRIS.

Post Installation

1. Once the scheduler has been installed, the administrator needs to configure IRIS to

use the scheduler and if required, Bureau Message Receipt(page58)

Admin Checklist

  1. Ensure a Client Installation has been performed on the PC on which the Administration Tools are to be installed.
  2. Check disk space is adequate.
  3. Run setup.exe from the Administration Tools folder in the IRIS Server location.

(page 34)

4.Installation Procedure

This document describes the procedure for installing the IRIS GUI product.

4.1Set-up Process

The Set-up process is divided into two parts, these being ‘Server’ and ‘Client’. In order for a successful installation to take place, these set-ups must both be completed. The ‘Server’ set up is run only once and the ‘Client’ set-up is run for each required PC. A further installation, Administration Tools Upgrade, will also need to be run on any PC where the user requires access to the Administration Functions within IRIS. (page 35)

Note: It is important to note that a ‘Server’ install must be performed before any ‘Client’ set-ups are run.

4.2Server Set-up

The set-up files that are distributed contain the 'Server' set-up process.

4.2.1Overview of Server Set-up

The Server set-up installs all the IRIS Server components, it requires the installer to specify the IRIS server location.

The Server Location

This will typically be on a shared network drive accessible to all Users, and the following items will be installed to it.

  • The Master Codes database.
  • The IRIS Configuration file.
  • The IRIS System Administration file and Template.
  • Installation utilities (named 'InstallMultiEnv.exe', ‘dbupdate.exe’, ‘Customerconfig.exe’) required for the set up of multiple environment functionality. These utilities are run during the Server set-up. It should never be run at any other time.
  • Client set-up files.
  • Scheduler set-up files.
  • Administration Tools upgrade set-up files.
  • AS/400 Help files.
  • Windows2000 folder, which contains the Microsoft Scripten utility.

When deciding on the server location the following issues should be considered.