docs.intersystems.com
Home  /  Getting Started with InterSystems IRIS Data Platform  /  Installation Guide  /  Installing InterSystems IRIS on Microsoft Windows


Installation Guide
Installing InterSystems IRIS on Microsoft Windows
[Back]  [Next] 
InterSystems: The power behind what matters   
Search:  


This chapter describes how to install InterSystems IRIS Data Platform™ on a Microsoft Windows system. It assumes you are familiar with Windows directory structures, utilities, and commands. Before beginning this installation, be sure you have read all the information that applies to this platform in the chapter Preparing to Install InterSystems IRIS.
This chapter contains the following major sections:
InterSystems IRIS Installation
The steps for installing each type of InterSystems IRIS configuration are fundamentally the same, but diverge slightly depending on the type of installation. The differences are detailed in subsections after the standard installation description.
Installing InterSystems IRIS
The installation procedure installs the required components for the selected setup type on the computer. To perform an installation follow this procedure:
  1. Ensure that the installation kit is available on your computer or on a network.
  2. Execute the installation file, for instance by double-clicking it in Windows Explorer or executing it on the command line as follows:
    C:\Users\Public\Downloads\IRIS-2018.1.0.508.0-win_x64.exe
    Note:
    By default, a newly installed InterSystems IRIS instance starts immediately after installation and the InterSystems IRIS launcher is placed in the system tray. To prevent InterSystems IRIS from starting, set the Windows Installer property ISCSTARTCACHE to 0; to prevent the launcher from being placed in the system tray, set ISCSTARTLAUNCHER to 0. You can do this using the command line, for example:
    C:\Users\Public\Downloads\IRIS-2018.1.0.508.0-win_x64.exe ISCSTARTCACHE=0 ISCSTARTLAUNCHER=0
    For a description of all InterSystems IRIS Windows installer properties, see Unattended Custom Installation.”
  3. The InterSystems IRIS setup begins. Within setup, the following buttons are activated to let you control the installation:
  4. If there are existing InterSystems IRIS instances installed on the system, the Select Instance dialog box lists their installation directories. Select New Instance to install a new InterSystems IRIS instance.
    Note:
    Select an existing instance to reinstall that instance.
  5. If you are installing a new instance of InterSystems IRIS on this computer, setup displays the License Agreement dialog box. Click I accept the terms in the license agreement to confirm that you accept the license agreement.
  6. The InterSystems IRIS Instance Name dialog box lets you assign a name to the new instance you are installing. The default name is IRIS (or if other instances exist, IRISn, where n is the number of InterSystems IRIS instances including this new one). Accept the default or enter another name, using alphanumeric chacaters only. Subsequent updates to this instance maintain the instance name you enter here.
  7. The Destination Folder dialog box lets you select a destination directory for the InterSystems IRIS software for the new instance; the default location is c:\InterSystems\IRIS (or IRISn when multiple instances exist).
    You can select or create a directory by clicking Change. If the specified directory does not exist, setup lets you create it.
  8. The Setup Type dialog box lets you specify how you intend to use InterSystems IRIS:
Note:
You can choose not to install the ISC_PACKAGE_USER_DATABASE, by changing the value to N (Y by default). Doing so will ensure this database/namespace definition is not installed and will not be created in iris.cpf.
The following table identifies which component groups are installed for each setup type. The Custom setup type lets you select specific component groups/components to install or remove; see the Performing an InterSystems IRIS Custom Installation section of this book:
Components Installed by Setup Type
Component Group Components Development Server Client Web
InterSystems IRIS Database Engine (InterSystems IRIS Server)
Server Monitoring Tools
User database
SQL Gateway
Agent Service (ISCAgent)
Apache FOP (Formatting Objects Processor)
X
X
   
InterSystems IRIS launcher  
X
X
X
 
Studio  
X
 
X
 
xDBC
ODBC Driver
Java Database Connectivity
X
 
X
 
InterSystems IRIS Application Development
Java Binding for InterSystems IRIS
InterSystems IRIS Engine Link Libraries
.NET Binding for InterSystems IRIS
Threaded Server Libraries
Other Samples)
X
     
Documentation
PDF Documentation
Online Documentation
X
X
   
Web Server Gateway
CSP for IIS
CSP for Apache 2.0.x
CSP for Apache 2.2.x
 
X
 
X
1 This component is supported only on the x86-32 bit platform.
Installing InterSystems IRIS Development or Server Components Only
If you wish, you can install only the components of InterSystems IRIS that are required on a development system or on a server system.
To perform a Development or Server installation:
  1. Select Development or Server in the Setup Type dialog box, described in the Installing InterSystems IRIS procedure, and click Next.
  2. The Initial Security Settings dialog box lets you decide how restrictive you want the initial InterSystems security settings to be. If you choose Minimal, the installation continues with the next step.
    Important:
    If you select Minimal for your initial security setting, but InterSystems IRIS requires network access to shared drives and printers, you must manually change the Windows user account under which to run the InterSystems service, choosing an existing account or creating a new account that has local administrator privileges on the server machine.
    If you select Normal or Locked Down, the installation includes the following steps:
    1. The Enter Credentials for InterSystems Service dialog lets you choose the credentials under which the Windows InterSystems service will run. The default is the local default SYSTEM account. You can also specify a defined (existing) Windows user account and password; when you do so, the installer verifies these credentials before proceeding. The installer also creates an InterSystems IRIS account with the same username, with the %All role for unrestricted access to the instance (the password for this account is provided on the next panel).
      Running the Windows InterSystems service under the default SYSTEM account is appropriate for many installations, but in some cases can cause issues relating to file permissions and network security access. If you anticipate potential problems in these areas for an InterSystems IRIS instance, for example due to your network configuration or security arrangements, specify an account for the Windows InterSystems service that has the needed privileges and/or access, for example that of a domain administrator.
      To change the service account (in Windows 10): Navigate to Control Panel > Administrative Tools > Services. Next, locate the correct InterSystems service. Then, right-click to open the properties dialog of the correct instance. Finally, change the credentials on the Log On Tab and restart InterSystems IRIS.
      Important:
      If you are using Kerberos, you must configure a service account before installing InterSystems IRIS; see Preparing the Security Environment for Kerberos in the “Preparing to Install InterSystems IRIS” chapter for more information.
      Note:
      See Shared Memory Allocation on Windows for information about granting the Windows “Lock Pages in Memory” (SELockMemory) privilege when running InterSystems IRIS under credentials other than the local system account.
    2. The first panel of the InterSystems IRIS Users configuration dialog let you enter the initial password for the following predefined InterSystems IRIS user accounts _SYSTEM, Admin, and SuperUser, as well as the username you specified if you selected a defined Windows account as the service account on the previous panel. The second panel of the InterSystems IRIS Users configuration dialog lets you enter the initial password for the CSPSystem predefined account. For more details on these predefined users, see the Predefined User Accounts section of the “Users” chapter of the Security Administration Guide.
    For a detailed explanation of these security settings, see Managing Access to the InterSystems IRIS Instance and the Initial InterSystems Security Settings sections of the “Preparing to Install InterSystems IRIS” chapter of this book.
  3. The Ready to Install dialog box lets you review the installation name, type, and directory, as well as the license key status.
    Click the License button to select an InterSystems IRIS license key. If the key is valid, the license is automatically activated, the License Key field on the Ready to Install dialog is updated to Valid, and the license key is copied to the instance’s manager directory (install-dir/mgr) as iris.key during installation; no further activation procedure is required. If you do not select a key, you can activate your InterSystems InterSystems IRIS license key following installation. See Activating a License Key in the “Managing InterSystems IRIS Licensing” chapter of the System Administration Guide for information about licenses, license keys and activation.
    Click Install to continue. Setup installs InterSystems IRIS in the selected directory.
  4. The InstallShield Wizard Complete dialog box indicates the installation has completed successfully. Choose whether you want to see the Getting Started page and click Finish.
The system starts automatically after installation is complete. The InterSystems IRIS launcher icon appears in the system tray area of the Windows tool bar. Click the launcher to bring up the InterSystems IRIS menu. In addition, there is an InterSystems IRIS item on the Windows Programs menu.
Installing InterSystems IRIS Client Components Only
If you wish, you can install only those parts of InterSystems IRIS that are required on a client machine.
To perform a client installation:
  1. Select Client in the Setup Type dialog box, described in the Installing InterSystems IRIS procedure, and click Next.
  2. The Ready to Install dialog box lets you review the installation name, type, and destination directory for the software files.
    Click Install to continue. Setup installs InterSystems IRIS in the selected directory.
  3. The InstallShield Wizard Complete dialog box indicates the installation has completed successfully. Click Finish.
After InterSystems IRIS is installed on a client, the InterSystems IRIS launcher icon appears in the system tray area of the Windows tool bar; it appears dimmed because there is no InterSystems IRIS server running.
Important:
Before you can use the client, you must specify the preferred server for this client; this procedure is described in the Define a Remote Server Connection section of the “Connecting to Remote Servers” chapter of the System Administration Guide.
Installing the Web Server Gateway Only
If you wish, you can install only those parts of InterSystems IRIS that are required on a Web Gateway machine.
To perform a Web Gateway installation:
  1. Select Web Server in the Setup Type dialog box, described in the Installing InterSystems IRIS procedure, and click Next.
  2. The Ready to Install dialog box lets you review the installation name, type, and destination directory for the software files.
    Click Install to continue. Setup installs InterSystems IRIS in the selected directory.
  3. The InstallShield Wizard Complete dialog box indicates the installation has completed successfully. Click Finish.
If a web server is running, a dialog box asks if you want to restart the web server. If you click Yes, the installation procedure restarts the web server. If you click No, the procedure does not restart the web server, in which case it does not start until you restart it manually or restart the system.
If the installer detects an Internet Information Services (IIS) web server installed on the system, it configures the web server for the Web Gateway. The installer also displays a check box for IIS; if you select this, Web Gateway IIS modules are installed in C:\InetPub\CSPGateway.
The Web Gateway configures the following application paths pointing to the server configured for the instance:
You can change the configurations manually after installation from the Web Gateway application; for information, see the Web Gateway Configuration Guide.
Note:
The installer cannot automatically configure an Apache web server for use with InterSystems IRIS and CSP; for information on the required manual configuration procedures, see the Web Gateway Configuration Guide.
Performing a Custom InterSystems IRIS Installation
The InterSystems IRIS installation program allows you to select certain InterSystems IRIS components to install on the computer. For example, you may want to install only the Web Server Gateway. Keep in mind that some selections require that you also install other components.
To perform a custom InterSystems IRIS installation:
  1. Select Custom in the Setup Type dialog box, described in the Installing InterSystems IRIS procedure, and click Next.
  2. In the Custom Setup dialog box, select the components you want to install as described in the Components Installed by Setup Type table.
    Important:
    If you are custom-installing the Documentation component group or any of its components, the InterSystems IRIS Database Engine (InterSystems IRIS Server) component group is a prerequisite.
    Note:
    You can remove previously-installed components by selecting the X menu item for any component group or component.
  3. Optionally, click Space to ensure that there is enough space on the disk for the selected components.
  4. The Enter Port Numbers lets you change the port numbers assigned by InterSystems IRIS.
    Note:
    You cannot enter a port number greater than 65535 or less than 1. For information about setting port numbers, see Set Port Numbers in the “Using Multiple Instances of InterSystems IRIS” chapter of the System Administration Guide.
    The following port numbers are valid for your InterSystems IRIS instance:
  5. The Initial Security Settings dialog box lets you decide how restrictive you want the initial InterSystems security settings to be. If you choose Minimal, the installation continues with the next step.
    Important:
    If you select Minimal for your initial security setting, but InterSystems IRIS requires network access to shared drives and printers, you must manually change the Windows user account under which to run the InterSystems service, choosing an existing account or creating a new account that has local administrator privileges on the server machine.
    If you select Normal or Locked Down, it displays Enter Credentials for InterSystems Service, where you can choose to run InterSystems service under:
    When you click Next, the installation verifies the following if you enter a defined user account:
    For a detailed explanation of these settings, see the Initial InterSystems Security Settings section of the “Preparing for InterSystems Security” section of this book.
  6. The Ready to Install dialog box lets you review the installation name, type, and destination directory for the software files.
    You can also click the License button to select an InterSystems IRIS license key. If the key is valid, the license is automatically activated and the license key is copied to the instance’s manager directory (install-dir/mgr) as iris.key during installation, and no further activation procedure is required. If you do not select a key, you can activate your InterSystems InterSystems IRIS license key following installation. See Activating a License Key in the “Managing InterSystems IRIS Licensing” chapter of the System Administration Guide for information about licenses, license keys and activation.
    Click Install to continue. Setup installs InterSystems IRIS in the selected directory.
  7. The InstallShield Wizard Complete dialog box indicates the installation has completed successfully. Choose whether you want to see the Getting Started page and click Finish.
Unattended Custom Installation
The InterSystems IRIS for Windows installer provides a way to perform unattended custom installation, upgrade, reinstallation (repair), and removal (uninstall) of instances of InterSystems IRIS on your computer. A typical install operation obtains necessary input from the user in the form of responses to dialog boxes. An unattended operation, however, does not prompt the user for input; instead, it gets input from properties passed to the InterSystems IRIS installation file on the command line. These properties are described in the Command-Line Reference section.
This section discusses the following topics:
Note:
No messages are displayed during unattended installation, upgrade, reinstallation, or uninstallation.
Running an Unattended Installation
To launch unattended installation of a new instance of InterSystems IRIS, use the following command:
<path>\<installer>.exe /instance <instancename> /q{b|n} <properties> 
where:
For example, to install an instance of InterSystems IRIS with the default instance name in an installation directory named C:\InterSystems\MyIris on a 64–bit Windows system, specify the following:
C:\downloads\IRIS-2018.1.0.508.0-win_x64.exe /qn INSTALLDIR=C:\InterSystems\MyIris
To install an instance of InterSystems IRIS with the instance name IrisA, specify the following:
C:\downloads\IRIS-2018.1.0.508.0-win_x64.exe /instance IrisA /qn 
Alternatively, you can custom install a subset of features using the ADDLOCAL property; see the Command-Line Properties table, as well as the Custom-Installable Features table for a list of features that can be specified. For example, to install only the launcher in an installation that uses the default instance name and default installation directory on a 64–bit Windows system, specify the following:
C:\downloads\IRIS-2018.1.0.508.0-win_x64.exe /qn ADDLOCAL=cube
Note:
An unattended installation does not install the Web Gateway by default; this must be specified using the ADDLOCAL property (see the Command-Line Properties table).
Running an Unattended Uninstallation
To launch an unattended uninstall, specify the instance to be uninstalled and the REMOVE=ALL property, as follows:
C:\downloads\IRIS-2018.1.0.508.0-win_x64.exe /instance IrisA /qn REMOVE=ALL 
You can also use the REMOVE property to remove specific features, as described in the Custom-Installable Features table. For example, to remove the Apache 2.0 Web Gateway from instance IrisC, use the following command:
C:\downloads\IRIS-2018.1.0.508.0-win_x64.exe /instance IrisC /qn REMOVE=cspgateway,cspapache20
Special Consideration
If you do not have access to the original installation package, you can run uninstall in unattended mode by using the Windows® Installer command-line application (msiexec) and information in the Registry, as follows:
msiexec /x {<product_guid>} /qn /l <logfile>
where <product_guid> is the ProductCode property value of the version you installed.
You can obtain the ProductCode property value from the Registry:
where <instance> is the name of the InterSystems IRIS instance you want to uninstall in unattended mode. The ProductCode property value is displayed in a row similar to the following:
ProductCode     REG_SZ   {80E3F658-2D74-4A81-92AD-FD16CD226154}
You can also use any of the properties in the Command-Line Properties table with msiexec. For information about msiexec, see the Microsoft msiexec (command-line options) TechNet article (http://technet.microsoft.com/en-us/library/cc759262.aspx).
Command-Line Reference
The Command-Line Properties table describes the InterSystems IRIS-specific unattended install properties that you can modify via the command-line interface. The property name must be uppercase, but the arguments are not case-sensitive; each property must be separated by one or more spaces, and properties can be specified in any order as PROPERTYNAME=argument. For example:
... ISCSTARTCACHE=0 UNICODE=0 WEBSERVERPORT=57779 INITIALSECURITY=Normal
Note:
In the following table, only the REINSTALL and REMOVE properties are used with installed instances, as described in Running an Unattended Upgrade or Reinstall and Running an Unattend Uninstall, respectively.
Command-Line Properties
Property Name Description
ADDLOCAL
Use this property to custom install a new instance of InterSystems IRIS with a subset of features or to omit optional databases (see the Custom-installable Features table) by specifying a comma-separated list of featurenames together with their group names, as described in the example following this table.
In the absence of the ADDLOCAL property, or if ADDLOCAL=ALL is specified, all features are installed.
See also the REINSTALL property, for use with installed instances.
IRISSERVICEDOMAIN Required if the service credentials are defined as UserDefined; see the SERVICECREDENTIALS property in this table. Use this property to specify the domain of the Windows InterSystems service login account specified by IRISSERVICEUSER.
If the service credentials are specified as LocalSystem, do not use this property.
IRISSERVICEPASSWORD
Required if the service credentials are defined as UserDefined; see the SERVICECREDENTIALS property in this table. Use this property to specify the password for the Windows InterSystems service account specified by IRISSERVICEUSER.
If the service credentials are specified as LocalSystem, do not use this property.
IRISSERVICEUSER
Required if the service credentials are defined as UserDefined; see the SERVICECREDENTIALS property in this table. Use this property to specify the username of the account under which to run the Windows InterSystems service.
If the service credentials are specified as LocalSystem, do not use this property.
IRISUSERPASSWORD
Required if the security level is Normalor Locked Down; see the INITIALSECURITY property in this table. Use this property to specify the password for the predefined InterSystems IRIS accounts _SYSTEM, Admin, and SuperUser, as well as the account with the username specified by IRISSERVICEUSER if SERVICECREDENTIALS is specified as UserDefined.
If the initial security level is None, do not use this property.
CSPSYSTEMUSERPASSWORD
If the security level is Normalor Locked Down (see the INITIALSECURITY property in this table), optionally use this property to specify a password for the CSPSystem predefined user. If this property is omitted, the value of IRISUSERPASSWORD is used.
If the initial security level is None, do not use this property.
INITIALSECURITY
Optionally use this property to specify the level of security to be used by the instance being installed. Specify None, Normal, or Locked Down.
Omit this property to accept the default of None.
See also the IRISUSERPASSWORD, CSPSYSTEMUSERPASSWORD, and SERVICECREDENTIALS properties in this table.
INSTALLDIR
Optionally use this property to specify the directory in which the instance is to be installed.
If the property is omitted, the default installation directory is C:\InterSystems\IRISn, where n is {empty}, 1, 2, ... 127.
INSTALLERMANIFEST
If installing with an installation manifest, as described in Using the Manifest in the chapter “Creating and Using an Installation Manifest”, you must use this property to specify the location of the installation manifest (that is, your exported manifest class) .
INSTALLERMANIFESTLOGFILE
If installing with an installation manifest, as described in Using the Manifest in the chapter “Creating and Using an Installation Manifest”, this property specifies where %Installer will print messages.
INSTALLERMANIFESTLOGLEVEL
If installing with an installation manifest, as described in Using the Manifest in the chapter “Creating and Using an Installation Manifest”, optionally use this property to specify the log level of the setup() method of your installation manifest class. The default log level is 1.
INSTALLERMANIFESTPARAMS
If installing with an installation manifest, as described in Using the Manifest in the chapter “Creating and Using an Installation Manifest”, use this property to specify the name/value pairs (name=value) to be passed to the first argument of the setup() method of your installation manifest clas. This property can be used to modify the configuration parameter file (iris.cpf) and activate the changes before your manifest runs. The following parameters can be specified:
For example:
INSTALLERMANIFESTPARAMS="bbsiz=512000,globals4kb=20, globals8kb=30,globals16kb=40,globals32kb=50, globals64kb=100,routines=40,gmheap=10000, LibPath=c:\libpath\,locksiz=2179648,MaxServerConn=5, Path=c:\lib\,ZFSize=2000,ZFString=3000"
The following would be useful in installing and activating 100 MB of 64KB buffers before running a manifest that creates a 64kb block size database:
INSTALLERMANIFESTPARAMS="globals64kb=100"
ISCSTARTCACHE Optionally set this property to 0 to prevent InterSystems IRIS from starting after installation. The default is 1, to start InterSystems IRIS.
ISCSTARTLAUNCHER Optionally set this property to 0 to prevent the InterSystems IRIS launcher from being added to the system tray. The default is 1, to add the launcher.
REINSTALL
Use this property to reinstall (repair) an installed instance of InterSystems IRIS or to change the custom-installed features (see the Custom-installable Features table) for an installed instance of InterSystems IRIS:
  • To reinstall whatever features are currently installed for the instance—whether that is a custom-installed subset of features or all features—specify ALL.
  • To reinstall a subset of InterSystems IRIS features that is different from the subset of features currently installed, specify a comma-separated list of featurenames together with their group names (as described in the example following this table).
See also the ADDLOCAL property (for use with new instances) and REMOVE property (for uninstalling installed instances).
REMOVE
Use this property to uninstall (remove) an instance of InterSystems IRIS or a subset of custom-installed features (see the Custom-installable Features table) installed for an installed instance of InterSystems IRIS:
  • To remove an instance of InterSystems IRIS, specify ALL.
  • To remove a subset of InterSystems IRIS features (see the Custom-installable Features table), specify a comma-separated list of featurename together with their group names (as described in the example following this table).
See also the ADDLOCAL (for new instances) and REMOVE properties in this table properties in this table.
SERVICECREDENTIALS
If the security level is Normalor Locked Down (see the INITIALSECURITY property in this table), optionally use this property to specify the credentials under which the Windows InterSystems service will run: LocalSystem for the default local system account or UserDefined (an existing Windows user account). If you do not specify the property, the default of LocalSystem is used.
If the initial security level is None, do not use this property.
See Managing Access to the InterSystems IRIS Instance for important information about the InterSystems service account.
If you specify UserDefined for this property, you must also specify the IRISSERVICEDOMAIN, IRISSERVICEPASSWORD, and IRISSERVICEUSER properties.
SUPERSERVERPORT
Optionally use this property to specify the Superserver port to be used by the instance being installed.
By default, this port is auto-determined, beginning with 51773 (if available), then 56773, and increasing by 1 for each installed instance of InterSystems IRIS.
UNICODE
Optionally use this property to specify whether 8–bit or 16–bit Unicode characters are to be supported by the instance being installed. For 8–bit characters, specify 0; for 16–bit characters, specify 1.
This setting applies to InterSystems IRIS instances only; InterSystems IRIS instances are always Unicode.
If you omit this property, is 8–bit specified by default for all languages except Chinese, Korean and Japanese; 16–bit is specified by default for Chinese, Korean, and Japanese systems.
WEBSERVERPORT
Optionally use this property to specify the Webserver port to be used by the instance being installed.
By default, this port is auto-determined, beginning with 52773 and increasing by 1 for each installed instance of InterSystems IRIS.
The Custom-Installable Features table lists component group/component names and the associated featurename for each. You can specify ALL” (to specify all available features) or a comma-separated list (with no spaces) of feature names (to specify individual features).
To specify components in ADDLOCAL, REINSTALL, and REMOVE properties (see the Command-Line Properties table), specify the featurename of a component group, followed by the featurename of each specific component from that group that you want installed. For example, to install only the USER database include the following in the command line:
ADDLOCAL=server,server_user
When specifying a component group, you must also specify at least one associated component; if no components are listed with a component group, the component group is ignored and no components are installed. For example, if you specify the following:
ADDLOCAL=documentation,documentation_pdf,server,development
the server component group is ignored and no server components are installed. (This requirement does not apply to the studio and cube groups as they have no components.)
Custom-Installable Features
Component Group (featurename) Components (featurename)
Server (server)
User database (server_user)
SQL Gateway (sqlgateway)
Apache Formatting Objects Processor (fop)
Server monitoring tools (server_monitoring)
Agent Service (agent_service)
Launcher (cube)
 
Studio (studio)
 
xDBC (sqltools)
ODBC (odbc)
JDBC (jdbc)
Development (development)
Callin (callin)
Callin, Threaded (callin_threaded)
.NET Binding (dotnetbind)
Threaded Server Libraries (server_threaded)
Other Samples (other_samples)
Documentation (documentation)
PDF Documentation (documentation_pdf)
Online Documentation (documentation_online)
Web Gateway (cspgateway)
IIS (cspiis)
Apache 2.0 (cspapache20)
Apache 2.2 (cspapache22)
Post-Installation Tasks
Review the following important post-installation tasks:
Special Considerations
The following topics describe particular issues or tasks associated with licensing, specific platforms, or kinds of installations:
Managing Access to the InterSystems IRIS Instance and Installation Tree
When InterSystems IRIS is installed with Normal or Locked-Down security, the account under which the Windows InterSystems service runs must have both of the following:
When you specify a service account to address these needs, the installer creates the following two user groups and adds the service account to each:
Please note the following points about these groups:
Important:
If you want to change the Windows InterSystems service account to one that is not in Administrators, do not use the Windows Control Panel for this purpose. Instead use the following command, which adds the specified account to the IRISServces and the IRIS_Instance_instancename groups:
<install-dir>\bin\IRISinstall.exe setserviceusername <instance-name> <username> <password>
Using an Installation Manifest
You can define an installation manifest that describes a specific InterSystems IRIS configuration and invoke it when executing the installation file. For more information on installation manifests, see the chapter Creating and Using an Installation Manifest.
Multiple InterSystems IRIS Installation Issues
You can install and simultaneously run multiple instances on a single Windows machine. Install InterSystems IRIS as for a single installation, giving each instance a unique name, a unique installation directory, and a unique port number.
Please refer to the Multiple InterSystems IRIS Instances section of the System Administration Guide for more detailed information.
Installing multiple InterSystems IRIS instances is limited by components where only one exists on a system. For example, typically there is only one web server on a system; and as such, the InterSystems IRIS installation configures the Web Gateway for the most recent installation. InterSystems IRIS client components stored in the registry encounter the same issue. InterSystems IRIS stores its ODBC driver in the registry using one name for each. Currently, the last installation updates these components to point to the last instance installed.
InterSystems makes an effort to move common components to a common directory that can be shared across InterSystems IRIS instances.
Registering Files
The InterSystems IRIS installation contains a Regfiles.bat script file in the install-dir/Bin directory that reregisters object tool files in a common InterSystems IRIS directory. You require Administrator privileges to run RegFiles.bat.
Important:
Running RegFiles.bat ALL when it is not necessary will prevent the uninstall procedure from removing some registry keys under HKLM\Software\Intersystems when you uninstall the last InterSystems IRIS instance.
Changing the InterSystems IRIS Language
When you install InterSystems IRIS, all supported language-specific utility DLLs are installed in the install-dir\Bin directory. Each DLL contains localized strings and messages.
The format of the name of the DLL is UTILaaa.DLL, where aaa is a 3-letter code that signifies the following languages:
Code Language
CHS Chinese (Simplified)
DEU German (Standard)
ENU English (United States)
ESP Spanish (Spain)
FRA French
ITA Italian (Standard)
JPN Japanese
KOR Korean
NLD Dutch (Standard)
PTB Portuguese (Brazilian)
RUS Russian
For information about changing the locale of an InterSystems IRIS installation, see Using the NLS Settings Page of the Management Portal in the “Configuring InterSystems IRIS” chapter of the InterSystems IRIS System Administration Guide.
Reinstalling or Uninstalling InterSystems IRIS
By running setup and selecting an InterSystems IRIS instance of the same version as the installer, or by selecting Programs and Features from Windows Control Panel and selecting an InterSystems IRIS instance, you can make changes to or uninstall the instance.
When you run setup as described in InterSystems IRIS Installation and select an InterSystems IRIS instance of the same version as the installer in the Select Instance box, or select an instance in Programs and Features and use the Change or Repair buttons, the Updating Instance instancename dialog box displays.
Note:
When you select the Uninstall button in Programs and Features, the uninstall operation begins immediately.
Click Next to display the Modify, repair or remove the program dialog box, then select the appropriate option on this dialog to change, repair, or uninstall the instance.
Important:
Use only the InterSystems IRIS installer or Windows Control Panel Programs and Features to uninstall InterSystems IRIS. Other uninstall programs are not supported and using them may cause unexpected results.
InterSystems InterSystems IRIS Packet Drivers
Install InterSystems IRIS Packet Driver for Windows 2000, XP, and 2003 Server
To use Raw Ethernet with InterSystems IRIS on Windows systems, you must install the appropriate packet driver as described below. First ensure that the appropriate driver file is available on your computer or on a network.
For Windows 2000, XP, and 2003 Server systems, install the InterSystems Packet Protocol Driver as follows:
  1. Right-click My Network Places on the desktop and click Properties.
    You can also click Start, point to Settings and click Network and Dial-up Connections.
  2. Right-click Local Area Connection and click Properties.
  3. Click Install.
  4. Click Protocol in the Select Network Component Type dialog box and then click Add.
  5. Click Have Disk in the Select Network Protocol dialog box.
  6. Enter the path to the packet driver kit and click OK.
    You can also enter the appropriate drive letter and click Browse to search for the correct path, \drivers\win2k, that contains the file ispkt2k.inf. Click Open and then click OK.
  7. Select the appropriate driver for your operating system, InterSystems Packet Driver for Windows 2000, XP and 2003 Server, for example, and click OK.
  8. After the driver is installed, click Close.
After you restart Windows, InterSystems IRIS is fully available to you.
Shared Memory Allocation on Windows
InterSystems recommends enabling InterSystems IRIS to allocate its memory as large pages on Windows systems, which provides more efficient use of memory and paging space. To do so, grant the Windows “Lock Pages in Memory” (SELockMemory) privilege to the user account used to run InterSystems IRIS, which allows InterSystems IRIS to request its memory as large pages. For finer grain control over the memlock parameters, see memlock in the Configuration Parameter File Reference.
Note:
If InterSystems IRIS is running under the default SYSTEM account, it has the “Lock Pages in Memory” privilege by default.
When you restart InterSystems IRIS while using large pages, you typically also need to restart Windows, to guarantee that all configured memory is allocated. If startup is unable to allocate the full amount of configured memory, it attempts to start up with less memory, and may or may not use large pages. You can check the actual memory allocated by reviewing the most recent InterSystems IRIS startup in the messages log.
Specifically, InterSystems IRIS allocates shared memory at Windows startup as follows:
  1. Request large pages, if allowed.
  2. If unable to allocate the full amount of configured memory in large pages, or if large pages are not allowed, request small pages.
  3. If unable to allocate the full amount of configured memory in small pages, reduce the allocation by one eighth (1/8) and begin again with step 1.