Home | Previous Page | Next Page   Installing Dynamic Server > Alternative Installation Methods >

Installing Using Extraction With a Command-Line Script

As an alternative to using the installation program, you can extract script-based installable Dynamic Server media (server and client products only). The extraction mode uses the installation program to extract the media and provide the Software License Agreement. After the extraction, when you are ready to install the product, you must run the command-line install script.

Read syntax diagramSkip visual syntax diagram>>-+-installserver----+-- -legacy--+-----------+---------------->
   +-installconn------+            '--- -gui---'
   '-installclientsdk-'
 
>--+--------------------+--+----------------------+------------->
   '- -log--logfilename-'  '- -javahome--Java dir-'
 
>--+----------------------+--+---------------------+-----------><
   '- -tempdir--temp path-'  +- -is:freediskblocks-+
                             '- -is:nospacecheck---'

The following table explains the syntax elements.

Table 12. Syntax Elements
Element Purpose Restrictions
Java dir Specifies the JRE on the host computer to use during installation instead of the JRE provided by the installation program The JRE must be version 1.3.2 or higher.
logfilename Specifies a non-default log filename None
temp path Specifies the path to temporary directory. If you receive an error during file extraction that there is not enough space in the /tmp directory, set the -tempdir option to a different temporary directory. None

The following table describes the extraction options.

Table 13. Installation Options
Option Meaning
installserver Extract database server only
installconn Extract IConnect only
installclientsdk Extract Client SDK only
-gui Start the extraction in GUI mode
-log Log installation program progress
-javahome Use specified JRE. To force the installation program to use the bundled JRE and ignore any local JREs, use the -javahome none argument.
-tempdir Use specified temporary directory
-is:freediskblocks Use to determine if there is adequate space for the product installation files prior to starting the installation.
-is:nospacecheck Use to prevent the installation program from checking if there is adequate space for product installation files. Use with caution: If there is not enough space to extract the temporary files, the installation program will fail.
-help Display list of supported options and their functions

The extraction with command-line installation alternative is provided for users who want to install the product to redistribute it.

This method of installing Dynamic Server does not add a JRE or an uninstall application on your computer.

To install Dynamic Server in extraction mode
  1. As the root user, run the installation command for the products you want to install: 
    ./installserver -legacy
    ./installconn -legacy
    ./installclientsdk -legacy

    The installation program is used for the extraction.

    You can use the -legacy argument to run the installation program in default console mode, GUI, or silent install mode. The following instructions are for the default console mode.

  2. Enter 1 to progress through the installation screens.

    The Software License Agreement displays.

  3. After you read the license agreement, enter 1 to accept the terms.
  4. Enter 1 to progress through the installation screens.
  5. Specify an install directory or press Enter to accept the default directory.

    The server product and installation files are extracted.

  6. To install the server only, change directories to the directory where you want to install the product ($INFORMIXDIR) and run the install script as the root user: 
    cd $INFORMIXDIR
./installserver

    You can install IConnect or Client SDK in a similar manner. Change directories to where you want to install the product and as the root user run one the following commands: 

    ./installconn

    ./installclientsdk

After the installation is complete, the installation script changes the owner of the INFORMIXDIR directory to user informix as well as any subdirectories and files under the INFORMIXDIR directory that the user informix must access or control.

Attention:
Do not use the oninit command if problems occur. If you use oninit, you might cause further installation problems.

For information about any errors that occur during the installation, check the install log in the $INFORMIXDIR/tmp/log.txt file.

For information on installing IBM Informix JDBC Driver, see IBM Informix: JDBC Driver Programmer's Guide.

Installing by Invoking the JAR File Directly

The following syntax diagram illustrates the installation options you can use when the Dynamic Server .jar file is invoked directly. To use this installation option, you must have a version of JRE 1.32 or higher.

Read syntax diagramSkip visual syntax diagram>>-java -cp----------------------------------------------------->
 
>--+-suite.jar:SERVER/IIF.jar:CSDK/UNIX/csdk.jar:ICONNECT/UNIX/conn.jar:JDBC/setup.jar-+-->
   +-relative_directory/IIF.jar--------------------------------------------------------+
   +-relative_directory/csdk.jar-------------------------------------------------------+
   +-relative_directory/conn.jar-------------------------------------------------------+
   '-relative_directory/setup.jar------------------------------------------------------'
 
>--run--+----------------------------+-------------------------->
        '--- -P legacy.active=true---'
 
>--+------------------------------+--+---------------------+---->
   '--- -p logFile--logfilename---'  +- -is:freediskblocks-+
                                     '- -is:nospacecheck---'
 
>--+- -swing-----------------------------+---------------------><
   '- -silent--+- -acceptlicense=yes---+-'
               '- -options--optionfile-'
Table 14.
Element Purpose Restrictions
relative_directory Specifies the path to the specified .jar file. If you execute the command from the directory where the .jar file resides, do not specify a path. None
logfilename Specifies a non-default log filename None
optionfile Specifies file name of *.ini file to preset installation properties None

The following table describes the Java-invoked application options.

Table 15.
Option Meaning
suite.jar The installation application for all the components of Dynamic Server
IIF.jar The installation application for Dynamic Server, database server only
csdk.jar The installation application for Client SDK
conn.jar The installation application for IConnect
setup.jar The installation application for JDBC
-P legacy.active=true Extracts files but does not install the product
-p logfile Log installation program progress
-is:freediskblocks Use to determine if there is adequate space for the product installation files prior to starting the installation.
-is:nospacecheck Use to prevent the installation program from checking if there is adequate space for product installation files. Use with caution: If there is not enough space to extract the temporary files, the installation program will fail.
-swing Set the Java-invoked application to GUI mode
-silent Set the Java-invoked application to silent mode
-options Use with optionfile. Specifies file name of *.ini file to preset installation properties
To install Dynamic Server by invoking the JAR file directly
  1. Invoke Java on the installation program, using the command that corresponds to the products you want to install; for example: 
    java -cp IIF.jar run

    You must execute this command from the directory of the IIF.jar file.

  2. Follow the procedure for installing with the application program.

    For more information, see Installing in Console Mode.

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]