Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Configurations Using the Configuration Wizard

# Tutorials: Using the Configuration Wizard

A domain, or WebLogic configuration, is the basic unit of administration used by WebLogic Server. It consists of one or more WebLogic Server instances, and logically related resources and services that are managed, collectively, as one unit. You must create a domain before you can deploy applications.

The Configuration Wizard simplifies the creation of domains and servers by having you work with configuration templates that already have many configured items set up. You start with templates instead of having to enter everything from scratch. The following tutorials show you how to use the Configuration Wizard to create and update a domain quickly and easily.

Table 15-1 Tutorials for Using the Configuration Wizard

In this tutorial... | You learn how to...
--- | ---
Tutorial: Creating Your First Domain | Create a single-server domain quickly and easily by using preconfigured settings.
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services | Create a multiserver domain that includes Managed Servers, a cluster, and application services by customizing preconfigured settings.
Tutorial: Extending an Existing Domain | Extend the single-server domain that you created in Tutorial: Creating Your First Domain by adding WebLogic Workshop functionality.

For more information about domains, see Brief Introduction to Domains.

# Tutorial: Creating Your First Domain

This section includes the following topics:

- Tutorial Goals—A summary of the concepts and tasks you can learn
- Tutorial Overview—A description of the overall task and the features you are to use
- Steps in This Tutorial—A summary of the high-level steps in the task
- To Create Your First Domain—A detailed set of instructions for completing the tutorial

## Tutorial Goals

In this tutorial, you learn how to use the Configuration Wizard's Express option to create a single domain and server that are based completely on settings provided in a prepackaged configuration template. The Express option is a quick and easy configuration method for novice and experienced users alike to set up a domain environment for running and deploying an application. The configuration of the resulting domain can be simple or extremely complex; it all depends on the default settings provided in the configuration template.

The goals of this tutorial are to help you learn how to:

- Use the Configuration Wizard to set up a basic domain that contains a single Administration Server administered by a single administrative user
- Locate and use prepackaged configuration templates
- Use the Configuration Wizard's Express option and a prepackaged configuration template to create a WebLogic domain configuration quickly and easily

If you are not familiar with the basic features and functionality of a domain, or WebLogic configuration, see Brief Introduction to Domains.

This tutorial takes about 5 minutes to complete.

## Tutorial Overview

In this tutorial, you use the Configuration Wizard's Express option and the Basic WebLogic Server Domain configuration template to create a single domain and server. The Basic WebLogic Server Domain template provides all the basic settings to configure the minimal required components for a domain: an Administration Server and a single administrative user. Because you use the Express option, you keep the default configuration settings already provided in this template and do not need to enter settings from scratch. The only setting you enter is the administrative user login setup.

## Steps in This Tutorial

This section provides a high-level summary of the steps that you follow to complete the tutorial.

  Step 1: Begin creating a new WebLogic configuration

  Start the Configuration Wizard in graphical mode and begin the steps toward creating a new WebLogic configuration.

  Step 2: Select a configuration template and instruct the Configuration Wizard how to handle it

  Select the Basic WebLogic Server Domain configuration template and the Express option to create your domain quickly using template defaults.

  Step 3: Set up the login for the administrative user

  Enter the user name and password used by the administrative user to log in to the Administration Server.

  Step 4: Configure the WebLogic environment

  Set up your server to start in development mode and select a Java Software Development Kit (SDK) to be used with your domain.

  Step 5: Create your new domain and administration server

  Instruct the Configuration Wizard to take your selections, create a new domain and server, and start the server.

  Step 6: Log in to the Administration Console and optionally review the configuration settings

  Log in to the server's Administration Console and optionally review the configuration settings provided by the Basic WebLogic Server Domain configuration template for your domain.

  Summary: Your First Domain

  Review the concepts and tasks covered in the tutorial.

## To Create Your First Domain

This section provides the detailed set of instructions to follow to complete the tutorial.

### Step 1: Begin creating a new WebLogic configuration

1. Start the Configuration Wizard in graphical mode as described in the following table.

Table 15-2 Starting the Configuration Wizard in Graphical Mode

On this platform... | Perform the following steps...
--- | ---
Windows | From the Start menu: Start—>Programs—>BEA WebLogic Platform 8.1—>Configuration Wizard From an MS-DOS command prompt window: 1. Go to the `\common\bin` subdirectory of the product installation directory. For example: `cd c:\bea\weblogic81\common\bin` 2. Enter `config.cmd`
UNIX | 1. Log in to the UNIX system. 2. Go to the `/common/bin` subdirectory of the product installation directory. For example: `cd $BEAHOME/weblogic81/common/bin` 3. Enter `sh config.sh`

The Create or Extend a Configuration window is displayed.

2. Select Create a new WebLogic configuration.
3. Click Next to go to the Select a Configuration Template window.

### Step 2: Select a configuration template and instruct the Configuration Wizard how to handle it

The Select a Configuration Template window displays a list of templates that are available in the current template directory.

The configuration template directory can be located anywhere on your system. By default, it resides in `WL_HOME``\common\templates\domains`, where `WL_HOME` is the directory that contains the product installation (by default, this directory is `c:\bea\weblogic81` on Windows).

1. Select the Basic WebLogic Server Domain from the list of WebLogic Configuration Templates.

