bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Installing WebLogic Platform

Installing WebLogic Platform Using Silent-Mode Installation

The following sections describe how to install WebLogic Platform using the installation program in silent mode on both Windows and UNIX systems:

- What Is Silent-Mode Installation?

- Before You Start

- Using Silent-Mode Installation: Main Steps

- Creating a Silent-Mode Installation Template File

- Starting the Silent-Mode Installation Process on a Windows System

- Starting the Silent-Mode Installation Process on a UNIX System

- Sample Template Files for Silent-Mode Installation

- What's Next?

What Is Silent-Mode Installation?

Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create prior to beginning the installation. The installation program does not display any configuration options during the installation process. Silent-mode installation works on both Windows and UNIX systems.

Note: Using silent-mode installation implies your consent to the BEA License Agreement. You neither see a copy of the BEA Software License Agreement nor have any means to accept the terms of the agreement.

The instructions in this section assume that you have already acquired the installation program, either on CD or from the Web. For more information, see WebLogic Platform Distribution Methods.

Before You Start

Before you start the WebLogic Platform installation, make sure the platform you are using is supported. For a complete list of supported platforms, see the Supported Platforms page at the following URL:

>     http://e-docs.bea.com/platform/docs70/support/index.html

You should also read Preparing to Install WebLogic Platform.

Note: You cannot reinstall WebLogic Platform over a previous WebLogic Platform installation. You must first uninstall WebLogic Platform, as described in Uninstalling WebLogic Platform, or install in another location.

Using Silent-Mode Installation: Main Steps

The silent-mode installation process comprises two tasks:

1. Creating a template file that defines the configuration settings that a user normally enters during an interactive installation process, such as graphical or console-mode installation. For example, values for the BEA Home directory, the product directory, and options for the Configuration Wizard are supplied in a silent-mode template file.

   For a detailed procedure, see Creating a Silent-Mode Installation Template File. For a sample template file, see Sample Template Files for Silent-Mode Installation.

2. Launching the silent-mode installation process using the template file you created in step 1.

   For a detailed procedure, see Starting the Silent-Mode Installation Process on a Windows System or Starting the Silent-Mode Installation Process on a UNIX System.

Important Notes About Silent-Mode Installation

You need to be aware of the following items when you are performing an installation in silent mode:

- You must use the package installer for silent-mode installation. Silent-mode installation is not supported with the net installer. Filenames for the net installer version of the installation program are preceded by net_, for example net_platform XXX_solaris.bin, where XXX is the version number of the software you are installing. Do not attempt to use installation programs with filenames beginning with net_ for silent-mode installation.

- Silent-mode installation supports typical installation only: you must install all the components of WebLogic Platform. For information about the components installed in a typical installation, see Choosing the Type of Installation.

- Silent-mode installation requires the same temporary disk space and uses the same temporary storage directories as a standard installation. For more information, see Temporary Disk Space Requirements. The installation program does not prompt you if there is not enough space in the temporary directory.

- A silent-mode installation takes the same amount of time as a standard installation. At the beginning of a silent-mode installation, an initial installation program window or message appears briefly, indicating that the installation has started. No message is displayed indicating the installation is in progress or has completed successfully.

- Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

- The XML definition (<?xml version="1.0" encoding="UTF-8"?>) must be at the very beginning of the silent.xml template file. There cannot be any spaces or line breaks before the XML definition.

Creating a Silent-Mode Installation Template File

When you install WebLogic Platform in silent mode, the installation program does not prompt you to provide information in real time. Instead, it queries an XML file called silent.xml to determine which installation options should be implemented and which values to use for required configuration settings. Therefore, before you can run the installation program in silent mode, you must first create a silent.xml file in which you specify the installation options that you want to have invoked.

Note: Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

To create a template file for use in the silent-mode installation process, follow these steps:

1. From a supported browser, download a sample template file for silent-mode installation. Several sample templates are available for various configurations:

   - Comprehensive Template File Sample

   - Sample Template for Configuring a Domain with an Administration Server with Managed Servers

   - Sample Template for Configuring a Cluster of Managed Servers

   - Sample Template for Adding a Managed Server to an Existing Domain

   The comprehensive template illustrates how to configure your domain for functionality from all the WebLogic Platform components (WebLogic Server, WebLogic Workshop, WebLogic Integration, and WebLogic Portal). The other three templates are narrower in scope, as suggested by their titles. All four templates are available later in this chapter at the following location:

   http://e-docs.bea.com/platform/docs70/install/silent.html#template

   You can download these templates from a browser using the instructions that are provided with each template. (If you are viewing these templates in PDF format, you can copy them directly from the Adobe Reader.)

2. Save the contents of the template as a text file named silent.xml in the directory containing the WebLogic Platform installation program.

   Note: The XML definition (<?xml version="1.0" encoding="UTF-8"?>) must be at the very beginning of the template file. There cannot be any spaces or line breaks before the XML definition.

3. In the silent.xml file, create your desired configuration by assigning values for the data-value names shown in the following table.

   Note: You must follow XML guidelines for characters when modifying values. That is, you cannot use characters reserved for use in XML, such as <, >, [, and ].

   Table 4-1 Silent-Mode Installation Template Values

   For this data-value name . . . | Enter the following value . . .
   --- | ---
   BEAHOME | The full pathname for the BEA Home directory of your choice. For details about the BEA Home directory, see Choosing a BEA Home Directory. Note: For silent-mode installation only, the BEA Home directory specified for this value cannot exist before installing the software.
   USER_INSTALL_DIR | The full pathname for the directory where you want to install the WebLogic Platform software. For details, see Choosing a Product Installation Directory.
   RUN_DOMAIN_WIZARD | true or yes to run the Configuration Wizard and create a domain as part of the installation, false or no to skip it. If you choose to run the Configuration Wizard, you must specify values for the appropriate data-values as listed in the following rows in this table. For more information, see Using the Configuration Wizard at the following URL: http://e-docs.bea.com/platform/docs70/confgwiz/index.html
   The remaining values apply to options for the Configuration Wizard.
   domain.directory | The full path to the domain directory. The name of the domain directory should match the name of the domain. Note: On UNIX systems, do not include spaces in the path of the domain directory.
   C_domainName | Name of the domain to be created. The name must match the directory name specified for domain.directory. Note: On UNIX systems, do not include spaces in the domain name.
   C_serverName | Name of the server to be configured. Used as the server name for standalone servers, the name of the Administration Server for domains with Managed Servers and Clustered Servers, and the name of the Managed Server for Managed Server with owning Admin Server configurations. Note: Do not include spaces in the server name.
   C_username | An administrative user name to start the server and access the Administration Console. Do not include spaces or XML reserved characters in this name.
   C_password | A password for the administrative user. It must contain at least eight characters but no more than 20 characters. Do not use spaces or XML reserved characters.
   C_serverListenAddress | The system IP address or DNS name for the server. You can leave this blank if you want to use localhost and the server IP address to access the server and the Administration Console.
   C_serverListenPort | A dedicated TCP/IP port number for the Administration Server. This number specifies the port at which the server listens for connections. The port number can be any integer from 1 to 65535.
   C_serverSSLListenPort | A dedicated secure listen port number for the Administration Server. The secure listen port number is used for secure Web connections based on the secure sockets layer (SSL) protocol. The port number can be any integer from 1 to 65535 and cannot be the same port as the C_serverListenPort.
   ClusterName | Name of the cluster to be created. This data-value is only applicable if you are creating a cluster. Note: Do not include spaces in the cluster name.
   ClusterPort | The MultiCast port used by the Administration Server to communicate with clustered servers. Typically, 7777. This data-value is only applicable if you are creating a cluster.
   ClusterMCAddr | The cluster MultiCast IP address used by the Administration Server to communicate with clustered servers. Typically, 237.0.0.1. This value must be a class D IP address. Valid MultiCast addresses begin with 237, 238, or 239. This data-value is only applicable if you are creating a cluster.
   ADMIN_HOST_NAME_OR_IP | The Administration Server name or IP address. Used when configuring a Managed Server.
   ADMIN_LISTEN_PORT | The port at which the Administration Server listens. Used when configuring a Managed Server.
   MANAGED_SERVER_ REGISTERED_NAME_IN_ADMIN | The machine or server name as registered with the Administration Server. Used when configuring a Managed Server.
   SERVER-RUN-AS | The type of server configuration to be created by the Configuration Wizard: Single Server (Standalone Server), Admin Server with Managed Server(s), Admin Server with Clustered Managed Server(s), or Managed Server (with owning Admin Server configuration).
   selectedJar | The full path of the template JAR file used by the Configuration Wizard to create the domain and configure servers.
   INSTALL_NT_SERVICE (Windows systems only) | yes to install the configured server as a Windows service; no to skip installing the configured server as a Windows service. Note: This data-value pair is used only if the selected template supports installing the server as a Windows service. If it does not, the value is ignored. This value is ignored on UNIX systems.
   INSTALL_WINDOWS_STARTUP_MENU (Windows systems only) | yes to add an option to the Windows Start menu to start the server; no (the default value) to skip the Start menu option. Note: This data-value pair is only used if the selected template supports installing Start menu options. If not, the value is ignored. This value is ignored on UNIX systems.
   DB_EMAIL_HOST | The default e-mail or SMTP server. Note: This data-value pair is used only if the selected template supports WebLogic Integration functionality. If it does not, the value is ignored.
   DB_EMAIL_ADDRESS | The address from which e-mail can be sent by a workflow instance in WebLogic Integration. Note: This data-value pair is used only if the selected template supports WebLogic Integration functionality. If it does not, the value is ignored.
   managedServers (data group) | The type of configuration for the group of Managed Servers in the domain. This data group is relevant only when you select "Admin Server with Managed Server(s)" as the value for SERVER-RUN-AS. For each Managed Server in your configuration, specify values for the following: managedServerRegName—the name of the server that is registered with the Administration Server. Use alphanumeric characters only; do not include spaces. managedServerHostIP—the IP address or DNS name of the machine on which the server is installed. managedServerListenPort—the listen port for the server. managedServerSSLListenPort—the secure listen port for the server.
   clusterServers (data group) | The type of configuration for the group of clustered Managed Servers in the domain. This data group is relevant only when you select "Admin Server with Clustered Managed Server(s)" as the value for SERVER-RUN-AS. For each server in the cluster, specify values for the following: clusterServerRegName—the name of the server that is registered with the Administration Server. Alphanumeric characters only; do not include spaces. clusterServerHostIP—the IP address or DNS name of the machine on which the server is installed. clusterServerListenPort—the listen port for the server. clusterServerSSLListenPort—the secure listen port for the server.

