Siebel Installation Guide for Microsoft Windows > Installing Siebel Enterprise Server and Related Components > Determining Your Installation and Configuration Method >

Medium-Sized Deployments

This topic is part of Determining Your Installation and Configuration Method.

Do you require a medium-sized deployment? Will you install all Siebel Enterprise Server components on the same machine? Siebel Enterprise Server components include Siebel Gateway Name Server, Siebel Server, and Database Configuration Utilities.

Where Siebel Enterprise Server components are to be installed on the same machine, but the Web server and Siebel Web Server Extension (SWSE) are to be installed on a different machine, use the Siebel Enterprise Server installer (after you have created the Siebel Database instance) to install the Enterprise Server components.

You can install in GUI or console mode, or use unattended installation. (See the discussion of large deployments for information about unattended installation.)

After GUI installation, the Configuration Wizard launches automatically so you can configure all Siebel Enterprise Server components. Optionally, you can cancel configuration and perform Configuration Wizard tasks later. In this case, first configure the Siebel Gateway Name Server, then the Siebel Enterprise, then the SWSE logical profile.

NOTE:  If you are installing in console mode, you must modify the siebel.ini file to prevent the Configuration Wizard from launching after installation. Launch the Configuration Wizard manually after installing. See also Editing siebel.ini Files for Console Mode Installation.

After installing and configuring the Siebel Enterprise Server components, you configure the Siebel Database. The Siebel Database itself is generally located on a different machine than the Siebel Enterprise Server software.

You install and configure the SWSE on the Web server machine, which includes applying the SWSE logical profile.