Creating WebLogic Configurations 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.
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. |
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.
This section includes the following topics:
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:
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.
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.
This section provides a high-level summary of the steps that you follow to complete the tutorial.
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.
Enter the user name and password used by the administrative user to log in to the Administration Server.
Set up your server to start in development mode and select a Java Software Development Kit (SDK) to be used with your domain.
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.
This section provides the detailed set of instructions to follow to complete the tutorial.
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).
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.
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.
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.
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.
Note: In this tutorial, you set up your server to start up in development mode, which is the default.
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
.
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.
Select Start Admin Server and click Done to close the Configuration Wizard and start the Administration Server. |
|
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.
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:
This section includes the following topics:
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:
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.
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:
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 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.
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://download.oracle.com/docs/cd/E13222_01/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://download.oracle.com/docs/cd/E13222_01/wls/docs81/samples.html
This section provides a high-level summary of the steps that you follow to complete the tutorial.
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.
Configure the Administration Server for the domain by specifying a name, listen address, and listen ports.
For scalability and high availability, create a cluster and target the three Managed Servers to the cluster.
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.
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.
Enter the user name and password used by the administrative user to log in to the Administration Server.
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.
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.
This section provides the detailed set of instructions to follow to complete the tutorial.
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.
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.
The Configure the Administration Server window prompts you to define the configuration information for the Administration Server, including:
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.
The Configure Managed Servers window prompts you to define the configuration information for one or more Managed Servers, including:
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.
The Configure Clusters window prompts you to define the configuration information for one or more clusters, including:
In the following steps, you add a single cluster to the domain:
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.
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.
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.
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.
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:
Note: Enter MedRec
as the password for the connection pool. Notice that you must enter the password twice as a security precaution.
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).
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.
pb/MedRecTxDataSource
for the JDBC data source and JNDI names, and set the remaining values as shown in the following illustration.Tx
prefix in the JDBC data source and JNDI names to indicate that the data source supports global transactions.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.
The Messaging (JMS) Options window prompts you to configure WebLogic Java Message Service (JMS).
In the following steps, you define:
CLIENT_ACKNOWLEDGE
mode. jms/MedRecQueueConnectionFactory
for the connection factory and JNDI names, and keep all other values set to their defaults as shown in the following illustration.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.
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.
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.
This window prompts you to define a JMS server to manage connections and message requests on behalf of clients, including:
Notice that the MedRecJMSServer
server, the only JMS server that is defined, is already selected in the JMS Server pane.
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.
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.
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.
jms/REGISTRATION_MDB_QUEUE
for the queue and JNDI names, and set the remaining values, as shown:jms/MAIL_MDB_QUEUE
and jms/XML_UPLOAD_MDB_QUEUE
, as shown in the following illustration.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.
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.
This window prompts you to configure server and cluster targets onto which you want to deploy applications and services.
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.
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.
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.
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.
Select Start Admin Server and click Done to close the Configuration Wizard and start the Administration Server. |
|
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.
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:
weblogic
as the username and password required to start the Administration Server. Then click Sign In.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:
This section includes the following topics:
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:
This tutorial takes about 5 minutes to complete.
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).
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.
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
Step 3: Select the extension template and instruct the Configuration Wizard how to handle it
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.
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.
The Choose a WebLogic Configuration Directory window prompts you to select an existing domain that you want to update with additional applications or services.
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
.
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.
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).
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.
This window prompts you to configure WebLogic Java Message Service (JMS). For this tutorial, keep the default configuration settings defined for mydomain.
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.
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.
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.
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.
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).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.
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:
weblogic
as the username and password required to start the Administration Server. Then click Sign In.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: