Creating WebLogic Configurations Using the Configuration Wizard

Creating a Script for Silent-Mode Configuration

Before you can run the Configuration Wizard in silent mode to create or extend a domain, as described in Starting in Silent Mode, you must first create a script in which you define the configuration settings for the domain. A sample script, based on the Basic WebLogic Server Domain template, is provided with the WebLogic Platform software in the common\templates\silent_scripts directory of your product installation. This sample script and additional scripts, based on other domain templates, are provided and described in Sample Configuration Scripts for Silent-Mode Configuration.

To create a script, do one of the following:

• Copy the contents of one of the sample scripts to a text file and edit it for your configuration (recommended)
• Open a new file in a text editor and manually specify the domain configuration settings (for experienced users of sample scripts)

Refer to the following sections for instructions on creating scripts for creating and extending domains:

• Creating a Script to Create a New Domain in Silent Mode
• Creating a Script to Extend an Existing Domain in Silent Mode

 

---

Creating a Script to Create a New Domain in Silent Mode

When you create a script, you specify operations to be performed by the Configuration Wizard when the script is executed. The following sections describe the operations that must be defined in the script to create a new domain:

• Step 1: Select the Configuration Template
• Step 2: Edit the Configuration Information
• Step 3: Create the Domain
• Step 4: Close the Configuration Template

Note: The code for each operation described in this section must be terminated by a semicolon.

Step 1: Select the Configuration Template

Select a configuration template to use as the basis of the domain you will create and configure. To select a configuration template, use the read operation, as follows:

read template from "template_jar_name";

Table 4-1 describes the single read template operation parameter for which you must specify a value.

 

In the following example, the Basic WebLogic Server Domain configuration template is specified with the absolute pathname for the template:

read template from "C:\bea\weblogic81\common\templates\domains\wls.jar";

Step 2: Edit the Configuration Information

Edit the default configuration information to create new configuration objects, edit existing values for configuration object attributes, or delete configuration objects.

Note: You can obtain information about your existing domain configuration from the config.xml and security.xml files in the template JAR file, or from the config.xml in the domain itself, once it is created. For information about the config.xml file, see WebLogic Server Configuration Reference at: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html.

You use silent mode to create and edit any valid configuration object and its child elements, except custom security objects. For more information about valid configuration objects, see WebLogic Server Configuration Reference at: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html.

The following table summarizes the edit operations described in the following sections.

 

Creating a Configuration Object

To create a configuration object, specify the type of object you want to create, assign it to a variable, and define the Name attribute. Then, you can set the remaining attributes (or edit the Name attribute), as described in Setting Configuration Object Attributes.

To create a configuration object, use the create operation, as follows:

create object_type "name" as variable;

Table 4-3 describes the create operation parameters for which you must specify values.

 

In the following example, a Server object is created and assigned to the variable s2, and the Name attribute is set to server_2:

create Server "server_2" as s2;

In the following example, a User object is created and assigned to the variable u1, and the Name attribute is set to user1:

create User "user1" as u1;

By default, the user is assigned to the group "Administrators."

Assigning an Existing Configuration Object to a Variable

Before you can edit an existing configuration object, the Configuration Wizard must find the object in the template and assign it to a variable. To assign a configuration object to a variable, use the find operation, as follows:

find object_type "name" as variable;

Table 4-4 describes the find operation parameters for which you must specify values.

 

In the following example, a Server object named "myserver" is assigned to the variable s1:

find Server "myserver" as s1;

Assigning an Existing Child Element to a Variable

Some configuration object types contain child elements. Before you can edit an existing child element, the Configuration Wizard must find the element in the template and assign it to a variable. To assign a child element to a variable, use the find operation, as follows:

find object_type.child_element "name.child_element_name" as variable;

Table 4-5 describes the find operation parameters for which you must specify values.

Note: Silent-mode configuration supports all child elements for the configuration object types. For a complete list of the child elements for the configuration objects, see WebLogic Server Configuration Reference at: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html.

 