For more information on the Configuration Wizard and the options you can select, see Using the Configuration Wizard at the following URL:

>     http://e-docs.bea.com/platform/docs70/confgwiz/index.html

Starting the Silent-Mode Installation Process on a Windows System

To start the silent-mode installation process on a Windows system, follow these steps:

1. Log in to the Windows system.

   If you want to install WebLogic Platform as a Windows service, you must have Administrator privileges. For information about installing WebLogic Platform as a Windows service, see "Setting Up a WebLogic Server Instance as a Windows Service" in the BEA WebLogic Server Administration Guide at the following URL:

   >     http://e-docs.bea.com/wls/docs70/adminguide/startstop.html#SettingUpServerAsWindowsService

2. Open an MS-DOS command prompt window.

3. Go to the directory that contains the installation file and launch the installation procedure by entering the following command, making sure to specify the full pathname of the silent.xml template file:

   filename.exe -mode=silent -silent_xml=full_path_to_silent.xml

   Here filename.exe is the name of the WebLogic Platform installation file, and full_path_to_silent.xml is the full path to the silent.xml template file.

   Note: To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line. For example:

   platform XXX_win32.exe -mode=silent -silent_xml=D:\silent.xml -log=D:\logs\platform_install.log

   The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file. In the filename used in this example, XXX is the version number of the software you are installing.

Starting the Silent-Mode Installation Process on a UNIX System

The WebLogic Platform installation program requires a Java run-time environment (JRE) to run. A Java 2 Software Development Kit (SDK), which includes a JRE, is bundled in the Windows installation program, and in some UNIX installation programs (those with filenames ending in .bin). For other UNIX platforms, the WebLogic Platform installation program does not include the Java 2 SDK. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have the appropriate version of the Java 2 SDK installed on your system, and include the bin directory of the SDK at the front of the PATH variable. It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory.

Starting Silent-Mode Installation for .bin Installation Files

Note: Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

To start the silent-mode installation process using installation files ending in .bin, follow these steps:

1. Log in to the target UNIX system.

2. Open a command-line shell.

3. Go to the directory that contains the installation file and launch the installation procedure by entering the following command, making sure to specify the full pathname of the silent.xml template file:

   chmod a+x filename

   ./filename.bin -mode=silent -silent_xml=/full_path_to_silent.xml

   Here filename.bin is the name of the WebLogic Platform installation file, and full_path_to_silent.xml is the full path to the silent.xml template file.

   Note: To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line. For example:

   platform XXX_solaris.bin -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/platform_install.log

   The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file. In the filename used in this example, XXX is the version number of the software you are installing.

Starting Silent-Mode Installation for .jar Installation Files

Note: Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

To start the silent-mode installation process for installation files ending in .jar, follow these steps:

1. Log in to the target UNIX system.

2. Open a command-line shell.

3. Include the bin directory of the appropriate SDK at the beginning of the PATH variable on the target system. For example:

   PATH=JAVA_HOME/bin:$PATH
   export PATH

   Here JAVA_HOME is the full path to the SDK directory.

4. Go to the directory that contains the installation file and start the installation procedure as described in the following table, making sure to specify the full pathname of the silent.xml template file.

   If you are . . . | Enter the following command . . .
   --- | ---
   Installing on a UNIX platform other than AIX | java -jar filename.jar -mode=silent -silent_xml=/full_path_to_silent.xml
   Installing on an AIX platform | java -classpath filename.jar com.bea.installer.BEAInstallController -mode=silent -silent_xml=/full_path_to_silent.xml

   In both cases, filename.jar is the name of the WebLogic Platform installation file (for example pj_platform XXX_generic.jar, where XXX is the version number of the software you are installing) and full_path_to_silent.xml is the full path to the silent.xml template file.

   Platform support sometimes varies by service pack release. To ensure you are installing the product on a supported platform, see the Supported Platforms page at the following URL:

   http://e-docs.bea.com/platform/docs70/support/index.html

   Note: To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line. For example:

   pj_platform XXX_generic.jar -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/platform_install.log

   The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file. In the filename used in this example, XXX is the version number of the software you are installing.

Sample Template Files for Silent-Mode Installation

This section provides samples of template files you can use for various types of domain configuration during a silent installation:

- Comprehensive Template File Sample

- Sample Template for Configuring a Domain with an Administration Server with Managed Servers

- Sample Template for Configuring a Cluster of Managed Servers

- Sample Template for Adding a Managed Server to an Existing Domain

You can download or copy the files in this section and modify them for your own needs, or study the differences (highlighted in bold) among the latter three templates, as a way of learning which parameter settings control which aspects of a configuration.

To learn more about the process of configuring domains with the Configuration Wizard, see "Creating a New WebLogic Domain" in Using the Configuration Wizard at:

>     http://e-docs.bea.com/platform/docs70/confgwiz/createdom.html

Comprehensive Template File Sample

The sample template shown in Listing 4-1 illustrates how you can configure a wide-ranging WebLogic Platform domain with the functionality of all components: WebLogic Server, WebLogic Workshop, WebLogic Integration, and WebLogic Portal.

To download this template from a browser, complete the following steps:

1. Click the following link:

   http://e-docs.bea.com/platform/docs70/install/scripts/silent-comp.xml

2. In the popup window that is displayed, choose File—> Save As...

3. Specify the file name silent.xml and save it in the directory containing the WebLogic Platform installation program.

In addition to showing you how template files are structured, this file also provides you with a simple method of putting together your own template file. You can modify it in accordance with Table 4-1, and use it to install WebLogic Platform 7.0 in silent mode.

Listing 4-1 Comprehensive Template File Sample

>     <?xml version="1.0" encoding="UTF-8"?>

>     <domain-template-descriptor>

>     <input-fields>
>        <data-value name="BEAHOME"                   value="C:\bea" />
>        <data-value name="USER_INSTALL_DIR"          value="C:\bea\weblogic700" />
>        <data-value name="RUN_DOMAIN_WIZARD"         value="true" />

>     <!--The following values are used by the Configuration Wizard to create and
>      configure a domain.-->

>        <data-value name="domain.directory"  value="C:\bea\user_domains\mydomain" />
>        <data-value name="C_domainName"               value="mydomain" />
>        <data-value name="C_serverName"               value="myserver" />
>        <data-value name="C_username"                 value="system" />
>        <data-value name="C_password"                 value="weblogic" />
>        <data-value name="C_serverListenAddress"      value="" />
>        <data-value name="C_serverListenPort"         value="7001" />
>        <data-value name="C_serverSSLListenPort"      value="7002" />

>     <!--If you are configuring an Admin Server with Clustered Managed Servers, please uncomment the following.-->
>     <!--  <data-value name="ClusterName"                value="mycluster" />  -->
>     <!--  <data-value name="ClusterPort"                value="7777" />       -->
>     <!--  <data-value name="ClusterMCAddr"              value="237.0.0.1" />  -->

>     <!--The selectedJar value determines the template that the Configuration Wizard
>      uses to create a domain and configure servers.-->

>        <data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />

>     <!--The SERVER-RUN-AS value determines the server configuration that the
>      Configuration Wizard creates. There are four options as indicated by the
>      following lines. Comment out the three options you do not want to use.-->

>             <data-value name="SERVER-RUN-AS" value="Single Server (Standalone Server)" />
>     <!--    <data-value name="SERVER-RUN-AS" value="Admin Server with Managed Server(s)" /> -->
>     <!--    <data-value name="SERVER-RUN-AS" value="Admin Server with Clustered Managed Server(s)" /> -->
>     <!--    <data-value name="SERVER-RUN-AS" value="Managed Server (with owning Admin Server configuration)" /> -->

>     <!--The following four data-values depend on options selected in the
>     Configuration Wizard template specified above. If the related options are not
>     selected in the template, the values for the following four data-values are
>     ignored.-->

>        <data-value name="INSTALL_NT_SERVICE"            value="no" />
>        <data-value name="INSTALL_WINDOWS_STARTUP_MENU"  value="no" />
>        <data-value name="DB_EMAIL_HOST"                 value="myserver"   />
>        <data-value name="DB_EMAIL_ADDRESS"              value="name@bea.com"  />

>     <!--   For Portal and Platform domain, please uncomment the following -->

>      <!--    <file-dir-customization> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/tools" -->
>      <!--            targetDir="beaApps/portalApp/tools"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/toolSupport" -->
>      <!--            targetDir="beaApps/portalApp/toolSupport"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/datasync" -->
>      <!--            targetDir="beaApps/portalApp/datasync"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/paymentWSApp" -->
>      <!--            targetDir="beaApps/paymentWSApp"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/taxWSApp" -->
>      <!--            targetDir="beaApps/taxWSApp"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/jars" -->
>      <!--            targetDir="beaApps/portalApp"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/projects/portalApp-project" -->
>      <!--            targetDir="beaApps/portalApp-project"/> -->
>      <!--     </file-dir-customization> -->

>     <!--The managedServers data group determines the configuration of the group of
>      managed servers in the domain. This data group applies only when you select "Admin
>      Server with Managed Server(s)" as the value for SERVER-RUN-AS. To use this data
>      group, uncomment all applicable lines.-->

>     <!--    <data-group name="managedServers"> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="managedServerRegName"   value="managed1"  /> -->
>     <!--          <data-value name="managedServerHostIP"        value="host1" /> -->
>     <!--          <data-value name="managedServerListenPort"    value="1001"  /> -->
>     <!--          <data-value name="managedServerSSLListenPort" value="1002"  /> -->
>     <!--       </data-element> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="managedServerRegName"    value="managed2" /> -->
>     <!--          <data-value name="managedServerHostIP"        value="host2" /> -->
>     <!--          <data-value name="managedServerListenPort"    value="2001"  /> -->
>     <!--          <data-value name="managedServerSSLListenPort"  value="2002"  /> -->
>     <!--       </data-element> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="managedServerRegName"    value="managed3" /> -->
>     <!--          <data-value name="managedServerHostIP"     value="host3"    /> -->
>     <!--          <data-value name="managedServerListenPort"    value="3001" /> -->
>     <!--          <data-value name="managedServerSSLListenPort" value="3002" /> -->
>     <!--       </data-element> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="managedServerRegName"    value="managed4" /> -->
>     <!--          <data-value name="managedServerHostIP"     value="host4"    /> -->
>     <!--          <data-value name="managedServerListenPort" value="4001"     /> -->
>     <!--          <data-value name="managedServerSSLListenPort" value="4002"  /> -->
>     <!--       </data-element> -->
>     <!--       </data-group> -->

>     <!--The clusterServers data group determines the configuration of the group of
>      managed clustered servers in the domain. This data group applies only when you
>      select "Admin Server with Clustered Managed Server(s)" as the value for
>      SERVER-RUN-AS. To use this data group, uncomment all applicable lines.-->

>     <!--    <data-group name="clusterServers"> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="clusterServerRegName"    value="cluster1" /> -->
>     <!--          <data-value name="clusterServerHostIP"       value="host1" /> -->
>     <!--          <data-value name="clusterServerListenPort"   value="1001"  /> -->
>     <!--          <data-value name="clusterServerSSLListenPort"  value="1002" /> -->
>     <!--       </data-element> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="clusterServerRegName"     value="cluster2" /> -->
>     <!--          <data-value name="clusterServerHostIP"       value="host2" /> -->
>     <!--          <data-value name="clusterServerListenPort"    value="2002"  /> -->
>     <!--          <data-value name="clusterServerSSLListenPort" value="2003"  /> -->
>     <!--       </data-element> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="clusterServerRegName"     value="cluster3" /> -->
>     <!--          <data-value name="clusterServerHostIP"      value="host3"    /> -->
>     <!--          <data-value name="clusterServerListenPort"    value="3003"  /> -->
>     <!--          <data-value name="clusterServerSSLListenPort" value="3004"  /> -->
>     <!--       </data-element> -->
>     <!--       <data-element> -->
>     <!--          <data-value name="clusterServerRegName"     value="cluster4" /> -->
>     <!--          <data-value name="clusterServerHostIP"        value="host4" /> -->
>     <!--          <data-value name="clusterServerListenPort"   value="4004"  /> -->
>     <!--          <data-value name="clusterServerSSLListenPort"  value="4005" /> -->
>     <!--       </data-element> -->
>     <!--    </data-group> -->

