bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Platform > Using the Configuration Wizard > Creating a New WebLogic Domain Using Silent Mode |
Using the Configuration Wizard
|
Creating a New WebLogic Domain Using Silent Mode
The following sections describe how to create a WebLogic domain using the Configuration Wizard in silent mode:
About Silent-Mode Configuration
Silent-mode configuration is a way of specifying domain configuration settings only once and then using those settings to create the domain on many machines. During configuration in silent mode, the Configuration Wizard reads the settings for your configuration from an XML file that you create prior to starting the domain creation process. The Configuration Wizard does not display any configuration options requiring user input while it is creating the domain. After the domain is created, a confirmation message is displayed on the console. Silent-mode configuration works on both Windows and UNIX systems.
The instructions in this section are based on the assumption that you have already installed BEA WebLogic Platform. For more information, see Installing BEA WebLogic Platform at http://download.oracle.com/docs/cd/E13196_01/platform/docs70/install/index.html.
Note: You can also create a domain in silent mode when you perform a silent-mode installation. When you do so, you define installation settings, as well as configuration settings. For more information, see "Installing WebLogic Platform Using Silent-Mode Installation" at http://download.oracle.com/docs/cd/E13196_01/platform/docs70/install/silent.html.
Using Silent-Mode Configuration: Main Steps
The silent-mode configuration process comprises two tasks:
For a detailed procedure, see Creating a Silent-Mode Configuration Template File. For a sample template file, see Sample Template Files for Silent-Mode Configuration.
For a detailed procedure, see Starting the Silent-Mode Configuration Process.
Important Notes About Silent-Mode Configuration
You need to be aware of the following items when you are creating a domain in silent mode:
Creating a Silent-Mode Configuration Template File
When you create a domain in silent mode, the Configuration Wizard does not prompt you to provide information in real time. Instead, it queries an XML file, called silent_cw.xml, to determine which values to use for required configuration settings. Therefore, before you can run the Configuration Wizard in silent mode, you must first create a silent_cw.xml file in which you specify the configuration settings that you want to have invoked.
To create a template file for use in the silent-mode configuration process, follow these steps:
Starting the Silent-Mode Configuration Process
To start the Configuration Wizard in silent mode on a Windows or UNIX system, follow these steps:
Sample Template Files for Silent-Mode Configuration
This section provides samples of template files you can use for various types of domain configuration:
These samples use the WLS Domain Template wls.jar, but you can specify other templates as required. WebLogic Platform provides preconfigured domain templates as part of the product installation. These preconfigured templates are located in the common\templates\domains subdirectory of the product installation directory (named weblogic700 by default). For more information about the template to select for your configuration, see Determine Which Configuration Wizard Template to Use.
In addition to showing you how a template file is structured, these samples also provide you with a simple method of putting together your own template file. You can use these samples, modified in accordance with Table 3-1, to create a template file for your configuration. For instructions, see Creating a Silent-Mode Configuration Template File. You can then use your template file to create a domain in silent mode.
Sample Template for Creating a Single Server Domain
The following sample template can be used for configuring a domain that consists of a single server. Running a WebLogic domain as a single server means that the server instance acts as both the Administration Server and Managed Server. There will be no failover functionality accommodated by this configuration because there is a single server instance. In this template, a domain named mydomain that consists of a single server, myserver, is created.
Listing 3-1 Configuring a Single Server Domain in Silent Mode
<?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" />
<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="weblogic" />
<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" />
<data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />
<data-value name="INSTALL_NT_SERVICE" value="no" />
<data-value name="INSTALL_WINDOWS_STARTUP_MENU" value="no" />
<!--For domains containing WebLogic Integration functionality, please uncomment the following -->
<!-- <data-value name="DB_EMAIL_HOST" value="myserver" /> -->
<!-- <data-value name="DB_EMAIL_ADDRESS" value="name@bea.com" /> -->
<!-- For Portal and Platform domains, 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> -->
<data-value name="SERVER-RUN-AS" value="Single Server (Standalone Server)" />
</input-fields>
</domain-template-descriptor>
Sample Template for Configuring a Domain with an Administration Server with Managed Servers
The following sample template can be used for configuring a domain that consists of an administration server plus one or more managed servers. In this template, a domain with an Administration Server myserver, and three Managed Servers: managed1, managed2, and managed3 is created.
Listing 3-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" />
<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="weblogic" />
<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" />
<data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />
<data-value name="INSTALL_NT_SERVICE" value="no" />
<data-value name="INSTALL_WINDOWS_STARTUP_MENU" value="no" />
<!--For domains containing WebLogic Integration functionality, please uncomment the following -->
<!-- <data-value name="DB_EMAIL_HOST" value="myserver" /> -->
<!-- <data-value name="DB_EMAIL_ADDRESS" value="name@bea.com" /> -->
<!-- For Portal and Platform domains, 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> -->
<data-value name="SERVER-RUN-AS" value="Admin Server with Managed Server(s)" />
<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-group>
</input-fields>
</domain-template-descriptor>
Sample Template for Configuring an Administration Server and a Cluster of Managed Servers
The following sample template can be used for configuring a domain that consists of an administration server plus a cluster of managed servers. In this template, a domain with an Administration Server myserver, a cluster named mycluster, and four clustered Managed Servers, cluster1, cluster2, cluster3, and cluster4 is created.
Listing 3-3 Configuring a Domain with an Administration Server with 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" />
<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="weblogic" />
<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" />
<data-value name="ClusterName" value="mycluster" />
<data-value name="ClusterPort" value="7777" />
<data-value name="ClusterMCAddr" value="237.0.0.1" />
<data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />
<data-value name="INSTALL_NT_SERVICE" value="no" />
<data-value name="INSTALL_WINDOWS_STARTUP_MENU" value="no" />
<!--For domains containing WebLogic Integration functionality, please uncomment the following -->
<!-- <data-value name="DB_EMAIL_HOST" value="myserver" /> -->
<!-- <data-value name="DB_EMAIL_ADDRESS" value="name@bea.com" /> -->
<!-- For Portal and Platform domains, 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> -->
<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="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 Adding a Managed Server to an Existing Domain
The following sample template can be used for adding a managed server to an existing domain. In this template, a Managed Server ms1 is added to a domain with an Administration Server named adminserver.
Listing 3-4 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" />
<data-value name="domain.directory" value="C:\bea\user_domains\mydomain" />
<data-value name="C_domainName" value="mydomain" />
<data-value name="C_serverName" value="ms1" />
<data-value name="C_username" value="weblogic" />
<data-value name="C_password" value="weblogic" />
<data-value name="C_serverListenAddress" value="" />
<data-value name="C_serverListenPort" value="7003" />
<data-value name="C_serverSSLListenPort" value="7004" />
<data-value name="selectedJar" value="C:\bea\weblogic700\common\templates\domains\wls.jar" />
<data-value name="INSTALL_NT_SERVICE" value="no" />
<data-value name="INSTALL_WINDOWS_STARTUP_MENU" value="no" />
<!--For domains containing WebLogic Integration functionality, please uncomment the following -->
<!-- <data-value name="DB_EMAIL_HOST" value="myserver" /> -->
<!-- <data-value name="DB_EMAIL_ADDRESS" value="name@bea.com" /> -->
<!-- For Portal and Platform domains, 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> -->
<data-value name="SERVER-RUN-AS" value="Managed Server (with owning Admin Server configuration)" />
<data-value name="ADMIN_HOST_NAME_OR_IP" value="adminserver" />
<data-value name="ADMIN_LISTEN_PORT" value="7001" />
<data-value name="MANAGED_SERVER_REGISTERED_NAME_IN_ADMIN" value="ms1" />
</input-fields>
</domain-template-descriptor>
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |