IBM i2 Products Packaging &

Deployment Guide
Version 8.9

May 2012
Copyright 0.1
Note: Before using this information and the product it supports, read the information in Notices on
page 115.

This edition applies to IBM® i2® software at version 8.9. and to all subsequent releases and
modifications until otherwise indicated in new editions.

This edition replaces part number 3069.

© Copyright International Business Machines Corporation 2007, 2012.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Contents

About This Guide 7

1: Packaging & Deploying IBM i2

Software Distributions 11
Introduction 12
About IBM i2 Software Distributions 13
Basic Installation 16
Custom Deployment Using the MSI File with Msiexec 21
Other Supported Deployment Technologies 31
Maintaining an IBM i2 Product Installation 32
Troubleshooting 39

A: IBM i2 Analyst's Notebook 43

Introduction 44
Prerequisite Software 45
Public Properties 46
Customizable Files 47
Product Features 48
Patches and Transforms 52

B: IBM i2 Analyst's Workstation 53

Introduction 54
Product Bundle 55
Prerequisite Software 56
Public Properties 57
Customizable Files 59
Product Features 60
Patches and Transforms 63

IBM i2 Products Packaging & Deployment Guide 3

Contents

C: IBM i2 Chart Reader 65

Introduction 66
Prerequisite Software 67
Public Properties 68
Customizable Files 69
Product Features 70

D: IBM i2 iBase 73
Introduction 74
Prerequisite Software 75
Public Properties 76
Customizable Files 77
Product Features 78
Patches and Transforms 83

E: IBM i2 Text Chart 85

Introduction 86
Prerequisite Software 87
Public Properties 88
Customizable Files 89
Product Features 90
Patches and Transforms 92

F: IBM i2 iBridge 93
Introduction 94
Prerequisite Software 95
Public Properties 96
Customizable Files 97
Product Features 98
Patches and Transforms 100

G: IBM i2 Analyst’s Notebook Connector for Esri 101

Introduction 102
Prerequisite Software 103
Public Properties 104
Customizable Files 105
Product Features 106
Patches and Transforms 107

4 IBM i2 Products Packaging & Deployment Guide

 Contents

H: IBM i2 iBase Retained Data Handover Interface 109

Introduction 110
Prerequisite Software 111
Public Properties 112
Customizable Files 113
Product Features 114
Patches and Transforms 115

Notices 117

Index 121

IBM i2 Products Packaging & Deployment Guide 5

Contents

6 IBM i2 Products Packaging & Deployment Guide

About This Guide

This guide explains the structure and functionality of the MSI installers that are
used to distribute IBM i2 products. The main part of the guide contains generic
information about installing IBM i2 products. The appendixes provide specific
information for individual IBM i2 products.

Intended audience
This guide is intended to be read by MSI packager and deployment staff.

Book structure
This guide includes the following:

Chapter 1, Packaging & Deploying IBM i2 Software Distributions

A reference list of how to perform some of the most common tasks and provides a
general overview of installing IBM i2 products.

Appendix A, IBM i2 Analyst's Notebook

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
Analyst’s Notebook® 8.9.

Appendix B, IBM i2 Analyst's Workstation

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM i2
Analyst's Workstation 8.9, specifically Data Miner 8.9.

IBM i2 Products Packaging & Deployment Guide 7

 Appendix C, IBM i2 Chart Reader
This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM i2
Chart Reader 8.9.

Appendix D, IBM i2 iBase

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM i2
iBase 8.9 (or IBM i2 iBase 8.9 as part of IBM i2 Analyst’s Workstation 8.9).

Appendix E, IBM i2 Text Chart

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM i2 Text
Chart 8.9.

Appendix F, IBM i2 iBridge

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM i2
iBridge 8.9.

Appendix G, IBM i2 Analyst’s Notebook Connector for Esri

This appendix contains information about the considerations you should make and
the options available to you, when you deploy, install, and maintain IBM i2
Analyst’s Notebook Connector for Esri 8.9.

Appendix H, IBM i2 iBase Retained Data Handover Interface

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM i2
iBase Retained Data Handover Interface 8.9.

Contacting IBM Support

IBM Support provides assistance with product defects, answers FAQs, and helps
users resolve problems with the product.

Before you begin

After trying to find your answer or solution by using other self-help options such as
technotes, you can contact IBM Support. Before contacting IBM Support, your
company or organization must have an active IBM software subscription and

8 IBM i2 Products Packaging & Deployment Guide

 support contract, and you must be authorized to submit problems to IBM. For
information about the types of available support, see the Support portfolio topic in
the "Software Support Handbook".

Procedure
To contact IBM Support about a problem:
1. Define the problem, gather background information, and determine the severity
of the problem. For more information, see the Getting IBM Support topic in the
Software Support Handbook.
2. Gather diagnostic information.
3. Submit the problem to IBM Support in one of the following ways:
Online through the IBM Support Portal: You can open, update, and view all of
your service requests from the Service Request portlet on the Service Request
page.
By phone: For the phone number to call in your region, see the Directory of
worldwide contacts web page.

Results
If the problem that you submit is for a software defect or for missing or inaccurate
documentation, IBM Support creates an Authorized Program Analysis Report
(APAR). The APAR describes the problem in detail. Whenever possible, IBM
Support provides a workaround that you can implement until the APAR is resolved
and a fix is delivered. IBM publishes resolved APARs on the IBM Support website
daily, so that other users who experience the same problem can benefit from the
same resolution.

How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information. To submit any comments about this book or any other
documentation, send your comments by email to [email protected].
Be sure to include the name of the book, the part number of the book, the version
of the software, and, if applicable, the specific location of the text that you are
commenting on (for example, a page number, table number, or a heading)

IBM i2 Products Packaging & Deployment Guide 9

10 IBM i2 Products Packaging & Deployment Guide
 1
Packaging & Deploying IBM i2 Software
Distributions

This chapter contains generic information about IBM i2 software distribution

installers. The appendixes provide specific information for individual IBM i2
products.

Contents
Introduction 12
About IBM i2 Software Distributions 13
Basic Installation 16
Custom Deployment Using the MSI File with Msiexec 21
Other Supported Deployment Technologies 31
Maintaining an IBM i2 Product Installation 32
Troubleshooting 39

IBM i2 Products Packaging & Deployment Guide 11

Introduction

Introduction 1.1
The aim of this guide is to assist with the deployment, installation, uninstallation
and maintenance of IBM i2 software, which is distributed using the Windows
Installer (MSI) technology. This guide is intended to be read by anyone installing
IBM i2 products, and particularly by systems administrators with responsibility for
packaging and deploying IBM i2 software.

The information in the main part of the guide is largely generic to all IBM i2
products. For specific information about packaging and deploying a particular IBM
i2 product, you should consult the appendixes in this guide.

Advantages of MSI technology

IBM i2 distributes the installation files for its products in Microsoft's MSI format. The
advantages of this format include:
• administrative and advertising (push and pull) network installations
• rollback of partial installs in the event of failure
• self-repair of installed applications if files become corrupted
• logging of installation and deployment events
• uninstallation with rollback and reference counting of shared components

The MSI technology allows software distribution in packages that support different
installation modes. These can vary from a fully automated installation on a single
machine, to a command line driven, customized installation that is published to all
the users on a network.

Prerequisites for installation

IBM i2 software requires version 2.0 SP1 of the .NET Framework, or later. The
installers check for the presence of the .NET Framework and will report its
absence, but they do not install it for you. If it is missing, you must install it yourself.

The Pre-requisites\Microsoft .NET Framework 2.0 SP1 folder of an IBM

distribution contains a .NET installer. Alternatively, you can visit the Microsoft
Update website and ensure that all of the computers on which you intend to install
IBM i2 software are up-to-date. If it is not already installed, the .NET Framework is
made available as an "optional" update.

In addition to the .NET Framework, some IBM i2 products have their own
prerequisites for installation. You can find lists of the prerequisites for the products
that you are using in the appendixes of this guide.

12 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

About IBM i2 Software Distributions 1.2

Depending on its nature and purpose, an IBM i2 software distribution can contain
files of up to six different types. They are:
1. A single file with the .msi extension (an "MSI file") that administrators can
drive and customize from the command line. You can use MSI files for first-time
installs and upgrades of IBM i2 products.
2. A single file with the .pdf extension (a "product definition file") that you can
use to create a deployment package in Microsoft Systems Management Server.
3. A Setup.exe file that is intended for double-click installation by end users.
This can be one of the following:
a. A simple wrapper around the .msi file. This type is inside a folder named
with the product name.
b. A small bootstrap utility, normally at the root of the deployment. See
Running the Installation Manager on page 16.
4. A single file called Update.exe or Hotfix.exe that allows end users to
patch their installed products just by double-clicking. Update.exe is a user-
friendly wrapper around the MSP file that is described next.
5. A single file with the .msp extension (a "patch file") that administrators can use
to update an existing installation of an IBM i2 product to a more recent version.
6. A set of files with the .mst extension (a "transform") that you can use to
configure or customize the contents or behavior of an MSI file before installing
it.

Of the above list an MSI file is present in all IBM i2 software distributions, while the
others depend on the product, and the type of the distribution. A patch file, for
example, would not be distributed with a new version of a product.

If your product distribution contains patch files or transforms, you should consult
the appendixes for detailed instructions on how to use them. This part of the guide
explains how to use the Installation Manager and MSI files that IBM distributes,
and provides generic information on the other file types.

IBM i2 Products Packaging & Deployment Guide 13

About IBM i2 Software Distributions

Certificates and signing

All installers are digitally signed with a certificate. This reduces the number of
warnings associated with User Account Control checks, especially on Windows
Vista or later.

Patches delivered as .msp files are signed with the same certificate so that, if
policy allows, end users can patch installed IBM i2 applications. The certificate
encoded within the installed application’s MSI file is used to validate the patch.

Note: If you modify an MSI file, the certificate it contains becomes invalid. This feature of
MSI files allows you to determine whether an installation package has been
modified since its release.

Microsoft Installer has an issue related to upgrading and uninstalling products that
were installed from MSI files: it can warn of an unsigned package even when all the
files involved in the operation are fully signed. In this situation, the following
procedure describes how to perform a manual check of the certificate’s validity.
1. Right-click on the MSI file and select Properties.
2. Click the Digital Signatures tab, and then click Details. The Digital Signature
Details dialog is displayed:

14 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

3. Check that the signature is still valid, and then click View Certificate to verify
that the certificate tree is valid too:

IBM i2 Products Packaging & Deployment Guide 15

Basic Installation

Basic Installation 1.3

The Setup.exe file is the easiest way to perform a default (or near-default)
installation of IBM i2 software on one or a few computers. It provides the following
features:
• An Installation Manager to assist with installation.
• Creation of a local cache of the installation files that will be used to repair the
installed application when necessary. After installation with the Installation
Manager, the distribution media should not be required again.

The Installation Manager controls files that use MSI technology, which relies on the
presence of the Msiexec executable on the local machine. Msiexec is a standard
part of the Windows operating system.

The Installation Manager deliberately does not offer all of the features of the MSI
distribution system – you cannot transform a Setup.exe file to change its
behavior, for example. In the appropriate circumstances, however, it offers a
convenient and quick solution.

License authorization
At version 8.9, IBM i2 products no longer support or require authorization
mechanisms such as dongles or software license management (SLM). When you
purchase or upgrade to version 8.9 of an IBM i2 product, you must upgrade your
other i2 products to version 8.9 at the same time.

Running the Installation Manager

Note: IBM i2 Intelligence Analysis software at version 8.9 is not compatible with earlier
versions of i2 software. Upgrading directly is not supported. To install IBM i2
software at version 8.9, you must first uninstall all of your existing i2 software, and
then install the new versions.

The Installation Manager installs, upgrades and configures IBM i2 products. The
contents of the pages depends on what you are installing, and what you currently
have installed. However, you are always given information about the product and a
convenient way to display a range of documentation including release notes and
online help.

If you have a product CD, then the Installation Manager starts automatically.

To install IBM i2 products select Install on the menu that is displayed on the left
side of the Installation Manager and follow the steps to complete the installation.

16 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Installing an IBM i2 product

You are guided through a series of installation dialogs that vary between products,
but have a number of common options. For example, you can choose where to
install a product on your machine:

You can also customize a product by adding and removing features from the
installation:

IBM i2 Products Packaging & Deployment Guide 17

Basic Installation

When you are happy with all the settings you have chosen, click Install on the final
dialog, and the installation proceeds as you have directed.

When the installation is finished click Finish to close the Installation Manager.

18 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Installation cache
After installation with Setup.exe, the installer creates a local cache of the
installation files.
• For Windows XP, in a folder called C:\Documents and Settings\All
Users\Application Data\i2\Installers Cache.
• For Windows 7/Vista, in a folder called C:\ProgramData\i2\Installers
Cache.

Note: ProgramData is a hidden folder.

The installer will use this cache to service any future requests to change, repair, or
remove the installation.

Location of installed files

The following table lists the default install locations of the different types of file that
are copied to your computer during installation with Setup.exe:

File type Default location on Windows XP

Read-only Program Files

documentation
executable

Common shared files Program Files\Common Files\i2 Shared

Start menu shortcuts Documents and Settings\All Users\Start Menu

Default file association Documents and Settings\All Users\Templates

templates

Example materials Documents and Settings\All Users\Documents\i2 or

Documents and Settings\All Users\Shared Documents\i2

Populating the user’s profile

Installers for IBM i2 products do not copy user-specific files directly to the user’s
profile. Instead, the application copies these files to an appropriate location when it
is first run, on a per-user basis.

In other words, it is the responsibility of the installer to install user-specific files

(such as example materials) to a central location:

Program Files\<productname>\Resources\Profile\...

IBM i2 Products Packaging & Deployment Guide 19

Basic Installation

Then, when an application is first run, it copies the files from this location into the
current user’s profile:

File type Default location on Windows XP

Example materials Documents and Settings\<username>\My Documents\i2 and

Documents and Settings\<username>\Application Data\i2

Shortcuts to useful Documents and Settings\<username>\My Documents\i2

locations

User-specific templates Documents and Settings\<username>\Templates

After the files have been copied once, they are not re-copied unless a change is
made to the Profile folder. In that case, the user’s profile may be upgraded with
the latest profile content.

Note: None of the default locations described above changes when you install using
Msiexec instead of the Installation Manager.

20 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Custom Deployment Using the MSI File with

Msiexec 1.4
The Installation Manager provides significant help with installing IBM i2 products. If
other products need to be installed first, then the Installation Manager may deal
with that as part of its normal operation.

An MSI file, on the other hand, just installs the product. If the product has
prerequisites, then you must install them yourself beforehand, perhaps by
instituting a chain of MSI installations with a batch sequence. On its own, an MSI
file will warn you of a missing prerequisite, but dealing with the warning is up to
you.

The relative simplicity of an MSI file makes it more suitable when you need to
control or customize an installation. Assuming you obey the prerequisites:
• MSI files let you install specific versions of different products. If a single product
is updated, you can install that instead of running a new version of the
Installation Manager.
• You can achieve finer control over the responsibility given to a user. For
example, you can arrange to suppress a particular installation dialog and hard-
wire the values it would normally set.
• You can run a transform against an MSI file that customizes it at the moment of
installation. (In other words, you can configure two different installations from a
single MSI file, instead of needing two different MSI files.)

Note: For MSI deployment, copy the file to the local machine and run it from there. This
way, if a repair is necessary, the installation media will not be required again.

The suggested location for MSI files is:

• Windows XP
C:\Documents and Settings\All Users\Application
Data\i2\Installers Cache.
• Windows 7/Vista
C:\ProgramData\i2\Installers Cache.

Double-click installation
When you control an installation using Msiexec, you will almost always invoke it
from the Windows command line. However, you can attempt to install the product
contained in an MSI file by double-clicking on the file. Doing so executes Msiexec
with a default set of options.

IBM i2 Products Packaging & Deployment Guide 21

Custom Deployment Using the MSI File with Msiexec

When you run the Msiexec like this, it performs similar checks to Setup.exe, but
it just reports any problems it encounters, instead of trying to deal with them. Such
problems could include an out-of-date version of Windows Installer, a missing
prerequisite, or an existing installation of the software.

If all of the prerequisites are in place, then double-clicking the MSI file displays the
same set of dialogs as clicking the Installation Manager, and installation proceeds
in exactly the same way. At the end of the process, however, Msiexec only caches
a "skeleton" of the MSI file on the target computer. If a repair or a reinstall is
required, users will need access to the original installation media – either the
downloaded distribution, a network copy of the MSI file, or a pre-cached version
(as described above).

Command line installation

The easiest use of Msiexec from the command line involves the /package
option. Subject to the described restrictions, this option performs an ordinary, local
installation of the product, and permits some simple customization. For example:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"

Issuing this command has exactly the same effect as double-clicking on the MSI
file, and therefore leads to the same sequence of installation dialogs. However, you
can provide options at the command line that modify the default behavior.

To install an IBM i2 product with all of its default settings, but with no need for
intervention from the user, you can perform a "silent install" like this:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi" /quiet

In terms of the installed product, issuing this command has the same effect as
double-clicking on the file and giving the simplest possible (affirmative) response to
every question. However, the user sees no feedback at all about the installation
process until the product shortcut is displayed in the Windows Start menu.

Note: On Windows Vista and later, a silent install with UAC switched on will fail, because
the system cannot display the message seeking permission for the process to run.
To run a silent install with UAC switched on, open the command prompt by right-
clicking on the cmd.exe file (or on Start ➧ Programs ➧ Accessories ➧ Command
Prompt), and selecting Run as Administrator In this mode, there is no
permission-seeking message, and the silent install runs successfully.

22 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

License acceptance in silent installations

Installations can be run in silent mode with no user interface either by using
Msiexec command line features (see Command line installation on page 22) or
using the Installation Manager (see Running the Installation Manager on page 16).

When an installation is run in silent mode no license acceptance dialogs are

displayed to allow the license to be accepted. By installing the product you are
accepting the terms of the license.

The license files are unique for each product and can be found in the License
folder in the product’s install location. To read these files in advance of installation,
perform an Administrative install (see Administrative installations on page 25) to
unpack the installation’s files and read the license files in the unpacked location.

\Program Files\{Product path}\License folder.

To provide the user with more information about what is happening to their
computer (but still using default options, and allowing no intervention), you can use
/passive instead of /quiet:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi" /passive

This command displays a dialog like this one, which remains on the user's desktop
until installation is complete:

Finally, the default installation folder for Analyst's Notebook 8 (for example) is
C:\Program Files\IBM i2 Analyst's Notebook 8. To change the folder
without requiring input from the user, you can do this:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"

/passive INSTALLDIR="C:\Notebook"

As well as sending the /passive option to Msiexec, this command sets the
public property called INSTALLDIR to change the install folder.

Note: Instead of /package here, you could use /i. The two options are equivalent.

IBM i2 Products Packaging & Deployment Guide 23

Custom Deployment Using the MSI File with Msiexec

Maintaining an IBM i2 Product Installation on page 32 describes how you can use
the Msiexec program to patch, repair, and uninstall an application as well as
installing it. In the above commands, the /package option specifies that you want
to install the application in the MSI file.

Custom public properties

INSTALLDIR is one in a long list of public properties that Msiexec supports.
Many are standard, and you can find full details about these on the MSDN website.
However, Msiexec also supports the use of custom public properties, on a per-
package basis. Most IBM i2 product packages define the following set of public
properties:

Property name Description

I2_LANGUAGE Specifies the installation language for a package

that has built-in support for more than one
language.
Providing a value for this property overrides the
default behavior, which is for the installer to
determine the correct language from the
computer's user locale settings.

I2_SHARED_PATH The location of the shared common files area for

IBM i2 products. Defaults to C:\Program
Files\Common Files\i2 Shared.
Be aware that this property only affects the first
IBM i2 application you install.

INSTALLDIR The location where the application will be

installed. For Analyst's Notebook 8, for example,
the default value is C:\Program Files\i2
Analyst's Notebook 8.

For example, you could force a British English installation on a computer that is set
to a US locale by providing a value for the I2_LANGUAGE public property:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"

/passive I2_LANGUAGE="en-GB"

Note: Changing the installation language of an IBM i2 application like this affects
template files, the semantic type library, and licenses. It does not change the
language used in the user interface.

24 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

In addition to the list in the table above, many IBM i2 products define their own
custom public properties. You can find lists of any custom public properties for the
products that you are using in the appendixes at the end of this guide.

Administrative installations
IBM i2 products support administrative installation: you can "install" from the
distribution media to an unpacked folder structure in a centralized network location.
Doing so provides two significant benefits:
• Users can install products from the network, instead of requiring access to the
distribution media.
• You can customize the product that will eventually be installed on end users'
machines by changing the contents of some of the files.

To perform an administrative installation, you replace the /package (or /i) option
to Msiexec with /a:

> Msiexec /a "IBM i2 Analyst's Notebook 8.msi"

This change adds a new dialog to the installation procedure. Instead of selecting a
destination folder, you must specify a network location:

If you want to perform the installation quietly or passively, you can provide a value
for the network location through a public property. For an ordinary installation, the
property was INSTALLDIR. For an administrative installation, it is TARGETDIR:

> Msiexec /a "IBM i2 Analyst's Notebook 8.msi"

/passive TARGETDIR=F:\

IBM i2 Products Packaging & Deployment Guide 25

Custom Deployment Using the MSI File with Msiexec

An administrative installation generates its unpacked folder structure at your

defined location, along with a new MSI file that has the same name as (but is
significantly smaller than) the original.

You can use the new MSI file for regular command line installations in exactly the
same way as you would use the original MSI file. If a user has all the prerequisites
installed, they can double-click on the file from its network location, or use
Msiexec /package to install it from the Windows command line.

Note: If an IBM i2 product has been installed from an administrative image, any patches
that IBM supplies for that product must be deployed using the method described in
Upgrading with an MSI file on page 35. MSI technology allows patches to be
applied to an administrative image. Once an administrative image has been used
to install on a target machine, that machine cannot be directly upgraded with a
patch and must be upgraded indirectly, using a patched administrative image.

Customizing an administrative installation

After you have performed an administrative installation, you can customize the
product that will eventually be installed on end users' machines by changing the
contents of the files in the unpacked folder structure. Any changes that you make
here will be installed for all users.

For example, an administrative installation of Analyst's Notebook 8 includes the

Standard template file, Standard.ant. This file is copied to the user's machine
when they install the product from the network. To provide users with a customized
template, you can modify the contents of the file in the administrative image. Then,
every user who installs from this location will receive the modified file, exactly as if
the file had been a part of the original installation.

Different IBM i2 products have different files that are particularly suitable for
customization in this fashion. You can find lists of such files for the products that
you are using in the appendixes at the end of this guide.

Customizing an administrative installation is a useful way of enforcing a site-wide

configuration change on all future installations of an IBM i2 product. It is limiting,
however, in that after the modification, it becomes impossible to use the
administrative files to perform a default installation. As described in Modifying an
MSI file on page 27, this limitation is not shared by transforms.

26 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Advertising installations
When you perform an advertising installation on a user's machine, the result is a
set of shortcuts and menu items that look as though a product has been fully
installed. However, the product is not actually installed until a user tries to launch
the application.

You can use either an original IBM i2 product MSI file or the MSI file from an
administrative installation as the basis for an advertising installation. To perform
the installation, you invoke Msiexec with the /jm option:

> Msiexec /jm "IBM i2 Analyst's Notebook 8.msi"

Note: The /jm option advertises the product to every user on the machine. IBM i2
products do not support installation with the /ju option, which can advertise an
installation only to the current user. If you attempt to use this option, you will see an
error message.

In addition, not all IBM i2 products support advertising installations. Neither iBase
nor Analyst's Workstation will install correctly if you use /jm or /ju on the
Msiexec command line.

After executing Msiexec /jm, a user selecting a product shortcut will trigger a full
installation, using the specified MSI file as the source. This takes place in the same
fashion as a passive installation: the user sees progress dialogs, but has no
opportunity to configure the product.

In an advertising installation, you cannot change a public property by setting it on

the command line, and a user cannot change details about the product when they
activate it. To alter the behavior of an advertising installation, you must modify the
MSI file, as described on page 27.

Modifying an MSI file

The public properties in the table in Custom public properties on page 24 provide
a way for you to change the behavior of an IBM i2 product installation. However,
the changes they enable are relatively small, and you can only apply them when
you start an installation from the command line.

To make more significant changes to the way an installation takes place, you can
edit the database that an MSI file contains, and from which Msiexec gets its
information about how to perform an installation. Doing so requires you to create a
transform.

IBM i2 Products Packaging & Deployment Guide 27

Custom Deployment Using the MSI File with Msiexec

Creating a transform with Orca

A transform is a collection of changes to an MSI installer, stored in a dedicated file
(with the .mst extension) that you can specify on the command line. For example,
you might create a transform that changes the name of the default program group
that IBM i2 installers create. You can then apply this transform to an MSI file during
installation.

As part of the freely downloadable Windows SDK, Microsoft provides the Orca tool
that allows you to make your own transforms, using a technique that is similar to
recording a macro in productivity applications. The procedure is:
1. Open an MSI file in Orca. This example uses IBM i2 Analyst's Notebook
8.msi.
2. From the Transform menu, select New Transform. The text "(transformed by
Untitled)" is added to the title of the Orca application window.
3. Select the Directory table, and then click on the header of the
Directory_Parent column to sort it.
4. Find the directory properties under the Directory_Parent column that refer to
ProgramMenuFolder:

28 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

5. Change the values in the DefaultDir column. You must change all the values,
or several different program groups will appear in the Start menu:

Values that you add, modify, or delete are highlighted in the Orca interface, as
shown above.
If the product has further subfolders in the Start menu program group, you can
change also change them in the Directory table. Search for the directory
property under the Directory_Parent column, and change the value in the
DefaultDir column.
6. From the Transform menu, select Generate Transform, and provide a name
for the transform that you are creating in the dialog that is displayed.
When you click Save, the transform file is created but not closed. You can make
more changes to the MSI file that will be "recorded" in the open transform.
7. When you have finished making changes to the MSI file, select Close
Transform from the Transform menu. Your transform is now ready to use.

When you close the transform, the MSI file reverts to its original state. In creating a
transform with Orca, you make no changes to the MSI file.

IBM i2 Products Packaging & Deployment Guide 29

Custom Deployment Using the MSI File with Msiexec

Transforming an installation from the command line

As described above, transforms enable you to customize and perform an
installation from the command line, simultaneously. The procedures for performing
a transformation are the same regardless of the origin of the transform:
• For a regular or administrative installation, you specify the transform in the
TRANSFORMS property on the command line:
> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"
/passive TRANSFORMS=transform.mst
Executing this command applies the transform to the MSI file before installation
takes place, so that the state of the installed product reflects the changes it
contains.
• For an advertising installation, you specify the transform in the /t option on the
command line.
> Msiexec /jm "IBM i2 Analyst's Notebook 8.msi"
/t transform.mst
Executing this command specifies the transform that will be applied, when a
user activates a full installation by selecting a shortcut. In this way, the source
MSI file remains unchanged, and may be used for other customized
installations.

In both of the forms described above, you can specify several transforms by
separating the file names with semicolons:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"

/passive TRANSFORMS=transform1.mst;transform2.mst

Msiexec applies the transforms in the order that you provide them on the
command line.

30 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Other Supported Deployment Technologies 1.5

IBM i2 products can be deployed using most ordinary deployment techniques. All
installations should be performed using the manufacturers’ recommended
processes.

IBM i2 Products Packaging & Deployment Guide 31

Maintaining an IBM i2 Product Installation

Maintaining an IBM i2 Product Installation 1.6

Deployment of an application from an MSI-based installer does not happen only at
installation time. There are four situations, post-installation, in which Msiexec can
be called into action:
• Repair of a damaged installation. This can be triggered automatically, or in
response to a user selecting Change in Add or Remove Programs in the
Windows Control Panel, and then selecting the Repair option. If the user has
access to the MSI file that was used for installation, they can also right-click on
the file and select Repair. In addition, you can exercise more control by
instigating a repair from the command line.
• Modification of an existing installation. This is usually triggered by a user
selecting Change in Add or Remove Programs in the Windows Control Panel,
and then selecting the Modify option.
• Patching an existing installation. When a product requires patching, upgrading,
or updating, IBM distributes files that Msiexec uses to bring the existing
installation up-to-date.
• Uninstalling the product. This is triggered in response to a user selecting
Remove in Add or Remove Programs in the Windows Control Panel, or by
selecting Change followed by Remove. Again, if the user has access to the
MSI file that was used for installation, they can also right-click on the file and
select Uninstall.

Repairing a damaged installation

In many circumstances, the MSI installation mechanism will detect damage to an
application that it has installed. If an essential file is accidentally deleted, Msiexec
runs automatically and attempts to repair the damage:
• If the application was originally installed using the Installation Manager,
Msiexec will use the cached MSI file to attempt the repair.
• If the application was originally installed from an MSI file, Msiexec needs
access to the location from which the installation took place, or the distribution
media.

User-initiated repair
If a user detects a problem with an application that is not being repaired
automatically, they can initiate a repair by selecting Change in Add or Remove
Programs in the Windows Control Panel.

Msiexec will attempt to restore the application, including all of its files and registry
settings, to its original condition.

32 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Repair from the command line

When you specify the /f option to Msiexec on the command line, you initiate a
repair. The /f option has a number of sub-options that control its behavior – in
particular, the circumstances under which it replaces a missing or damaged file.

For example, the user-initiated repairs described above are equivalent to invoking a
repair with the o, m, u, and s sub-options on the command line:

> Msiexec /fomus "IBM i2 Analyst's Notebook 8.msi"

The MSI file that you specify here must be the one that was used to install the
application in the first place.

Alternatively, you can re-run an installation completely, reinstalling all files and re-
caching the local package, by specifying the a, m, u, s, and v sub-options:

> Msiexec /famusv "IBM i2 Analyst's Notebook 8.msi"

The MSDN Library contains a complete reference to the sub-options of the /f

command line option to Msiexec.

Modifying an installation
Users can change the configuration of an installed application (that is, change the
installed features) in more or less the same way as they initiate a repair. Select
Change in Add or Remove Programs in the Windows Control Panel, you modify an
application by selecting Modify instead of Repair on the resulting dialog.

IBM i2 Products Packaging & Deployment Guide 33

Maintaining an IBM i2 Product Installation

Modification from the command line

To modify an installed application from the command line, you call Msiexec with
the same /package (or /i) option that you use when installing the application for
the first time. To change the installed features, you must specify some public
properties, of which two are particularly important:
• REMOVE, which you set to a comma-separated list of the features to be
removed from the installed application, or "ALL" to remove all non-essential
features.
• ADDLOCAL, which you set to a comma-separated list of the features to be
added to the installed application, or "ALL" to install all features.

Note: To prevent the Install Type dialog from displaying (in which the user is able to select
the Custom, Typical or Complete option), call Msiexec with the /quiet or
/passive option.

In general, you do not know the configuration of an installed application before you
modify it. A typical approach is to remove all features, and add the ones you want.
For example:

> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"

REMOVE=ALL /q
> Msiexec /package "IBM i2 Analyst's Notebook 8.msi"
ADDLOCAL=i2ANB,ThirdParty /q

The list of features comes from the Feature table in the MSI database, and varies
from product to product. The appendixes in this guide contain per-product details.

Patching/Upgrading/Updating an IBM i2 product installation

When IBM i2 updates or upgrades one of its products, it distributes four new
installation files. These are:
• A new version of Setup.exe, which installs all the latest product files on a
machine that has not had the application installed before, or updates an
existing installation to the latest version.
• A file called Update.exe or Hotfix.exe, which updates an existing
installation to the latest version. Because it only contains the files necessary to
perform the update, this file is typically much smaller than Setup.exe.

34 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

• A new MSI file that contains the new version of the product. You can use this for
a new installation or – by specifying appropriate options on the command line –
to update an existing installation.
• A file with a .msp extension (an "MSP file") that you can use to update an
ordinary installation or an administrative installation to the latest version, from
the command line. Subsequent installs from the administrative installation will
be the latest version.

The MSI distribution mechanism means that you can uninstall a patch and revert to
an earlier installed version, should you need to do so.

Patching with Setup.exe and Update.exe

As long as the target computer has an existing IBM i2 product installation with the
same major version number as the version in Setup.exe or Update.exe,
double-clicking on either executable has the same effect. If you need anything
other than the default settings, use the MSP file and Msiexec from the command
line.

Upgrading with an MSI file

Upgrading an MSI file to upgrade an existing product installation to a new version
is similar to instigating a repair from the command line. Conceptually, the operation
lies between a simple repair and a complete reinstallation. You invoke Msiexec
against the new MSI file, specifying the /f command line option with the o, m, u, s,
and v sub-options:

> Msiexec /fomusv "IBM i2 Analyst's Notebook 8.msi"

This command instructs Windows Installer to retain as much of the existing

installation as it can, but to take changes and new files from the updated MSI file.

Note: Unlike MSP files (described below), you cannot use an MSI file to patch an
administrative installation. Instead, you can create an up-to-date administrative
installation from the new MSI file.

IBM i2 Products Packaging & Deployment Guide 35

Maintaining an IBM i2 Product Installation

Patching with an MSP file

When you patch an existing IBM i2 product installation with an MSP file, you pass
the file name as a command line argument to Msiexec. You can use an MSP file
to patch ordinary and administrative installations.
• To patch an ordinary installation on a user's machine, you specify the location
of the MSP file to Msiexec's /update or /p option:
> Msiexec /update NewVersion.msp
In this situation, Msiexec can determine the location of an existing installation
and update it accordingly. You do not need to provide any extra information.
• To patch silently requires the REINSTALL properties below:
> Msiexec /update NewVersion.msp REINSTALL=ALL
REINSTALLMODE=omus /qb
• To patch an administrative installation, you must also provide the location of the
installed MSI file that is to be updated, with the /a option:
> Msiexec /update NewVersion.msp /a ExistingInstall.msi
This will update the network share with the new content; the administrative
install will now contain an updated MSI file that must be reinstalled to users
through the REINSTALL property.
To reinstall the entire MSI file, use:
> Msiexec /i [AdminInstallPath\msifile]
REINSTALL=ALL REINSTALLMODE=omus
If only some features are to be installed, use:
> Msiexec /i [AdminInstallPath\msifile]
REINSTALL=FeatureList REINSTALLMODE=omus

Note: An administrative installation does not add information to the registry, so

Msiexec is unable to determine the location of an existing product
automatically in this case.

• If the product is not already installed, it is possible to install both the base
product and the patch concurrently. The following command applies the patch
as a transform to the MSI file prior to installation, ensuring that the updated
product is installed:

36 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

> Msiexec /i <path to msi> PATCH="<path to msp>" /qb

Note: The /qb option is required to ensure that the MSI package is correctly
installed after the patch is applied. If you are installing a patch, you
cannot also use the installer user interface.

Note: The PATCH property cannot be set in a command line where the /p
option is used. If the PATCH property is set when the /p option is used,
the value of the PATCH property is ignored.

Uninstalling an IBM i2 software installation

Like repairing, modifying, and patching an installation, you can uninstall an IBM i2
product through the Control Panel or the command line. By the nature of
uninstalling an application, there is little to choose between the effects of the two
techniques.

To uninstall an IBM i2 product from the Control Panel, you follow the same
procedure as for any application that has been installed using MSI technology:
1. In the Windows Control Panel, open Add or Remove Programs.
2. Select the IBM i2 product you want to uninstall.
3. Click Remove, and then Yes on the dialog that is displayed next.

Note: Uninstalling a product that was originally installed using Setup.exe does not
delete the cached MSI file. You must remove this part of the product by hand.

To uninstall an IBM i2 product from the command line, you invoke Msiexec with
either the /uninstall or the /x option, followed by the location of an MSI file.
For example:

> Msiexec /uninstall "IBM i2 Analyst's Notebook 8.msi"

If the application was originally installed using Setup.exe, then the MSI file you
specify here must be the file that was cached during installation. If the application
was installed from an MSI file, then you must specify the same MSI file for
uninstallation.

Note: Other Msiexec options like /quiet and /passive still work for uninstall
operations in the same way as they work for install operations.

To retain compatibility with other versions of IBM i2 products, uninstallation does

not automatically delete the shared semantic type library. If you know that you no
longer require it, you can delete the semantic type library by deleting the folder at
Program Files\Common Files\i2 Shared\Semantic Types.

IBM i2 Products Packaging & Deployment Guide 37

Maintaining an IBM i2 Product Installation

Note: After uninstalling the last IBM i2 application on your computer, you can ensure that
everything has been removed by deleting:
1. The folder at Program Files\Common Files\i2 Shared, if it exists.
2. The following assemblies from the Windows\assembly folder (GAC):
SemanticMatchingBehaviour
SemanticUtilities
SMBInterfaces
3. The registry key at HKEY_LOCAL_MACHINE\Software\i2, and all of its
children.

Uninstalling a patch from the command line

If you installed a patch using the /update or /p option to Msiexec, then you can
remove that patch without uninstalling the whole application by specifying both the
patch and the original MSI file on the command line:

> Msiexec /uninstall "NewVersion.msp"

/package "IBM i2 Analyst's Notebook 8.msi"

Once again, you must provide the correct versions of the MSI and MSP files to
Msiexec in a command like this. If you fail to do so, an error will result.

38 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

Troubleshooting 1.7
The MSI technology that IBM i2 product installers use provides two main
mechanisms for troubleshooting software deployment:
1. All installation/modification/uninstallation operations that use the MSI
mechanism write information about their progress to the system event log.
2. Optionally, you can arrange for these operations to log more verbose
information to a text file of your choosing.

Reading the System Event Log

The MSI install process automatically sends notices of its activity to the system
event log. To read the event log, you use the Event Viewer, which you can access
through the Administrative Tools applet in the Control Panel.

Any events logged by the MSI install process have their source set to MsiInstaller.
In general, these types of log entry are informational, and report the success or
failure of install or removal operations. If there is a problem with an operation, you
will see a warning or an error message that describes more about what went
wrong. There are messages for events such as:
• Success or failure of an installation
• Removal or repair of a product
• Errors that occur during configuration
• Detection of corrupted configuration data

The MSDN Library provides a complete list of the event messages that the MSI
install process can generate. The same source contains further information on how
to interpret these messages.

IBM i2 Products Packaging & Deployment Guide 39

Troubleshooting

Enabling verbose logging

To enable more verbose logging about the install process than the system event
log provides, you must add a value to a key in the registry. The key in question is
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\
Installer, which has values called (Default) and EnableAdminTSRemote. The
new addition is a string value named Logging, with the value voicewarmup:

With this value in the registry, any (direct or indirect) call to Msiexec generates a
file in the current user's Local Settings\Temp folder. This file is named
MSIxxxxx.LOG, where xxxxx is a hexadecimal number.

This log contains details of everything that took place during the MSI operation,
including properties being set and retrieved, and registry entries being read and
created. It provides more information, and greater opportunity to discover the
cause of any problems.

Note: If you experience a problem with installation that requires you to contact IBM
Technical Support, the team will require a verbose log in order to assist you.

Understanding the verbose log

The log file that Msiexec generates as a result of this registry setting contains a
record of every action that took place during a particular installer operation,
including property changes, file system operations, registry manipulation, and so
on. Each line is marked (c) or (s):
• (c) indicates the client, which is the application that asks Windows Installer to
do something. This could be the shell, or the Control Panel, for example.
• (s) indicates the Windows Installer service, which acts upon the information in
an MSI file, and makes changes to the computer as a result.

40 IBM i2 Products Packaging & Deployment Guide

 Chapter 1: Packaging & Deploying IBM i2 Software Distributions

A typical sequence of actions is for the client to prepare itself for the installation
before passing a set of properties that reflect its current state to the service. The
service then performs the installation, and passes a changed set of properties
back to the client. In other words, you see a set of (c) actions, followed by a set of
(s) actions, followed by a final, smaller set of (c) actions.

Note: For more information on this aspect of Windows Installer, and an annotated
sample log file, you can read the white paper at Microsoft's Technet website.

Resolving problems with Terminal Server

As described in Repairing a damaged installation on page 32, a standard feature
of an MSI-based installation is the automatic repair of a damaged application. If a
remote user of a Terminal Server installation detects such damage, an automatic
repair is triggered, but will fail: the user does not have permission to perform the
repair.

If this situation arises, an administrator must launch the damaged application on

the Terminal Server. The repair will then take place successfully, and remote users
will be able to resume their work with the application.

IBM i2 Products Packaging & Deployment Guide 41

Troubleshooting

42 IBM i2 Products Packaging & Deployment Guide

 A
IBM i2 Analyst's Notebook

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
Analyst’s Notebook®.

For full instructions on how to use the features and functionality described here,
you should refer to Chapter 1, Packaging & Deploying IBM i2 Software
Distributions.

Contents
Introduction 44
Prerequisite Software 45
Public Properties 46
Customizable Files 47
Product Features 48
Patches and Transforms 52

IBM i2 Products Packaging & Deployment Guide 43

Introduction

Introduction A.8
This appendix contains information about the product-specific features of Analyst's
Notebook 8.9 that can affect the way you deploy it. It describes:
• The Installation Manager that manages the installation of the products in the
bundle.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user’s installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.

44 IBM i2 Products Packaging & Deployment Guide

 Appendix A: IBM i2 Analyst's Notebook

Prerequisite Software A.9

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of Analyst's Notebook, please refer to the release notes that are available on the
installation media.

IBM i2 Products Packaging & Deployment Guide 45

Public Properties

Public Properties A.10

Analyst's Notebook supports all the custom public properties described in the
main part of the guide. The following table lists the additional properties that you
can specify on the Msiexec command line for this product:.

Property name Description Default

ADMINONLY_SOFTWARE_UPDATES A flag that prohibits non-admin FALSE

users from executing the online
updates for software.

ADMINONLY_SOURCE_UPDATES A flag that prohibits non-admin FALSE

users from executing the online
updates for source configuration
files.

REPLACE_FLAG_TEMPLATE Reserved for future versions. 1

REPLACE_MILITARY_TEMPLATE Reserved for future versions. 1

REPLACE_REPORTER_SPEC Reserved for future versions. 0

REPLACE_STANDARD_TEMPLATE Reserved for future versions. 1

REPLACE_USER_GUIDE_EXAMPLES Reserved for future versions. 1

USER_CAN_CANCEL_REPLACE Reserved for future versions. 1

46 IBM i2 Products Packaging & Deployment Guide

 Appendix A: IBM i2 Analyst's Notebook

Customizable Files A.11

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked folder structure containing all the files that will be copied to a user’s
machine when they install the product. You can therefore customize an installation
by replacing some of the standard files with your own versions.

The following is a list of the files in an administrative installation of Analyst's

Notebook that you might want to replace:

File name Description

Reporter.rep Contains the report specification definitions that Analyst’s

Notebook provides by default. If your organization has
custom report specifications, you can save them in a file
named Reporter.rep and replace the shipped file.

Standard.ant Contains the Standard template that Analyst’s Notebook

uses by default as the base for all new charts. If your
organization has its own base template file, you can
rename it Standard.ant, and copy it over the existing
file with that name.

IBM i2 Products Packaging & Deployment Guide 47

Product Features

Product Features A.12

During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties,
with the option /passive (/qb) or /quiet (/q) to request a passive or silent
installation.

The following list contains the names of all the features in the Feature table of the
MSI database for Analyst's Notebook 8:

Feature name Description Also requires

i2ANB Analyst’s Notebook main ThirdParty,

program files SpellingChecker with
one dictionary

ThirdParty Non-i2 system files See note below

Examples Optional example materials i2ANB

(charts and templates)

Help Optional online help files i2ANB

OnlineiLink Online iLink enables real- i2ANB

time access to IBM i2
Information Exchange
Visualizer-enabled data
sources

OISCCPAutoTrackXP Online iLink source OnlineiLink

configuration files

OISCDandB Online iLink source OnlineiLink

configuration files

OISCLN Online iLink source OnlineiLink

configuration files

OIThirdParty Online iLink source OnlineiLink

configuration files

OIHelp Optional Online iLink help. OnlineiLink

SpellingChecker Spelling checker software i2ANB

48 IBM i2 Products Packaging & Deployment Guide

 Appendix A: IBM i2 Analyst's Notebook

Feature name Description Also requires

i2LangAmerican Spelling checker dictionary i2ANB,

i2LangBrazilian files. You must select one of SpellingChecker
i2LangBritish these languages.
i2LangDanish
i2LangDutch
i2LangFinnish
i2LangFrench
i2LangFrenchCanadian
i2LangGerman
i2LangItalian
i2LangNorwegian
i2LangPortuguese
i2LangSpanish
i2LangSwedish

For example, to configure an installation of Analyst's Notebook 8 in order to

change from British- to French-language spelling, you must first remove support for
the former:

> Msiexec /i "IBM i2 Analyst's Notebook 8.msi"

REMOVE=i2LangBritish /q

And then add support for the latter:

> Msiexec /i "IBM i2 Analyst's Notebook 8.msi"

ADDLOCAL=i2LangFrench /q

Third party merge modules

ThirdParty and OnlineiLink features are provided so that you can install the
Microsoft and other third-party merge modules separately, and then use the
Analyst’s Notebook installer to install only the IBM i2 files.

Analyst’s Notebook requires all of the merge modules that the ThirdParty feature
installs, as listed in the following table:

DLL version
Module name
number

Microsoft Common Dialog ActiveX Control DLL 6.1.97.82

Microsoft Common Controls 2 ActiveX Control DLL 6.1.98.12

IBM i2 Products Packaging & Deployment Guide 49

Product Features

DLL version
Module name
number

Microsoft Flexgrid Control 6.0 6.1.98.11

Microsoft OLE 2.40 for Windows NT(TM) and Windows 2.40.4275.1,

95(TM) Operating Systems 5.0.4275.1

Microsoft Visual Basic Virtual Machine 6.0 6.0.97.82

MSXML 4.0 4.10.9404.0,

4.20.9818.0

VC User CRT71 RTL X86 7.10.3052.4

VC User MFC71 RTL X86 7.10.3077.0

VC User STL71 RTL X86 7.10.3077.0

Visual C++ 8.0 ATL (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 ATL.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 CRT (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 CRT.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 9.0 ATL (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 CRT (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFC (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFCLOC (x86) WinSXS MSM 9.0.21022.8

stdole DLL 7.0.9466.0

i23rdPartyWoodBuryUnicodeToolbox 1.4.0.1, 1.3.0.1,

1.1.0.32

Windows Common Controls ActiveX Control DLL 6.1.97.86

Visual C++ 8.0 MFCLOC.Policy (x86) WinSXS MSM 8.0.50727.4053

50 IBM i2 Products Packaging & Deployment Guide

 Appendix A: IBM i2 Analyst's Notebook

To enable real-time access to IBM i2 Information Exchange Visualizer-enabled

data sources, Analyst’s Notebook also requires the merge modules that the
OnlineiLink feature installs:

DLL version
Module name
number

i23rdPartyCyberActiveX 1.0.0.258,
1.2.0.18,
1.0.0.51,
1.0.0.4,
1.0.0.96

i23rdPartyWoodBuryUnicodeFlexGrid 1.3.0.6,
2.0.0.0

UniToolbox control suite

Analyst’s Notebook uses the UniToolbox components provided by Woodbury
Associates Ltd. These components are installed into their own folders in
Program Files\Woodbury Associates to avoid any incompatibility with other
products that use the same controls.

IBM i2 Products Packaging & Deployment Guide 51

Patches and Transforms

Patches and Transforms A.13

The distribution of Analyst’s Notebook that this document accompanies contains
no patch files or transforms.

52 IBM i2 Products Packaging & Deployment Guide

 B
IBM i2 Analyst's Workstation

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain the
products in the IBM® i2® Analyst's Workstation product bundle.

This appendix also provides information about Data Miner. For information specific
to IBM i2 Analyst’s Notebook®, see Appendix A, IBM i2 Analyst's Notebook, for
information specific to IBM i2 iBase, see Appendix D, IBM i2 iBase.

For full instructions on how to use the features and functionality described here,
you should refer to Chapter 1, Packaging & Deploying IBM i2 Software
Distributions.

Contents
Introduction 54
Product Bundle 55
Prerequisite Software 56
Public Properties 57
Customizable Files 59
Product Features 60
Patches and Transforms 63

IBM i2 Products Packaging & Deployment Guide 53

Introduction

Introduction A.14
This appendix contains information about the product-specific features of the
Analyst's Workstation 8 product bundle that can affect the way you deploy it. Some
of this information applies to Data Miner only–separate appendices provide
information on Analyst’s Notebook 8 and iBase 8.

It describes:
• The Installation Manager that manages the installation of the products in the
bundle.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of Data Miner. The public properties for
Analyst’s Notebook 8 and iBase 8 are described in separate appendices.
• The files created during an administrative installation that you might replace in
order to customize a user's installation.
• The features of Data Miner that you can choose to add or remove during
installation, or during modification of the installed product.
• Any Data Miner-specific patches and transforms that are shipped with this
version of the product.

54 IBM i2 Products Packaging & Deployment Guide

 Appendix B: IBM i2 Analyst's Workstation

Product Bundle A.15

Analyst's Workstation 8 is provided as a bundle of three product installers, a
documentation installer and the Installation Manager utility to help install and
upgrade the bundled products. The products in this bundle are:
• IBM i2 Analyst's Notebook 8.9
• IBM i2 iBase 8.9
• Data Miner 8.9
• Analyst's Workstation 8 Extras

The bundle allows individual products to be upgraded separately when the

constituent products have new releases from IBM.

The Installation Manager manages the installation and upgrading of previous

versions of the products and provides assistance in installing the prerequisites as
well as providing useful information and links to the documentation.

IBM i2 Products Packaging & Deployment Guide 55

Prerequisite Software

Prerequisite Software A.16

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of Analyst's Workstation, please refer to the release notes that are available on the
installation media.

Microsoft SQL Server Analysis Services

Before you can run Analyst’s Workstation on a client machine, you need to install
the relevant Analysis Services client components for your version of SQL Server.
See the release notes for more details.

56 IBM i2 Products Packaging & Deployment Guide

 Appendix B: IBM i2 Analyst's Workstation

Public Properties A.17

Data Miner 8 supports all the custom public properties described in the main part
of the guide.

The following table lists the additional properties that you can specify on the
Msiexec command line for Data Miner 8 or when using the Custom Setup option:

Property name Description Default

AS2005SERVER Machine for building cubes Database Machine

with SQL Server 2005 or
2008.

AS2005INSTANCE Instance for building cubes Same as SQL

with SQL Server 2005 or Server
2008.

In the previous table AS2005SERVER can take these values:

Property value Description

Local Machine The cube will be built locally.

Database Machine The cube will be built on the machine running the
SQL Server instance used by the iBase database.

Not Available Cube building is not allowed.

Any other value The name of a specific machine on which the cube
is to be built (including an IP address).

Similarly, AS2005INSTANCE can have the following values:

Property value Description

Same as SQLServer Use the Analysis Server instance that matches the
SQL Server instance name. This is the default
when cubes are built on the database machine.

Default Use the default instance on the local machine

(MSSQLSERVER).

IBM i2 Products Packaging & Deployment Guide 57

Public Properties

Property value Description

MSSQLSERVER Use the default instance on the local machine

(MSSQLSERVER).

Any other value The name of an instance on the machine

referenced by the AS2005SERVER property.

If these properties are set on the command line then they will be used when doing
a silent install or when using the Complete Setup option. They will also become the
defaults for the Custom Setup option, which allows you to customize them further.

Note: For information on Analyst’s Notebook public properties, see page 46, and for the
iBase public properties, see page 76.

58 IBM i2 Products Packaging & Deployment Guide

 Appendix B: IBM i2 Analyst's Workstation

Customizable Files A.18

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked directory structure containing all the files that will be copied to a
user's machine when they install the product. You can therefore customize an
installation by replacing some of the standard files with your own versions.

The distribution of Data Miner that this document accompanies has no files that
you can customize in this way.

IBM i2 Products Packaging & Deployment Guide 59

Product Features

Product Features A.19

During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties,
with the option /passive (/qb) or /quiet (/q) to request a passive or silent
installation.

The following list contains the names of all the features in the Feature table of the
MSI database for Data Miner 8, and the requirements of each feature:

Feature name Description Also requires

DataMiner Ability to build iBase data into Shared, ThirdParty

cubes for multidimensional
analysis.

Help Online help files DataMiner

AdminCenter Documentation for administrators

of Analyst’s Workstation.

Shared Shared components used by both

Analyst's Notebook and iBase.

ThirdParty Microsoft and other third-party See note below.

merge modules.

Note: You can install the Administration Center without installing the Data Miner 8
software, so that you may read the documentation before installation. Alternatively,
you can access the documentation in the Analyst’s Workstation 8 distribution
package, in the Administration Center directory.

For example, to install the Administration Center only:

> Msiexec /i "IBM i2 Analyst’s Workstation Data Miner 8.msi"

ADDLOCAL=AdminCenter

To install both Data Miner 8 and the Administration Center:

> Msiexec /i "IBM i2 Analyst’s Workstation Data Miner 8.msi"

ADDLOCAL=DataMiner,AdminCenter

Note: For information on Analyst’s Notebook product features, see page 48, and for the
iBase product features, see page 78.

60 IBM i2 Products Packaging & Deployment Guide

 Appendix B: IBM i2 Analyst's Workstation

Third party merge modules

The ThirdParty feature is provided so that you can install the Microsoft and other
third-party merge modules separately, and then use the Data Miner 8 installer to
install only the IBM i2 files.

Data Miner 8 requires all of the merge modules that the ThirdParty feature installs,
as listed in the following table:

DLL version
Module name
numbers

CMDialog ActiveX Control DLL 6.0 6.1.97.82

Microsoft (R) C++ Runtime Library 6.0 6.0.8972.0

Microsoft ADO Data Control 6.1.97.82

Microsoft Common Controls 2 ActiveX Control DLL 6.1.97.82

Microsoft Common Controls 3 ActiveX Control DLL 6.7.0.8988

Windows Common Controls ActiveX Control DLL 6.1.97.86

Microsoft Hierarchical FlexGrid Control 6.0.88.4

Microsoft Rich Textbox Control Library (version 6) 6.0.88.77

MSFlexGrid Control 6 6.1.97.82

MSXML 4.0 NT 4.10.9404.0

MSXML 4.0 XP and Later 4.20.9818.0

VB Control mschart RTL X86 6.0.88.4

VC User CRT71 RTL X86 7.10.3052.4

VC User MFC71 RTL X86 7.10.3077.0

VC User STL71 RTL X86 7.10.3077.0

Visual Basic Virtual Machine 6.0.97.82

Visual C++ 8.0 ATL (x86) WinSXS MSM 8.0.50727.7.4053

Visual C++ 8.0 CRT (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC (x86) WinSXS MSM 8.0.50727.7.4053

Visual C++ 8.0 OpenMP (x86) WinSXS MSM 8.0.50727.4053

IBM i2 Products Packaging & Deployment Guide 61

Product Features

DLL version
Module name
numbers

Visual C++ 8.0 MFCLOC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC.Policy (x86) WinSXS MSM 8.0.50727.4053

Windows Common Controls ActiveX Control DLL (5) 6.0.81.5

stdole 7.0.9466.0

Note: For information on Analyst’s Notebook third party merge modules, see page 49,
and for the iBase third party merge modules, see page 81.

62 IBM i2 Products Packaging & Deployment Guide

 Appendix B: IBM i2 Analyst's Workstation

Patches and Transforms A.20

The distribution of Data Miner 8 that this document accompanies contains no
patch files or transforms.

Note: For information on Analyst’s Notebook, see Patches and Transforms on page 52,
and for iBase, see Patches and Transforms on page 83.

IBM i2 Products Packaging & Deployment Guide 63

Patches and Transforms

64 IBM i2 Products Packaging & Deployment Guide

 C
IBM i2 Chart Reader

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
Chart Reader 8.9.

For full instructions on how to use the features and functionality described here,
you should refer to Chapter 1, Packaging & Deploying IBM i2 Software
Distributions.

Contents
Introduction 66
Prerequisite Software 67
Public Properties 68
Customizable Files 69
Product Features 70

IBM i2 Products Packaging & Deployment Guide 65

Introduction

Introduction A.21
This appendix contains information about the product-specific features of Chart
Reader that can affect the way you deploy it. It describes:
• The prerequisite software that you must have installed before you can attempt
to install the product itself.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user’s installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.

66 IBM i2 Products Packaging & Deployment Guide

 Appendix C: IBM i2 Chart Reader

Prerequisite Software A.22

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of Chart Reader, please refer to the release notes that are available on the
installation media.

IBM i2 Products Packaging & Deployment Guide 67

Public Properties

Public Properties A.23

Chart Reader supports all the custom public properties described in the main part
of the guide. The following table lists the additional properties that you can specify
on the Msiexec command line for this product:

Property name Description Default

ADMINONLY_SOFTWARE_UPDATES A flag that prohibits non-admin users from FALSE

executing the online updates for software.

ADMINONLY_SOURCE_UPDATES A flag that prohibits non-admin users from FALSE

executing the online updates for source
configuration files.

CHARTREADER_ENABLE_PRINT Controls whether the user is allowed to print 1 (True)

charts.

CHARTREADER_ENABLE_SAVE Controls whether the user is allowed to save 1 (True)

charts.

68 IBM i2 Products Packaging & Deployment Guide

 Appendix C: IBM i2 Chart Reader

Customizable Files A.24

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked folder structure containing all the files that will be copied to a user's
machine when they install the product. You can therefore customize an installation
by replacing some of the standard files with your own versions.

The distribution of Chart Reader that this document accompanies has no files that
you can customize in this way.

IBM i2 Products Packaging & Deployment Guide 69

Product Features

Product Features A.25

During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties,
with the option /passive (/qb) or /quiet (/q) to request a passive or silent
installation.

The following list contains the names of all the features in the Feature table of the
MSI database for Chart Reader:

Feature name Description Also requires

i2CR Chart Reader main program ThirdParty

files

ThirdParty Non-IBM i2 system files See note below

OISCCPAutoTrackXP Online iLink source OnlineiLink

configuration files

OIHelp Optional Online iLink help OnlineiLink

files.

OISCDandB Online iLink source OnlineiLink

configuration files

OISCLN Online iLink source OnlineiLink

configuration files

OIThirdParty Online iLink source OnlineiLink

configuration files

70 IBM i2 Products Packaging & Deployment Guide

 Appendix C: IBM i2 Chart Reader

Third party merge modules

ThirdParty and OnlineiLink features are provided so that you can install the
Microsoft and other third-party merge modules separately, and then use the Chart
Reader installer

Chart Reader requires all of the merge modules that the ThirdParty feature installs,
as listed in the following table:

DLL version
Module name
number

Microsoft Common Dialog ActiveX Control DLL 6.1.97.82

MCI OLE Control DLL 6.0.84.18

Microsoft Common Controls 2 ActiveX Control DLL 6.1.98.12

Microsoft Flexgrid Control 6.0 6.1.98.11

Microsoft OLE 2.40 for Windows NT(TM) and Windows 2.40.4275.1,

95(TM) Operating Systems 5.0.4275.1

Microsoft Visual Basic Virtual Machine 6.0 6.0.97.82

MSXML 4.0 4.10.9404.0,

4.20.9818.0

VC User CRT71 RTL X86 7.10.3052.4

VC User MFC71 RTL X86 7.10.3077.0

VC User STL71 RTL X86 7.10.3077.0

Visual C++ 8.0 ATL (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 ATL.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 CRT (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 CRT.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC (x86) WinSXS MSM 8.0.50727.4053

IBM i2 Products Packaging & Deployment Guide 71

Product Features

DLL version
Module name
number

Visual C++ 9.0 ATL (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 CRT (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFC (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFCLOC (x86) WinSXS MSM 9.0.21022.8

stdole DLL 7.0.9466.0

i23rdPartyWoodBuryUnicodeToolbox 1.4.0.1, 1.3.0.1,

1.1.0.32

Windows Common Controls ActiveX Control DLL 6.1.97.86

Visual C++ 8.0 MFCLOC.Policy (x86) WinSXS MSM 8.0.50727.4053

To enable real-time access to IBM i2 Information Exchange Visualizer-enabled

data sources, Chart Reader also requires the merge modules that the OnlineiLink
feature installs:

DLL version
Module name
number

i23rdPartyCyberActiveX 1.0.0.258,
1.2.0.18,
1.0.0.51,
1.0.0.4,
1.0.0.96

i23rdPartyWoodBuryUnicodeFlexGrid 1.3.0.6,
2.0.0.0

i23rdPartyWoodBuryUnicodeToolbox 1.4.0.1,
1.3.0.1,
1.1.0.32

UniToolbox control suite

Chart Reader uses the UniToolbox components provided by Woodbury Associates
Ltd. These components are installed into their own folders in
Program Files\Woodbury Associates to avoid any incompatibility with other
products that use the same controls.

72 IBM i2 Products Packaging & Deployment Guide

 D
IBM i2 iBase

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
iBase 8.9.

For full instructions on how to use the features and functionality described here,
you should refer to Chapter 1, Packaging & Deploying IBM i2 Software
Distributions.

Contents
Introduction 74
Prerequisite Software 75
Public Properties 76
Customizable Files 77
Product Features 78
Patches and Transforms 83

IBM i2 Products Packaging & Deployment Guide 73

Introduction

Introduction A.26
This appendix contains information about the product-specific features of iBase 8
that can affect the way you deploy it. It describes:
• The prerequisite software that you must have installed before you can attempt
to install the product itself.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user's installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.
• Any product-specific patches and transforms that are shipped with this version
of the product.

Note: iBase 8 now includes the IBM i2 iBase Plate Analysis installer as a feature.

74 IBM i2 Products Packaging & Deployment Guide

 Appendix D: IBM i2 iBase

Prerequisite Software A.27

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of iBase, please refer to the release notes that are available on the installation
media.

Report Viewer
If you wish to use the code list history report functionality, then you need the
Microsoft Report Viewer 2005 libraries. You can download this from the Microsoft
website.

IBM i2 Products Packaging & Deployment Guide 75

Public Properties

Public Properties A.28

iBase 8 supports all the custom public properties described in the main part of the
guide. The following table lists the additional property that you can specify on the
Msiexec command line for this product:

Property name Description Default

DATABASEDIR The location of the C:\Documents and Settings\

iBase 8 Scheduler All Users\
database. Application Data\i2\
i2 iBase 8\en-US\
Scheduler\

76 IBM i2 Products Packaging & Deployment Guide

 Appendix D: IBM i2 iBase

Customizable Files A.29

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked directory structure containing all the files that will be copied to a
user's machine when they install the product. You can therefore customize an
installation by replacing some of the standard files with your own versions.

The following is a list of some of the files in an administrative installation of iBase 8

that you might want to replace:

File name Description

i2_default.apr Contains the default project file for the ArcView 3

interface.

i2_default.mxd Contains the default map document file for the

ArcGIS interface.

i2_default.wor Contains the default workspace file for the MapInfo

interface.

Iconlist.txt A list of the icons available for use in iBase 8.

IBM i2 Products Packaging & Deployment Guide 77

Product Features

Product Features A.30

During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties,
with the option /passive (/qb) or /quiet (/q) to request a passive or silent
installation.

Note: If an upgrade from iBase 8.0 or 8.1 is performed silently or with a basic UI, using
the /quiet, /q or /qb switches it is advisable to perform a manual MSI Repair
operation following the upgrade. If the manual repair is not performed, the
Windows Installer Self-Heal will be run on first use of iBase and will automatically
repair the installation.

The following list contains the names of all the features in the Feature table of the
MSI database for iBase 8, and the requirements of each feature:

Feature name Description Also requires

AdminCenter Documentation for

administrators of iBase

AdminCenterReplication Documentation for AdminCenter

administrators of iBase
Database Replication

ANPR Plate Analysis features iBase, ThirdParty

ANPRDocs Plate Analysis iBase, ThirdParty

documentation files

ANPRHelp Plate Analysis help files iBase, ThirdParty

ChartItemExtractor Extracts charts into iBase, ThirdParty

individual properties
allowing them to be stored
in iBase

Cyber IP/DNS resolution, iBase, ThirdParty

geo-location, and spam
blacklisting for iBase

DesignerExamples An example database to ThirdParty

use with iBase Designer

78 IBM i2 Products Packaging & Deployment Guide

 Appendix D: IBM i2 iBase

Feature name Description Also requires

DesignerHelp Help on using the Designer ThirdParty

dialogs

GIS Interfaces to GIS products iBase, ThirdParty

GISArcGIS Interface to ArcGIS iBase, GIS,

ThirdParty

GISArcView3 Interface to ArcView 3 iBase, GIS,

ThirdParty

GISBlue8World Interface to Blue8 World iBase, GIS,

ThirdParty

GISBlue8XD Interface to Blue8 XD iBase, GIS,

ThirdParty

GISHelp Mapping help files iBase, GIS,

ThirdParty

GISMapInfo Interface to MapInfo iBase, GIS,

ThirdParty

GISMapPoint Interface to MapPoint iBase, GIS,

ThirdParty

iBase Investigative database ThirdParty

iBaseCoordinateExt Enables multiple coordinate iBase, ThirdParty

systems in one database

iBaseDesigner Design and administer ThirdParty

iBase databases and
security files

iBaseReplication Use Microsoft SQL Server iBase, iBaseSSE,

merge replication to enable ThirdParty
distributed use of iBase

iBaseScheduler Schedule batch imports iBase, ThirdParty

and exports

iBaseSchedulerHelp iBase Scheduler Help files iBase, ThirdParty

iBaseSchedulerService Run scheduled tasks iBase,

iBaseScheduler,
ThirdParty

IBM i2 Products Packaging & Deployment Guide 79

Product Features

Feature name Description Also requires

iBaseSchemaUpdate Update database schemas iBase,

from a database template iBaseDesigner,
(requires Designer) ThirdParty

iBaseServer iBase Server components ThirdParty

for the search service

iBaseServerHelp iBase Indexing Server Help ThirdParty

files

iBaseSSE Store data in Microsoft SQL iBase, ThirdParty

Server databases

iBaseTools Includes Audit Viewer and iBase, ThirdParty

tools for maintaining iBase
databases

iBaseToolsHelp iBase Audit Viewer Help iBase, ThirdParty

files

iBaseUser Use the iBase application iBase, ThirdParty

UserDocs Quick Start Guide iBase, ThirdParty

UserExamples An example database to iBase, ThirdParty

use with iBase

UserHelp Help on using the iBase iBase, ThirdParty

dialogs

ThirdParty Microsoft and other third- See note below

party merge modules

You can install the Administration Center without installing the iBase 8 software, so
that you may read the documentation before installation. Alternatively, you can
access the documentation on the iBase 8 distribution CD, in the
Administration Center directory.

For example, to install the Administration Center only (without the iBase database
replication part):

> Msiexec /i "IBM i2 iBase 8.msi" ADDLOCAL= AdminCenter /q

To install iBase 8 including iBase Designer, and enable use with SQL Server:

> Msiexec /i "IBM i2 iBase 8.msi" ADDLOCAL=iBase,iBaseUser,

iBaseDesigner,iBaseSSE,ThirdParty /q

80 IBM i2 Products Packaging & Deployment Guide

 Appendix D: IBM i2 iBase

Third party merge modules

The ThirdParty feature is provided so that you can install the Microsoft and other
third-party modules separately, and then use the iBase 8 installer only to install the
IBM i2 files.

iBase 8 requires all of the merge modules that the ThirdParty feature installs, as
listed in the following table:

Module name DLL version number

CMDialog ActiveX Control DLL 6.1.97.82

Microsoft (R) C++ Runtime Library 6.0.8972.0

Microsoft ADO Data Control 6.0.88.4

Microsoft Common Controls 2 ActiveX Control DLL 6.1.98.12

Microsoft Common Controls 3 ActiveX Control DLL 6.7.0.8988

Microsoft Hierarchical FlexGrid Control 6.0.88.4

Microsoft Rich Textbox Control Librar y (version 6) 6.0.88.77

MSFlexGrid 6.1.98.11

MSXML 4.0 4.10.9404.0,

4.20.9818.0

VB Control mschart RTL X86 6.0.88.4

stdole 7.0.9466.0

VC User STL71 RTL X86 7.10.3077.0

Windows Common Controls ActiveX Control DLL 6.0.81.5

Windows Common Controls ActiveX Control DLL 6.1.97.86

Visual Basic Virtual Machine 6.0.97.82

Visual C++ 8.0 ATL (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 ATL.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 CRT (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 CRT.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC (x86) WinSXS MSM 8.0.50727.4053

IBM i2 Products Packaging & Deployment Guide 81

Product Features

Module name DLL version number

Visual C++ 8.0 MFC.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 OpenMP (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 9.0 ATL (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 ATL.Policy (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 CRT (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 CRT.Policy (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFC (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFC.Policy (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFCLOC (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFCLOC.Policy (x86) WinSXS 9.0.21022.8

MSM

Woodbury Associates Unicode Flexgrid Controls 1.3.06

2.0.0.0

Woodbury Associates Unicode UniBox Controls 1.4.0.1

1.3.0.1
1.1.0.32

82 IBM i2 Products Packaging & Deployment Guide

 Appendix D: IBM i2 iBase

Patches and Transforms A.31

The distribution of iBase 8 that this document accompanies contains no patch files
or transforms.

IBM i2 Products Packaging & Deployment Guide 83

Patches and Transforms

84 IBM i2 Products Packaging & Deployment Guide

 E
IBM i2 Text Chart

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
Text Chart 8.9.

For full instructions on how to use the features and functionality described here,
you should refer to Chapter 1, Packaging & Deploying IBM i2 Software
Distributions.

Contents
Introduction 86
Prerequisite Software 87
Public Properties 88
Customizable Files 89
Product Features 90
Patches and Transforms 92

IBM i2 Products Packaging & Deployment Guide 85

Introduction

Introduction A.32
This appendix contains information about the product-specific features of
Text Chart 8.9 that can affect the way you deploy it. It describes:
• The prerequisite software that you must have installed before you can attempt
to install the product itself.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user's installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.
• Any product-specific patches and transforms that are shipped with this version
of the product.

86 IBM i2 Products Packaging & Deployment Guide

 Appendix E: IBM i2 Text Chart

Prerequisite Software A.33

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of Text Chart, please refer to the release notes that are available on the installation
media.

IBM i2 Products Packaging & Deployment Guide 87

Public Properties

Public Properties A.34

Text Chart supports all the custom public properties described in the main part of
the guide. The following table lists the additional properties that you can specify on
the Msiexec command line for this product:

Property name Description

I2_USERNAME The username of an account with extended

rights that can be used to run the Auto Mark
services.

I2_PASSWORD The password of an account with extended

rights that can be used to run the Auto Mark
services.

Note: If you are a Windows 7 or Windows user, you will need to configure a specific local
user account with Administrative privileges and have the Log on as a Service
security right

88 IBM i2 Products Packaging & Deployment Guide

 Appendix E: IBM i2 Text Chart

Customizable Files A.35

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked directory structure containing all the files that will be copied to a
user's machine when they install the product. You can therefore customize an
installation by replacing some of the standard files with your own versions.

The distribution of Text Chart that this document accompanies has no files that you
can customize in this way.

IBM i2 Products Packaging & Deployment Guide 89

Product Features

Product Features A.36

During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties.

The following list contains the names of all the features in the Feature table of the
MSI database for Text Chart:

Feature Description Also Requires

i2TextChart Main Text Chart 8 ThirdParty

components.

ThirdParty Microsoft and other third- See note below

party merge modules,

i2TextChartDesigner Text Chart 8 Designer i2TextChart, ThirdParty

iBaseLive iBase Live i2TextChart, ThirdParty

AutoMark Enables features of Text i2TextChart, ThirdParty

Chart Auto Mark on an
English locale.
See Patches and
Transforms on page 92,
for more information.

Help Help files i2TextChart, ThirdParty

Docs Documentation files i2TextChart, ThirdParty

Examples Example Text Chart files i2TextChart, ThirdParty

Third party merge modules

The ThirdParty feature is provided so that you can install the Microsoft and third-
party merge modules separately, and then use the Text Chart installer to install
only the IBM i2 files.

90 IBM i2 Products Packaging & Deployment Guide

 Appendix E: IBM i2 Text Chart

Text Chart requires all of the merge modules that the ThirdParty feature installs, as
listed in the following table:

Module name DLL version numbers

Microsoft (R) C++ Runtime Library 6.0.8972.0

MSXML 4.0 4.10.9404.0,

4.20.9818.0

VC User CRT71 RTL X86 7.10.3052.4

VC User MFC71 RTL X86 7.10.3077.0

VC User STL71 RTL X86 7.10.3077.0

Visual Basic Virtual Machine 6.0.97.82

Visual C++ 8.0 CRT (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 9.0 CRT (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 CRT.Policy (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFC.Policy (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFC (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFCLOC (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 MFCLOC.Policy (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 ATL (x86) WinSXS MSM 9.0.21022.8

Visual C++ 9.0 ATL.Policy (x86) WinSXS MSM 9.0.21022.8

IBM i2 Products Packaging & Deployment Guide 91

Patches and Transforms

Patches and Transforms A.37

The distribution of Text Chart that this document accompanies contains no patch
files or transforms.

The Auto Mark feature is not usually available by default on a machine running in a
non-English locale. If you would like to install the Auto Mark feature on a non-
English locale then please contact IBM Support. For information about how to
contact IBM Support, see Contacting IBM Support on page 8.

92 IBM i2 Products Packaging & Deployment Guide

 F
IBM i2 iBridge

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
iBridge.

For full instructions on how to use the features and functionality described here,
you should refer to Chapter 1, Packaging & Deploying IBM i2 Software
Distributions.

Contents
Introduction 94
Prerequisite Software 95
Public Properties 96
Customizable Files 97
Product Features 98
Patches and Transforms 100

IBM i2 Products Packaging & Deployment Guide 93

Introduction

Introduction A.38
This appendix contains information about the product-specific features of iBridge
that can affect the way you deploy it. It describes:
• The Installation Manager that manages the installation of the products in the
bundle.
• The prerequisite software that you must have installed before you can attempt
to install the product itself.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user's installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.
• Any product-specific patches and transforms that are shipped with this version
of the product.

94 IBM i2 Products Packaging & Deployment Guide

 Appendix F: IBM i2 iBridge

Prerequisite Software A.39

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of iBridge, please refer to the release notes that are available on the installation
media.

Analyst’s Notebook 8.9.1

Analyst’s Notebook 8.9.1, or later must be installed before installing iBridge.

Internet Explorer 6
iBridge needs Microsoft Internet Explorer version 6 Service Pack 1 (or later). You
must install an appropriate version of Internet Explorer before installing iBridge.
Internet Explorer is included on the distribution CD, in the Pre-requisites\ IE
6 SP1 directory. Alternatively, you can download the latest version from the
Microsoft website.

MDAC
iBridge needs the Microsoft MDAC libraries version 2.6 (or later). On Windows
2000 systems, you must install an appropriate version of the MDAC libraries before
installing iBridge. MDAC 2.8 SP1 is included in the distribution package, in the
Pre-requisites\MDAC directory. Alternatively, you can download the latest
version from the Microsoft website.

MSXML 6.0
iBridge needs the Microsoft Core XML Services (MSXML) 6.0 libraries. On
systems earlier than Windows , you must install an appropriate version of these
libraries before installing iBridge. Microsoft Core XML Services (MSXML) 6.0 is
included on the distribution CD, in the Pre-requisites\MSXML 6.0 directory.
Alternatively, you can download the latest version from the Microsoft website.

IBM i2 Products Packaging & Deployment Guide 95

Public Properties

Public Properties A.40

iBridge 8 supports all the custom public properties described in the main part of
the guide. The distribution of iBridge 8 that this document accompanies has no
additional public properties.

96 IBM i2 Products Packaging & Deployment Guide

 Appendix F: IBM i2 iBridge

Customizable Files 1.41

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked directory structure containing all the files that will be copied to a
user's machine when they install the product. You can therefore customize an
installation by replacing some of the standard files with your own versions.

There are no specific files which may be customized.

IBM i2 Products Packaging & Deployment Guide 97

Product Features

Product Features A.42

During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties,
with the option /passive (/qb) or /quiet (/q) to request a passive or silent
installation.

The following list contains the names of all the features in the Feature table of the
MSI database for iBridge 8:

Feature name Description Also requires

i2iBridge Main iBridge 8 ThirdParty

components.

ThirdParty Microsoft and other third- See note below

party merge modules.

Help Help about using the ThirdParty

dialogs.

Examples User Guide example ThirdParty

materials.

i2iBridgeDesigner iBridge Designer ThirdParty

components.

DesignerHelp Designer Help about ThirdParty

configuration.

DesignerDocs Designer Guide for ThirdParty

Access, Oracle and SQL
Server databases.

DesignerExamples Designer Guide example ThirdParty

materials.

Third party merge modules

The ThirdParty feature is provided so that you can install the Microsoft and other
third-party merge modules separately, and then use the iBridge 8 installer only to
install the IBM i2 files.

98 IBM i2 Products Packaging & Deployment Guide

 Appendix F: IBM i2 iBridge

iBridge 8 requires all of the merge modules that the ThirdParty feature installs, as
listed in the following table:

Module name DLL version

numbers
CMDialog ActiveX Control DLL 6.1.97.82

MCI OLE Control DLL 6.0.84.18

Microsoft (R) C++ Runtime Library 6.0.8972.0

Microsoft Common Controls 2 ActiveX Control DLL 6.1.97.82

Microsoft Common Controls 3 ActiveX Control DLL 6.7.0.9782

Microsoft Hierarchical FlexGrid Control 6.0.88.4

Microsoft Rich Textbox Control Library (version 6) 6.0.88.77

Microsoft Standard Data Formatting Object DLL 6.1.97.82

MSFlexGrid 6.1.97.82

MSXML 4.0 4.10.9404.0,

4.20.9818.0

TABCTL32 OLE Control DLL 6.1.97.82

Windows Common Controls ActiveX Control DLL 6.1.97.82

Visual C++ 8.0 MFC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFC.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC (x86) WinSXS MSM 8.0.50727.4053

Visual C++ 8.0 MFCLOC.Policy (x86) WinSXS MSM 8.0.50727.4053

Visual Basic Virtual Machine 6.0.89.64

i23rdPartyWoodBuryUnicodeFlexGrid 1.3.0.6
2.0.0.0

i23rdPartyWoodBuryUnicodeToolbox 1.4.0.1
1.3.0.1
1.1.0.32

IBM i2 Products Packaging & Deployment Guide 99

Patches and Transforms

Patches and Transforms A.43

The distribution of iBridge 8 that this document accompanies contains no patch
files or transforms.

100 IBM i2 Products Packaging & Deployment Guide

 G
IBM i2 Analyst’s Notebook
Connector for Esri

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
Analyst’s Notebook Connector for Esri.

For full instructions on how to use the features and functionality described here,
you should refer to the main part of the guide.

Contents
Introduction 102
Prerequisite Software 103
Customizable Files 105
Product Features 106
Patches and Transforms 107

IBM i2 Products Packaging & Deployment Guide 101

Introduction

Introduction A.44
This appendix contains information about the product-specific features of IBM i2
Analyst’s Notebook Connector for Esri that can affect the way you deploy it. It
describes:
• The prerequisite software that you must have installed before you can attempt
to install the product itself.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user's installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.
• Any product-specific patches and transforms that are shipped with this version
of the product.

102 IBM i2 Products Packaging & Deployment Guide

 Appendix G: IBM i2 Analyst’s Notebook Connector for Esri

Prerequisite Software A.45

All IBM i2 products require version 2.0 SP1, or version 3.5 of the .NET Framework,
which the main part of the guide explains how to install. For the other prerequisites
of Analyst's Notebook, please refer to the release notes that are available on the
installation media.

IBM i2 Products Packaging & Deployment Guide 103

Public Properties

Public Properties A.46

Analyst’s Notebook 8.9.1 or above is required to install Analyst’s Notebook
Connector for Esri.

Analyst’s Notebook Connector for Esri supports all the custom public properties
described in the main part of the guide.

104 IBM i2 Products Packaging & Deployment Guide

 Appendix G: IBM i2 Analyst’s Notebook Connector for Esri

Customizable Files A.47

When you perform an administrative installation of an IBM i2 product, the result is
an unpacked folder structure containing all the files that will be copied to a user’s
machine when they install the product. You can therefore customize an installation
by replacing some of the standard files with your own versions.

The following is a list of the files in an administrative installation of Analyst’s

Notebook Connector for Esri that you might want to replace:

File name Description

ServerEndpoints.config This file should be configured for the

Esri servers on the network. The file
provided refers to demonstration
servers which may not exist. Refer to
product documentation for details on
configuring these servers.

Note: You must make sure that the coordinate systems of the maps on your Esri server
are also present in the user’s CoordinateSystemWkts file.

For more information about coordinate systems and configuring server endpoints,
see the IBM i2 Analyst’s Notebook Esri Connector Configuration Guide.

IBM i2 Products Packaging & Deployment Guide 105

Product Features

Product Features A.48

During a GUI-based installation, the Destination Folder page of the InstallShield
wizard allows you to change the location of the main Analyst’s Notebook
Connector for Esri components.

The following list contains the name of the feature in the Feature table of the MSI
database for Analyst’s Notebook Connector for Esri:

Feature name Description Also requires

EsriMapping Main Analyst’s Notebook

Connector for Esri
components.

Help Optional online help EsriMapping

Third party merge modules

Analyst’s Notebook Connector for Esri uses no third party merge modules.

106 IBM i2 Products Packaging & Deployment Guide

 Appendix G: IBM i2 Analyst’s Notebook Connector for Esri

Patches and Transforms 1.49

The distribution of Analyst’s Notebook Connector for Esri that this document
accompanies contains no patch files or transforms.

IBM i2 Products Packaging & Deployment Guide 107

Product Features

108 IBM i2 Products Packaging & Deployment Guide

 H
IBM i2 iBase Retained Data
Handover Interface

This appendix contains information about the considerations you should make,
and the options available to you, when you deploy, install, and maintain IBM® i2®
iBase Retained Data Handover Interface.

For full instructions on how to use the features and functionality described here,
you should refer to the main part of the guide.

Contents
Introduction 110
Prerequisite Software 111
Public Properties 112
Customizable Files 113
Product Features 114
Patches and Transforms 115

IBM i2 Products Packaging & Deployment Guide 109

Introduction

Introduction
This appendix contains information about the product-specific features of IBM i2
iBase Retained Data Handover Interface that can affect the way you deploy it. It
describes:
• The prerequisite software that you must have installed before you can attempt
to install the product itself.
• The custom public properties that you can specify on the Msiexec command
line in order to change the behavior of the installed product.
• The files created during an administrative installation that you might replace in
order to customize a user's installation.
• The features of the product that you can choose to add or remove during
installation, or during modification of the installed product.
• Any product-specific patches and transforms that are shipped with this version
of the product.

110 IBM i2 Products Packaging & Deployment Guide

 Appendix H: IBM i2 iBase Retained Data Handover Interface

Prerequisite Software
iBase 8.9 or later must have been installed before installing IBM i2 RDHI

IBM i2 Products Packaging & Deployment Guide 111

Public Properties

Public Properties
IBM i2 RDHI supports none of the custom public properties described in the main
part of the guide.

The application is installed as an iBase plug-in and the files are installed in the
location selected when iBase itself was installed.

The distribution that this document accompanies has no additional public

properties

112 IBM i2 Products Packaging & Deployment Guide

 Appendix H: IBM i2 iBase Retained Data Handover Interface

Customizable Files
When you perform an administrative installation of an IBM product, the result is an
unpacked directory structure containing all the files that will be copied to a user's
machine when they install the product. You can therefore customize an installation
by replacing some of the standard files with your own versions.

There are no specific files which may be customized.

IBM i2 Products Packaging & Deployment Guide 113

Product Features

Product Features
During a GUI-based installation, the Custom Setup page of the InstallShield wizard
allows you to add and remove optional features to and from the installed product.
As the main part of the guide explains, you can do the same thing from the
Msiexec command line by using the REMOVE and ADDLOCAL public properties.

The following list contains the names of all the features in the Feature table of the
MSI database for IBM i2 RDHI:

Feature name Description Also requires

iBaseRDHI Retained Data Handling Interface

(RDHI) Importer for iBase.

Help iBase RDHI Importer help files iBaseRDHI

Third party merge modules

IBM i2 RDHI uses no third party merge modules.

114 IBM i2 Products Packaging & Deployment Guide

 Appendix H: IBM i2 iBase Retained Data Handover Interface

Patches and Transforms

The distribution of IBM i2 RDHI that this document accompanies contains no patch
files of transforms.

IBM i2 Products Packaging & Deployment Guide 115

Patches and Transforms

116 IBM i2 Products Packaging & Deployment Guide

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk,
NY 10504-1785U.S.A.

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express
or implied warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements and/
or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.

IBM i2 Products Packaging & Deployment Guide 117

Notices

Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:

IBM United Kingdom Limited

Hursley House
Hursley Park
Winchester,
Hants,
SO21 2JNUK

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-
level systems and there is no guarantee that these measurements will be the same
on generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM
has not tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

118 IBM i2 Products Packaging & Deployment Guide

 Notices

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual
business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations
may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.

Other names may be trademarks of their respective owners. Other company,

product, and service names may be trademarks or service marks of others.

IBM i2 Products Packaging & Deployment Guide 119

Notices

120 IBM i2 Products Packaging & Deployment Guide

Index

Symbols customizable files 47

product features 48
third party merge modules 49
.msi public properties 46
invalid 14 Analyst’s Notebook Connector for Esri
modifying 27 customizable files 105
software distributions 13 patches 107
upgrading 35 prerequisites 103
.msp product features 106
IBM i2 software distributions 13 public properties 104
running patches 36 Analyst’s Workstation product bundle 53, 55
.mst
creating transforms 28
IBM i2 software distributions 13 C
transforming from the command line 30
.NET Framework Cache
installing 12 installation 19
requirement 12
Certicates and signing 14
Chart Reader 65
A customizable files 69
prerequisites 67
product features 70
Administrative installations 25 third party merge modules 71
customizing 26 public properties 68
Advantages Command line
MSI 12 modifying IBM i2 installations from 34
repairing damage from 33
Advertising installations 27
transforming installations 30
Analyst’s Notebook 43, 101 uninstalling patches 38

IBM i2 Products Packaging & Deployment Guide 121

Index

Custom public properties 24

I
Customizable files
Analyst’s Notebook 47
iBase 73
Analyst’s Notebook Connector for Esri 105
Chart Reader 69 customizable files 77
Data Miner 59 patches 52, 83
iBase 77 prerequisite software 75
iBridge 97 prerequisites 75
Text Chart 89 product features 78
third party merge modules 81
Customizing administrative installations 26 public properties 76
transforms 52, 83
IBM i2 custom public properties 24
D INSTALLDIR 24
IBM i2 installation
Data Miner maintaining 32
customizable files 59 modifying 33
patches 63 from the command line 34
product features 60 repairing damaged 32
public properties 57 from command line 33
transforms 63 user-initiated 32
uninstalling 37
Deployment
custom IBM i2 installers, digitally signed 14
Msiexec 21 IBM i2 product-specific requirements 12
packages
PDF 13 IBM i2 software distributions
files
Digital certificate 14
.msp 13
i2 installers .mst 13
User Account Control checks 14 location of installed files 19
IBM i2 installers 14 MSI 13
PDF 13
Setup.exe 13
F Update.exe 13
iBridge
Framework customizable files 97
patches 100
.NET 12
prerequisites 95
product features 98
third party merge modules 98
public properties 96
transforms 100

122 IBM i2 Products Packaging & Deployment Guide

 Index

Installation advantages 12
administrative 25 invalid 14
customizing 26 modifying 27
advertising 27 requirements 12
cache 19 upgrading 35
location of installed files 19 Msiexec 16
maintaining IBM i2 32
custom deployment 21
Installation Manager double-click installation 21
Running 16 modifying from the command line 34
patching with MSP file 36
INSTALLDIR Setup.exe reliance on 16
Custom public properties upgrading with an MSI file 35
INSTALLDIR 24
Installing
.Net Framework 12 O
with Setup.exe 16
Invalid .msi files 14 Orca
creating transforms 28

L
P
Location of installed files 19
Patches
.msp files 13
M Analyst’s Notebook Connector for Esri 107
iBridge 100
running
Maintaining IBM i2 installations 32 with MSP file 36
Merge modules with Setup.exe 35
with Update.exe 35
third party
Analyst’s Notebook 49 PDF
Chart Reader 71 Portable Definition file
Data Miner 61 deployment packages 13
iBase 81
iBridge 98 Prerequisites
Text Chart 90 Analyst’s Notebook 45
Analyst’s Notebook Connector for Esri 103
Modifying Analyst’s Workstation 56
.msi files 27 Chart Reader 67
IBM i2 installations 33 Data Miner 56
MSI iBase 75
IBM i2 product-specific 12

IBM i2 Products Packaging & Deployment Guide 123

Index

iBridge 95 installing with 16

MSI 12 Msiexec
.NET Framework 12 reliance on 16
Text Chart 87 patching with 35
running patches 35
Product bundles
Analyst’s Workstation 55 System Event Log
Troubleshooting 39
Product Definition File (PDF) 13
Product features
Analyst’s Notebook 48
Analyst’s Notebook Connector for Esri 106
T
Chart Reader 70
Data Miner 60 Terminal Server
iBase 78 troubleshooting 41
iBridge 98
Text Chart 90 Text Chart
customizable files 89
Public properties
prerequisite software 87
Analyst’s Notebook 46 product features
Analyst’s Notebook Connector for Esri 104 third party merge modules 90
Chart Reader 68 public properties 88
Data Miner 57
iBase 76 Third party merge modules
iBridge 96 Analyst’s Notebook 49
Text Chart 88 Chart Reader 71
Data Miner 61
iBase 81
iBridge 98
R Text Chart 90
Transforms
Repairing damaged IBM i2 installation 32 .mst files 13
from the command line 33 creating with Orca 28
user-initiated 32 iBridge 100
Requirements transforming from the command line 30
IBM i2 product-specific 12 Troubleshooting 39
MSI 12 System Event Log 39
.NET Framework 12 Terminal Server 41
verbose log
enabling 40
S understanding 40

Setup.exe
IBM i2 software distributions 13

124 IBM i2 Products Packaging & Deployment Guide

 Index

U
Uninstalling
IBM i2 installations 37
patches from command line 38
Update.exe
IBM i2 software distributions 13
patching with 35
running patches 35
Upgrading
running
with MSI file 35
User Account Control checks
Windows Vista 14

V
Verbose log
enabling 40
understanding 40

W
Windows Vista
User Account Control checks 14

IBM i2 Products Packaging & Deployment Guide 125

Index

126 IBM i2 Products Packaging & Deployment Guide