In the following example, a Server object named "myserver" with a WebServer child element named "mywebserver" is assigned to the variable ws1:

find Server.WebServer "myserver.mywebserver" as ws1;

Setting Configuration Object Attributes

To set a configuration attribute, specify the variable and attribute name for it, as follows:

set variable.attribute "value";

Table 4-6 describes the parameters for which you must specify values.

 

In the following example, the ListenAddress and ListenPort attributes for the Server configuration object referenced by s2 (that is, server_2) are set to localhost and 7001, respectively:

set s2.ListenAdress "localhost";
set s2.ListenPort "7001";

Considerations for Setting the JDBC Connection Pool Properties Attribute

The JDBC Connection Pool Properties attribute specifies the list of properties passed to the JDBC Driver, and is used when creating physical database connections.

When specifying this attribute, ensure that you provide the complete list of the properties required by the JDBC Driver being used.

Because the values that you specify for the Properties attribute will override all values currently set, if you omit a value from the Properties list, that property will remain undefined, resulting in unexpected results.

Setting a Specific Attribute for a Child Element

To assign a value to an attribute for a child element, specify the variable assigned to the child element and the name of the attribute, as follows:

set variable.attribute "value";

Table 4-7 describes the parameters for which you must specify values.

 

In the following example, a Server named "myserver" with a WebServer child element named "mywebserver" is assigned to the variable ws1. Then, the LogFileName attribute for the webserver child element is assigned the value of c:\bea\weblogic\logs\newAccess.log.

find Server.WebServer "myserver.mywebserver" as ws1;
set ws1.LogFileName "c:\bea\weblogic\logs\newAcess.log";

Setting an Attribute for All Instances of a Child Element

To assign a value to an attribute for all instances of a particular type of child element, use the following format:

set variable.child_element.attribute "value";

Table 4-8 describes the parameters for which you must specify values.

 

In the following example, the server named "myserver" is assigned to the variable s1. Then, all ThreadCount attributes for the ExecuteQueue child element of the server referenced by s1 are set to 25:

find Server "myserver" as s1;
set s1.ExecuteQueue.ThreadCount "25";

Setting Attributes for Unnamed Child Elements

When the Name attribute of a child element instance is not defined, you cannot reference that child element individually. In this case, the only way you can assign a value to an attribute of an unnamed child element is by setting all instances of the child element attribute, as described in Setting an Attribute for All Instances of a Child Element.

Setting an HTTP Proxy Server for a Cluster

You can also use the set operation to designate an HTTP proxy server for a cluster as follows:

set variable.ProxyServer "unclustered_managed_server";

Note: Only an unclustered Managed Server can be used as a proxy server.

Table 4-9 describes the parameters for which you must specify values when setting an HTTP Proxy server.

 

In the following example, the cluster named myCluster is assigned to the variable mycluster. Then, the server AnUnClusteredServer is assigned to the attribute ProxyServer for the cluster referenced by mycluster.

create Cluster "myCluster" as mycluster;
set mycluster.ProxyServer "AnUnClusteredServer";

Setting Configuration Options When Creating a New Domain

You can also use the set operation to specify configuration options for the domain, as follows:

set configuration_option value;

Table 4-10 describes the parameters for which you must specify values.

 

In the following example, a Windows Start Menu shortcut for the domain is not created.

set CreateStartMenu "false";

Table 4-11 describes the configuration options that you can specify using the set operation.

 

Assigning Servers to Clusters

You can assign servers to clusters by using the assign Server operation as follows:

assign Server "server" to Cluster "cluster";

Table 4-12 describes the assign Server operation parameters for which you must specify a value.

 

In the following example, the servers named myServer1 and myServer2 are assigned to the cluster myCluster.

assign Server "myServer1,myServer2" to Cluster "myCluster";

Assigning All Applications and Services to Servers and Clusters

You can assign all the applications and services in a domain to servers and clusters by using the assign all operation as follows:

• To assign all applications to a server or cluster, use the assign all Applications operation as follows:

assign all Applications to Target "server_or_clusters"

In the following example, all applications in the domain are assigned to the targets AdminServer and Cluster1:

assign all Applications to Target "adminServer,cluster1";

• To assign all services to a server or cluster, use the assign all Services operation as follows:

assign all Services to Target "server_or_clusters";

In the following example, all services in the domain are assigned to the targets AdminServer and Cluster1:

assign all Services to Target "adminServer,cluster1";

Table 4-13 describes the single assign all operation parameter for which you must specify a value.

 

If you use the assign all Services operation, any of the following services that are defined in the config.xml for the domain, or that you added in this script, are assigned to the target server or cluster:

• MigratableRMIService
• Shutdownclass
• Startupclass
• FileT3
• RMCFactory
• MailSession
• MessagingBridge
• JMSConnectionFactory
• JDBCConnectionPool
• JDBCMultipool
• JDBCTxDataSource
• JDBCDataSource
• JDBCPoolComp
• JoltConnectionPool
• WLECConnectionPool
• WTCServer

Assigning Individual Applications to Servers and Clusters

You can assign individual applications and application components (such as Web applications and EJB modules) to a server or cluster using the assign Application operation as follows:

assign Application "application_names" to Target "server_or_clusters";

Table 4-14 describes the assign Application operation parameters for which you must specify a value.

 

In the following example, the applications named MedRecEAR and PhysicianEAR are assigned to the server myServer1.

assign Application "MedRecEAR, PhysicianEAR" to Target "myServer1";

In the following example, the application component SessionEJB for the application MedRecEAR is assigned to the server MedRecServer.

assign Application "MedRecEAR.SessionEJB" to Target "MedRecServer";

Assigning Individual Services to Servers and Clusters

You can assign an individual service to a server or cluster by name or category, as follows:

assign service_type "service_names" to Target "server_or_clusters";

Table 4-15 describes the assign operation parameters for which you must specify a value when you are assigning individual services to servers or clusters.

 

In the following example, the service MedRecJMSServer is assigned to the server myServer1.

assign JMSServer "MedRecJMSServer" to Target "myServer1";

In the following example, all JMS Servers are assigned to myServer1.

assign JMSServer "*" to Target "myServer1";

Creating Security Assignments

When you are creating a new domain, you can perform the following assignments:

• Assign users to groups—You can designate individual users as members of a particular group. Groups allow you to manage multiple users simultaneously. This is generally more efficient than managing each user individually.

Note: When you create a user, it is assigned automatically to the Administrators group.

• Assign groups to groups—You can designate one group a subgroup of another, to refine security management.

To assign users to groups, use the assign User operation as follows:

assign User "username" to Group "group";

To assign groups to groups, use the assign Group operation as follows:

assign Group "group" to Group "group";

Table 4-16 describes the assign operation parameters for which you must specify a value when you are assigning users and groups to groups.

 

In the following example, the user weblogic is assigned to the group Monitors and the group Deployers is assigned as a subgroup of the group Monitors.

assign User "weblogic" to Group "Monitors";
assign Group "Deployers" to Group "Administrators";

Removing Assignments Using the Unassign Operation

You can use the unassign operation to remove assignments using the same operations as the assign command. To do so, change assign to unassign and the to operator to from.

The following examples illustrate sample usage for the unassign operation:

unassign Application "MedRecEAR, PhysicianEAR" from Target "myServer1";
unassign all Services from Target "adminServer,cluster1";
unassign User "weblogic" from Group "Monitors";

Deleting a Configuration Object

To delete a configuration object, use the delete operation, as follows:

delete variable;

Table 4-17 describes the single delete operation parameter for which you must specify a value.

 

In the following example, the Server configuration object referenced by s2 (that is, server_2) is deleted:

delete s2;

Step 3: Create the Domain

To create the domain using the configuration settings that you have defined in step 2, use the write operation, as follows:

write domain to "domain_name";

Table 4-18 describes the single write operation parameter for which you must specify a value.

 

In the following example, the domain is created in the C:\bea\user_projects\ directory and is named wlsDomain:

write domain to "C:\bea\user_projects\wlsDomain";

Step 4: Close the Configuration Template

To close the configuration template, use the close operation, as follows:

close template;

When you have finished defining the configuration, save the script. You can name the script as desired, and pass the relative or full pathname for it to the config command, as described in Starting in Silent Mode.

 

---

Creating a Script to Extend an Existing Domain in Silent Mode

The following sections describe the steps that you must perform in the script to create a new domain.

• Step 1: Select the Domain Directory
• Step 2: Add the Extension Template to the Domain
• Step 3: Edit the Existing Configuration Information (Optional)
• Step 4: Update the Domain
• Step 5: Close the Domain

Note: Each operation described in this section must be terminated by a semicolon.

Step 1: Select the Domain Directory

To select a domain directory that you want to update with additional applications and services, use the read operation, as follows:

read domain from "domain_directory_name";

Table 4-19 describes the single read domain operation parameter for which you must specify a value.

 

In the following example, the absolute pathname to a domain named mydomain is specified:

read domain from "C:\bea\user_projects\domains\mydomain";

Step 2: Add the Extension Template to the Domain

An extension template defines applications and services, such as JDBC or JMS components, and startup/shutdown classes, that can be used to extend an existing domain. Use the add operation to add an extension template to the domain you specified using the read domain operation in step 1.

add template extension_template_jar_name;

Table 4-20 describes the single add template operation parameter for which you must specify a value.

 

In the following example, an extension template adding a basic Web application is specified, using the absolute pathname for the template:

add template "C:\bea\weblogic81\common\templates\applications\DefaultWebApp.jar";

Step 3: Edit the Existing Configuration Information (Optional)

You can edit the default configuration information to create new configuration objects, edit existing values for configuration object attributes, delete configuration objects, and assign applications and services to servers or clusters.The operations available for these tasks are the same for extending an domain and creating a new domain. For instructions about using these operations, see the following sections:

• Creating a Configuration Object
• Assigning an Existing Configuration Object to a Variable
• Setting Configuration Object Attributes
• Deleting a Configuration Object
• Assigning All Applications and Services to Servers and Clusters
• Assigning Individual Applications to Servers and Clusters
• Assigning Individual Services to Servers and Clusters

You can also set configuration options when extending a domain, as described in Setting Configuration Options When Extending a Domain.

You can use silent mode to create and edit any valid configuration object and its child elements, except security objects. For more information about valid configuration objects, see WebLogic Server Configuration Reference at: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html.

Setting Configuration Options When Extending a Domain

When you are extending a domain, you can use the set operation to specify configuration options for the domain as follows:

set configuration_option value;

Table 4-21 describes the parameters for which you must specify values.

 

Table 4-22 lists the configuration options that you can specify using the set operation when you are extending an existing domain.

 

Step 4: Update the Domain

Update the domain opened in the read domain operation, use the update operation, as follows:

update domain;

Note: You must specify the add template operation before you can update the domain.

Step 5: Close the Domain

To close the domain, use the close operation, as follows:

close domain;

When you have finished defining the configuration, save the script. You can name the script as desired, and pass the relative or full pathname for it to the config command, as described in Starting in Silent Mode.

 

---

Sample Configuration Scripts for Silent-Mode Configuration

The following sample scripts are provided to demonstrate the basic concepts required to create and update domains using silent-mode configuration.

Sample Scripts for Creating a New Domain from a Configuration Template

The following sections provide samples scripts you can use to create a new domain from a configuration template. Topics include:

• Sample Script Based on the Basic WebLogic Server Domain Template
• Sample Script Based on the Avitek Medical Records Sample Domain Template
• Sample Script Based on the Basic WebLogic Portal Domain Template

Sample Script Based on the Basic WebLogic Server Domain Template

The following sample script is based on the Basic WebLogic Server Domain template. This script is provided in the common\templates\silent_scripts directory of your product installation.

The numbers shown along the left-hand margin mark the beginning of each section of code that performs a major task within the script. For details about a particular task, see the description corresponding to the numeric callout in Table 4-23.

Listing 4-1 Sample Script for Creating a New Domain Based on the Basic WebLogic Server Domain

read template from "C:\bea\weblogic81/common/templates/domains/wls.jar";
//////////////////////////////////////////////////////////////////////////
//Find and configure the Admin Server.
/////////////////////////////////////////////////////////////////////////


find Server "myserver" as s1;
set s1.ListenAddress "";
set s1.ListenPort "7001";
set s1.SSL.Enabled "true";
set s1.SSL.ListenPort "7002";
//////////////////////////////////////////////////////////////////////////
//Create a JMSQueue.
//////////////////////////////////////////////////////////////////////////
//A JMSServer has to be created first.


create JMSServer "myJMSServer" as jmsserver;
create JMSQueue "myJMSQueue" as myq;
//required attribute
set myq.JNDIName "jms/myjmsqueue";
//required attribute
set myq.JMSServer "myJMSServer";
//optional attribute
//set myq.StoreEnabled "false";
//target "myJMSServer" to server "myserver"
assign JMSServer "myJMSServer" to target "myserver";
//////////////////////////////////////////////////////////////////////////
//Create a JDBCConnectionPool.
//////////////////////////////////////////////////////////////////////////


create JDBCConnectionPool "demoPool" as mypool;
//required attribute
set mypool.DriverName "com.pointbase.jdbc.jdbcUniversalDriver";
//required attribute
set mypool.URL "jdbc:pointbase:server://localhost:9092/demo";
//required attribute
set mypool.Password "PBPUBLIC";
//optional attribute (but it's recommended you set the db user...)
set mypool.Properties "user=PBPUBLIC";
//target all JDBC connection pools to server "myserver"
assign JDBCConnectionPool "*" to target "myserver";
//////////////////////////////////////////////////////////////////////////
//target existing applications.
//////////////////////////////////////////////////////////////////////////
//target applications only when they exist in current domain template


//assign application "*" to target "myserver";
//////////////////////////////////////////////////////////////////////////
//Find the admin user and set the password, since it has not been set in the 
// template.
//////////////////////////////////////////////////////////////////////////


find User "weblogic" as u1;
set u1.password "weblogic";
//////////////////////////////////////////////////////////////////////////
//Write out the domain.
//////////////////////////////////////////////////////////////////////////


set OverwriteDomain "true";


write domain to "C:\bea/user_projects/domains/wls";
//////////////////////////////////////////////////////////////////////////
//Close domain template to indicate completion of work.
//////////////////////////////////////////////////////////////////////////


close template;

The sample script based on the WebLogic Server Domain template performs the tasks defined in the following table.

 

Sample Script Based on the Avitek Medical Records Sample Domain Template

The following sample script is based on the Avitek Medical Records Sample Domain template. More detailed scripts are provided in the common\templates\silent_scripts directory of your product installation.

The numbers shown along the left-hand margin mark the beginning of each section of code that performs a major task within the script. For details about a particular task, see the description corresponding to the numeric callout in Table 4-24.

Listing 4-2 Sample Script for Creating a New Domain Based on the Avitek Medical Records Sample Domain

/* Create a new domain from a configuration template */


read template from "C:\bea\weblogic81\common\templates\domains\medrec.jar";
 
//medrec.jar already sets the password for the predefined user "weblogic". 
//some templates do not have the password pre-set and you need to set it


create User "user1" as u1;
set u1.Password "password";
//by default "user1" is in "Administrators" group
unassign User "user1" from Group "Administrators";
assign User "user1" to Group "Deployers"; 
 
//creation of servers will trigger auto configuration


create Server "myServer1" as s1;
set s1.ListenPort "8001";
set s1.SSL.Enabled "true";
set s1.SSL.ListenPort "8002"; 
 
//find a child element and set its attribute


find Server.ExecuteQueue "MedRecServer.default" as eq1;
set eq1.ThreadCount "25";
 
// if you do not have applications, do not do assignments for them 


assign all Applications to Target "MedRecServer";
assign all Services to Target "MedRecServer, myServer1";
//JMSServer can't be assigned by "assign all Services".


assign JMSServer "*" to Target "myServer1"; 
 


set ServerStartMode "prod";
set JavaHome "C:\bea\jrockit81sp3_142_04";
set CreateStartMenu "false";
//no effect here since MedRec template does not specify app separation
set AppDir "C:\bea\user_projects\applications\myMedRec"; 
 


write domain to "C:\bea\user_projects\domains\myMedRec";


close template; 

The sample script based on the Avitek Medical Records Sample Domain template performs the tasks defined in the following table.

 

Sample Script Based on the Basic WebLogic Portal Domain Template

The following sample script is based on the Basic WebLogic Portal Domain template.

The numbers shown along the left-hand margin mark the beginning of each section of code that performs a major task within the script. For details about a particular task, see the description corresponding to the numeric callout in Table 4-25.

Listing 4-3 Sample Script for Creating a New Domain Based on the Basic WebLogic Portal Domain

/* Create a new domain from a configuration template */


read template from "C:\bea\weblogic81\common\templates\domains\wlp.jar";
 
//some templates do not have the password pre-set and you need to set it


create User "system" as u1;
set u1.Password "password";
find User "weblogic" as u2;
set u2.Password "password";

//find server and set its attributes


find Server "portalServer" as s1;
set s1.Name "adminServer";
set s1.ListenPort "7001";
set s1.SSL.Enabled "true";
set s1.SSL.ListenPort "7002";



set ServerStartMode "dev";
set JavaHome "C:\bea\jrockit81sp3_142_04";
set CreateStartMenu "false";

// if you do not have applications, do not do assignments for them 


assign all Applications to Target "adminServer";
assign all Services to Target "adminServer";



assign JMSConnectionFactory "*" to Target "adminServer";
//JMSServer can't be assigned by "assign all Services".
assign JMSServer "*" to Target "adminServer"; 

//If you switch to use a database with an XA driver, you must uncomment the 
//following lines. The portalPool JDBC connection pool must have 
//SuportsLocalTransaction set to "false".
//find JDBCConnectionPool "portalPool" as portalcp; 
//set portalcp.SupportsLocalTransaction "false";
 


write domain to "C:\bea\user_projects\domains\mywlp";


close template; 

The sample script based on the Basic WebLogic Portal Domain template performs the tasks defined in the following table.

 

Sample Script for Creating a New Domain and Updating It Using an Extension Template

The following sample script creates a new domain based on the Basic WebLogic Server Domain template and then updates it using the Default WebApp extension template.

The numbers shown along the left-hand margin mark the beginning of each section of code that performs a major task within the script. For details about a particular task, see the description corresponding to the numeric callout in Table 4-26.

Listing 4-4 Sample Script for Creating a New Domain and Updating It Using an Extension Template

/*Create a domain from a configuration template and update it */
 


read template from "C:\bea\weblogic81\common\templates\domains\wls.jar";
 


find User "weblogic" as admin;
set admin.Password "newPassword";
create User "user1" as u1;
set u1.Password "password";
assign User "user1" to Group "Deployers";
 


set ServerStartMode "dev";
set JavaHome "C:\bea\jrockit81sp3_142_04";
set CreateStartMenu "false";
 


write domain to "C:\bea\user_projects\domains\wls";


close template;     
 
/* update an existing domain */


read domain from "C:\bea\user_projects\domains\wls";
 
//keep originals if there are duplicates from added extension template
//We do not really need this here since wls template does not have
  applications.


set ReplaceDuplicates "false";
 
//add an extension template


add template
    "C:\bea\weblogic81\common\templates\applications\DefaultWebApp.jar";
 

assign Application "DefaultWebApp" to Target "myserver";
 


update domain;


close domain; 

The sample script performs the tasks defined in the following table.

 

Contact BEA |  Feedback |  Privacy  |