GUI mode

GUI mode

GUI mode is the default method of installing and configuring Siebel Business Applications.

GUI installation uses the product's siebel.ini file, either default or edited. (All installation modes require the siebel.ini file.)

GUI configuration launches automatically after installation.

Console mode

GUI installation uses the product's siebel.ini file, either default or edited.

NOTE:  Cancel GUI configuration after it launches. Alternatively, edit the product's siebel.ini file before installing to disable launching GUI configuration.

Console configuration must be launched manually after installation.

Unattended mode (execute mode)

GUI installation uses the product's siebel.ini file, either default or edited.

NOTE:  Cancel GUI configuration after it launches. Alternatively, edit the product's siebel.ini file before installing to disable launching GUI configuration or to configure automatically launching unattended configuration.

Unattended configuration requires a configuration response file (XML).

• To launch unattended configuration manually after installation, launch the Configuration Wizard in execute mode from the command line, and specify the configuration response file.
• To launch unattended configuration automatically after installation, you must have edited the siebel.ini file to launch the Configuration Wizard in execute mode and specify the configuration response file.

Console mode

GUI mode

Console installation uses the product's siebel.ini file.

NOTE:  You must edit the product's siebel.ini file before installing to disable launching GUI configuration.

GUI configuration must be launched manually after installation.

Console mode

Console installation uses the product's siebel.ini file.

NOTE:  You must edit the product's siebel.ini file before installing to disable launching GUI configuration.

Console configuration must be launched manually after installation.

Unattended mode (execute mode)

Console installation uses the product's siebel.ini file.

NOTE:  You must edit the product's siebel.ini file before installing to disable launching GUI configuration or to configure automatically launching unattended configuration.

Unattended configuration requires a configuration response file (XML).

• To launch unattended configuration manually after installation, launch the Configuration Wizard in execute mode from the command line, and specify the configuration response file.
• To launch unattended configuration automatically after installation, you must have edited the siebel.ini file to launch the Configuration Wizard in execute mode and specify the configuration response file.

Unattended mode

GUI mode

Unattended installation requires an installation response file (siebel.ini) you create using the installer's record mode.

NOTE:  Generating the installation response file disables launching GUI configuration.

GUI configuration must be launched manually after installation.

Console mode

Unattended installation requires an installation response file (siebel.ini) you create using the installer's record mode.

NOTE:  Generating the installation response file disables launching GUI configuration.

Console configuration must be launched manually after installation.

Unattended mode (execute mode)

Unattended installation requires an installation response file (siebel.ini) you create using the installer's record mode.

NOTE:  Generating the installation response file disables launching GUI configuration.

Unattended configuration requires a configuration response file (XML).

• To launch unattended configuration manually after installation, launch the Configuration Wizard in execute mode from the command line, and specify the configuration response file.
• To launch unattended configuration automatically after installation, you must have edited the siebel.ini file to launch the Configuration Wizard in execute mode and specify the configuration response file.

NOTE:  For unattended configuration for a product that was just installed, you may need to use a configuration response file you generated from a different product installation session.