>         </input-fields>

>     </domain-template-descriptor>

Sample Template for Configuring a Domain with an Administration Server with Managed Servers

The sample template shown in Listing 4-2 can be used for configuring a domain that consists of an administration server plus one or more managed servers during a silent installation. The strings highlighted in bold are significant in defining the configuration. Compare the settings for these strings to the settings for corresponding strings in the other sample template files.

To download this template from a browser, complete the following steps:

1. Click the following link:

   http://e-docs.bea.com/platform/docs70/install/scripts/silent-as-ms.xml

2. In the popup window that is displayed, choose File—> Save As...

3. Specify the file name silent.xml and save it in the directory containing the WebLogic Platform installation program.

You can modify this file in accordance with Table 4-1, and use it to install WebLogic Platform 7.0 in silent mode.

For more information about how to configure a domain with an administration server and one or more managed servers, see "Creating a Domain with Administration Server and Managed Servers" in Using the Configuration Wizard at:

http://e-docs.bea.com/platform/docs70/confgwiz/creatdom.html

Listing 4-2 Configuring a Domain with an Administration Server with Managed Server(s)

>     <?xml version="1.0" encoding="UTF-8" ?>

>     <domain-template-descriptor>

>     <input-fields>
>          <data-value name="BEAHOME"            value="C:\bea" />
>          <data-value name="USER_INSTALL_DIR"   value="C:\bea\weblogic700" />
>          <data-value name="RUN_DOMAIN_WIZARD"  value="true" />

>     <!--The following values are used by the Configuration Wizard to create and
>     configure a domain.-->

>          <data-value name="domain.directory"     value="C:\bea\user_domains\d1" />
>          <data-value name="C_domainName"          value="d1"        />
>          <data-value name="C_serverName"          value="admin"     />
>          <data-value name="C_username"            value="system"    />
>          <data-value name="C_password"            value="weblogic"  />
>          <data-value name="C_serverListenAddress" value=""          />
>          <data-value name="C_serverListenPort"    value="8001"      />
>          <data-value name="C_serverSSLListenPort" value="8002"      />

>     <!-- The selectedJar value determines the template that the Configuration Wizard
>     uses to create a domain and configure servers.-->
>          <data-value name="selectedJar" value="C:\bea\weblogic700\common\\templates\domains\wls.jar" />

>      <!--   For Portal and Platform domain, please uncomment the following -->

>      <!--    <file-dir-customization>                                -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/tools"        -->
>      <!--            targetDir="beaApps/portalApp/tools"/>           -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/toolSupport"  -->
>      <!--            targetDir="beaApps/portalApp/toolSupport"/>     -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/datasync"     -->
>      <!--            targetDir="beaApps/portalApp/datasync"/>        -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/paymentWSApp"    -->
>      <!--            targetDir="beaApps/paymentWSApp"/>              -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/taxWSApp"        -->
>      <!--            targetDir="beaApps/taxWSApp"/>                  -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/jars"            -->
>      <!--            targetDir="beaApps/portalApp"/>                 -->
>      <!--         <dirCopy  srcDir="bea/portal/projects/portalApp-project" -->
>      <!--            targetDir="beaApps/portalApp-project"/>         -->
>      <!--     </file-dir-customization>                              -->

>      <!--The following four data-values depend on options selected in the
>     Configuration Wizard template specified above. If the related options are not
>     selected in the template, the values for the following four data-values are
>     ignored.-->

>        <data-value name="INSTALL_NT_SERVICE"            value="no" />
>        <data-value name="INSTALL_WINDOWS_STARTUP_MENU"  value="no" />
>        <data-value name="DB_EMAIL_HOST"                 value="myserver"   />
>        <data-value name="DB_EMAIL_ADDRESS"              value="name@bea.com"  />

>     <!-- The SERVER-RUN-AS value determines the server configuration that the
>     Configuration Wizard creates.-->

>     <data-value name="SERVER-RUN-AS" value="Admin Server with Managed Server(s)" />
>          <data-group name="managedServers">
>              <data-element>
>                  <data-value name="managedServerRegName"       value="ms1" />
>                  <data-value name="managedServerHostIP"        value="host1" />
>                  <data-value name="managedServerListenPort"    value="1001" />
>                  <data-value name="managedServerSSLListenPort" value="1002" />
>              </data-element>

>              <data-element>
>                   <data-value name="managedServerRegName"       value="ms2" />
>                   <data-value name="managedServerHostIP"        value="host2" />
>                   <data-value name="managedServerListenPort"    value="2001" />
>                   <data-value name="managedServerSSLListenPort" value="2002" />
>              </data-element>
>         </data-group>

>     </input-fields>

>     </domain-template-descriptor>

Sample Template for Configuring a Cluster of Managed Servers

The sample template shown in Listing 4-3 can be used for configuring a domain that consists of an administration server plus a cluster of managed servers during a silent installation. The strings highlighted in bold are significant in defining the configuration. Compare the settings for these strings to the settings for corresponding strings in the other sample template files.

To download this template from a browser, complete the following steps:

1. Click the following link:

   http://e-docs.bea.com/platform/docs70/install/scripts/silent-clus.xml

2. In the popup window that is displayed, choose File—> Save As...

3. Specify the file name silent.xml and save it in the directory containing the WebLogic Platform installation program.

You can modify this file in accordance with Table 4-1, and use it to install WebLogic Platform 7.0 in silent mode.

For more information about how to configure a domain with an administration server for a cluster of managed servers, see "Creating a Domain with Administration Server and Cluster" in Using the Configuration Wizard at:

http://e-docs.bea.com/platform/docs70/confgwiz/creatdom.html

Listing 4-3 Configuring a Domain with Administration server and Clustered Managed Server(s)

>     <?xml version="1.0" encoding="UTF-8" ?>

>     <domain-template-descriptor>

>     <input-fields>
>            <data-value name="BEAHOME"             value="C:\bea" />
>            <data-value name="USER_INSTALL_DIR"    value="C:\bea\weblogic700" />
>            <data-value name="RUN_DOMAIN_WIZARD"   value="true" />

>     <!-- The following values are used by the Configuration Wizard to create and configure a domain.-->
>             <data-value name="domain.directory"  value="C:\bea\user_domains\myCluster" />
>            <data-value name="C_domainName"             value="myCluster" />
>            <data-value name="C_serverName"             value="admin" />
>            <data-value name="C_username"               value="system" />
>            <data-value name="C_password"               value="weblogic" />
>            <data-value name="C_serverListenAddress"    value="localhost" />
>            <data-value name="C_serverListenPort"       value="8001" />
>            <data-value name="C_serverSSLListenPort"    value="8002" />
>            <data-value name="ClusterName"              value="mycluster" />
>            <data-value name="ClusterPort"              value="7777" />
>            <data-value name="ClusterMCAddr"            value="237.0.0.1" />

>     <!-- The selectedJar value determines the template that the Configuration
>     Wizard uses to create a domain and configure servers.-->
>            <data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />

>     <!--   For Portal and Platform domain, please uncomment the following -->

>      <!--    <file-dir-customization> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/tools"          -->
>      <!--            targetDir="beaApps/portalApp/tools"/>             -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/toolSupport"    -->
>      <!--            targetDir="beaApps/portalApp/toolSupport"/>       -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/datasync"       -->
>      <!--            targetDir="beaApps/portalApp/datasync"/>          -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/paymentWSApp"      -->
>      <!--            targetDir="beaApps/paymentWSApp"/>                -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/taxWSApp"          -->
>      <!--            targetDir="beaApps/taxWSApp"/>                    -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/jars"              -->
>      <!--            targetDir="beaApps/portalApp"/>                   -->
>      <!--         <dirCopy  srcDir="bea/portal/projects/portalApp-project" -->
>      <!--            targetDir="beaApps/portalApp-project"/>           -->
>      <!--     </file-dir-customization>                                -->

>      <!--The following four data-values depend on options selected in the
>     Configuration Wizard template specified above. If the related options are not
>     selected in the template, the values for the following four data-values are
>     ignored.-->

>        <data-value name="INSTALL_NT_SERVICE"             value="no" />
>        <data-value name="INSTALL_WINDOWS_STARTUP_MENU"   value="no" />
>        <data-value name="DB_EMAIL_HOST"                  value="myserver"   />
>        <data-value name="DB_EMAIL_ADDRESS"               value="name@bea.com"  />

>     <!-- The SERVER-RUN-AS value determines the server configuration that the
>     Configuration Wizard creates.-->

>            <data-value name="SERVER-RUN-AS" value="Admin Server with Clustered Managed Server(s)" />

