Siebel Installation Guide for UNIX > Installing Siebel Mobile Web Clients >

About Customizing the Siebel Client Installer

Most of the topics in this chapter focus on installations using default installation parameters set for the Siebel applications. However, you can modify installer behavior in certain ways.

If you want to prepare custom software installation packages for distribution to end users, you install the Siebel client as a model installation. After completing client installation and configuration, you run the Siebel Packager utility. A model client installation serves as the basis for a package. For details about using Siebel Packager, see Going Live with Siebel Business Applications.

Whether or not you use Siebel Packager, you can modify the behavior of the client installer by updating the siebel.ini and setup.ini files for the Siebel client installer. These files are part of the Siebel image you created in Creating the Siebel Installation Image on the Network.

The siebel.ini file controls Siebel settings for the install session.

For more information about the function of the siebel.ini file and how you can modify it, see comments contained within the siebel.ini file itself, see installation topics on My Oracle Support, and see Going Live with Siebel Business Applications.

Although unattended or console installation is not supported for the Siebel client installer, some information in Installing and Configuring in Unattended and Console Modes is also relevant to modifying the siebel.ini file for the client installer.

In general, do not modify values in the siebel.ini file for the client installer that contain variables. Some specific values of this type are described below.

• The values $(MobileClient)=no or $(MobileClient)=yes contain variables and must not be modified.
  • $(MobileClient)=no means that the parameter applies if you are installing the Developer Web Client and does not apply if you are installing the Mobile Web Client.
  • $(MobileClient)=yes means that the parameter applies if you are installing the Mobile Web Client and does not apply if you are installing the Developer Web Client.
• The value $(Slipstream)=no contains a variable and must not be modified. This value means that the parameter applies if the current Siebel product is not being installed using slipstream installation. For more information about slipstream installation, see About Installing Siebel Releases and see the applicable Siebel Maintenance Release Guide on My Oracle Support.

After you install the Siebel client, the file predeploy.htm is loaded. This file downloads ActiveX controls to the client machine. For information about suppressing the loading of this file by editing the siebel.ini file, see Installing the Siebel Mobile Web Client and Developer Web Client.

When EnableLangDlg is set to Y (the default) in the [Startup] section of the siebel.ini file, the dialog box for selecting Language Packs to install will be displayed. If you want a client installer to be used only for adding particular Language Packs to existing installations, set EnableLangDlg to N. Then, in the [Defaults.LanguageSelection] section of the file, set each language to be installed to yes.

The setup.ini file controls InstallShield settings for the install session. When EnableLangDlg is set to Y (the default) in the [Startup] section of the setup.ini file, the dialog box for choosing the installer language (labeled Choose Setup Language) will be displayed. If EnableLangDlg is set to N, the installer runs in the language for the user's locale or in the default language defined in setup.ini (usually English). For more information, see The Language in Which Siebel Installers and Wizards Run.