The Optim™ server environment includes the required components for computers that will manage run time operations.
Installing IBM InfoSphere Optim Manager
Installing IBM InfoSphere Optim Proxy
Using IBM Installation Manager to install the IBM Optim Server components
To install IBM InfoSphere Optim Test Data Management Solution, first use the Optim Repository launchpad to install the repository, and then use the Optim Client and Optim Server launchpads to complete the installation.
IBM InfoSphere Optim Test Data Management Solution requires an installation of IBM InfoSphere Optim Manager and IBM InfoSphere Optim Proxy:
To install IBM InfoSphere Optim Solutions, use the IBM InfoSphere Optim installer.
For the most up to date IBM InfoSphere Optim system requirements, see the technote on the Web: http://www.ibm.com/support/docview.wss?uid=swg27024294.
IBM InfoSphere Optim Manager (manager) is a web application that you can use to configure, run, monitor, and manage services. You also use manager to configure the components that are used to run these services. Optim Manager is also known as the manager. The Optim Manager functions are also available from a public web services interface, Optim Service Interface.
The Optim Manager components can be installed on supported Linux, UNIX, and Windows platforms.
Running the repository during installation is recommended, as the installation process can configure the repository location for the Optim Manager. You can also configure the repository location after installation.
To install the Optim Manager components, use IBM Installation Manager.
The following components must be installed on an Optim Manager computer:
Optim Manager is a web application that is used to run and monitor Optim data management services. Use this version of Optim Manager only with the same version of other Optim solution components.
The Optim Manager functions are also available from a public web services interface, Optim Service Interface. Optim Service Interface is based on RESTful Web services and is an optional component that can be used in place of Optim Manager.
Optim Manager and Optim Service Interface require an installation of a J2EE application server, such as IBM WebSphere Application Server Community Edition (WAS-CE).
The Optim Manager installation copies two Web Archive (WAR) files to the computer: optim.war (for Optim Manager) and optim-service-interface.war (for Optim Web Service Interface).
IBM WebSphere Application Server Community Edition (WAS-CE) is a lightweight J2EE application server. It is based upon Apache Geronimo technology developed by the Apache Software Foundation. If you plan on using WAS-CE as your application server, install only this instance of WAS-CE on this machine. This version of WAS-CE is optimized for use with the version of Optim solution components that is delivered with this version of WAS-CE.
WAS-CE is not available for HP platforms.
InfoSphere Optim Repository Services is the client software for the InfoSphere Optim Repository Server database. InfoSphere Optim Repository Services is required for IBM InfoSphere Optim components to connect to InfoSphere Optim Repository Server. InfoSphere Optim Repository Services is an IBM Informix® client. Before you install InfoSphere Optim Repository Services, uninstall any Informix® client software that is on the computer.
The Optim Proxy components can be installed on supported Linux, UNIX, and Windows platforms.
Running the repository during installation is recommended, as the installation process can configure the repository location for the Optim Proxy. You can also configure the repository location after installation.
To install Optim Proxy and Optim Repository Services, use IBM Installation Manager.
To install IBM InfoSphere Optim Solutions, use the IBM InfoSphere Optim installer.
The following components must be installed on an Optim Proxy computer:
Optim Proxy is a distributed process that executes data management services on Manager. For fastest processing, install the Optim Proxy on the same machine as the data source or on a computer with a fast connection to the data source. Use this version of Optim Proxy only with the same version of other Optim solution components.
The Optim Proxy computer requires an installation of IBM InfoSphere Optim.
InfoSphere Optim Repository Services is the client software for the InfoSphere Optim Repository Server database. InfoSphere Optim Repository Services is required for IBM InfoSphere Optim components to connect to InfoSphere Optim Repository Server. InfoSphere Optim Repository Services is an IBM Informix® client. Before you install InfoSphere Optim Repository Services, uninstall any Informix client software that is on the computer.
The IBM InfoSphere Optim solutions manage enterprise data throughout every stage of the information lifecycle, enabling your company to assess, classify, subset, archive, store, and access enterprise application data.
Use the Installation Manager product to install, update, and uninstall the Optim Server components.
For information about configuring and using the Optim Manager environment, refer to the documentation location on the installation disc.
The installation roadmap lists the high-level steps for installing the IBM Optim Server components.
This roadmap describes a typical installation using the Installation Manager Install wizard. If you are installing the product silently, see the Silent installation road maps.
The typical silent installation path is to use the Installation Manager installer to install Installation Manager, and then to use Installation Manager to record a response file, then to silently install software packages. Optionally, you can use the Installation Manager installer to install Installation Manager and software packages at the same time. When you install in silent mode, the user interface is not available; instead, a response file inputs the commands that are required to install the software packages.
This section contains instructions for installing, updating, and uninstalling your product package.
Understanding these terms and conventions can help you take full advantage of the installation information and your product.
These terms are used in the installation topics.
The installation documentation uses conventions such as Shared resources directory that infer specific directory locations. This topic describes the conventions in use for this product and the associated default value.
Name | Convention in installation documentation | Default Value |
---|---|---|
Installation Manager installation directory | Installation Manager directory |
|
Installation Manager shared resources directory | Shared resources directory |
|
Product installation directory | Product directory |
|
Product workspace directory | workspace directory |
|
Read all of the following topics before you begin to install or update any of the product features. Effective planning and an understanding of the key aspects of the installation process can help ensure a successful installation.
IBM Installation Manager is a program for installing, updating, and modifying packages. It helps you manage the IBM applications, or packages, that it installs on your computer. Installation Manager does more than install packages: It helps you keep track of what you have installed, determine what is available for you to install, and organize installation directories.
Installation Manager provides tools that help you keep packages up to date, modify the packages, manage the licenses for your packages if required, and uninstall the packages from your system.
Version 1.5.2 of Installation Manager is included with the product. All instructions in this Installation Guide assume that you are using the included version of Installation Manager. If you upgrade later to a higher version of Installation Manager, some of the instructions might not be accurate. The Installation Manager information center is on the Web at: http://pic.dhe.ibm.com/infocenter/install/v1r5/index.jsp
IBM Installation Manager is the tool that you use to install your software packages. It is installed automatically when you start the installation for your product offering.
The latest version of Installation Manager might be required for your package. Updates are discovered if you have not cleared the Search service repositories for updates check box on Repositories page in the Preferences window of Installation Manager.
If you start the installation of the product from the launchpad, IBM Installation Manager automatically starts even if it is not already installed.
Installation requires the correct hardware, operating system, software, and other factors.
Before you can install the product, verify that your hardware and software meet or exceed the minimum requirements. If your hardware and software do not meet the minimum requirements, you might be unable to install or run the product.
For the most up to date IBM InfoSphere Optim system requirements, see the technote on the Web: http://www.ibm.com/support/docview.wss?uid=swg27024294.
You must have a user ID that meets specific requirements before you can install your product.
Your user ID must not contain double-byte characters.
There are two methods of installation: administrative and non-administrative. For information about how to choose between these two options, see the topic: Installation terminology
User ID authority | Case where you install as Non-administrative | Case where you install as Administrative |
---|---|---|
Non-administrative (current user) |
|
|
Administrative | An error message occurs. |
|
If you use a Linux or Unix operating system, then you must check that your computer meets the requirements listed in this topic.
You might need to set the environment variable MOZILLA_FIVE_HOME to the folder containing your Firefox or Mozilla installation. For example, setenv MOZILLA_FIVE_HOME /usr/lib/firefox-1.5.
To support the SWT browser widget, your Firefox browser must be dynamically linked, which means it was not downloaded from mozilla.org, but was compiled from source. This is typically the case when the Firefox comes as part of the distribution (that is, it is in a place such as /usr/lib/firefox).
One way to ensure that this is true is to see if it is the browser that is pointed at by /etc/gre.conf. The purpose of this gre.conf file is to point at an embeddable browser.
If your operating system is SUSE Linux Enterprise Desktop 10 SP1 or SUSE Linux Enterprise Server 10 SP1, then you might need the following operating system update to resolve a problem with text not being displayed in some editors:http://support.novell.com/techcenter/psdb/44ab155e3202595389c101e6cf7e20f2.html.
You can customize your software product by selecting which features to install.
The following tables show the features of the product that you can install for each package. Default selections of features to install might vary. If a feature already exists in your shared resources directory, it will not be selected by default and will not be installed again.
Feature | Description |
---|---|
Optim Manager WAR File | The Optim Manager WAR file provides a web-based GUI that is used to run and monitor Optim data management services. After installation, deploy the Optim Manager WAR file to your preferred application server, such as IBM WebSphere Application Server Community Edition (WAS-CE). |
Optim Service Interface WAR File | The Optim Service Interface WAR file provides an API that is used to run and monitor Optim data management services. After installation, deploy the Optim Service Interface WAR file to your preferred application server, such as IBM WebSphere Application Server Community Edition (WAS-CE). |
Optim Designer and Optim Manager Documentation | All of the available Optim Designer and Optim Manager Documentation in PDF format. |
Command-line application for the service interface | A Java-based command-line application that can be used to submit requests to the services interface. The service interface must be deployed to an application server before you can use this application. |
Feature | Description |
---|---|
Optim Proxy | The Optim Proxy is a distributed process that executes data management services on Manager. For fastest processing, install the Optim Proxy on the same machine as the data source or on a computer with a fast connection to the data source. Use this version of Optim Proxy only with the same version of other Optim solution components. |
Feature | Description |
---|---|
IBM WebSphere Application Server Community Edition (WAS-CE) | IBM WebSphere Application Server Community Edition (WAS-CE) is a lightweight J2EE application server. It is based upon Apache Geronimo technology developed by the Apache Software Foundation. If you plan on using WAS-CE as your application server, install only this instance of WAS-CE on this machine. This version of WAS-CE is optimized for use with the version of Optim solution components that is delivered with this version of WAS-CE. |
Feature | Description |
---|---|
Optim Repository Client | Installs the files to access an Optim Repository on a remote machine or virtual machine running locally. This option is required on any machine where Optim is installed. |
Part of planning entails making decisions about things such as installation locations, working with other applications, or extending Eclipse. This information helps you with these decisions.
IBM Installation Manager uses two directories when installing product artifacts.
The shared resources directory is where some product resources are installed so that they can be used by multiple product package groups. You define the shared resources directory the first time that you install IBM Installation Manager. For best results, use your largest disk drive for shared resources directories. You cannot change the directory location unless you uninstall Installation Manager.
Optim Server includes several installation packages.
The following installation packages are available.
IBM WebSphere Application Server Community Edition (WAS-CE) is a lightweight J2EE application server. It is based upon Apache Geronimo technology developed by the Apache Software Foundation. If you plan on using WAS-CE as your application server, install only this instance of WAS-CE on this machine. This version of WAS-CE is optimized for use with the version of Optim solution components that is delivered with this version of WAS-CE.
WAS-CE is not available for HP platforms.
Optim Manager is a web application that is used to run and monitor Optim data management services. Use this version of Optim Manager only with the same version of other Optim solution components.
The Optim Manager functions are also available from a public web services interface, Optim Service Interface. Optim Service Interface is based on RESTful Web services and is an optional component that can be used in place of Optim Manager.
Optim Manager and Optim Service Interface require an installation of a J2EE application server, such as IBM WebSphere Application Server Community Edition (WAS-CE).
The Optim Manager installation copies two Web Archive (WAR) files to the computer: optim.war (for Optim Manager) and optim-service-interface.war (for Optim Web Service Interface).
Optim Proxy is a distributed process that executes data management services on Manager. For fastest processing, install the Optim Proxy on the same machine as the data source or on a computer with a fast connection to the data source. Use this version of Optim Proxy only with the same version of other Optim solution components.
The Optim Proxy computer requires an installation of IBM InfoSphere Optim.
InfoSphere Optim Repository Services is the client software for the InfoSphere Optim Repository Server database. InfoSphere Optim Repository Services is required for IBM InfoSphere Optim components to connect to InfoSphere Optim Repository Server. InfoSphere Optim Repository Services is an IBM Informix® client. Before you install InfoSphere Optim Repository Services, uninstall any Informix client software that is on the computer.
Coexistence refers to the installed products on the same computer.
You can install multiple compatible packages into the same package group. This is sometimes also referred to as "shell sharing".
When you install each product package, you select whether you want to install the product package into an existing package group or whether you want to create a new package group. IBM Installation Manager offers only products that are designed to share a package group and meet version compatibility and other requirements. If you want to install more than one product at a time, the products must be able to share a package group.
The Optim components can be installed at the same time.
Any number of eligible products can be installed to a package group. When a product is installed, the product functions are shared with all of the other products in the package group. If you install a development product and a testing product into one package group, when you start either of the products, you have both the development and testing functions available to you in your user interface. If you add a product with modeling tools, all of the products in the package group will have the development, testing, and modeling functions available.
The Optim version 9.1.0 components cannot exist on the same system as previous versions of the Optim components.
Before you install, you might need to prepare or configure your computer.
Review the following information and ensure the pre-installation steps are completed as required.
If you download the installation files from IBM Passport Advantage, you must extract the electronic image from the compressed files before you can install the software.
If you select the Download Director option for downloading the installation files, the Download Director applet automatically verifies the completeness of each file that it processes.
With some operating systems, such as Linux or Unix, you must mount the appropriate drive before you can access data on the product disc.
A repository is a location for storing installation or update package data. By default, IBM Installation Manager uses an embedded URL in each product package to connect to a repository server through the Internet and search for available installation packages and new features. You can set these repository locations on the Repositories page in the Preferences window.
This task is only necessary to complete if you are installing from a repository other than the default repository on the Internet or the product media. For example, your organization might require you to redirect the repository to use intranet sites.
The repository is located in the /repo directory on the installation disc.
To specify a repository, complete the following steps:To install your product package, follow the procedures and information in these topics.
This topic provides the instructions for installing Optim Server with the Installation Manager Install wizard.
This information describes how to start the product package installation for a typical installation. You typically install the product package using the installation launchpad and the Installation Manager Install wizard. For information about how to install the product package silently, see the silent installation information.
The launchpad includes options to perform either an administrative or a non-administrative installation.
To install IBM InfoSphere Optim Server with the Installation Manager Install wizard:You can install a product package silently by using either Installation Manager in silent installation mode or by using the Installation Manager installer. When you run Installation Manager in silent mode, the user interface is not available; instead, a response file inputs the commands that are required to install the product package.
The typical silent installation path is to use the Installation Manager installer to install Installation Manager, and then to use Installation Manager to record a response file, then to silently install software packages. Optionally, you can use the Installation Manager installer to install Installation Manager and software packages at the same time. When you install in silent mode, the user interface is not available; instead, a response file inputs the commands that are required to install the software packages.
The Installation Manager installer is the tool used to install Installation Manager silently. It can also be used to install packages.
The Installation Manager installer is a command-line utility. Run the Installation Manager installer to silently install and uninstall Installation Manager. You can also install software packages using the Installation Manager installer.
If you do not already have Installation Manager installed on your computer, you might choose to use the Installation Manager installer to install both Installation Manager and packages together using a single command. This sample response file provides an example for installing Installation Manager and a software package. If you already have Installation Manager installed on your computer, you can simply use Installation Manager to install packages .
Use the Installation Manager installer to install Installation Manager silently.
The Installation Manager installer is used to install the Installation Manager. You can install the Installation Manager as an administrator, or in non-administrator modes. Follow the example below to install Installation Manager.
You can change the default location for installing Installation Manager by modifying the install.xml response file.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean='true' temporary='true'>
<!-- add a profile and specify the installation location using the data value attribute. The location must end in \eclipse -->
<profile kind='self' installLocation='C:\IBM\InstallationManager\eclipse' id='IBM Installation Manager'>
<data key='eclipseLocation' value='C:\IBM\InstallationManager\eclipse'/>
</profile>
<server>
<repository location='.'/>
</server>
<!-- add the profile information but do not modify the features, id, and version number -->
<install>
<offering profile='IBM Installation Manager' features='agent_core,agent_jre' id='com.ibm.cic.agent' version='1.4.3.20110624_0100'/>
</install>
</agent-input>
Use the Installation Manager installer to install Installation Manager and other software packages.
You can use the Installation Manager installer to silently install Installation Manager and software packages at the same time. Optionally, use the installer to install Installation Manager, then use Installation Manager to install packages silently.
To silently install packages using the Installation Manager installer, from the InstallerImage_platform directory, enter the following command:
Argument | Description |
---|---|
-vm |
Specifies the Java™ launcher. In silent mode, always use java.exe on Windows, and java on other platforms. |
-nosplash |
Specifies that the splash screen should be suppressed. |
--launcher.suppressErrors |
Specifies that the JVM error dialog should be suppressed. |
-input |
Specifies an XML response file as the input to Installation Manager installer or the Installation Manager. A response file contains commands that installer or Installation Manager runs. |
-acceptLicense |
Include the -acceptLicenseoption in your command when the package you are installing requires that you accept the licensing agreement. |
-log |
(Optional) Specifies a log file that records the result of
the silent installation. The log file is an XML file. If your silent installation session is successful, the log file will contain just the root element of <result> </result>. However, if errors occur during the installation, the silent install log file will contain error elements and messages. |
-updateAll |
(Optional) All available updates to are installed. |
-installAll |
(Optional) All available products are installed. |
-accessRights |
Defines whether the IM operates in admin or nonAdmin mode.
For nonAdmin mode this argument should always be used with 'nonAdmin'
parameter: -accessRights nonAdminFor admin mode it should be used with admin parameter: -accessRights admin If
this argument is not used, the default value is set based on current
user permissions.
Note:
For Windows XP
users who are members of Administrator group, the default is always -accessRights
admin. For these users to run in nonAdmin mode -accessRights
nonAdmin argument should be passed explicitly. |
-showProgress |
Displays a progress bar to the console. |
-ShowVerboseProgress |
Displays progress text to the console. For example, the text "Rebooting the machine to complete the install" is displayed when a reboot is required. |
-accessRights admin -vm C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr5_20070511\jre\bin\java.exe -nosplash --launcher.suppressErrors -silent -vmargs -Xquickstart -Xgcpolicy:gencon
<?xml version="1.0" encoding="UTF-8"?> <result> </result>The log file will contain an error element if the operation was not completed successfully.
Launch Installation Manager in silent mode with a response file to install, uninstall, update, or modify packages silently. Installation Manager is the tool that you typically use to install packages silently.
If you do not already have Installation Manager installed on your computer, you can also use the Installation Manager installer to install both Installation Manager and packages together silently using a single command.
Use Installation Manager in silent mode to install product packages from a command line.
After you install Installation Manager, use it in silent mode to install packages. This file explains how to install packages using the Installation Manager.
Argument | Description |
---|---|
-vm |
Specifies the Java launcher. In silent mode, always use java.exe on Windows, and java on other platforms. |
-nosplash |
Specifies that the splash screen should be suppressed. |
--launcher.suppressErrors |
Specifies that the JVM error dialog should be suppressed. |
-acceptLicense |
Include the -acceptLicenseoption in your command when the package you are installing requires that you accept the licensing agreement. |
-input |
Specifies an XML response file as the input to Installation Manager installer or the Installation Manager. A response file contains commands that installer or Installation Manager runs. |
-log |
(Optional) Specifies a log file that records the result of
the silent installation. The log file is an XML file. If your silent installation session is successful, the log file will contain just the root element of <result> </result>. However, if errors occur during the installation, the silent install log file will contain error elements and messages. |
-updateAll |
(Optional) Specifies that all available updates are installed. |
-installAll |
(Optional) Specifies that all available products are installed. |
-showProgress |
Displays a progress bar to the console. |
-ShowVerboseProgress |
Displays progress text to the console. For example, the text "Rebooting the machine to complete the install" is displayed when a reboot is required. |
-accessRights |
Specifies whether the Installation Manager operates in admin
or nonAdmin mode. For nonAdmin mode, this argument should always be
used with the 'nonAdmin' parameter: -accessRights nonAdminFor admin mode, this argument should be used with the 'admin' parameter: -accessRights admin If
this argument is not used, the default value is set based on current
user permissions.
Note:
For Windows XP
users who are members of Administrator group, the default is always -accessRights
admin. For these users to run in nonAdmin mode, the -accessRights
nonAdmin argument should be passed explicitly. |
-accessRights admin -vm C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr5_20070511\jre\bin\java.exe -nosplash --launcher.suppressErrors -silent -vmargs -Xquickstart -Xgcpolicy:gencon
<?xml version="1.0" encoding="UTF-8"?> <result> </result>The log file will contain an error element if the operation was not completed successfully.
You can search for and silently install all available products using the Installation Manager.
You can use Installation Manager to silently search for and install updates for all currently installed products.
You can silently install from an authenticated repository; however, authenticated repositories need the appropriate credentials for access.
To access authenticated repositories in silent mode, complete the following steps:
Use Installation Manager in silent mode to install the Optim components from a command line.
Use the Optim silent install response files to install the Optim components silently.
The following response files are located in the scripts directory of the product DVD.
The following keys are included in the Optim component response files:
The informix user name.
The repository requires the user name 'informix' as the database server user name. This value must not be changed.
The create informix user name flag.
Set to true if the 'informix' user name does not exist on the Repository Server machine or false otherwise. If set to true, both user.informixPassword and user.informixConfirmPassword must be passed in. If set to false, user.informixPassword is required and user.informixConfirmPassword is ignored. If set to false, the Repository Server installer will validate the informix user name and password using PAM services on the repository machine.
The informix user password (encrypted).
This field is only used during validation and is not stored in any file. The password is used by the informix user on the repository machine. This field is used to validate the password of the informix user. This field is only required when user.createInformixUser=true. To generate this value, run the installer in record mode or use the Installation Manager imutilsc utility.
The informix confirm password (encrypted).
The Optim encrypted informix password (encrypted).
This value is stored as the informix password in the eclipse.ini file of Optim Proxy, Optim Repository Manager, and Optim Designer. It is also stored in the Optim Manager and Optim Interface Service WAR files. To generate this value, run the installer in record mode. You can also use the optimcmd tool, that is installed as part of the Optim Manager, to generate new password values. In addition, whenever a new password is used during a wizard mode installer, this value is stored in the following files: Windows 7 - C:\Users\All Users\IBM\Installation Manager\.settings\optim.properties, Windows XP - C:\Documents and Settings\All Users\IBM\Installation Manager\.settings\optim.properties, UNIX - ~/var/ibm/InstallationManager/.settings/optim.properties.
The salt encrypted informix password (encrypted).
A salt encrypted password is used by most Linux and UNIX system to create passwords. The Repository Server installer passes this value to the operating system when it is necessary to create the informix user on a Linux and UNIX machine. To generate this value, run the installer in record mode on a Linux or UNIX system. You can also generate a new salt encrypted password by using the perl crypt() method. For more information refer to the URL: http://www.perlscriptsjavascripts.com/tutorials/howto/encrypt_unix_passwords.html. If you are unable to generate a salt encrypted password, manually create the user in the repository operating system before installing the Repository Server component, then specify false for user.createInformixUser.
The optim user name.
The user name used by the Optim components to access the repository. The user name must exist in the operating system of the repository. The user name 'optim' is pre-defined in the repository component.
The create optim user name flag.
Set to true if the 'optim' user name does not exist on the Optim Repository Manager machine or false otherwise. If set to true, both the user.optimPassword and user.optimConfirmPassword must be passed in. If set to false, the user.optimPassword is required and the user.optimConfirmPassword is ignored. If set to false, the Repository Manager installer will validate the optim user name and password using PAM services on the Optim Repository Manager machine.
The Optim encrypted optim password (encrypted).
This value is stored as the optim password in the eclipse.ini file of the Optim Proxy, Optim Repository Manager, and Optim Designer. It is also stored in the Optim Manager and Optim Interface Service WAR files. To generate this value, run the installer in record mode. You can also use the optimcmd tool, that is installed as part of the Optim Manager, to generate new password values. In addition, whenever a new password is used during a wizard mode installer, this value is stored in the file: Windows 7 - C:\Users\All Users\IBM\Installation Manager\.settings\optim.properties, Windows XP - C:\Documents and Settings\All Users\IBM\Installation Manager\.settings\optim.properties, UNIX - ~/var/ibm/InstallationManager/.settings/optim.properties.
The salt encrypted optim password (encrypted).
A salt encrypted password is used by most Linux and UNIX system to create passwords. The Repository Server installer passes this value to the operating system when it is necessary to create the optim user on a Linux and UNIX machine. To generate this value, run the installer in record mode on a Linux or UNIX system. You can also generate a new salt encrypted password by using the perl crypt() method. For more information refer to the URL:http://www.perlscriptsjavascripts.com/tutorials/howto/encrypt_unix_passwords.html. If you are unable to generate a salt encrypted password, manually create the user in the repository operating system before installing the Repository Server component, then specify false for user.createInformixUser.
The Informix installation directory.
The fully qualified installation directory of the Informix database server. Informix is installed as part of the Repository Server component. This directory is the value "ids11750" appended to the Repository Server installation directory.
The installing Optim Repository flag.
When set, the Optim Repository is being installed. This informational value is generated by the installer.
The installing Repository Manager flag.
When set, the Repository Manager is being installed. This informational value is generated by the installer.
The installing Repository Server flag.
When set, the Repository Server is being installed. This informational value is generated by the installer.
A flag indicating if PAM is available.
Set to true if the repository operation system contains the PAM modules.
The Optim Proxy work directory.
The directory used by the Optim Proxy component to store temporary run time information. This directory will be created if it does not exist. You must specify a directory that is outside of the installation directory.
The IBM InfoSphere Optim installation directory.
The private Optim directory name.
The name of the private Optim directory that is contained in the repository. You should only change this value if you plan on having multiple repositories.
The perform repository import option.
When set, the installer will configure an import script that you must run after the install or update to import your data from a previous export. If this is the first time you are installing this component, set user.performImport to false and user.skipRepositoryImport to true.
The skip repository import option.
When set, the installer will configure an import script that you must run after the install or update to import your data from a previous export. If this is the first time you are installing this component, set user.performImport to false and user.skipRepositoryImport to true.
The perform export option.
When set, an export of the repository database files will occur.
The skip export option.
When set, an export of the repository database files will not occur.
The repository export directory.
The directory used by the repository or Optim Server components to store exported repository data. This directory must exist. When doing an import, the export files must exist. When doing an export, any existing export files will be deleted. You must specify a directory that is outside of the installation directory.
The repository database directory.
The directory used by the Optim Repository Server component to store the repository database. The directory will be created if it does not exist. When doing an install, any existing files will be deleted. You must specify a directory that is outside of the installation directory.
The Repository Server installation complete flag.
When set, the Repository Server has been installed. This informational value is generated by the installer.
The Repository Server install directory.
This value is used by the Repository Manager installer to 'source' the Informix environment variables prior to starting the Repository Manager.
The repository host name.
The machine host name or IP address of the repository machine. This value should NOT be set to localhost.
The repository port number.
The TCP port number used by the Repository Server. When this variable is provided for the Repository Server installer, the value must not be in use or reserved by the operating system. The default value is typically reserved on the operating system file /etc/services. You must manually remove the selected port number entry from the file before installing the Repository Server. When this variable is provided for any Optim client or server installer, you must manually add the following entry optimrepo 9088/tcp to the operating system 'services' file. This file can be found in the following locations: Windows - C:\WINDOWS\system32\drivers\etc\services, UNIX/Linux - /etc/services.
The Repository Server name.
This value must not be changed.
The repository service name.
This value must not be changed.
The repository port number.
The TCP port number used by the Repository Manager. When this variable is provided for the Repository Manager installer, the value must not be in use or reserved by the operating system. The default value is typically reserved on the operating system file /etc/services. You must manually remove the selected port number from the file before installing the Repository Manager.
The Repository Manager URL.
This URL is dynamically built by the installer to validate that the repository manager is running. It is for informational purposes only.
The client validation flag.
A value of true will validate all of the values provided for an installer. To ensure that the components are configured correctly, always specify a value of true.
The server validation flag.
A value of true will validate all of the values provided for an installer. To ensure that the components are configured correctly, always specify a value of true.
The client repository validation flag.
A value of true will validate all of the values provided for an installer against an active repository. To ensure that the components are configured correctly, always specify a value of false.
Use the uninstall script to silently uninstall Installation Manager.
A response file is an XML file that contains the data needed to perform installation operations in silent mode.
Response files are used by both Installation Manager and the Installation Manager installer to perform installation operations silently. You can record a response file by recording preferences and installation actions in Installation Manager in user interface mode, or you can create one manually using the documented list of response file commands and preferences.
A response file is an XML file that contains data read by Installation Manager in silent mode. Using a response file, you can perform almost any action that you can perform using Installation Manager in wizard mode. For example, with a response file you can specify the location of the repository that contains the packages, which package to install, and which features to install for that package. You can also use a response file to modify your installed package, to apply updates, and to apply a license.Sample response file: Installing Installation Manager and packages
You can create a response file by recording your actions in Installation Manager. When you record a response file, all of the selections that you make in Installation Manager are stored in an XML file. When you run Installation Manager in silent mode, Installation Manager uses the data in the XML response file to perform the installation.
If you want to use the silent installation capabilities of Installation Manager, you need to create a response file that contains all of the commands that Installation Manager must run. The recommended way to do this is to create a response file by recording your actions as you install a package. However, you can also create or edit a response file manually.
You can use this reference table to learn more about response file commands.
Response file commands | Description |
---|---|
Profile <profile id="the profile (package group) id" installLocation="the install location of the profile"> <data key="key1" value=”value1”/> <data key="key2" value=”value2”/> </profile> |
A profile is an installation location. Use this command to
create a package group (or installation location). If the specified
package group already exists, then the command has no effect. Currently,
when creating the profile, the silent install will also create two
installation contexts; one for Eclipse and one
for native. You can use the <data> element to set profile properties. The following list contains the currently
supported keys and related values:
Note: Separate multiple NL values with commas.
The
following list contains the language codes. Not every language is
supported in every product:
|
Repositories <server> <repository location="http://example/ repository/"> <repository location=”file:/C:/ repository/”> <!—add more repositories below--> <…> </server> |
Use this command to specify the repositories that are used during a silent installation. Use a URL or UNC path to specify remote repositories; or use directory paths to specify local repositories. |
Install <install> <offering profile= "profile id" features= "feature ids" id= "offering id" version= "offering version" selected="true"></offering> <!—add more offerings below> <…> </install> |
Use this command to specify the installation packages that
will be installed. The profile ID must match an existing profile or a profile created by the set profile command. Feature IDs can be optionally specified by a comma-delimited list, such as "feature1, feature2” and so on. If no feature IDs are specified, all the default features in the specified offering will be installed. Note: Required
features will be included for installation, even if they are not explicitly
specified in the comma-delimited list.
The version number is not required. If no version is specified, the Installation Manager will install the most recent product with the specified id and any available updates and fixes. The 'selected' attribute is optional. By default, 'selected' is set to "true". When 'selected' is set to "false", silent install will not install the package. While running in the wizard mode, the package will be displayed in the package selection page but not selected initially. |
Update (in wizard mode) <update> <offering profile= "profile id"> </update> |
Use this command to specify the profile that will be updated.
The profile ID must match an existing profile. Note: This command
can only be used in wizard mode to invoke the update wizard; it does
not work in silent mode.
|
Modify (in wizard mode) <modify> <offering profile= "profile id"> </modify> |
Use this command to specify the profile that will be modified.
The profile ID must match an existing profile. Note: This command
can only be used in wizard mode to invoke the update wizard; it does
not work in silent mode.
|
Modify <install modify="true"> or <uninstall modify="true"> (optional attribute) <uninstall modify="true"> <offering profile="profile id" id="Id" version="Version" features="-"/> </uninstall> |
Use the <install modify="true"> attribute on install and uninstall commands to indicate that you want to modify an existing install. The default value is false. If the intent of the modify operation is only to install additional language packs, then a hyphen “-“ should be used in the offering feature id list to indicate that no new features are being added. Important: You must specify modify="true" and
a hyphen "-" for the features list as specified
in the example; otherwise, the install command will install the offering's
default features and the uninstall command will remove all of the
features.
|
Uninstall <uninstall> <offering profile= "profile id" features= "feature ids" id= "offering id" version= "offering version"></offering> <!—add more offerings below> <…> </uninstall> |
Use this command to specify the packages that will be uninstalled. The profile ID must match an existing profile or a profile specified in a profile command. In addition, if there are no feature IDs specified, then all of the features in the specified offering will be uninstalled; if there are no offering IDs specified, then all of the installed offerings in the specified profile will be uninstalled. |
Rollback <rollback> <offering profile= "profile id" id= "offering id" version= "offering version"> </offering> <!—add more offerings below <…> </rollback> |
Use this command to roll back to the specified offerings from the version that is currently installed on the specified profile. You cannot specify features in a roll back command. |
InstallAll <installALL/> Note: This
command is equivalent to using
. |
Use this command to silently search for and install all available packages. |
UpdateAll <updateALL/> Note: This
command is equivalent to using
. |
Use this command to silently search for and update all available packages. |
License <license policyFile=“policy file location”/> For example:
|
If your product package requires an installed license, use
this command to generate a response file that contains a license command
by starting the license wizard after starting Installation Manager
in record mode. During record mode, if you set flex options through the license management wizard, the options that you set will be recorded in a license policy file named “license.opt” in the same directory as the generated response file and the response file will contain a license command that references the policy file. |
Response file attribute | Description |
---|---|
Clean <agent-input clean="true"> </agent-input> |
By default, the clean attribute is set to 'false'. Installation Manager will use the repository and other preferences that are specified in the response file as well as the existing preferences that are set in the Installation Manager. If a preference is specified in the response file and set in the Installation Manager, the preference that is specified in the response file takes precedence. If the clean attribute is set to 'true', Installation Manager will use the repository and other preferences that are specified in the response file and the existing preferences that are set in the Installation Manager will not be used. |
Temporary <agent-input clean="true" temporary="false"> </agent-input> |
By default, the temporary attribute is set to 'false' and the preferences that are set in your response file will be persisted. When you set the temporary attribute to 'true', the preferences that are set in the response file will not be persisted. You can use the temporary and clean attributes together. For example, if you set clean to 'true' and temporary to 'false', after running the silent install the repository setting that is specified in the response file will override the preferences that were set in the previous sessions using Installation Manager. |
License agreement acceptance <agent-input acceptLicense="false"> </agent-input> |
By default, you do not agree to accept the licenses that an installation package carries when using Installation Manager in silent installation mode. If the package you are installing has a license agreement that must be accepted, the silent installation operation will fail. To accept the license agreement, you must set the attribute to <agent-input acceptLicense="true">. By doing so, you agree to accept the license agreements for every package specified in the response file. |
Reboot later <agent-input rebootLater="false"> </agent-input> |
By default, rebootLater is set to
'false' and if the response file installs any package that requires
rebooting the system on Windows,
Installation Manager will reboot the system after the execution of
the response file is finished. When rebootLater is set to 'true', the system will not reboot. |
Although you typically specify preferences using the Preferences window, you can also specify preferences (identified as keys) in a response file for use during a silent installation.
When you define preferences in a response file, your XML code will look similar to the following example:
<preference
name = “the key of the preference"
value = “the value of the preference to be set">
</preference>
Use the following table to identify keys
and their associated values for silent installation preferences:Key | Value | Notes |
---|---|---|
com.ibm.cic.common.core.preferences.logLocation | Specifies the location of Installation Manager log file. | Important: This key is optional and is designed
for testing and debugging. If you do not specify a location for the
log file, both silent installation and the UI version of Installation
Manager will use the same location.
|
com.ibm.cic.license.policy.location | Specifies a URL that defines where the remote license policy file resides. | Not required for products that do not require an installed license. |
com.ibm.cic.common.core.preferences.http.proxyEnabled | True or False | Proxy servers enable connection to remote servers from behind the firewall. False is the default value. Use this option to enable an HTTP or SOCKS proxy. After the proxy is enabled, the proxy will be used for all server communications. |
com.ibm.cic.common.core.preferences.http.proxyHost | Host name or IP address | |
com.ibm.cic.common.core.preferences.http.proxyPort | Port number | |
com.ibm.cic.common.core.preferences.http.proxyUseSocks | True or False | Proxy servers enable connection to remote servers from behind the firewall. False is the default value. Enable this option so that you can specify a SOCKS proxy host address (required) and a SOCKS proxy port number (optional). |
com.ibm.cic.common.core.preferences.SOCKS.proxyHost | Host name or IP address | |
com.ibm.cic.common.core.preferences.SOCKS.proxyPort | Port number | |
com.ibm.cic.common.core.preferences.ftp.proxyEnabled | True or False | False is the default value. An FTP proxy is an application-level gateway for FTP. An FTP proxy securely forwards command and data streams between a client and server. This forwarding function is useful to firewalls and FTP masquerades. An FTP proxy also can fix connections to the FTP server and helps provide proxy authentication. |
com.ibm.cic.common.core.preferences.ftp.proxyHost | Host name or IP address | |
com.ibm.cic.common.core.preferences.ftp.proxyPort | Port number | |
com.ibm.cic.common.core.preferences.eclipseCache | c:\IBM\common (Windows) /opt/IBM/common (Linux)
Note: The
paths are default values for this preference; typically, install packages
provide their own values for this preference.
|
You cannot change this location if you have already installed a package. |
com.ibm.cic.agent.core.pref.offering.service.repositories.areUsed | True or False | Change this preference to False to disable it. When this preference is set to True, all linked repositories will be searched when products are installed or updated. |
com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts | True or False | Change this preference to False to disable it. When this preference is set to True, the files that are required to roll the package back to a previous version are stored on your system. When this preference is set to False, these files are not stored. If you do not store these files, you must connect to your original repository or media to roll back. |
com.ibm.cic.common.core.preferences.repositoryLocations_EDITABLE | True or False | Use this preference to specify whether users can make changes to the repositories after the product is installed. |
com.ibm.cic.common.core.preferences.directArtifactAccessMode | True or False | The default is False. Before Installation Manager begins the installation process, all required installation files are downloaded to the shared repository location. When this preference is set to True, Installation Manager accesses the installation files directly from the input repositories during the installation process instead of first downloading and verifying them. |
com.ibm.cic.common.core.preferences.searchForUpdates | True or False | The default is False. When this preference is set to True, Installation Manager searches for updates to itself before performing the silent installation. |
You can use an XML-based response file to specify predefined information such as silent installation preferences, repository locations, installation profiles, and so on. Response files are beneficial for teams and companies that want to install software packages silently and to standardize the locations and preferences for the packages.
It can be helpful to record a response file and then tailor the contents to suit your needs. See Recording a response file with Installation Manager for more information on recording a response file.
Sample response files for each Optim package are included in the scripts subdirectory of the package installation directories.
Sample response files are also included on the installation disc, in the scripts directory.
This is a sample response file for installing Installation Manager and a package at the same time.
Sample response file for installing Installation Manager and a software package |
---|
|
This is a sample response file for installing a software package.
Sample response file for a software package |
---|
<agent-input> <server> <repository location= "http://a.site.com/local/products/sample/20060615_1542/repository/"></repository> </server> <!-- use default installation location and choose the latest version of the offering that is available in the repository --> <install> <offering features= "core" id= "ies"> </offering> </install> </agent-input> |
You can install, update, modify, or uninstall software packages with Installation Manager in wizard mode, using a response file.
Installation Manager can be run in silent mode or wizard mode. To start Installation Manager in wizard mode, enter the following on the command line:IBMIM -mode wizard -input <response> where <response> is the response file path and name.
Based on the commands in your response file, Installation Manager will start in one of the following wizards: install, update, modify, or uninstall. Your response file can only contain commands for one of the Installation Manager wizards. For example, the response file can include either:
You can generate a .zip file that contains data for problem analysis. This file is used by IBM Support to help troubleshoot the problem.
If you cannot install Installation Manager, the Installation Manager installer can optionally be used to perform other silent installation operations.
You can search for and silently install all available products using the Installation Manager installer.
You can silently search for and install updates for all installed products with the Installation Manager installer.
You can silently install from an authenticated repository; however, authenticated repositories need the appropriate credentials for access.
To access authenticated repositories in silent mode, complete the following steps:
If you need to install the product to multiple systems, refer to the available articles on the installation Web site.
The Installation Manager information center contains articles that will help you install your product in an enterprise environment. Visit the information center for Installation Manager 1.5.0 at http://pic.dhe.ibm.com/infocenter/install/v1r5/index.jsp.
After you have installed your product package, complete the post-installation tasks or configure your product package as required.
After you have installed your product, complete several tasks to configure and verify the installation.
The Modify Packages wizard in the IBM Installation Manager enables you to change the feature and language selections of an installed product package. You can also use the Modify Packages wizard to install new features that might be included in a package update, such as a refresh pack.
Package updates provide fixes and updates to installed product packages. You can use the Update Packages wizard in IBM Installation Manager to install updates for product packages that were installed by using IBM Installation Manager.
Each installed package has the location embedded for its default IBM update repository. For Installation Manager to search the IBM update repository locations for the installed packages, the preference Search service repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.
See the Installation Manager help for more information.You can remove an update, such as a fix pack, to a product package to revert to a previous version by using the Roll Back Packages wizard of IBM Installation Manager.
Use the rollback feature if you have applied an update to a product package and decide later that you want to remove the update and revert to the earlier version of the product. When you use the rollback feature, Installation Manager uninstalls the updated resources and reinstalls the resources from the previous version. You can only roll back one version level at a time.
For more information, see the Installation Manager online help or Information Center.
To revert an update to a previous version, complete the following steps:
You can use the Uninstall option in IBM Installation Manager to uninstall software that was installed by using Installation Manager from your computer.
You can use the Uninstall option in IBM Installation Manager to uninstall a product package from a single installation location. You can also uninstall all the installed packages from every installation location.
You can follow the instructions below to uninstall IBM Installation Manager.
If the icon is not present, open a terminal window and run the uninstall command from the uninstall directory in the Installation Manager installation directory.
Use a response file to uninstall a package.
To uninstall a package in silent mode:
Operating system | Command |
---|---|
Windows | imcl.exe input c:\response_files\uninstall.xml -log c:\mylog\uninstall_log.xml -acceptLicense |
Linux and UNIX | ./imcl input /response_files/uninstall.xml -log /mylog/uninstall_log.xml -acceptLicense |
Enclose file paths that include spaces with double quotation marks.
Use the installer to install IBM InfoSphere Optim on supported Windows, Linux, and UNIX platforms.
The installation process unloads Optim from the installation DVD to the target workstation and additional workstations or servers.
You begin the installation phase by using the program to load the application software at the first workstation. You must enter your company name and the identification number indicated in the email sent when Optim is shipped to you. You must also designate a destination directory for the application software.
You can install Optim on individual workstations or on a file server for multiple users to share.
Your decision to install Optim on individual workstations or on a file server does not affect licensing requirements, but there are considerations for either method. The advantages of installing on individual workstations include:
In contrast, a single installation on a file server offers the following advantage:
Regardless of your choice, you should install and configure each additional workstation to create desktop shortcuts and create necessary Windows registry entries.
Installing Optim takes only a few minutes. You can install Optim using the installer wizard, console install, or a silent install. When installation completes, use the Configuration program to prepare your workstations to use Optim.
You can install IBM InfoSphere Optim using the installer wizard.
In a Windows environment, you can install Optim from the console.
In a Windows environment, you can install Optim using the silent installer.
The Optim installation includes the optim_installer.properties file located in the distributed\RTWin directory of the product DVD. To use the silent installer, open the optim_installer.properties file and make any modifications to the variables to customize it for your installation. You can modify the following variables:
CHOSEN_INSTALL_FEATURE_LIST=Optim,Optim Online Documentation,Optim Archive ODBC Interface,
Optim ODM Interface,Sample Files,5.x PST Directory Conversion Files
INSTALL_APP_FOR_ALLUSER=1
To
install Optim for the current
user only, specify:INSTALL_APP_FOR_ALLUSER=0
USER_INSTALL_DIR=C:\\Program Files\\IBM Optim
USER_INPUT_ODM_INSTALL=1
USER_INPUT_ODM_COPYONLY=0
USER_INPUT_ODM_INSTALL=0
USER_INPUT_ODM_COPYONLY=1
USER_INPUT_ODM_ENABLE_TRIAL=0
USER_INPUT_ODM_SPECIFY_LICENSE=1
USER_INPUT_ODM_ENABLE_TRIAL=1
USER_INPUT_ODM_SPECIFY_LICENSE=0
USER_SHORTCUT_NEW_PRG_MENU=1
Use
either USER_SHORTCUT_NEW_PRG_MENU= or USER_SHORTCUT_EXST_PRG_MENU=,
do not specify both. USER_SHORTCUT_EXST_PRG_MENU=1
Use
either USER_SHORTCUT_NEW_PRG_MENU= or USER_SHORTCUT_EXST_PRG_MENU=,
do not specify both.USER_SHORTCUTS=C:\Documents and Settings\All Users\StartMenu\Programs\IBM Optim
Specify
USER_SHORTCUTS= if you used either USER_SHORTCUT_NEW_PRG_MENU= or
USER_SHORTCUT_EXST_PRG_MENU=.USER_SHORTCUT_DESKTOP=1
USER_SHORTCUT_QCK_LAUNCH_BAR=1
USER_SHORTCUT_START_MENU=1
USER_INPUT_VIEW_REL_NOTES=1
USER_INPUT_LAUNCH_CONFIG=1
After you specify the variables in the optim_installer.properties file, use one of these commands to start the silent installer.
IBMOptim.exe –i silent
IBMOptim.exe -f directorypath\optim_installer.properties
where directorypath is the fully-qualified path to the directory for the optim_installer.properties file.
The first step in the Configuration process is to sign a valid exit (i.e., the Optim default exit or a user-supplied exit). You can then use the Configuration program to create the Optim Directory, establish connectivity to databases for Optim, and perform other maintenance tasks.
Use the Configuration program for the following tasks:
The installation process for Optim on a Linux or UNIX platform differs depending on your environment. Linux and UNIX platforms only support an Optim Server installation.
You can use the Sun Solaris operating environment under SPARC; the Hewlett-Packard HP-UX operating environment; the IBM AIX® operating environment; or the Red Hat Application Server. Note that an Optim Server installed in a UNIX environment cannot access an Optim Directory in an SQL Server database. Configuration files, included with the installation, must be modified to adapt the Server to the requirements of your environment.
After completing the installation and configuration, processing initiated on a Windows workstation can be directed to the Server. Additionally, processing can be initiated from a console using a Command Line Interface.
You can install Optim using the installer wizard.
In a UNIX or Linux environment, you can run the installer from the console to install Optim server. The information in this section applies to all UNIX or Linux platforms except Red Hat Linux 3 .
You can use the silent installer in supported UNIX and Linux platforms to install the Optim Server.
The Optim installation includes the optim.installer.properties file in the distributed/platform_type directory of the product DVD (for example distributed/RTAIX). To use the silent installer, open the optim.installer.properties file and make any modifications to the variables to customize it for your installation. You can modify the following variables:
USER_INPUT_ODM_NOW= and USER_INPUT_ODM_LATER= should be included in the properties file only if you are installing the ODM feature. Otherwise, remove them from the file.
Otherwise, remove USER_INPUT_ODM_USERLIC= and USER_INPUT_ODM_TRIAL= from the file.
Include ODM_LICENSE_FILE_FULL_PATH= only if allthese conditions are met:
Otherwise, remove ODM_LICENSE_FILE_FULL_PATH= from the file.
After you specify the variables in the optim.installer.properties file, use one of the following commands to start the silent installer.
./install.bin –i silent
./install.bin -fdirectorypathoptim.installer.properties
where directorypath is the fully-qualified path to the directory for the optim.installer.properties file.
After the installation completes, see Configuration to establish defaults for the Server.
You can install Optim on Red Hat Linux 3 using the installer wizard or the command line.
You can install Optim using the installer wizard.
To install the Server from the command line, use the setup options file, setupopts, located on the product DVD.
To install the Server, mount the product DVD and copy setupopts from the root directory to a location for which you have write access. You can edit the file using an ASCII editor. Enable a keyword by removing the leading ‘###' characters from the line. Define a parameter for a keyword by editing the characters after the ‘='.
Open a console to thedistributed/RtHEL3 directory of the product DVD. Run the setup process from the command line, using the following command:
./setup -silent -options <file-name>
For example, if setupopts is in the /users/name directory, enter the following:
./setup -silent -options /users/name/setupopts
If you are upgrading or installing on a machine that has one or more Servers installed in another directory, you must manually shut down all Server processing. To shut down a Server, you must log on as the processing user account for each Server and run the following command before manually shutting the Server down.
rt/mw/bin/mwadm stop
The syntax conventions used to describe the setupopts keywords are as follow:
–W LicensePanel.selection={ 1 | 2 }
–P installLocation=installdirectory
[ –P ProgramFeature.active=[ true | false ] ]
[ –P SampleFeature.active=[ true | false ] ]
[ –P ODMFeature.active=[ true | false ] ]
[ –W ConfigureODMPromptPanel.ConfigureODMChoice=[ 1 | 2 ] ]
[ –W ODMLicensePanel.ODMLicenseField=licensepath ]
[ –W UpdateFilesPanel.Update_rtsetenv=[ 0 | 1 ] ]
[ –W UpdateFilesPanel.Update_rtserver= [ 0 | 1 ] ]
[ –W UpdateFilesPanel.Update_rt4s=[ 0 | 1 ] ]
[ –W UpdateFilesPanel.Update_pstserv=[ 0 | 1 ] ]
[ –W UpdateFilesPanel.Update_pstlocal=[ 0 | 1 ] ]
[ –W UpdateFilesPanel.Update_locale=[ 0 | 1 ] ]
[ –W View_Readme.Value=[ 0 | 1 ] ]
-W LicensePanel.selection=1
-P installLocation=/opt/IBM/Optim/rt
-P ProgramFeature.active=true
-P SampleFeature.active=true
-W ConfigureODMPromptPanel.ConfigureODMChoice
.-P ODMFeature.active=false
-W ConfigureODMPromptPanel.ConfigureODMChoice=2
-W ConfigureODMPromptPanel.ConfigureODMChoice=2.
-W ODMLicensePanel.ODMLicenseField=/opt/ODM/license.txt
-W UpdateFilesPanel.Update_rtsetenv=0
-W UpdateFilesPanel.Update_rtserver=0
-W UpdateFilesPanel.Update_rt4s=0
-W UpdateFilesPanel.Update_pstserv=0
-W UpdateFilesPanel.Update_pstlocal=0
-W UpdateFilesPanel.Update_locale=0
-W View_Readme.Value=0
Configuration files and shell scripts are installed with the executable files when you install the Server in a supported UNIX environment. These objects establish defaults for the Server and must be customized to reflect your network environment. Use a text editor (for example, vi, emacs, CDE Text Editor, textedit, or xedit) to modify these files.
Configuration files are ASCII text files and are installed in the /etc directory that is subordinate to the PSTHOME directory. PSTHOME is an environment variable, set during installation, that points to the directory in which the Server is installed.
The configuration file names for the Server are:
The appropriate Configuration file is loaded and validated when pr0svce or the Command Line Utility starts up. You can also use pr0svce -v to validate pstserv.cfg or pr0cmnd -v to validate pstlocal.cfg.
To reload the configuration file for prosvce while it is running, use pr0svce -u from a console under the user account for the daemon (or use pr0svce -u userid from root). After all clients have logged off, the file is read, reloaded, and validated. A console message and system log verify the file has been loaded.
The installed shell scripts are:
The following conventions are used in shell scripts and .cfg files:
The syntax conventions used to describe the configuration files, shell scripts, and commands are:
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 Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
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.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites 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.
IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.S.A.
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 information 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.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
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.
IBM
IBM logo
DB2
AIX
Informix
InfoSphere
Optim
Netezza® is a registered trademark of IBM International Group B.V., an IBM Company.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.
Apache Derby is a trademark of The Apache Software Foundation.
Eclipse is a trademark of Eclipse Foundation, Inc.
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 are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.