Note: For purposes of this tutorial, we instruct you to select the Basic WebLogic Server Domain configuration template because it contains the minimal settings needed to create a domain: an Administration Server and a single administrative user.

You could also select a template that contains default settings for a slightly more complex configuration. You might, for example, select the Avitek Medical Records Sample Domain template, which includes settings for an Administration Server, JMS queues, and multiple users, as well as the Medical Records application itself. Creating a more complex domain is no more difficult than creating a simple one when you use a template with the appropriate default settings. However, the goal of this tutorial is to create a simple domain, and the Basic WebLogic Server Domain configuration template is sufficient for this purpose.

2. Click Next to go to the Choose Express or Custom Configuration window.

This window provides the following modes for using the Configuration Wizard:

- Express—To create a domain by accepting the default template settings
- Custom—To create a domain by customizing the template settings to better meet the requirements of your domain environment

3. Select Express to create a domain quickly, using the default template settings.

Note: The Express option is a quick and easy configuration method for novice and experienced users alike to set up a domain environment. By relying on default template settings, you do not need to enter settings from scratch.

4. Click Next to go to the Configure Administrative Username and Password window.

### Step 3: Set up the login for the administrative user

1. In the Configure Administrative Username and Password window, enter weblogic for both the user name and password. Notice that you must enter the password twice as a security precaution.

Note: Only an administrative user can boot and connect to the Administration Server that the Configuration Wizard creates for your domain. The user name and password that you set up here become the login information for the administrative user.

2. Click Next to go to the Configure Server Start Mode and Java SDK window.

### Step 4: Configure the WebLogic environment

The Configure Server Start Mode and Java SDK window allows you to determine whether to start the server in development mode or production mode, and select which Java SDK to use.

1. Review the default settings for the start mode and the Java SDK selection. Keep the development mode setting for the server start mode. You optionally can change the Java SDK selection.

Note: In this tutorial, you set up your server to start up in development mode, which is the default.

2. Click Next to go to the Create WebLogic Configuration window.

### Step 5: Create your new domain and administration server

The Create WebLogic Configuration window prompts you to review details about the configuration and define the path and filenames for the domain.

The configuration directory can be located anywhere on your system. By default, it resides in `BEA_HOME``\user_projects\domains\``domain`, where `BEA_HOME` is a repository for common files that are used by multiple BEA products installed on the same machine (by default, this directory is `c:\bea` on Windows), and `domain` is the directory defined, by default, by the selected configuration template. For the Basic WebLogic Server Domain template, the default directory is `mydomain`.

1. Keep the default settings for the path and filenames and click Create to create the domain.

The progress bar tracks the creation progress until the domain configuration is created.

The Configuration Wizard creates a domain that is based on the Basic WebLogic Server Domain template—a simple WebLogic Server domain with an Administration Server that can be administered by a single administrative user.

2. In the Creating Configuration window, perform the steps in the following table, as required by your platform, to close the Configuration Wizard and start the Administration Server.

On this platform . . . | Perform the following task . . .
--- | ---
Windows | Select Start Admin Server and click Done to close the Configuration Wizard and start the Administration Server.
UNIX and Linux | Click Done. To start the Administration Server: 1. Open a shell on the computer on which you created the domain. 2. Navigate to the directory in which you created the domain. 3. Enter the following command: `startWebLogic.sh`

### Step 6: Log in to the Administration Console and optionally review the configuration settings

Once the Administration Server is running, you can optionally log in to the domain's Administration Console and review the configuration settings provided by the Basic WebLogic Server Domain configuration template for your domain.

1. Open a Web browser to the following URL:

`http://``hostname:port``/console`

Where you replace `hostname` with the DNS name or IP address of the Administration Server, and replace `port` with the address of the port on which the Administration Server is listening for requests (7001 by default). For example:

`http://localhost:7001/console`

2. On the Administration Console login page, enter `weblogic` as the username and password required to start the Administration Server. Then click Sign In.
3. In the left pane of the Administration Console, expand the Servers folder.
4. Click the name of the server, for example, `myserver`.
5. In the right pane, select the Configuration tab and review the information available in the Configuration area.

### Summary: Your First Domain

This tutorial introduced you to the basics of using the Configuration Wizard to create a WebLogic domain configuration. The concepts and tasks you learned include the following:

- The Configuration Wizard simplifies domain creation by working from a configuration template that contains preconfigured settings.
- Your product installation includes prepackaged configuration templates that you can use immediately with the Configuration Wizard.
- You can use the Configuration Wizard's Express option and a prepackaged configuration template to create a WebLogic configuration quickly and easily.

# Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

This section includes the following topics:

- Tutorial Goals—A summary of the concepts and tasks you can learn
- Tutorial Overview—A description of the overall task and the features you are to use
- Steps in This Tutorial—A summary of the high-level steps in the task
- To create a custom domain with Managed Servers, a cluster, and application services—A detailed set of instructions for completing the tutorial

## Tutorial Goals

In this tutorial, you learn how to use the Configuration Wizard's Custom option to create a clustered, multiserver domain by customizing the settings provided in a prepackaged configuration template. The Custom option is a configuration method where you start with a template's default settings and then change those settings to match more precisely the requirements for the domain in which you want to deploy and run an application. Whether you want to change one setting or more, or want to create a simple domain or a more complex domain, the Configuration Wizard Custom option gives you the same ability to view, add, change, or delete any of the template settings.

The goals of this tutorial are the following:

- Understand how you can use the Configuration Wizard to set up a clustered, multiserver domain provisioned with database and messaging application resources
- Locate and use prepackaged configuration templates
- Learn how you can use the Custom option to modify some of the default settings provided in a configuration template to create a custom domain that matches your application's requirements more precisely

If you are not familiar with the basic features and functionality of a domain, or WebLogic configuration, see Brief Introduction to Domains.

This tutorial takes about 15 minutes to complete.

## Tutorial Overview

In this tutorial, you use the Configuration Wizard to create a domain that is based on the Basic WebLogic Server Domain configuration template, as you did in Tutorial: Creating Your First Domain. In this case, however, you customize your domain to include:

- Three Managed Servers

A Managed Server hosts application components and resources, which are deployed and managed as part of the domain. The three Managed Servers are in addition to the single Administration Server that you also set up in this tutorial.

- A single cluster

A cluster is a group of WebLogic Server instances that work together to provide scalability and high availability for applications. Clusters can improve performance and provide failover if a server instance becomes unavailable. The servers within a cluster can run on the same machine, or they can run on different machines. To the client, a cluster appears as a single WebLogic Server instance. In this tutorial, all the servers and the cluster created by the Configuration Wizard are to run on your local machine.

- Database and messaging application services

Specifically, the WebLogic Java Database Connectivity (JDBC) and WebLogic Java Message Service (JMS) application services are set up.

This tutorial is loosely based on the Avitek Medical Records (MedRec) sample, which demonstrates WebLogic Server and J2EE features, as well as best practices. The Medical Records Clustering Tutorials, available at http://e-docs.bea.com/wls/docs81/medrec_cluster/index.html, guides you through the process of creating and configuring a new cluster using the Configuration Wizard to define the Managed Servers and cluster, and the Administration Console to define the application services.

This tutorial guides you through a similar scenario, using only the Configuration Wizard to define the infrastructure components and application services. For more information about the Medical Records sample, see WebLogic Server Application Examples and Tutorials at the following URL:

http://e-docs.bea.com/wls/docs81/samples.html

## Steps in This Tutorial

This section provides a high-level summary of the steps that you follow to complete the tutorial.

  Step 1: Begin creating a new WebLogic configuration

  Start the Configuration Wizard in graphical mode and begin the steps toward creating a new WebLogic configuration.

  Step 2: Select a configuration template and instruct the Configuration Wizard how to handle it

  Select the Basic WebLogic Server Domain configuration template and the Custom option in order to customize the configuration to support Managed Servers, a cluster, and application services.

  Step 3: Configure the Administration Server

  Configure the Administration Server for the domain by specifying a name, listen address, and listen ports.

  Step 4: Configure the Managed Servers

  Set up three Managed Servers to host application components and resources.

  Step 5: Configure the Cluster

  For scalability and high availability, create a cluster and target the three Managed Servers to the cluster.

  Step 6: Configure the JDBC options

  To enable your application to interface with a database, set up resources, such as JDBC connection pools and a JDBC data source, and test your connection to the database.

  Step 7: Configure the JMS options

  To enable your application to handle messaging, set up resources, such as a JMS connection factory, a database store to persist messages, a JMS server to manage the connections and messages for clients, and destination queues.

  Step 8: Set up the login for the administrative user

  Enter the user name and password used by the administrative user to log in to the Administration Server.

  Step 9: Configure the WebLogic environment

  Enable your domain to be used specifically in a Windows environment. Also, set up your server to start in development mode, and select a Java Software Development Kit (SDK) to be used with your domain.

  Step 10: Create the new domain

  Instruct the Configuration Wizard to take your selections and modifications as input, create a new domain and server, and start the Administration Server.

  Step 11: Log in to the Administration Console and optionally review the configuration settings

  Log in to the server's Administration Console and optionally review both the configuration settings provided by the Basic WebLogic Server Domain configuration template and those customized by you for your domain.

  Summary: Your First Custom Domain

  Review the concepts and tasks covered in the tutorial.

## To create a custom domain with Managed Servers, a cluster, and application services

This section provides the detailed set of instructions to follow to complete the tutorial.

### Step 1: Begin creating a new WebLogic configuration

1. Start the Configuration Wizard in graphical mode as described in the following table.

Table 15-3 Starting the Configuration Wizard in Graphical Mode

On this platform... | Perform the following steps...
--- | ---
Windows | From the Start menu: Start—> Programs—> BEA WebLogic Platform 8.1—> Configuration Wizard From an MS-DOS command prompt window: 1. Go to the `\common\bin` subdirectory of the product installation directory. For example: `cd c:\bea\weblogic81\common\bin` 2. Enter `config.cmd`
UNIX | 1. Log in to the UNIX system. 2. Go to the `/common/bin` subdirectory of the product installation directory. For example: `cd $BEAHOME/weblogic81/common/bin` 3. Enter `sh config.sh`

The Create or Extend a Configuration window is displayed.

2. Select Create a new WebLogic configuration.
3. Click Next to go to the Select a Configuration Template window.

### Step 2: Select a configuration template and instruct the Configuration Wizard how to handle it

1. In the Select a Configuration Template window, select the Basic WebLogic Server Domain from the list of WebLogic Configuration Templates.

Note: By starting with the Basic WebLogic Server Domain configuration template, you learn to customize settings so you can then create a domain similar to the Avitek Medical Records Sample domain. If, instead, for this tutorial, you were to start with the Avitek Medical Records Sample Domain configuration template, you may learn less about how to customize settings because most of the domain configuration is already set up in the template.

2. Click Next to go to the Choose Express or Custom Configuration window.
3. Select Custom to create a domain with customized settings.

The Custom option is a configuration method that allows you to start with a template's default settings and then change those settings so that they more precisely match the requirements for the domain in which you want to deploy and run an application. Using the Custom option, you can view, add, change, or delete any of the template settings.

4. Click Next to go to the Configure the Administration Server window.

### Step 3: Configure the Administration Server

The Configure the Administration Server window prompts you to define the configuration information for the Administration Server, including:

- Administration Server name
- Listen address
- Nonsecure and secure (optional) listen ports

Servers can be reached through the following URL: `protocol``://``listen-address``:``listen-port`)

The Administration Server provides a central point for managing the domain and enabling access to the WebLogic Server administration tools. A domain always includes one WebLogic Server instance that is configured as an Administration Server.

1. Enter the values shown in the following illustration for your Administration Server.

2. Click Next to go to the Managed Servers, Clusters, and Machines Options window.

This window prompts you to define the additional infrastructure components that are needed to set up a distributed configuration, including Managed Servers, clusters, and host machines. In the following steps, you define three Managed Servers and one cluster for your domain.

3. Select Yes to step through the procedure for configuring Managed Servers, clusters, and machines.
4. Click Next to go to the Configure Managed Servers window.

### Step 4: Configure the Managed Servers

The Configure Managed Servers window prompts you to define the configuration information for one or more Managed Servers, including:

- Managed Server name
- Listen address
- Nonsecure and secure (optional) listen ports

Servers can be reached through the following URL: `protocol``://``listen-address``:``listen-port`.

In the following steps, you add three Managed Servers to the domain.

1. Click Add to add a Managed Server.
2. Enter the values shown in the following illustration for the Managed Server.

3. Repeat steps 1 and 2 to add two additional Managed Servers. Enter the values shown in the following illustration for the additional Managed Servers.

4. Click Next to go to the Configure Clusters window.

### Step 5: Configure the Cluster

The Configure Clusters window prompts you to define the configuration information for one or more clusters, including:

- Cluster name
- Multicast address and port
- Cluster address that identifies the Managed Servers in the cluster
- Frontend host if you are using a proxy server or a firewall.
- Frontend HTTP port if you are using a proxy server or a firewall.

In the following steps, you add a single cluster to the domain:

1. Click Add to add a cluster.
2. Enter the values in the following illustration for the cluster.

Note: Because all the Managed Servers listen at the same IP address (relying on unique port numbers to keep them separate), you should set the Cluster Address to the same IP address as the Managed Servers. You will not be using a proxy server or a firewall, so you do not need to enter values for Frontend host or FrontendHTTP port.

3. Click Next to go to the Assign Servers to Clusters window.

This window prompts you to assign the available Managed Servers to a cluster within the domain. By default, `MedRecCluster`, the only cluster that is defined, is already selected in the Cluster pane.

4. Shift-click the name of each Managed Server on the Server pane so that all Managed Servers are selected.
5. Click the right arrow to assign the Managed Servers to the cluster, `MedRecCluster`.

The names of the Managed Servers are removed from the Server pane and added, below the name of the target cluster, to the Cluster pane.

6. Click Next to go to the Configure Machines window.

This window prompts you to define the configuration information for the Windows and UNIX machines in the domain. This step is optional.

Note: In this tutorial, all the servers in the domain are to reside on your local machine, so it is unnecessary to set up additional machines and target resources to them. Therefore, you can skip the machine configuration steps.

7. Click Next to go to the Database (JDBC) Options window.

### Step 6: Configure the JDBC options

The Database (JDBC) Options window prompts you to configure WebLogic Java Database Connectivity (JDBC). In the following steps, you define a JDBC connection pool and data source for the PointBase database management system. A JDBC connection pool is a ready-to-use pool of connections to your DBMS.

To configure the JDBC options:

1. Select Yes to step through the JDBC configuration setup.
2. Click Next to go to the Configure JDBC Connection Pools window.

This window prompts you to create a JDBC connection pool, including:

- Connection pool name
- Database vendor, driver, and class name used to create the physical connections between WebLogic Server and the DBMS for this connection pool
- Database name, host, and port number
- URL for the database used to create the connections in the connection pool
- User name and password used to create the physical database connections
- Properties list passed to the JDBC Driver for use when creating physical database connections

3. Click Add to add a JDBC connection pool.
4. Enter values shown in the following illustration for the Connection Pool.

Note: Enter `MedRec` as the password for the connection pool. Notice that you must enter the password twice as a security precaution.

Notes:

When you select a database vendor from the Vendor list, a number of fields are automatically populated for you, including the Driver, Class Name, Dbms Host, Dbms Port, and JDBC URL. The Class Name and JDBC URL values are read-only. All others can be modified, if required for your environment.

For this tutorial, you select a JDBC driver that does not support distributed transactions (nonXA driver).

5. Click Next to go to the Configure JDBC MultiPools window.

This window prompts you to configure JDBC MultiPools. A JDBC MultiPool is a group of JDBC connection pools that you can set up to accommodate either a high-availability algorithm or a load-balancing algorithm. It is used in the same way a connection pool is used.

Note: For this tutorial, you can skip the configuration of JDBC MultiPools because you do not need them in your domain.

6. Click Next to go to the Configure JDBC Data Sources window.

This window prompts you to configure the data sources that are bound to the JNDI tree, including:

- Data source name
- JNDI pathname to which this data source is bound
- Connection pool to which the data source is assigned
- Whether or not the data source supports global transactions

7. Click Add to add a JDBC data source.
8. Enter `pb/MedRecTxDataSource` for the JDBC data source and JNDI names, and set the remaining values as shown in the following illustration.

Note:

- You assign the JDBC data source to the JDBC Connection Pool defined previously.
- You set the Honor Global Transaction toggle switch to enable the support of global transactions.
- You use the `Tx` prefix in the JDBC data source and JNDI names to indicate that the data source supports global transactions.

9. Click Next to go to the Test JDBC Connection Pools and Setup JDBC Database window.

This window prompts you to test the JDBC connection pool configuration on the local machine.

Note: Because you are using PointBase in this tutorial, you do not need to test or set up any JDBC resources in this window. The Configuration Wizard configures the PointBase database for you during domain creation.

10. Click Next to go to the Messaging (JMS) Options window.

### Step 7: Configure the JMS options

The Messaging (JMS) Options window prompts you to configure WebLogic Java Message Service (JMS).

In the following steps, you define:

- Connection factory—Encapsulated connection configuration information that enables JMS applications to create a connection.
- JDBC store—JDBC-accessible database store used to store persistent messages.
- JMS Server—Server that manages connections and message requests on behalf of clients.
- Destination—Queues (to support the point-to-point model) that serve as a destination for a JMS server.

To define the JMS options:

1. Select Yes to step through the JMS configuration setup.
2. Click Next to go to the Configure JMS Connection Factories window.

This window prompts you to define a JMS connection factory, including:

- Connection factory name
- JNDI pathname used to look up the connection factory within the JNDI namespace
- Default delivery mode used for messages for which a delivery mode is not explicitly defined
- Default priority used for messages for which a priority is not explicitly defined.
- Acknowledge policy for nontransacted sessions that use the `CLIENT_ACKNOWLEDGE` mode.

3. Click Add to add a JMS connection factory.
4. Enter `jms/MedRecQueueConnectionFactory` for the connection factory and JNDI names, and keep all other values set to their defaults as shown in the following illustration.

5. Click Next to go to the Configure JMS Destination Key(s) window.

This window prompts you to define the sort order for messages that arrive at a specific JMS destination.

Note: You can skip the configuration of JMS Destination Keys because the domain that you create in this tutorial does not require them.

6. Click Next to go to the Configure JMS Template(s) window.

This window prompts you to define templates that can be used to define multiple JMS destinations.

Note: You can skip the configuration of JMS Templates because the domain that you create in this tutorial does not require them.

7. Click Next to go to the Configure JMS File Stores window.

This window prompts you to define a JMS file store for storing persistent messages.

Note: You can skip the configuration of a JMS file store because the domain that you create in this tutorial does not require one. You set up a JMS JDBC store instead.

8. Click Next to go to the Configure JMS JDBC Store window.

This window prompts you to define a JMS JDBC store for storing persistent messages, including:

- JDBC store name
- JDBC connection pool for this persistent store
- Prefix name that uniquely identifies JMS tables in the backing store

9. Click Add to add a JMS JDBC store.
10. Enter the values shown in the following illustration for the JMS JDBC store.

11. Click Next to go to the Configure JMS Servers window.

This window prompts you to define a JMS server to manage connections and message requests on behalf of clients, including:

- Server name
- Persistent store for the JMS server
- Paging store for the JMS server, used exclusively for paging out nonpersistent messages for the JMS server and its destinations
- The name of an existing JMS template to use when creating all temporary queues and topics for this JMS server
- Amount of time, in seconds, that the JMS server pauses between its cycles of scanning its destinations for expired messages to process (according to the specified Expiration Policy on the destinations)

12. Click Add to add a JMS server.
13. Enter the values in the following illustration for the JMS server.

14. Click Next to go to the Assign JMS Servers to WebLogic Servers window.

This window prompts you to assign the JMS server to a WebLogic Server instance.

15. Select MedRec1 in the Server pane.

Notice that the `MedRecJMSServer` server, the only JMS server that is defined, is already selected in the JMS Server pane.

16. Click the right arrow to assign the `MedRecJMSServer` server to `MedRec1`.

The name of the JMS server is removed from the JMS Server pane and added, below the name of the target WebLogic Server instance, to the Server pane.

Note: Because you set up multiple Managed Servers and configured them in a cluster, it is a good idea to target the JMS Server to an independent, migratable server instance that can support the scalability and reliability of the server cluster. In this tutorial, you target the JMS Server to the MedRec1 Managed Server. This target choice is somewhat arbitrary as you could target the JMS Server to any other Managed Server as well. Also, by targeting the JMS Server to a Managed Server, you keep the Administration Server available for management tasks.

17. Click Next to go to the Configure JMS Topics window.

This window prompts you to create a JMS topic. JMS topics support the publish/subscribe (Pub/sub) messaging model enabling an application to send a message to multiple applications. Pub/sub messaging applications send and receive messages by subscribing to a topic.

Note: For this tutorial, you set up JMS queues, so you can skip the configuration of JMS topics.

18. Click Next to go to the Configure JMS Queues window.

This window prompts you to create a JMS queue, including:

- Queue name
- JNDI pathname used to look up the queue within the JNDI namespace
- Flag specifying whether or not the destination uses the persistent store specified by the JMS server
- JMS template from which the destination is derived
- Associated JMS server

JMS queues support the point-to-point (PTP) messaging model enabling one application to send a message to another application. PTP messaging applications send and receive messages using named queues.

19. Click Add to add a JMS queue.
20. Enter `jms/REGISTRATION_MDB_QUEUE` for the queue and JNDI names, and set the remaining values, as shown:

21. Repeat steps 19 and 20 to add two additional queues, `jms/MAIL_MDB_QUEUE` and `jms/XML_UPLOAD_MDB_QUEUE`, as shown in the following illustration.

22. Click Next to go to the Configure JMS Distributed Topics window.

This window prompts you to create a JMS distributed topic. Distributed topics consist of a set of physical topics to support service continuity in the event of a WebLogic Server failure within a cluster.

Note: For this tutorial, you can skip the configuration of JMS distributed topics because you do not have JMS topics set up in your domain.

23. Click Next to go to the Configure JMS Distributed Queues window.

This window prompts you to create a JMS distributed queue. Distributed queues consist of a set of physical queues to support service continuity in the event of a WebLogic Server failure within a cluster.

Note: For this tutorial, you can skip the configuration of JMS distributed queues because you do not need them in your domain.

24. Click Next to go to the Applications and Services Targeting Options window.

This window prompts you to configure server and cluster targets onto which you want to deploy applications and services.

25. Select Yes to step through the targeting configuration setup.
26. Click Next to go to the Target Services to Servers or Clusters window.

This window prompts you to specify the target servers and clusters onto which you want to deploy the application components, such as Web applications and EJB modules, that are included in your domain or imported extension templates.

Target all application services to the `MedRecCluster`.

27. Select MedRecCluster on the Target list.
28. Click Select All.

All application services are targeted automatically to each of the Managed Servers within the MedRecCluster.

29. Click Next to go to the Configure Administrative Username and Password window.

### Step 8: Set up the login for the administrative user

1. On the Configure Administrative Username and Password window, enter `weblogic` for the user name and password. Notice that you must enter the password twice as a security precaution.

Note: You do not need to configure additional users, groups, or global roles because you do not need to set up security for additional domain users. For this tutorial, you set up only one administrative user for your domain.

2. Click Next to go to the Configure Windows Options window (Windows platform only).

### Step 9: Configure the WebLogic environment

The Configure Windows Options window (Windows platform only) prompts you to decide whether to create a shortcut in the Windows Start Menu and set up the Administration Server as a Windows service.

Note: For this tutorial, keep the default template settings displayed in this window.

1. Click Next to go to the Build Start Menu Entries window (Windows platform only).

This window prompts you to build entries for the Windows Start Menu.

Note: For this tutorial, keep the default template settings displayed in this window.

2. Click Next to go to the Configure Server Start Mode and Java SDK window.

This window prompts you to select the server startup mode and the Java Software Development Kit (SDK) to be used with your domain.

Note: For this tutorial, keep the default template settings displayed in this window.

3. Click Next to go to the Create WebLogic Configuration window.

### Step 10: Create the new domain

The Create WebLogic Configuration window is displayed.

Note: The Configuration Summary area shows the Deployment view by default. By selecting different options from the Summary View drop-down list, you can see different views of the configuration summary, for example, the Service and Cluster views.

1. Enter `clusterdomain` in the Configuration Name field.

Note: When you create a new domain, give it a new name that is different from `mydomain`, which you created in Tutorial: Creating Your First Domain. You do not want to overwrite an existing domain called `mydomain`. Overwriting an existing domain may result in intermittent problems with the domain, such as failure of the server to boot.

2. Click Create to create the domain.

The progress bar tracks the creation progress until the domain configuration is created.

3. In the Creating Configuration window, perform the steps in the following table, as required by your platform, to close the Configuration Wizard and start the Administration Server.

On this platform . . . | Perform the following task . . .
--- | ---
Windows | Select Start Admin Server and click Done to close the Configuration Wizard and start the Administration Server.
UNIX and Linux | Click Done. To start the Administration Server: 1. Open a shell on the computer on which you created the domain. 2. Navigate to the directory in which you created the domain. 3. Enter the following command: `startWebLogic.sh`

### Step 11: Log in to the Administration Console and optionally review the configuration settings

Once the Administration Server is running, you can optionally log in to the domain's Administration Console and review both the configuration settings provided by the Basic WebLogic Server Domain configuration template and those customized by you for your domain.

1. Open a Web browser to the following URL:

`http://``hostname:port``/console`

Replace `hostname` with the DNS name or IP address of the Administration Server, and replace `port` with the address of the port on which the Administration Server is listening for requests (7001 by default). For example:

`http://localhost:7001/console`

2. When the login page is displayed, enter `weblogic` as the username and password required to start the Administration Server. Then click Sign In.
3. In the left pane of the Administration Console, expand the Servers folder.
4. Click the name of the server, for example, `medrecadmin`.
5. In the right pane, select the Configuration tab and review the information available in the Configuration area.
6. To review additional configuration information, expand the Clusters and Services folders in the left pane and then review the respective configuration information in the right pane.

### Summary: Your First Custom Domain

This tutorial introduced you to the use of the Configuration Wizard for creating a custom WebLogic domain by modifying settings provided in a prepackaged configuration template. The concepts and tasks you learned include the following:

- The Configuration Wizard simplifies domain creation by working from a configuration template that contains preconfigured settings.
- Your product installation includes prepackaged configuration templates that you can use immediately with the Configuration Wizard.
- Through the Configuration Wizard's Custom option, you can view and access a rich set of configured items that are available for creating a new domain, such as for Managed Servers, clusters, JDBC, and JMS resources.
- You can use the Custom option to modify one or all the settings provided in a configuration template to create a custom domain that matches your application's requirements more precisely.

# Tutorial: Extending an Existing Domain

This section includes the following topics:

- Tutorial Goals—A summary of the concepts and tasks you can learn
- Tutorial Overview—A description of the overall task and the features you are to use
- Steps in This Tutorial—A summary of the high-level steps in the task
- To extend an existing domain by adding WebLogic Workshop functionality—A detailed set of instructions for completing the tutorial

## Tutorial Goals

In this tutorial, you learn how to use the Configuration Wizard's Extend an existing WebLogic configuration option to extend a basic domain with additional applications and resources that are provided in prepackaged extension templates. The ability to extend a configuration using the Configuration Wizard provides a quick and easy method for incrementally adding resources and applications to existing domains. The configuration of the resulting domain can be simple or extremely complex; it all depends on the functionality imported into the domain from the extension templates.

The goals of this tutorial are the following:

- Use the Configuration Wizard to extend a basic domain
- Locate and use prepackaged extension templates
- Use the Configuration Wizard's extension option and a prepackaged extension template to import resources into an existing domain

This tutorial takes about 5 minutes to complete.

## Tutorial Overview

In this tutorial, you use the Configuration Wizard's Extend an existing WebLogic configuration option and a prepackaged extension template to extend an existing domain. You extend the basic WebLogic Server domain that you created in Tutorial: Creating Your First Domain with resources provided from the WebLogic Workshop extension template.

Note: The availability of predefined extension templates depends on which WebLogic Platform components are installed. To use the WebLogic Workshop extension template, you must have installed the WebLogic Workshop component.

The basic WebLogic Server domain that you created contains a single Administration Server administered by a administrative user. Using the WebLogic Workshop extension template, you can extend the domain to support WebLogic Workshop runtime functionality, including Web applications, Web Services and custom controls. WebLogic Workshop resources are required before you can extend a domain to support WebLogic Integration, WebLogic Portal, or both (that is, a full Platform domain).

## Steps in This Tutorial

This section provides a high-level summary of the steps that you follow to complete the tutorial.

Note: Before you start this tutorial, you must have already created a WebLogic Server domain as described in Tutorial: Creating Your First Domain.

  Step 1: Begin extending an existing WebLogic configuration

  Start the Configuration Wizard in graphical mode and select the Extend an existing WebLogic configuration option.

  Step 2: Select an existing configuration to extend with additional functionality

  Select the mydomain configuration from the list of available configurations.

  Step 3: Select the extension template and instruct the Configuration Wizard how to handle it

  Select the WebLogic Workshop extension template and specify any additional configuration settings.

  Step 4: Import resources and services into the existing configuration

  Instruct the Configuration Wizard to accept your selections and import the WebLogic Workshop resources and services into the `mydomain` configuration.

  Step 5: Start the Administration Server, Log in to the Administration Console and optionally review the configuration settings

  Start the server, log in to the server's Administration Console, and optionally review both the configuration settings provided by the Basic WebLogic Server Domain configuration template and those added by the extension template.

  Summary: Your First Extended Domain

  Review the concepts and tasks covered in the tutorial.

## To extend an existing domain by adding WebLogic Workshop functionality

This section provides the detailed set of instructions to follow to complete the tutorial.

Note: Before you start this tutorial, you must have already created a WebLogic Server domain as described in Tutorial: Creating Your First Domain.

### Step 1: Begin extending an existing WebLogic configuration

1. Start the Configuration Wizard in graphical mode as described in the following table.

Table 15-4 Starting the Configuration Wizard in Graphical Mode

On this platform... | Perform the following steps...
--- | ---
Windows | From the Start menu: Start—> Programs—> BEA WebLogic Platform 8.1—> Configuration Wizard From an MS-DOS command prompt window: 1. Go to the `\common\bin` subdirectory of the product installation directory. For example: `cd c:\bea\weblogic81\common\bin` 2. Enter `config.cmd`
UNIX | 1. Log in to the UNIX system. 2. Go to the `/common/bin` subdirectory of the product installation directory. For example: `cd $BEAHOME/weblogic81/common/bin` 3. Enter `sh config.sh`

The Create or Extend a Configuration window is displayed.

2. Select Extend an existing WebLogic configuration.
3. Click Next to go to the Choose a WebLogic Configuration Directory window.

### Step 2: Select an existing configuration to extend with additional functionality

The Choose a WebLogic Configuration Directory window prompts you to select an existing domain that you want to update with additional applications or services.

1. In this window, select the mydomain configuration from the list of configurations.

Note: Make sure that the domain is not active; you cannot update an active domain.

Note: The configuration directory can be located anywhere on your system. By default, it resides in `BEA_HOME``\user_projects\domains\``domain`, where `BEA_HOME` is a repository for common files that are used by multiple BEA products installed on the same machine (by default, this directory is `c:\bea` on Windows), and `domain` is the directory defined, by default, by the selected configuration template. For the Basic WebLogic Server Domain we created in Tutorial: Creating Your First Domain, the default directory is `mydomain`.

2. Click Next to go to the Select a Configuration Extension Template window.

### Step 3: Select the extension template and instruct the Configuration Wizard how to handle it

The Select a Configuration Extension Template window prompts you to specify one or more extension templates to be included when the domain is updated. You must select at least one extension template.

1. In the Select a Configuration Extension Template window, select the WebLogic Workshop Extension template.

The extension template directory can be located anywhere on your system. By default, it resides in `WL_HOME``\common\templates\applications`, where `WL_HOME` is the directory that contains the product installation (by default, this directory is `c:\bea\weblogic81` on Windows).

2. Click Next to go to the Database (JDBC) Options window.

The Database (JDBC) Options window prompts you to configure WebLogic Java Database Connectivity (JDBC). For this tutorial, keep the default configuration settings defined for mydomain.

3. Click Next to go to the Messaging (JMS) Options window.

This window prompts you to configure WebLogic Java Message Service (JMS). For this tutorial, keep the default configuration settings defined for mydomain.

4. Click Next to go to the Applications and Services Targeting Options window.

This window prompts you to configure server and cluster targets onto which you want to deploy applications and services. For this tutorial, keep the default configuration settings defined for mydomain.

5. Click Next to go to the Security Configuration Options window.

This window prompts you to configure additional security features by defining users and groups and assigning them to global security roles. You can skip additional security configuration.

Note: When you created the mydomain configuration, you specified `weblogic` for both the administrative user name and password. You will use this same user name/password combination to start the Administration Console in the extended domain.

6. Click Next to go to the Create WebLogic Configuration window.

### Step 4: Import resources and services into the existing configuration

The Create WebLogic Configuration window prompts you to review the details for your extension, and launch the process that updates the domain.

Note: The Configuration Summary area shows the Deployment view by default. By selecting different options from the Summary View drop-down list, you can see different views of the configuration summary, for example, the Service and Application views.

1. Click Import to import the WebLogic Workshop resources and services into the basic WebLogic Server domain mydomain.

The progress bar tracks the progress of the files being imported until the domain extension is completed.

2. Click Done to close the Configuration Wizard.

The domain directory is updated to contain required WebLogic Workshop resources, including properties files and XML descriptors, and PointBase-specific information used when creating and initializing a database.

### Step 5: Start the Administration Server, Log in to the Administration Console and optionally review the configuration settings

1. Start the server as follows:

1. Open a shell (command prompt) on the computer on which you created the domain.
2. Navigate to the directory in which you created the domain. In this tutorial, this directory is `BEA_HOME``\user_projects\domains\mydomain`, where `BEA_HOME` is a repository for common files that are used by multiple BEA products installed on the same machine (by default, this directory is `c:\bea` on Windows).
3. Enter the command appropriate for your platform:

`startWebLogic.cmd` (Windows)

`startWebLogic.sh` (UNIX)

Once the Administration Server is running, you can optionally log in to the domain's Administration Console and review both the configuration settings provided by the Basic WebLogic Server Domain configuration template and those added by the WebLogic Workshop extension template.

2. Open a Web browser to the following URL:

`http://``hostname:port``/console`

Replace `hostname` with the DNS name or IP address of the Administration Server, and replace `port` with the address of the port on which the Administration Server is listening for requests (7001 by default). For example:

`http://localhost:7001/console`

3. When the login page is displayed, enter `weblogic` as the username and password required to start the Administration Server. Then click Sign In.
4. In the left pane of the Administration Console, expand the Servers folder.
5. Select `myserver`.
6. In the right pane, you can view the resources and applications added with the WebLogic Workshop extension template by selecting the EJB Modules and Services tabs.
7. To review additional configuration information, expand the Deployments and Services folders in the left pane and then review the respective configuration information in the right pane.

### Summary: Your First Extended Domain

This tutorial introduced you to the use of the Configuration Wizard for extending an existing WebLogic domain with WebLogic Workshop functionality. The concepts and tasks you learned include the following:

- The Configuration Wizard simplifies the process for extending a domain using extension templates that contain preconfigured resources and services.
- Your product installation includes prepackaged extension templates that you can use immediately with the Configuration Wizard.
- You can easily extend an existing WebLogic domain by using the Configuration Wizard's Extend an existing WebLogic configuration option and selecting one or more of the predefined extension templates.