>          <data-group name="clusterServers">
>            <data-element>
>                 <data-value name="clusterServerRegName"         value="cs1" />
>                 <data-value name="clusterServerHostIP"          value="host1" />
>                 <data-value name="clusterServerListenPort"      value="1001" />
>                 <data-value name="clusterServerSSLListenPort"   value="1002" />
>            </data-element>

>            <data-element>
>                <data-value name="clusterServerRegName"          value="cs2" />
>                <data-value name="clusterServerHostIP"           value="host2" />
>                <data-value name="clusterServerListenPort"       value="2001" />
>                <data-value name="clusterServerSSLListenPort"    value="2002" />
>            </data-element>
>          </data-group>

>     </input-fields>

>     </domain-template-descriptor>

Sample Template for Adding a Managed Server to an Existing Domain

The sample template shown in Listing 4-4 can be used for adding a managed server to an existing domain. The strings highlighted in bold are significant in defining the configuration. Compare the settings for these strings to the settings for corresponding strings in the other sample template files.

To download this template from a browser, complete the following steps:

1. Click the following link:

   http://e-docs.bea.com/platform/docs70/install/scripts/silent-add.xml

2. In the popup window that is displayed, choose File—> Save As...

3. Specify the file name silent.xml and save it in the directory containing the WebLogic Platform installation program.

You can modify this file in accordance with Table 4-1, and use it to install WebLogic Platform 7.0 in silent mode.

For more information about how to add a managed server to an existing domain, see "Extending an Existing WebLogic Domain" in Using the Configuration Wizard at:

http://e-docs.bea.com/platform/docs70/confgwiz/creatdom.html

Listing 4-4 Template for Adding a Managed Server to an Existing Domain

>     <?xml version="1.0" encoding="UTF-8" ?>

>     <domain-template-descriptor>

>     <input-fields>
>               <data-value name="BEAHOME"          value="C:\bea" />
>               <data-value name="USER_INSTALL_DIR" value="C:\bea\weblogic700" />
>               <data-value name="RUN_DOMAIN_WIZARD" value="true" />

>     <!-- The following values are used by the Configuration Wizard to create and configure a domain.-->
>               <data-value name="domain.directory" value="C:\bea\user_domains\d2" />
>               <data-value name="C_domainName"           value="d2" />
>               <data-value name="C_serverName"           value="ms1" />
>               <data-value name="C_username"             value="system" />
>               <data-value name="C_password"             value="weblogic" />
>               <data-value name="C_serverListenAddress"  value="" />
>               <data-value name="C_serverListenPort"     value="8001" />
>               <data-value name="C_serverSSLListenPort"  value="8002" />
>               <data-value name="ADMIN_HOST_NAME_OR_IP"  value="adminserver" />
>               <data-value name="ADMIN_LISTEN_PORT"      value="9999" />
>               <data-value name="MANAGED_SERVER_REGISTERED_NAME_IN_ADMIN" value="mmss1" />
>               <data-value name="MANAGED_SERVER_REGISTERED_NAME_IN_ADMIN" value="mmss2" />

>      <!-- The selectedJar value determines the template that the Configuration Wizard
>     uses to create a domain and configure servers.-->
>               <data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />

>     <!--   For Portal and Platform domain, please uncomment the following -->

>      <!--    <file-dir-customization> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/tools" -->
>      <!--            targetDir="beaApps/portalApp/tools"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/toolSupport" -->
>      <!--            targetDir="beaApps/portalApp/toolSupport"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/webapps/datasync" -->
>      <!--            targetDir="beaApps/portalApp/datasync"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/paymentWSApp" -->
>      <!--            targetDir="beaApps/paymentWSApp"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/taxWSApp" -->
>      <!--            targetDir="beaApps/taxWSApp"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/apps/jars" -->
>      <!--            targetDir="beaApps/portalApp"/> -->
>      <!--         <dirCopy  srcDir="bea/portal/projects/portalApp-project" -->
>      <!--            targetDir="beaApps/portalApp-project"/> -->
>      <!--     </file-dir-customization> -->

>     <!-- The SERVER-RUN-AS value determines the server configuration that the
>     Configuration Wizard creates.-->

>            <data-value name="SERVER-RUN-AS" value="Managed Server (with owning Admin Server configuration)" />
>     </input-fields>

>     </domain-template-descriptor>

What's Next?

When you install WebLogic Platform, an evaluation license file is also installed in the BEA Home directory that you created during installation so that you can start using the product immediately. We recommend that you use the QuickStart application to familiarize yourself with the software, take the WebLogic Platform Tour, and execute the samples provided. For additional information, see Performing Post-Installation Tasks.